<?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>76</VOL>
  <NO>182</NO>
  <DATE>Tuesday, September 20, 2011</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR/>
      <PRTPAGE P="iii"/>
      <HD>Administrative Conference of the United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Committee on Rulemaking,</SJDOC>
          <PGS>58237</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24056</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agriculture</EAR>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Farm Service Agency</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food and Nutrition 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>Grain Inspection, Packers and Stockyards Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Regulated Navigation Areas:</SJ>
        <SJDENT>
          <SJDOC>Saugus River, Lynn, MA,</SJDOC>
          <PGS>58105-58108</PGS>
          <FRDOCBP D="3" T="20SER1.sgm">2011-24051</FRDOCBP>
        </SJDENT>
        <SJ>Safety Zones:</SJ>
        <SJDENT>
          <SJDOC>Giannangeli Wedding Fireworks, Lake St. Clair, Harrison Township, MI,</SJDOC>
          <PGS>58110-58112</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-24143</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>M/V DAVY CROCKETT, Columbia River,</SJDOC>
          <PGS>58112-58114</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-24146</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Ryder Cup Captain's Duel Golf Shot, Chicago River, Chicago, IL,</SJDOC>
          <PGS>58108-58110</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-24142</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Waiver of Citizenship Requirements for Crewmembers on Commercial Fishing Vessels; Correction,</DOC>
          <PGS>58226</PGS>
          <FRDOCBP D="0" T="20SEP1.sgm">2011-24055</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Assessments; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Nationwide Implementation of the Interagency Operations Centers,</SJDOC>
          <PGS>58286-58288</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24052</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>International Maritime Organization Guidelines for Exhaust Gas Cleaning Systems for Marine Engines,</SJDOC>
          <PGS>58288-58289</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24138</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Foreign-Trade Zones Board</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>International Trade Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institute of Standards and Technology</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Oceanic and Atmospheric Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Commodity Futures</EAR>
      <HD>Commodity Futures Trading Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Swap Transaction Compliance and Implementation Schedule:</SJ>
        <SJDENT>
          <SJDOC>Clearing and Trade Execution Requirements under Section 2(h) of CEA,</SJDOC>
          <PGS>58186-58197</PGS>
          <FRDOCBP D="11" T="20SEP1.sgm">2011-24124</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Trading Documentation and Margining Requirements under Section 4s of CEA,</SJDOC>
          <PGS>58176-58186</PGS>
          <FRDOCBP D="10" T="20SEP1.sgm">2011-24128</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Consumer Product</EAR>
      <HD>Consumer Product Safety Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Safety Standards for Play Yards,</DOC>
          <PGS>58167-58175</PGS>
          <FRDOCBP D="8" T="20SEP1.sgm">2011-24101</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Acquisition</EAR>
      <HD>Defense Acquisition Regulations System</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Annual Representations and Certifications,</DOC>
          <PGS>58140-58142</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23947</FRDOCBP>
        </DOCENT>
        <SJ>Defense Federal Acquisition Regulation Supplement:</SJ>
        <SJDENT>
          <SJDOC>Alternative Line Item Structure,</SJDOC>
          <PGS>58138-58140</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23953</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Construction and Architect-Engineer Services Performance Evaluation,</SJDOC>
          <PGS>58155-58156</PGS>
          <FRDOCBP D="1" T="20SER1.sgm">2011-23952</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Designation of a Contracting Officers Representative,</SJDOC>
          <PGS>58136-58137</PGS>
          <FRDOCBP D="1" T="20SER1.sgm">2011-23950</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Material Inspection and Receiving Report,</SJDOC>
          <PGS>58122-58136</PGS>
          <FRDOCBP D="14" T="20SER1.sgm">2011-23958</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Multiyear Contracting,</SJDOC>
          <PGS>58152-58155</PGS>
          <FRDOCBP D="3" T="20SER1.sgm">2011-23963</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Discussions Prior to Contract Award,</DOC>
          <PGS>58150-58152</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23949</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Passive Radio Frequency Identification,</DOC>
          <PGS>58142-58144</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23945</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Positive Law Codification of Title 41 U.S.C.,</DOC>
          <PGS>58137-58138</PGS>
          <FRDOCBP D="1" T="20SER1.sgm">2011-23951</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Presumption of Development Exclusively at Private Expense,</DOC>
          <PGS>58144-58149</PGS>
          <FRDOCBP D="5" T="20SER1.sgm">2011-23956</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Ships Bunkers Easy Acquisition Card and Aircraft Ground Services (DFARS Case 2009-D019),</DOC>
          <PGS>58149-58150</PGS>
          <FRDOCBP D="1" T="20SER1.sgm">2011-23944</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Defense Acquisition Regulations System</P>
      </SEE>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Privacy Act of 1974; Implementation,</DOC>
          <PGS>58103-58105</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23758</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Smoking Cessation Program under TRICARE,</DOC>
          <PGS>58199-58202</PGS>
          <FRDOCBP D="3" T="20SEP1.sgm">2011-23764</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>TRICARE Sanction Authority for Third-party Billing Agents,</DOC>
          <PGS>58202-58204</PGS>
          <FRDOCBP D="2" T="20SEP1.sgm">2011-23763</FRDOCBP>
        </DOCENT>
        <SJ>TRICARE:</SJ>
        <SJDENT>
          <SJDOC>Changes Included in National Defense Authorization Act for Fiscal Year 2010, etc.,</SJDOC>
          <PGS>58204-58206</PGS>
          <FRDOCBP D="2" T="20SEP1.sgm">2011-23765</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>58250-58252</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24131</FRDOCBP>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24137</FRDOCBP>
        </DOCENT>
        <SJ>Applications for New Awards:</SJ>
        <SJDENT>
          <SJDOC>Statewide, Longitudinal Data Systems Program,</SJDOC>
          <PGS>58252-58255</PGS>
          <FRDOCBP D="3" T="20SEN1.sgm">2011-24151</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>PROPOSED RULES</HD>
        <SJ>Energy Conservation Program:</SJ>
        <SJDENT>
          <SJDOC>Test Procedures for Residential Dishwashers, Dehumidifiers, and Conventional Cooking Products,</SJDOC>
          <PGS>58346-58371</PGS>
          <FRDOCBP D="26" T="20SEP2.sgm">2011-22812</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Approvals and Promulgations of Air Quality Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>Delaware; Requirements for Preconstruction Review, Prevention of Significant Deterioration,</SJDOC>
          <PGS>58120-58122</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23984</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>District of Columbia, Maryland, and Virginia; 2002 Base Year Emission Inventory, Reasonable Further Progress Plan, etc.,</SJDOC>
          <PGS>58116-58120</PGS>
          <FRDOCBP D="4" T="20SER1.sgm">2011-23967</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Pennsylvania; Control of Particulate Matter Emissions from the Operation of Outdoor Wood-Fired Boilers,</SJDOC>
          <PGS>58114-58116</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-24099</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Approval and Promulgation of Air Quality Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>District of Columbia, Maryland, and Virginia,</SJDOC>
          <PGS>58206-58210</PGS>
          <FRDOCBP D="4" T="20SEP1.sgm">2011-24098</FRDOCBP>
        </SJDENT>
        <SJ>Approval and Promulgation of Implementation Plans, etc.:</SJ>
        <SJDENT>
          <SJDOC>North Carolina; Redesignation of the Hickory-Morganton-Lenoir 1997 Annual Fine Particulate Matter Nonattainment Area to Attainment,</SJDOC>
          <PGS>58210-58226</PGS>
          <FRDOCBP D="16" T="20SEP1.sgm">2011-24103</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <PRTPAGE P="iv"/>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>NESHAP for Engine Test Cells/Stands (Renewal),</SJDOC>
          <PGS>58272-58273</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24109</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NESHAP for Friction Materials Manufacturing (Renewal),</SJDOC>
          <PGS>58269-58270</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24111</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NESHAP for Leather Finishing Operations (Renewal),</SJDOC>
          <PGS>58265-58266</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24108</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NESHAP for Primary Copper Smelters (Renewal),</SJDOC>
          <PGS>58270-58272</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24110</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Outer Continental Shelf Air Regulations,</SJDOC>
          <PGS>58273-58275</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24093</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Reporting Requirements for BEACH Act Grants (Renewal),</SJDOC>
          <PGS>58266-58268</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24089</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>TSCA Training and Certification, Accreditation and Standards for Lead-Based Paint Activities, etc.,</SJDOC>
          <PGS>58268-58269</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24112</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Mobile Sources Technical Review Subcommittee,</SJDOC>
          <PGS>58275</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24097</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Presidential Documents</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Farm Service</EAR>
      <HD>Farm Service Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Guaranteed Loan Fees,</DOC>
          <PGS>58089-58094</PGS>
          <FRDOCBP D="5" T="20SER1.sgm">2011-23724</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>328 Support Services GmbH Model 328-100 and -300 Airplanes,</SJDOC>
          <PGS>58094-58098</PGS>
          <FRDOCBP D="4" T="20SER1.sgm">2011-22032</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Boeing Co. Airplanes,</SJDOC>
          <PGS>58098-58100</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-23709</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>58275-58276</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24255</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Election</EAR>
      <HD>Federal Election Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>58276</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24169</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Emergency</EAR>
      <HD>Federal Emergency Management Agency</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Emergency Declarations:</SJ>
        <SJDENT>
          <SJDOC>Connecticut; Amendment No. 3,</SJDOC>
          <PGS>58289</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24059</FRDOCBP>
        </SJDENT>
        <SJ>Major Disaster Declarations:</SJ>
        <SJDENT>
          <SJDOC>Connecticut; Amendment No. 4,</SJDOC>
          <PGS>58291</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24062</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Missouri; Amendment No. 2,</SJDOC>
          <PGS>58291</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24074</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York; Amendment No. 7,</SJDOC>
          <PGS>58290</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24075</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>North Carolina; Amendment No. 7,</SJDOC>
          <PGS>58289-58290</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24060</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vermont; Amendment No. 5,</SJDOC>
          <PGS>58290-58291</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24077</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Virginia; Amendment No. 1,</SJDOC>
          <PGS>58290</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24064</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Electric Reliability Organization Interpretation of Transmission Operations Reliability Standard,</DOC>
          <PGS>58101-58103</PGS>
          <FRDOCBP D="2" T="20SER1.sgm">2011-24088</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Applications for Abandonment by Sale and Certificates of Public Convenience and Necessity:</SJ>
        <SJDENT>
          <SJDOC>ANR Pipeline Company, TC Offshore LLC,</SJDOC>
          <PGS>58255-58256</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24022</FRDOCBP>
        </SJDENT>
        <SJ>Applications:</SJ>
        <SJDENT>
          <SJDOC>Copper Valley Electric Association, Inc.,</SJDOC>
          <PGS>58256-58257</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24020</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>58257-58260</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24033</FRDOCBP>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24053</FRDOCBP>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24054</FRDOCBP>
        </DOCENT>
        <SJ>Environmental Assessments; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>FPL Energy Maine Hydro LLC, Madison Paper Industries, Merimil Limited Partnership,</SJDOC>
          <PGS>58260-58261</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24092</FRDOCBP>
        </SJDENT>
        <SJ>Petitions for Declaratory Orders:</SJ>
        <SJDENT>
          <SJDOC>Sunoco Pipeline LP,</SJDOC>
          <PGS>58261</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24023</FRDOCBP>
        </SJDENT>
        <SJ>Preliminary Permit Applications:</SJ>
        <SJDENT>
          <SJDOC>American River Power I, LLC,</SJDOC>
          <PGS>58261-58262</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24018</FRDOCBP>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24021</FRDOCBP>
        </SJDENT>
        <SJ>Proposed Restricted Service List for Section 106 Consultation:</SJ>
        <SJDENT>
          <SJDOC>Boott Hydropower Inc., et al.,</SJDOC>
          <PGS>58262-58263</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24087</FRDOCBP>
        </SJDENT>
        <SJ>Requests for Jurisdictional Determinations, etc.:</SJ>
        <SJDENT>
          <SJDOC>Kenai Pipe Line Co., et al.,</SJDOC>
          <PGS>58263</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24091</FRDOCBP>
        </SJDENT>
        <SJ>Requests Under Blanket Authorizations:</SJ>
        <SJDENT>
          <SJDOC>Columbia Gas Transmission, LLC,</SJDOC>
          <PGS>58263-58264</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24090</FRDOCBP>
        </SJDENT>
        <SJ>Terminations of Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Michael J. Donahue,</SJDOC>
          <PGS>58264-58265</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24019</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Maritime</EAR>
      <HD>Federal Maritime Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Passenger Vessel Operator Financial Responsibility Requirements for Nonperformance of Transportation,</DOC>
          <PGS>58227-58236</PGS>
          <FRDOCBP D="9" T="20SEP1.sgm">2011-23906</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Railroad</EAR>
      <HD>Federal Railroad Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Program for Capital Grants for Rail Line Relocation and Improvement Projects,</DOC>
          <PGS>58334-58341</PGS>
          <FRDOCBP D="7" T="20SEN1.sgm">2011-24125</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies,</DOC>
          <PGS>58276-58277</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-23998</FRDOCBP>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24065</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Animal Drug User Fee Act,</SJDOC>
          <PGS>58279-58281</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24082</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Animal Generic Drug User Fee Act,</SJDOC>
          <PGS>58277-58279</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24083</FRDOCBP>
        </SJDENT>
        <SJ>Public Workshops:</SJ>
        <SJDENT>
          <SJDOC>Magnetic Resonance Imaging Safety,</SJDOC>
          <PGS>58281-58282</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24030</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Nutrition</EAR>
      <HD>Food and Nutrition Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Supplemental Nutrition Assistance Program Pre-Screening Tool,</SJDOC>
          <PGS>58237-58238</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24085</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Waivers under Section 6(o) of the Food and Nutrition Act,</SJDOC>
          <PGS>58238-58240</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24086</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Shiga Toxin-Producing Escherichia coli in Certain Raw Beef,</DOC>
          <PGS>58157-58165</PGS>
          <FRDOCBP D="8" T="20SEP1.sgm">2011-24043</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Foreign Trade</EAR>
      <HD>Foreign-Trade Zones Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Reorganizations under Alternative Site Framework:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 41, Milwaukee, WI,</SJDOC>
          <PGS>58243</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24119</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Forest</EAR>
      <HD>Forest Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Motorized Travel Management, Modoc National Forest, Alturas, CA,</SJDOC>
          <PGS>58240</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-23613</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Grain Inspection</EAR>
      <HD>Grain Inspection, Packers and Stockyards Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Designations for Aberdeen, SD; Decatur, IL; Hastings, NE; Fulton, IL; the State of Missouri, State of South Carolina Areas,</DOC>
          <PGS>58241</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24041</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <PRTPAGE P="v"/>
          <DOC>Opportunity for Designations in the Jamestown, ND; Lincoln, NE; Memphis, TN; and Sioux City, IA Areas,</DOC>
          <PGS>58241-58243</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24040</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Health Resources and Services Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Performance Review Board Members,</DOC>
          <PGS>58277</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24039</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health Resources</EAR>
      <HD>Health Resources and Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>58282-58283</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24121</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>National Advisory Council on Migrant Health,</SJDOC>
          <PGS>58283</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24127</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Coast Guard</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Emergency Management Agency</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Housing</EAR>
      <HD>Housing and Urban Development Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Local Appeals to Single-Family Mortgage Limits,</SJDOC>
          <PGS>58291-58292</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-23970</FRDOCBP>
        </SJDENT>
        <SJ>Announcement of Funding Awards for Fiscal Year 2011:</SJ>
        <SJDENT>
          <SJDOC>Doctoral Dissertation Research Grant Program,</SJDOC>
          <PGS>58292-58293</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24037</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Indian Affairs</EAR>
      <HD>Indian Affairs Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Rate Adjustments for Indian Irrigation Projects,</DOC>
          <PGS>58293-58298</PGS>
          <FRDOCBP D="5" T="20SEN1.sgm">2011-24057</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Indian Affairs Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Land Management Bureau</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>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>Survey of International Air Travelers,</SJDOC>
          <PGS>58243-58244</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24050</FRDOCBP>
        </SJDENT>
        <SJ>Antidumping Duty Administrative Reviews; Rescissions, In Part:</SJ>
        <SJDENT>
          <SJDOC>Polyethylene Terephthalate Film, Sheet and Strip from India,</SJDOC>
          <PGS>58244-58245</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24148</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Applications for Duty-Free Entry of Scientific Instruments,</DOC>
          <PGS>58245</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24122</FRDOCBP>
        </DOCENT>
        <SJ>Consolidated Decisions on Applications for Duty-Free Entry of Electron Microscope:</SJ>
        <SJDENT>
          <SJDOC>Ohio State University, et al.,</SJDOC>
          <PGS>58245-58246</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24123</FRDOCBP>
        </SJDENT>
        <SJ>Decisions on Applications for Duty-Free Entry of Scientific Instruments:</SJ>
        <SJDENT>
          <SJDOC>Purdue University,</SJDOC>
          <PGS>58246</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24120</FRDOCBP>
        </SJDENT>
        <SJ>Partial Rescission of Antidumping Duty Administrative Review:</SJ>
        <SJDENT>
          <SJDOC>Certain Activated Carbon from the People's Republic of China,</SJDOC>
          <PGS>58246-58247</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24145</FRDOCBP>
        </SJDENT>
        <SJ>Rescission, In Part, of Countervailing Duty Administrative Review:</SJ>
        <SJDENT>
          <SJDOC>Polyethylene Terephthalate Film, Sheet and Strip from India,</SJDOC>
          <PGS>58248</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24147</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Scheduling of Full Five-Year Reviews Concerning Antidumping Duty Orders:</SJ>
        <SJDENT>
          <SJDOC>Brass Sheet And Strip From France, Germany, Italy, And Japan,</SJDOC>
          <PGS>58299-58300</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24042</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Prisons Bureau</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Lodging Of Consent Decree Under The Comprehensive Environmental Response, Compensation And Liability Act,</DOC>
          <PGS>58300</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24117</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Labor Department</EAR>
      <HD>Labor Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Mine Safety and Health Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Filing of Plats of Survey:</SJ>
        <SJDENT>
          <SJDOC>Alaska,</SJDOC>
          <PGS>58298-58299</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24107</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Mine</EAR>
      <HD>Mine Safety and Health Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Affirmative Decisions on Petitions for Modification Granted in Whole or in Part,</DOC>
          <PGS>58300-58301</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24096</FRDOCBP>
        </DOCENT>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals</SJ>
        <SJDENT>
          <SJDOC>Automatic Fire Sensor and Warning Device Systems; Examination and Test Requirements,</SJDOC>
          <PGS>58301-58303</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24095</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>NASA</EAR>
      <HD>National Aeronautics and Space Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>NASA Advisory Council; Science Committee; Planetary Science Subcommittee,</SJDOC>
          <PGS>58303</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24129</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Highway</EAR>
      <HD>National Highway Traffic Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>58341-58342</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24038</FRDOCBP>
        </DOCENT>
        <SJ>Grants of Petitions for Decision of Inconsequential Noncompliance:</SJ>
        <SJDENT>
          <SJDOC>Bentley Motors Inc.,</SJDOC>
          <PGS>58343-58344</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24126</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institute of Standards and Technology</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals</SJ>
        <SJDENT>
          <SJDOC>Three-Year Generic Request for Customer Service-Related Data Collections,</SJDOC>
          <PGS>58248-58249</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24049</FRDOCBP>
        </SJDENT>
      </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>58284-58286</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24130</FRDOCBP>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24134</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Center for Scientific Review; Amended,</SJDOC>
          <PGS>58286</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24144</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Eunice Kennedy Shriver National Institute of Child Health and Human Development,</SJDOC>
          <PGS>58283-58284</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24136</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Heart, Lung, and Blood Institute,</SJDOC>
          <PGS>58285</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24133</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Dental and Craniofacial Research,</SJDOC>
          <PGS>58284</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24135</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Mental Health,</SJDOC>
          <PGS>58285</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24132</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Fisheries of the Exclusive Economic Zone Off Alaska:</SJ>
        <SJDENT>
          <SJDOC>Pollock in Statistical Area 610 in the Gulf of Alaska,</SJDOC>
          <PGS>58156</PGS>
          <FRDOCBP D="0" T="20SER1.sgm">2011-24104</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <PRTPAGE P="vi"/>
        <HD>NOTICES</HD>
        <SJ>Availability of Proposed Low Effect Habitat Conservation Plans:</SJ>
        <SJDENT>
          <SJDOC>Tumalo Irrigation District's Tumalo Conservation Project,</SJDOC>
          <PGS>58249-58250</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24105</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Neighborhood</EAR>
      <HD>Neighborhood Reinvestment Corporation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>58303</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24161</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Rulemaking Petitions Submitted by the Natural Resources Defense Council, Inc.,</DOC>
          <PGS>58165-58167</PGS>
          <FRDOCBP D="2" T="20SEP1.sgm">2011-24079</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Applications and Amendments to Facility Operating Licenses Involving No Significant Hazards Considerations,</DOC>
          <PGS>58303-58311</PGS>
          <FRDOCBP D="8" T="20SEN1.sgm">2011-23790</FRDOCBP>
        </DOCENT>
        <SJ>Draft License Renewal Interim Staff Guidance:</SJ>
        <SJDENT>
          <SJDOC>Ongoing Review of Operating Experience,</SJDOC>
          <PGS>58311-58312</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24061</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>58312</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24228</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Regulatory</EAR>
      <HD>Postal Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Post Office Closings,</DOC>
          <PGS>58312-58315</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24017</FRDOCBP>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24029</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Presidential Documents</EAR>
      <HD>Presidential Documents</HD>
      <CAT>
        <HD>PROCLAMATIONS</HD>
        <SJ>Special Observances:</SJ>
        <SJDENT>
          <SJDOC>National Hispanic Heritage Month (Proc. 8712),</SJDOC>
          <PGS>58373-58376</PGS>
          <FRDOCBP D="3" T="20SED0.sgm">2011-24332</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National POW/MIA Recognition Day (Proc. 8713),</SJDOC>
          <PGS>58377-58378</PGS>
          <FRDOCBP D="1" T="20SED1.sgm">2011-24333</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Prisons</EAR>
      <HD>Prisons Bureau</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Pre-Release Community Confinement,</DOC>
          <PGS>58197-58199</PGS>
          <FRDOCBP D="2" T="20SEP1.sgm">2011-23684</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Facilitating Shareholder Director Nominations,</DOC>
          <PGS>58100</PGS>
          <FRDOCBP D="0" T="20SER1.sgm">2011-24118</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>58315</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24212</FRDOCBP>
        </DOCENT>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>EDGA Exchange, Inc.,</SJDOC>
          <PGS>58315-58317</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24067</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>EDGX Exchange, Inc.,</SJDOC>
          <PGS>58317-58319</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24068</FRDOCBP>
        </SJDENT>
        <SJ>Temporary Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Kroll Bond Rating Agency, Inc,</SJDOC>
          <PGS>58319-58321</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24028</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Selective</EAR>
      <HD>Selective Service System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>58321-58327</PGS>
          <FRDOCBP D="6" T="20SEN1.sgm">2011-24044</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Small Business</EAR>
      <HD>Small Business Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Disaster Declarations:</SJ>
        <SJDENT>
          <SJDOC>Connecticut; Amendment 1,</SJDOC>
          <PGS>58329</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24070</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New Hampshire; Amendment 1,</SJDOC>
          <PGS>58330</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24063</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York;  Amendment 5,</SJDOC>
          <PGS>58329</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24073</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York; Amendment 6,</SJDOC>
          <PGS>58328</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24058</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>North Carolina; Amendment 5,</SJDOC>
          <PGS>58328</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24069</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Pennsylvania,</SJDOC>
          <PGS>58328-58327</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24080</FRDOCBP>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24081</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Texas,</SJDOC>
          <PGS>58329-58330</PGS>
          <FRDOCBP D="1" T="20SEN1.sgm">2011-24076</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Vermont; Amendment 4,</SJDOC>
          <PGS>58329</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24072</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Javits Report 2012,</DOC>
          <PGS>58330</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24114</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>International Telecommunication Advisory Committee,</SJDOC>
          <PGS>58332</PGS>
          <FRDOCBP D="0" T="20SEN1.sgm">2011-24116</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Shipping Coordinating Committee,</SJDOC>
          <PGS>58330-58332</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24115</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Proposed Commercial Export Licenses,</DOC>
          <PGS>58332-58334</PGS>
          <FRDOCBP D="2" T="20SEN1.sgm">2011-24113</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Transportation Department</EAR>
      <HD>Transportation Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Aviation Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Railroad Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Highway Traffic Safety Administration</P>
      </SEE>
    </AGCY>
    <PTS>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Energy Department,</DOC>
        <PGS>58346-58371</PGS>
        <FRDOCBP D="26" T="20SEP2.sgm">2011-22812</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Presidential Documents,</DOC>
        <PGS>58373-58378</PGS>
        <FRDOCBP D="3" T="20SED0.sgm">2011-24332</FRDOCBP>
        <FRDOCBP D="1" T="20SED1.sgm">2011-24333</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>76</VOL>
  <NO>182</NO>
  <DATE>Tuesday, September 20, 2011</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="58089"/>
        <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Farm Service Agency</SUBAGY>
        <CFR>7 CFR Part 762</CFR>
        <RIN>RIN 0560-AH41</RIN>
        <SUBJECT>Guaranteed Loan Fees</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Farm Service Agency, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Farm Service Agency (FSA) is amending the regulations for guaranteed loans to change the amount charged and collected in order for FSA to provide a guarantee. Except in certain limited cases, FSA currently charges a fee of 1 percent (1%) of the guaranteed amount on all guaranteed loans. The rule change is necessary for FSA to be able to offset the cost of the guaranteed loan program to maintain program funding to farmers and ranchers. Specifically, FSA is changing the current guaranteed loan fee from 1 percent to 1.5 percent.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>October 1, 2011.</P>
          <P>
            <E T="03">Comment Date:</E>We will consider comments that we receive by November 21, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>We invite you to submit comments on this interim rule. In your comment, include the volume, regulation identifier (RIN) date, and page number of this issue of the<E T="04">Federal Register</E>. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the online instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Director, Loan Making Division, Farm Loan Programs, FSA, USDA, 1400 Independence Avenue, SW., Stop 0522, Washington, DC 20250-0522.</P>
          <P>•<E T="03">Hand Delivery or Courier: Deliver comments to:</E>USDA FSA, Farm Loan Programs, Loan Making Division, 1400 Independence Avenue, SW., Washington, DC 20250.</P>
          <P>Comments will be available for inspection online at<E T="03">http://www.regulations.gov</E>and in the Office of the Director, Loan Making Division, FSA, at 1400 Independence Avenue, SW., Washington, DC, Monday through Friday between 8 a.m. to 4:30 p.m.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Tracy L. Jones, telephone: (202) 720-3889. Persons with disabilities or who require alternative means for communications (Braille, large print, audio tape, etc.) should contact the USDA Target Center at (202) 720-2600 (voice and TDD).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>FSA published a proposed rule on May 15, 2006, (71 FR 27978-27980) proposing to amend regulations governing fees on loans made in the Guaranteed Loan Program.</P>
        <P>As specified in 7 CFR part 762, FSA provides guaranteed loans to eligible lenders (for example banks, Farm Credit System institutions, credit unions) with a guarantee of up to 95 percent of the loss of principal and interest on a loan in certain cases. Farmers and ranchers apply to an agricultural lender, who then applies for the guarantee. The FSA guarantee permits lenders to make agricultural credit available to farmers who do not meet the lender's normal underwriting standards.</P>

        <P>FSA guaranteed loans may be made for farm ownership, conservation, and operating purposes. Guaranteed farm ownership loans (FO) generally may be made to purchase farmland, construct or repair buildings and other fixtures, develop farmland to promote soil and water conservation, or refinance debt. Guaranteed operating loans (OL) generally may be used to purchase livestock, farm equipment, pay for minor improvements to buildings, costs associated with land and water development, annual operating expenses, family living expenses, and to refinance debts under certain conditions. Guaranteed conservation loans (CL) may be made to implement conservation projects deemed necessary by a farmer's Natural Resources Conservation Service conservation plan. On May 13, 2011, a<E T="04">Federal Register</E>notice (76 FR 27986) announced that FSA is no longer accepting direct or guaranteed loan applications for CL Program due to a lack of funding. A notice will be published in the<E T="04">Federal Register</E>announcing the date FSA will resume accepting direct and guaranteed loan applications for the CL Program if funding becomes available.</P>
        <P>The authority for FSA to set the amount of the fee is through several laws. The Consolidated Farm and Rural Development Act (CONTACT) section 307(b) (7 U.S.C. 1927) authorizes fees on farm ownership loans. As specified in the CONACT, the fees are to be set at an amount as “the Secretary may require.” For the OL and CL Program, Title V of the Independent Offices Appropriations Act of 1952 (31 U.S.C. 9701) authorizes fees be prescribed for services or things of value to individuals or businesses provided by the Government.</P>
        <P>FSA currently charges a one-time guarantee fee of 1 percent (1.0%) on guaranteed loans at the time of loan origination as specified in 7 CFR 762.130. FSA does not charge continuation fees for annual renewal of lines of credit (LOC) type OLs, loan servicing, or restructuring actions.</P>

        <P>In the proposed rule, FSA proposed increasing the existing one-time guarantee fee from 1 percent to 1.5 percent and adding a new annual continuation fee of 0.75 percent for advances on LOCs. This rule will change the regulation for the one-time guarantee fee from a fixed rate of 1 percent to a calculated rate that will initially be set at 1.5 percent on October 1, 2011. The fee schedule with this new rate will be available at<E T="03">http://www.fsa.usda.gov/Internet/FSA_File/loanschartoct11.pdf</E>and at any FSA office and is subject to future necessary revisions.</P>
        <P>The increase to 1.5 percent is required now because as proposed in the 2012 budget FSA will have less authority to fund guaranteed loans. Based on the proposed 2012 budget, the fee will need to be increased to 1.5 percent for FO, OL, and CL guarantees. FSA expects future budgets will result in occasional small increases in the future, but does not expect that routine annual increases would be required.</P>

        <P>The assumptions used in the President's Fiscal Year (FY) 2012 Budget proposal included “Upfront fees” of 1.5 percent in calculating the subsidy costs for FO, OL, and CL guarantees. In addition, the 2012 budget<PRTPAGE P="58090"/>proposes a substantially lower budget authority for the Guaranteed Loan Program. Without the increase in the guarantee fee, there will be no budget authority to make any guaranteed FOs and very little budget authority to make guaranteed OLs.</P>
        <P>The budget process for FSA loans is governed by the Federal Credit Reform Act (Credit Reform) of 1990. Credit Reform changed the way the costs of direct loans and loan guarantees are accounted for in the Federal Budget, placing the costs of credit programs on a budgetary basis equivalent to other Federal spending. These costs, referred to as subsidy costs, are developed based on criteria published in the Office of Management and Budget (OMB) Circular No. A-11, “Preparation, Submission, and Execution of the Budget.” Annual appropriations for the FSA Guaranteed Loan Program are based on these subsidy costs, not the actual principal of the loans guaranteed, and are recorded as budget authority.</P>
        <P>In summary, the subsidy cost represents the cost to the Government for each dollar guaranteed and this is the amount of “budget authority” appropriated to the agency. For example, if the subsidy cost is $0.03 for each dollar guaranteed, the subsidy rate is 3 percent. The total principal amount that can be guaranteed by FSA in a fiscal year, referred to as “program authority,” is determined by dividing the budget authority by the subsidy rate (program authority = budget authority ÷ subsidy rate). FSA program authority is reduced if there is a decrease in budget authority, without a corresponding decrease in subsidy rate, or an increase in subsidy rate, without a corresponding increase in budget authority. Expenses such as employee salaries, office leases and supplies, and software development are excluded from the program's budget authority.</P>
        <P>As discussed below in the discussion of comments, FSA reconsidered the proposed annual continuation fee of 0.75 percent for a LOC included in the proposed rule and is not implementing that proposed new continuation fee.</P>
        <HD SOURCE="HD1">Discussion of Comments</HD>
        <P>FSA received 619 comments on the proposed rule from individuals, employees, and the District of Columbia.</P>
        <P>The following provides a summary of the issues raised in the comments to the proposed rule and our responses, including changes we are making to the regulations in response to the comments.</P>
        <P>An overwhelming majority of the comments received opposed the rule change. Although most comments were specific about either the proposed fee increase or the new annual fee, other comments responded to the proposed rule in general.</P>
        <P>The majority of the comments opposed adding an annual 0.75 percent fee to LOCs as an excessive and cumbersome fee to collect on an annual basis. FSA has taken into consideration the requirements of the budget and the burden this administrative fee will have on LOCs, and is not adding the proposed 0.75 percent annual continuation fee. For guaranteed LOCs the guarantee fee would still be due in the first year, but farmers would have access to funding in future years without any additional fee cost. Because FSA will not change the regulation regarding the LOC annual fee, the detailed discussion of comments and responses below focuses on the comments that include the proposed increase in the existing guarantee fee.</P>
        <P>Several commenters supported the rule change suggesting that a guarantee fee of 1.5 percent would be manageable for FO, OL, and LOC. Several commenters supported the change noting that the costs of the guaranteed program have increased since the inception of the current pricing schedule in the early 1980s, and did not dispute increasing the fee to 1.5 percent on both term loans and lines of credit. The supporters believe the fee increase will not materially affect the borrower's cashflow because the 0.5 percent increase will be amortized over the term of the operating and farm ownership loans. Supporters indicated it would be better to charge a one-time fee rather than the annual continuation fee, even if the one-time fee was higher than the 1.5 percent.</P>
        <P>Below are summarized issues raised in the comments FSA received regarding the guarantee fees:</P>
        <P>
          <E T="03">Comment:</E>Fees associated with the guarantee program may add from $1 to $7,000 to the cost of originating a loan, and in many cases may be the difference between a positive and negative cashflow. Increasing existing fees for operating and ownership loans up to the proposed 1.5 percent level would hurt a large number of producers.</P>
        <P>
          <E T="03">Response:</E>The 0.5 percent increase will have a greater impact on borrowers of LOCs and term OLs. For LOCs, the fee change has the greatest effect because the entire fee is paid by the farmer during the initial year of the loan; however, no additional fees will be charged in subsequent years when loan funds are readvanced. For term OLs, the fee increase has a lesser effect than with LOCs on the repayment requirements because the maximum term for these loans is 7 years, which limits the period over which the fee can be amortized. The impact on farmers receiving FO loans should be less significant. These are long term loans and amortization of the fee should have a minimal effect on cashflow. Based on a maximum loan of $1,119,000, the increase in the fee would be an additional $5,036 ($1,119,000 × 90 percent typical guarantee × 0.5 percent increase in fee) that could be amortized over the life of the loan. In FY 2010 the average fee was $2,544. If the fee on those loans were 1.5 percent, the average fee would have been $3,816. If the difference between the two fees is amortized over 7 years, at an interest rate of 5 percent, it would be an additional $220 annually. However, beginning farmers and socially disadvantaged (those who have been historically underserved) farmers who participate in the Downpayment Loan Program, along with borrowers who participate in the FSA Interest Assistance Program or a State Beginning Farmer Program and those direct FSA borrowers who are refinancing their direct loans will continue to have the one-time guarantee fee waived as provided in 7 CFR 762.130(d)(4)(iii)(C). In FY 2010, 13 percent of all guaranteed loans approved were not charged a fee under this regulation.</P>
        <P>
          <E T="03">Comment:</E>The proposed changes are burdensome on rural America. It is doubtful that FSA would cashflow with an additional 0.5 percent increase in guarantee fees. Therefore, the fee should stay as it is. While it is understood that the cost of doing business is increasing for everyone (including the Federal Government), proposing to increase costs targeting this segment of our population is unwise and ill-advised.</P>
        <P>
          <E T="03">Response:</E>The increase in the guarantee fee is not tied to expenses such as employees' salaries, office leases and supplies, and software development. The increase in the fee is necessary to insure that the guaranteed program has the funding necessary to implement the program and provide guarantee services to approved farm lenders. It is not to mitigate the above mentioned administrative expenses. Over the years, the cost of implementing the Guaranteed Loan Program has stayed relatively constant, which is attributed to the successful performance of the guaranteed lenders.</P>
        <P>
          <E T="03">Comment:</E>Instead of the proposed fee changes, change the guarantee fee to a 2 percent to 2.5 percent fee upfront.</P>
        <P>
          <E T="03">Response:</E>Based on the anticipated FY 2012 budget, the fee increase of 0.5 percent is the most appropriate increase at this time. This allows for a balance<PRTPAGE P="58091"/>between increased cost to the borrower and funds available. As noted above, the fee schedule is available at<E T="03">http://www.fsa.usda.gov/Internet/FSA_File/loanschartoct11.pdf</E>and at any FSA office and may change in the future as needed.</P>
        <P>
          <E T="03">Comment:</E>Apply the proposed change only to new guarantees, not existing ones.</P>
        <P>
          <E T="03">Response:</E>There will be no changes to the existing loan guarantees. The guarantee fee change will take effect on October 1, 2011. For loans obligated before October 1, 2011, the existing 1 percent fee will be charged. Loans obligated after October 1, 2011, will pay the new 1.5 percent fee.</P>
        <P>
          <E T="03">Comment:</E>The proposed fee increase will make it harder for farmers to stay profitable, or ultimately survive. Increasing the fee on guaranteed loans only enhances the probability of default as fees would rise in excess of 350 percent on top of fees that are not being paid by other farmers. As an example, a five-year, $100,000 guaranteed LOC would now cost the operator an additional $3,500 (an extra 0.50 percent in 1 year + 0.75 percent for the remaining four years).</P>
        <P>
          <E T="03">Response:</E>As discussed above, FSA is not implementing the proposed 0.75 percent fee on annual advances for line of credits as presented in the proposed rule. Therefore in the above example ($100,000 loan) the guarantee fee would increase only by $450 ($100,000 loan × 0.90 typical guarantee × 0.005 increase in fee).</P>
        <P>
          <E T="03">Comment:</E>Without the new fee increases, many farmers could survive. However, with the fee increases, it may be the end of the road for many of these producers as they also face weather disasters and higher fuel and fertilizer expenses. With the economic crisis that producers are suffering, the last thing that they need is another expense.</P>
        <P>
          <E T="03">Response:</E>FSA is committed to providing the resources necessary to meet the challenges of rising operating expenses. FSA is aware of the unforeseen weather factors and the current state of the economy. FSA offers relief through loan servicing options and disaster or emergency loan assistance in the event weather conditions or other unforeseen circumstances prevent the borrower from meeting their financial obligations. FSA is dedicated to providing guaranteed credit to as many farmers as possible.</P>
        <P>
          <E T="03">Comment:</E>With higher fees, many farmers are not likely to meet the required loan terms to even qualify for the guaranteed loans. This puts more pressure on the direct loan program funding, which has had budget cuts over the years.</P>
        <P>
          <E T="03">Response:</E>FSA is limited by budgetary constraints and the increase in the guarantee fee is necessary to continue the program. Based on the average fee charged on loans closed in FY 2010, the proposed increase in the fee would equate to an additional $1,272 or $220 annually for a 7 year loan at 5 percent interest. Some operators with minimal cash flow margins will be unable to obtain guaranteed credit and may have to rely on the FSA direct loan program.</P>
        <P>
          <E T="03">Comment:</E>The proposed fee increase is an added expense to farmers and producers that they in turn cannot pass on to someone else.</P>
        <P>
          <E T="03">Response:</E>The guarantee fee is charged to and collected from the lender; however, FSA does allow the fee to be passed on to the borrower and, in practice, the fee is almost always passed on to the borrower and amortized in the loan. While this does increase the borrower's loan payments, budgetary constraints will not allow FSA to guarantee loans without the fee increase. FSA is not implementing the annual continuation fee that had been previously proposed.</P>
        <P>
          <E T="03">Comment:</E>USDA and FSA are taking advantage of a group of producers that do not have other options available to them.</P>
        <P>
          <E T="03">Response:</E>Some operators with minimal cash flow margins will be unable to obtain guaranteed credit. These operators would have the option and opportunity to apply for an FSA direct loan. However, to be able to continue to provide guaranteed credit to those farmers who do qualify for a guaranteed loan, FSA must increase the guarantee fee.</P>
        <P>
          <E T="03">Comment:</E>The fees would directly impact the most vulnerable farmers, namely, those who cannot qualify for receiving commercial loans. These farmers would be the least able to pay the new and higher fees. The result would be that these less credit-worthy farmers would have a very difficult time graduating to commercial credit, assuming they would even be able to remain in business in the first place.</P>
        <P>
          <E T="03">Response:</E>The guarantee fee is waived for loans involving interest assistance, loans where a majority of the funds are used to refinance an Agency direct loan (graduation), loans to beginning or socially disadvantaged farmers involved in the direct Downpayment Loan Program, and loans made through a qualified State Beginning Farmer Program per 7 CFR 762.130(d)(4)(iii)(c).</P>
        <P>
          <E T="03">Comment:</E>It is not fair for FSA to increase guaranteed loan fees as it would negatively impact the borrower's farming operation. FSA can generate additional revenues through some other means than increasing the cost of credit for the family farmers. FSA should find alternative ways to cut costs such as a reduction in staff. By increasing fees, FSA will be losing what presence it has with agricultural lenders not to mention the agriculture borrower.</P>
        <P>
          <E T="03">Response:</E>FSA's source to fund guaranteed loans is the subsidy provided by the budget, which takes into account payments made by the government to the public and payments made to the government by the public. Any savings recognized because of cuts in other areas would not alleviate the anticipated budget constraints within the funding levels of the guaranteed loan program. A reduction in FSA administrative costs, such as salaries, has no impact on the budget authority for loan funds. FSA budget for administrative costs is separate from the budget for funding the guaranteed loan program.</P>
        <P>
          <E T="03">Comment:</E>Increasing loan fees on the FSA guaranteed loan program is inconsistent with the goals of the program, which is to help those farmers and ranchers who could qualify for commercial credit if they had some additional support.</P>
        <P>
          <E T="03">Response:</E>The goal of the guaranteed loan program is to help farmers. By increasing the guarantee fee by only 0.5 percent, FSA will maintain the level of funds available to those farmers who could not qualify for commercial credit without a guaranteed loan. FSA is committed to serving the agriculture credit needs of all eligible farmers and ranchers. The fees charged will be lower than other government loan guarantee programs.</P>
        <P>
          <E T="03">Comment:</E>If the program becomes fee based, FSA would have to increase fees each year in order to provide the same level of funding. Without annual appropriations to support the guaranteed loan program, future fees could range widely from year to year.</P>
        <P>
          <E T="03">Response:</E>Guarantee fees could vary year to year however historically the cost of the guaranteed program has not varied greatly from year to year. FSA anticipates the guarantee fee will vary, but we believe it will not vary widely from year to year.</P>
        <P>
          <E T="03">Comment:</E>FSA should not have the authority to change fees in the future without formal promulgation of a change to the<E T="03">Code of Federal Regulations.</E>
        </P>
        <P>
          <E T="03">Response:</E>The proposed rule provided that the level of fees charged for a guaranteed loan may change in the future without promulgation of a rule to<PRTPAGE P="58092"/>amend the guaranteed loan regulations. To accurately predict future fee requirements would not be possible, and the change in the fees may be required quickly after the adoption of a budget; therefore, FSA will not publish the fee amount in the regulations and will not change the fee through rulemaking. The guarantee fee will be posted on the FSA Web site at<E T="03">http://www.fsa.usda.gov/Internet/FSA_File/loanschartoct11.pdf</E>and available at any FSA office. The guarantee fee will be adjusted when needed based on the budget authority for the fiscal year.</P>
        <P>
          <E T="03">Comment:</E>The Farm Credit System is required by law to provide financial services to young, beginning, and small farmers. Through the use of FSA guarantees, the Farm Credit System is able to provide financing to farmers that might not otherwise be assisted. To the extent the fee increases lessen participation in the Guaranteed Loan Program; the mission of the Farm Credit System is inhibited.</P>
        <P>
          <E T="03">Response:</E>Both FSA and the Farm Credit System are mutually committed to providing agriculture credit to the nation's farmers and ranchers. FSA does not believe the mission of the Farm Credit System will be inhibited by the increase in the guarantee fee. FSA believes that by implementing only the guarantee fee increase, the impact on a few farmers will be minimal when compared to the alternative of a reduction in available funds for all eligible farmers.</P>
        <P>
          <E T="03">Comment:</E>The fees will be a disincentive to attracting new banks into the FSA Guaranteed Loan Program. A number of banks will likely stop using the program and FSA will probably not find support for this fee increase in the banking industry. Fewer farmers and lenders using the program could cause the demise of the program.</P>
        <P>
          <E T="03">Response:</E>FSA believes that only a small percentage of lenders and farmers will choose not to participate, and will not have a significant impact on the sustainability of the program. The Guaranteed Loan Program offers risk management portfolio exposure to lenders. Many lenders value this aspect of the program, and will continue to use our program. Budget constraints will not allow FSA to operate at its current level without the guarantee fee increase.</P>
        <P>
          <E T="03">Comment:</E>The Small Business Administration (SBA) programs have experienced fewer banks and fewer rural customers using the program since increasing their fee structure.</P>
        <P>
          <E T="03">Response:</E>SBA makes direct business loans and guarantees loans to small businesses, as well as loans to victims of natural disasters. SBA also works to get government procurement contracts for small businesses and assists business owners with management and technical assistance and business training. In addition to loans for small business owners, SBA is authorized to provide loans for agriculturally related industries. Many of the customers that work with SBA are different from those customers that work with FSA. Both agencies charge guaranteed loan fees for participation in their programs, which can be passed on to the borrower. However, the fees charged by SBA are much higher than those that would be charged by FSA based on this rule. In both cases, the fees can be financed into the loan and amortized over the life of the loan resulting in minimal costs per year.</P>
        <P>
          <E T="03">Comment:</E>Offer a discount for the Preferred Lender Program (PLP).</P>
        <P>
          <E T="03">Response:</E>PLP was developed to recognize experienced lenders, who have demonstrated expertise in, and understanding of, agricultural lending and the FSA Guaranteed Farm Loan Program. PLP is beneficial to both lenders and FSA. The streamlined loan making and servicing processes in 7 CFR part 762 allow lenders to reduce administrative costs and provide a quick turnaround time and a higher level of service to their customers. These incentives are sufficient. PLP lenders must pay the loan origination fee just like the Standard Eligible Lenders (SEL) and Certified Loan Program (CLP) lenders. We are not making any change in response to this suggestion.</P>
        <HD SOURCE="HD1">Miscellaneous Conforming Changes</HD>
        <P>Since the publication of the proposed rule, there have been several Farm Loan Programs rule changes, and a few of those that implemented provisions of the Food, Conservation, and Energy Act of 2008(Pub. L. 110-246, referred to as “the 2008 Farm Bill”) require conforming changes in this rule.</P>

        <P>The current regulation specifies several guaranteed loan transactions that are not charged the guarantee fee, one of these is loans to farmers involved in the Direct Downpayment Program (see 7 CFR 762.130(d)(4)(iii)(C)). At the time the exemption was established, the exemption was for loans to beginning farmers involved in the Direct Beginning Farmer Downpayment Program. On December 8, 2008, a final rule published in the<E T="04">Federal Register</E>(73 FR 74343-74346) implemented provisions of the 2008 Farm Bill required for socially disadvantaged and beginning farmers. The changes to the regulations made by that final rule included expanding and renaming the Downpayment Program to include socially disadvantaged farmers. Therefore, we are making a conforming change by revising and expanding the exception in 7 CFR 762.130(d)(4)(iii)(C) to specify that the guarantee will not be charged for loans to beginning or socially disadvantaged farmers involved in the Direct Downpayment Program (or beginning farmers participating in a qualified State beginning farmer program as discussed below).</P>
        <P>In addition, as specified in 7 U.S.C. 1929(i)(3), USDA may “not charge any person (including a lender) any fee with respect to the provision of any guarantee” under subsection (i) “Coordination of Assistance for Qualified Beginning Farmers and Ranchers.” Subsection (i) addresses requirements related to State beginning farmer programs. As defined in 7 U.S.C. 1929(i)(5), the term “State beginning farmer program” means:</P>
        <EXTRACT>
          
          <P>* * * any program that is—</P>
          <P>(A) carried out by, or under contract with, a State; and</P>
          <P>(B) designed to assist persons in obtaining the financial assistance necessary to enter agriculture and establish viable farming or ranching operations.</P>
        </EXTRACT>
        
        <P>Therefore, we are making a conforming change by revising and expanding the exception in 7 CFR 762.130(d)(4)(iii)(C) to specify that the guarantee will not be charged for loans to beginning farmers participating in a qualified State beginning farmer program.</P>
        <P>On September 3, 2010, an interim rule was published in the<E T="04">Federal Register</E>(75 FR 54005-54016) implementing the new CL Program, which was established by the 2008 Farm Bill. Therefore, we are making a conforming change by to specify that the guarantee fee also will be calculated for the CL Program guaranteed loans.</P>
        <HD SOURCE="HD1">Effective Date</HD>

        <P>The Administrative Procedure Act (APA, 5 U.S.C. 553) provides generally that before rules are issued by Government agencies, the rule must be published in the<E T="04">Federal Register</E>, and the required publication of a substantive rule is to be not less than 30 days before its effective date. One of the exceptions is when the agency finds good cause for not delaying the effective date. If the guarantee fee is not increased to 1.5 percent for FY 2012, then FSA will not be able to guarantee any new FOs and very few OLs. Therefore, FSA finds that there is good cause for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. FSA has decided it is appropriate to issue its final policy as an interim rule to give the public more opportunity to<PRTPAGE P="58093"/>comment on the increase to the one-time guarantee fee and to understand better the need to increase the fee. Publishing this rule as an interim rule allows FSA to increase the guarantee fee and therefore maintain the Guaranteed Loan Program, while allowing time for public comment.</P>
        <HD SOURCE="HD1">Executive Order 12866</HD>
        <P>The Office of Management and Budget (OMB) designated this rule as not significant under Executive Order 12866 and therefore, OMB has not reviewed this interim rule.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to the notice and comment rulemaking requirements under the Administrative Procedure Act (5 U.S.C. 553) or any other statute, unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. FSA has determined that this rule will not have a significant impact on substantial number of small entities for the reasons explained below. Therefore, FSA has not prepared a regulatory flexibility analysis.</P>
        <P>All guarantee fees are charged to and collected from the lender by FSA. FSA allows the fee to be passed on to the applicant and, in practice, the expense is almost always passed on to the borrower or applicant. All FSA guaranteed loan borrowers and all farm entities affected by this rule are small businesses according to U.S. Small Business Administration small business size standards. There is no diversity in size of the entities affected by this rule, and the costs to comply with it are the same for all sizes of entities. The costs of compliance with this rule are expected to be minimal. FSA certifies that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD1">Environmental Evaluation</HD>
        <P>The environmental impacts of this rule have been considered in a manner consistent with provisions of the National Environmental Policy Act (NEPA, 42 U.S.C. 4321-4347), the regulations of the Council on Environmental Quality (40 CFR parts 1500-1508), and the FSA regulations for compliance with NEPA (7 CFR part 799). The changes to the guaranteed loan program that are identified in this rule are administrative in nature. Therefore, FSA has determined that no environmental assessment or environmental impact statement will be prepared.</P>
        <HD SOURCE="HD1">Executive Order 12372</HD>
        <P>Executive Order 12372, “Intergovernmental Review of Federal Programs,” requires consultation with State and local officials. The objectives of the Executive Order are to foster an intergovernmental partnership and a strengthened Federalism, by relying on State and local processes for State and local government coordination and review of proposed Federal Financial assistance and direct Federal development. For reasons set forth in the Notice to 7 CFR part 3015, subpart V (48 FR 29115, June 24, 1983), the programs and activities within this rule are excluded from the scope of Executive Order 12372.</P>
        <HD SOURCE="HD1">Executive Order 12988</HD>
        <P>This rule has been reviewed in accordance with Executive Order 12988, “Civil Justice Reform.” The provisions of this rule will not have preemptive effect with respect to any State or local laws, regulations, or policies that conflict with such provision or which otherwise impede their full implementation. The rule will not have retroactive effect. Before any judicial action may be brought regarding this rule, all administrative remedies in accordance with 7 CFR part 11 must be exhausted.</P>
        <HD SOURCE="HD1">Executive Order 13132</HD>
        <P>This rule has been reviewed under Executive Order 13132, “Federalism.” The policies contained in this rule do not have any substantial direct effect on States, the relationship between the Federal government and the States, or the distribution of power and responsibilities among the various levels of government. Nor does this rule impose substantial direct compliance costs on State and local governments. Therefore, consultation with the States is not required.</P>
        <HD SOURCE="HD1">Executive Order 13175</HD>
        <P>This rule has been reviewed for compliance with Executive Order 13175, “Consultation and Coordination with Indian Tribal Governments.” This Executive Order imposes requirements on the development of regulatory policies that have tribal implications or preempt tribal laws. The USDA Office of Tribal Relations has concluded that the policies contained in this rule do not have Tribal implications that preempt Tribal law. FSA will provide government-to-government consultation with Tribal governments to discuss this interim rule. The Tribal consultation will be available through a teleconference. Leadership from all Federally recognized Tribes that have lands within the affected counties will be invited to the consultation. FSA will respond in a timely and meaningful manner to all Tribal government requests for Tribal consultation about this rule and will provide additional avenues, such as webinars and teleconferences, to periodically host collaborative conversations with Tribal leaders and their representatives about ways to improve this rule in Indian country. When Tribal consultation is complete, FSA will analyze the feedback and incorporate any required changes through the final rule.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995</HD>
        <P>Title II of the Unfunded Mandate Reform Act of 1995 (UMRA, Pub. L. 104-4) requires Federal agencies to assess the effects of their regulatory actions on State, local, or tribal governments or the private sector. Agencies generally must prepare a written statement, including a cost benefit analysis, for proposed and final rules with Federal mandates that may result in expenditures of $100 million or more in any 1 year for State, local, or tribal governments, in the aggregate, or to the private sector. UMRA generally requires agencies to consider alternatives and adopt the more cost effective or least burdensome alternative that achieves the objectives of the rule. This rule contains no Federal mandates as defined by Title II of UMRA for State, local, or tribal governments or for the private sector. Therefore, this rule is not subject to the requirements of sections 202 and 205 of UMRA.</P>
        <HD SOURCE="HD1">Federal Assistance Programs</HD>
        <P>The title and number of the Federal assistance programs, as found in the Catalog of Federal Domestic Assistance, to which this rule applies are:</P>
        
        <FP SOURCE="FP-1">10.099—Conservation Loans,</FP>
        <FP SOURCE="FP-1">10.406—Farm Operating Loans,</FP>
        <FP SOURCE="FP-1">10.407—Farm Ownership Loans.</FP>
        <HD SOURCE="HD1">Paperwork Reduction Act of 1995</HD>
        <P>The amendments to 7 CFR part 762 in this interim rule require no new collection or changes to the current information collections approved by OMB under the control number 0560-0155.</P>
        <HD SOURCE="HD1">E-Government Act Compliance</HD>

        <P>FSA is committed to complying with the E-Government Act, to promote the use of the Internet and other<PRTPAGE P="58094"/>information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 762</HD>
          <P>Agriculture, Credit, Loan programs—Agriculture.</P>
        </LSTSUB>
        
        <P>For reasons discussed above, this rule amends 7 CFR part 762 as follows:</P>
        <REGTEXT PART="762" TITLE="7">
          <PART>
            <HD SOURCE="HED">PART 762—GUARANTEED FARM LOANS</HD>
          </PART>
          <AMDPAR>1. Revise the authority citation for part 762 to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 301 and 7 U.S.C. 1989.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="762" TITLE="7">
          <AMDPAR>2. Amend § 762.130 by revising paragraphs (d)(4)(ii) and (d)(4)(iii)(C) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 762.130</SECTNO>
            <SUBJECT>Loan approval and issuing the guarantee.</SUBJECT>
            <STARS/>
            <P>(d) * * *</P>
            <P>(4) * * *</P>

            <P>(ii) The guarantee fee is established by the Agency at the time the guarantee is obligated. The current fee schedule is available at<E T="03">http://www.fsa.usda.gov</E>and any FSA office. Guaranteed fees may be adjusted annually based on factors that affect program costs. The nonrefundable fee is paid to the Agency by the lender. The fee may be passed on to the borrower and included in loan funds. The guarantee fee for the loan type will be calculated as follows:</P>
            <P>(A) FO guarantee fee = Loan Amount × % guaranteed × (FO percentage established by FSA).</P>
            <P>(B) OL guarantee fee = Loan Amount × % guaranteed × (OL percentage established by FSA).</P>
            <P>(C) CL guarantee fee = Loan Amount × % guaranteed × (CL percentage established by FSA).</P>
            <P>(iii) * * *</P>
            <P>(C) Loans to beginning or socially disadvantaged farmers involved in the direct Downpayment Loan Program or beginning farmers participating in a qualified State Beginning Farmer Program.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Signed on September 12, 2011.</DATED>
          <NAME>Bruce Nelson,</NAME>
          <TITLE>Administrator, Farm Service Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23724 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-05-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-2010-1163; Directorate Identifier 2009-NM-233-AD; Amendment 39-16795; AD 2011-18-13]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; 328 Support Services GmbH (Type Certificate Previously Held by AvCraft Aerospace GmbH; Fairchild Dornier GmbH; Dornier Luftfahrt GmbH) Model 328-100 and -300 Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), Department of Transportation (DOT).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are superseding an existing airworthiness directive (AD) that applies to the products listed above. This AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as:</P>
          
          <EXTRACT>
            <P>During a routine inspection, cracks have been found on an aeroplane at the lower wing panel rear trailing edge inboard of flap lever arm 1 (rib 5). A subsequent inspection of the other aeroplanes in that operator's fleet revealed several more aeroplanes with cracks at the same location. This condition, if not corrected, could lead to structural failure of the affected wing panel, possibly resulting in the wing separating from the airplane with consequent loss of control.</P>
            <STARS/>
          </EXTRACT>
          
          <P>We are issuing this AD to require actions to correct the unsafe condition on these products.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This AD becomes effective October 25, 2011.</P>
          <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of October 25, 2011.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</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 U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Tom Rodriguez, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue, SW., Renton, Washington 98057-3356; telephone (425) 227-1137; fax (425) 227-1149.</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 was published in the<E T="04">Federal Register</E>on December 2, 2010 (75 FR 75159), and proposed to supersede AD 2008-10-51, Amendment 39-15535 (73 FR 30752, May 29, 2008). That NPRM proposed to correct an unsafe condition for the specified products. The MCAI states:</P>
        
        <EXTRACT>
          <P>During a routine inspection, cracks have been found on an aeroplane at the lower wing panel rear trailing edge inboard of flap lever arm 1 (rib 5). A subsequent inspection of the other aeroplanes in that operator's fleet revealed several more aeroplanes with cracks at the same location. This condition, if not corrected, could lead to structural failure of the affected wing panel, possibly resulting in the wing separating from the airplane with consequent loss of control.</P>
          <P>To correct this unsafe condition, EASA [European Aviation Safety Agency] issued Emergency AD 2008-0087-E [dated May 8, 2008] to require detailed visual inspections (DVI) of both the left (LH) and right (RH) wing panel rear trailing edge around rib 3 and rib 5 and a subsequent Eddy Current inspection (NDI) [non-destructive inspection] of the same area to detect cracks, follow-up repair actions when cracks are found, and the reporting of all findings. The TC [type certificate] holder has now developed a modification, consisting of the cold expansion of the former lower wing panel CAMLOC holes together with the installation of new attachment material that will prevent the onset of cracks in the affected wing panel.</P>
          <P>For the reasons described above, this [EASA] AD retains the inspection and repair requirements of AD 2008-0087-E, which is superseded, adds repetitive inspections and a requirement to modify both the LH and RH wing panel rear trailing edges from rib 3 to rib 9. Modification does not constitute terminating action for the new repetitive inspection requirements of this AD.</P>
        </EXTRACT>
        
        <P>The new inspections are eddy current inspections. The modification includes cold expansion of the former lower wing panel CAMLOC holes and installation of new attachment material. You may obtain further information by examining the MCAI in the AD docket.</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to participate in developing this AD. We considered the comments received.</P>
        <HD SOURCE="HD1">MCAI Reference Updates</HD>

        <P>EASA issued AD 2009-0194R1 on March 10, 2011, which was corrected on March 22, 2011. References have been updated in Note 1 and paragraph (p) of this AD to include this revision.<PRTPAGE P="58095"/>
        </P>
        <HD SOURCE="HD1">Request to Remove Repetitive Inspection Interval From Paragraph (h) of This AD</HD>
        <P>Garner CAD Technic Design Organization (GCT DO) Airworthiness Office requested that the 400-flight-cycle repetitive inspection interval be removed from paragraph (h) of the NPRM (75 FR 75159, December 2, 2010). GCT DO Airworthiness Office stated that, based on fatigue data, this repetitive inspection is not required, and is not specified in revised EASA AD 2009-0194R1, dated March 10, 2011, and corrected on March 22, 2011.</P>
        <P>We agree. Based on fatigue data, we have determined that the 400-flight-cycle repetitive inspection interval should be removed from paragraph (h) of this AD. The repetitive inspection was removed from revised EASA AD 2009-0194R1, dated March 10, 2011, and corrected on March 22, 2011. Paragraph (h) of this AD has been changed accordingly. References to the 400-flight-cycle repetitive inspections also were removed from paragraphs (i) and (j) of this AD.</P>
        <P>To ensure that operators get credit for the most recent inspection done in accordance with Dornier Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 1, both dated May 8, 2008; or 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008; we have clarified paragraph (g) of this AD. We have replaced the phrase, “in accordance with the requirements of paragraph (h) of this AD,” with the phrase, “in accordance with Dornier Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 1, both dated May 8, 2008; or 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008.”</P>
        <HD SOURCE="HD1">Request for Extended Inspection Interval in Paragraph (i) of This AD</HD>
        <P>GCT DO Airworthiness Office requested that the initial compliance time and repetitive inspection interval defined in paragraph (i) of the NPRM (75 FR 75159, December 2, 2010) be extended from 800 flight cycles to 1,500 flight cycles. GCT DO Airworthiness Office stated that this extension has been allowed based on fatigue data, and was specified in revised EASA AD 2009-0194R1, dated March 10, 2011, and corrected on March 22, 2011.</P>
        <P>We agree to extend the initial compliance time and repetitive inspection intervals for the reasons given by the commenter. Paragraph (i) of this AD has been changed accordingly.</P>
        <HD SOURCE="HD1">Request To Extend Threshold for Post-Modification Inspections</HD>
        <P>GCT DO Airworthiness Office requested that based on fatigue data, the threshold for the post-modification initial inspection be extended from 800 flight cycles to 25,000 flight cycles for the Model 328-100 airplane, and from 800 flight cycles to 20,000 flight cycles for Model 328-300 airplanes, and that the repetitive inspections be extended from 800 flight cycles to 1,500 flight cycles.</P>
        <P>We agree to extend the threshold for post-modification initial inspections as requested. Based on fatigue data, the referenced EASA AD has included these extensions; therefore, we have added paragraph (k) to the AD to include the new compliance times.</P>
        <HD SOURCE="HD1">Additional Change to NPRM</HD>
        <P>The NPRM (75 FR 75159, December 2, 2010) would have allowed issuance of a special flight permit if a crack was found that “exceeds” 12.5 mm (0.49 inch). We have changed paragraph (o)(4)(ii) of this AD to change the wording from “exceeds” to “is less than or equal to.”</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>We reviewed the available data, including the comments received, and determined that air safety and the public interest require adopting the AD with the changes described previously. We determined that these changes will not increase the economic burden on any operator or increase the scope of the AD.</P>
        <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information</HD>
        <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information.</P>
        <P>We might also have required different actions in this AD from those in the MCAI in order to follow our FAA policies. Any such differences are highlighted in a NOTE within the AD.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this AD will affect about 49 products of U.S. registry.</P>
        <P>The actions that are required by AD 2008-10-51 and retained in this AD take about 2 work-hours per product, at an average labor rate of $85 per work-hour. Required parts cost about $0 per product. Based on these figures, the estimated cost of the currently required actions is $170 per product.</P>
        <P>We estimate that it will take about 8 work-hours per product to comply with the new basic requirements of this AD. The average labor rate is $85 per work-hour. Required parts will cost about $11,600 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these parts. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of this AD to the U.S. operators to be $601,720, or $12,280 per product.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>For the reasons discussed above, I certify this AD:</P>
        <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
        <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and</P>

        <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities<PRTPAGE P="58096"/>under the criteria of the Regulatory Flexibility Act.</P>
        <P>We prepared a regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD docket.</P>
        <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 Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains the NPRM, the regulatory evaluation, any comments received, and other information. The street address for the Docket Operations office (telephone (800) 647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
        <REGTEXT PART="39" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="39" TITLE="14">
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by removing Amendment 39-15535 (73 FR 30752, May 29, 2008) and adding the following new AD:</P>
            
            <EXTRACT>
              <FP SOURCE="FP1-2">
                <E T="04">2011-18-13 328Support Services GmbH (Type Certificate Previously Held by AvCraft Aerospace GmbH; Fairchild Dornier GmbH; Dornier Luftfahrt GmbH):</E>Amendment 39-16795. Docket No. FAA-2010-1163; Directorate Identifier 2009-NM-233-AD.</FP>
              <HD SOURCE="HD1">Effective Date</HD>
              <P>(a) This airworthiness directive (AD) becomes effective October 25, 2011.</P>
              <HD SOURCE="HD1">Affected ADs</HD>
              <P>(b) This AD supersedes AD 2008-10-51, Amendment 39-15535 (73 FR 30752, May 29, 2008).</P>
              <HD SOURCE="HD1">Applicability</HD>
              <P>(c) This AD applies to 328 Support Services GmbH (Type Certificate previously held by AvCraft Aerospace GmbH; Fairchild Dornier GmbH; Dornier Luftfahrt GmbH) Model 328-100 and -300 airplanes; all serial numbers; certificated in any category.</P>
              <HD SOURCE="HD1">Subject</HD>
              <P>(d) Air Transport Association (ATA) of America Code 57: Wings.</P>
              <HD SOURCE="HD1">Reason</HD>
              <P>(e) The mandatory continuing airworthiness information (MCAI) states:</P>
              
              <P>During a routine inspection, cracks have been found on an aeroplane at the lower wing panel rear trailing edge inboard of flap lever arm 1 (rib 5). A subsequent inspection of the other aeroplanes in that operator's fleet revealed several more aeroplanes with cracks at the same location. This condition, if not corrected, could lead to structural failure of the affected wing panel, possibly resulting in the wing separating from the airplane with consequent loss of control.</P>
              <STARS/>
              <P>The new inspections are eddy current inspections. The modification includes cold expansion of the former lower wing panel CAMLOC holes and installation of new attachment material.</P>
              <HD SOURCE="HD1">Compliance</HD>
              <P>(f) You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
              <HD SOURCE="HD1">Restatement of Requirements of AD 2008-10-51 (73 FR 30752, May 29, 2008), With Updated Service Information and Removal of Certain Repetitive Inspections</HD>
              <HD SOURCE="HD1">Repetitive Detailed Visual Inspections for Cracks</HD>
              <P>(g) Within 10 flight cycles, or 10 flight hours, or 7 days, whichever occurs first after June 3, 2008 (the effective date of AD 2008-10-51 (73 FR 30752, May 29, 2008)): Accomplish a detailed visual inspection of both the left-hand (LH) and right-hand (RH) lower wing panel inboard and outboard of flap lever arm 1 (rib 5) for cracks, in accordance with the Accomplishment Instructions of Dornier Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 1, both dated May 8, 2008, as applicable; or 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008, as applicable. After the effective date of this AD, use only 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008, as applicable. If no crack is detected, repeat the detailed visual inspection thereafter at intervals not to exceed 50 flight hours. If any crack is detected, before further flight, do an eddy current inspection, in accordance with Dornier Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 1, both dated May 8, 2008, as applicable; or 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008, as applicable.</P>
              <HD SOURCE="HD1">Eddy Current Inspections for Cracks</HD>
              <P>(h) Except as required by paragraph (g) of this AD, within 400 flight hours or 3 months after June 3, 2008, whichever occurs first: Accomplish an eddy current inspection for cracking of both the LH and RH lower wing panel in the vicinity of rib 3 and inboard and outboard of flap lever arm 1 (rib 5), in accordance with the Accomplishment Instructions of Dornier Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 1, both dated May 8, 2008, as applicable; or 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008, as applicable. After the effective date of this AD, use only 328 Support Services Alert Service Bulletin ASB-328J-57-015 or ASB-328-57-037, both Revision 2, both dated May 20, 2008, as applicable. Accomplishment of the eddy current inspection terminates the detailed visual inspection required by paragraph (g) of this AD.</P>
              <HD SOURCE="HD1">New Requirements of This AD</HD>
              <HD SOURCE="HD1">New Repetitive Intervals for Eddy Current Inspections</HD>
              <P>(i) Within 1,500 flight cycles after the most recent eddy current inspection done in accordance with the applicable service bulletin listed in table 1 of this AD, or within 60 days after the effective date of this AD, whichever occurs later, do an eddy current inspection for cracking of the lower wing panel (outside) around the flap lever arm 1 (rib 5), in accordance with the Accomplishment Instructions of 328 Support Services Alert Service Bulletin ASB-328-57-037 (for Model 328-100 airplanes) or ASB-328J-57-015 (for Model 328-300 airplanes), both Revision 2, both dated May 20, 2008. Repeat the inspection thereafter at intervals not to exceed 1,500 flight cycles, except as provided by paragraph (k) of this AD.</P>
              <GPOTABLE CDEF="s100,12,xs72" COLS="3" OPTS="L2,i1">
                <TTITLE>Table 1—Service Bulletins</TTITLE>
                <BOXHD>
                  <CHED H="1">Service Bulletin</CHED>
                  <CHED H="1">Revision</CHED>
                  <CHED H="1">Date</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">Dornier Alert Service Bulletin ASB-328-57-037</ENT>
                  <ENT>1</ENT>
                  <ENT>May 8, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">Dornier Alert Service Bulletin ASB-328J-57-015</ENT>
                  <ENT>1</ENT>
                  <ENT>May 8, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328-57-037</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328J-57-015</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
              </GPOTABLE>
              <PRTPAGE P="58097"/>
              <HD SOURCE="HD1">Inspection and Modification of Lower Wing Panel</HD>
              <P>(j) Within 24 months after the effective date of this AD, do an eddy current inspection for cracking of the lower wing panel (outside) around the flap lever arm 1 (rib 5). If no cracking is found, within 24 months after the effective date of this AD, modify the lower wing panel by doing a cold expansion of the CAMLOC holes and installing new attachment material from rib 9 LH to rib 9 RH. Do all actions required by this paragraph in accordance with the Accomplishment Instructions of 328 Support Services Service Bulletin SB-328-57-481 (for Model 328-100 airplanes) or SB-328J-57-230 (for Model 328-300 airplanes), both Revision 1, both dated October 15, 2009.</P>
              <P>(k) After the modification required by paragraph (j) is done, do the eddy current inspection required by paragraph (i) of this AD at the applicable time specified in paragraph (k)(1) or (k)(2) of this AD. Repeat the inspections thereafter at the intervals specified in paragraph (i) of this AD.</P>
              <P>(1) For Model 328-100 airplanes: Within 25,000 flight cycles after accomplishing the modification specified in paragraph (j) of this AD.</P>
              <P>(2) For Model 328-300 airplanes: Within 20,000 flight cycles after accomplishing the modification specified in paragraph (j) of this AD.</P>
              <HD SOURCE="HD1">Repair</HD>
              <P>(l) If any cracking is found during any inspection required by this AD, before further flight contact 328 Support Services GmbH for repair instructions and do the repair using a method approved by either the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or European Aviation Safety Agency (EASA) (or its delegated agent).</P>
              <HD SOURCE="HD1">Inspections Accomplished According to Previous Issues of Service Bulletins</HD>
              <P>(m) Inspections accomplished before the effective date of this AD according to Dornier Alert Service Bulletin ASB-328-57-037 or Dornier Alert Service Bulletin ASB-328J-57-015, both Revision 1, both dated May 8, 2008, as applicable, are considered acceptable for compliance with the inspection requirements of paragraphs (i) and (j) of this AD.</P>
              <HD SOURCE="HD1">Report</HD>

              <P>(n) At the applicable times specified in paragraphs (n)(1) and (n)(2) of this AD: Send 328 Support Services GmbH a report of findings (both positive and negative) found during each inspection required by paragraphs (g), (h), (i), and (j) of this AD. The report must include the inspection results, a description of any cracks found, the airplane serial number, and the number of landings and flight hours on the airplane. Send the report to 328 Support Services GmbH, Global Support Center, P.O. Box 1252, D-82231 Wessling, Federal Republic of Germany; Telephone +49 8153 88111 6666; fax +49 8153 88111 6565; e-mail:<E T="03">gsc.op@328support.de.</E>
              </P>
              <P>(1) For any inspection done on or after the effective date of this AD: Within 30 days after the inspection.</P>
              <P>(2) For any inspection done before the effective date of this AD: Within 30 days after the effective date of this AD.</P>
              <HD SOURCE="HD1">FAA AD Differences</HD>
              <NOTE>
                <HD SOURCE="HED">Note 1:</HD>
                <P>This AD differs from the MCAI and/or service information as follows:</P>
                <P>EASA Airworthiness Directive 2009-0194R1, dated March 10, 2011, corrected March 22, 2011, gives credit for eddy current inspections conducted in accordance with the maintenance review board tasks. We are not giving credit for those inspections.</P>
              </NOTE>
              <HD SOURCE="HD1">Other FAA AD Provisions</HD>
              <P>(o) The following provisions also apply to this AD:</P>
              <P>(1)<E T="03">Alternative Methods of Compliance (AMOCs):</E>The Manager, International Branch, ANM-116, 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 International Branch, send it to ATTN: Tom Rodriguez, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue, SW., Renton, Washington 98057-3356; telephone (425) 227-1137; fax (425) 227-1149. Information may be e-mailed to:<E T="03">9-ANM-116-AMOC-REQUESTS@faa.gov.</E>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. The AMOC approval letter must specifically reference this AD.</P>
              <P>(2)<E T="03">Airworthy Product:</E>For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.</P>
              <P>(3)<E T="03">Reporting Requirements:</E>A Federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with a collection of information subject to the requirements of the Paperwork Reduction Act unless that collection of information displays a current valid OMB Control Number. The OMB Control Number for this information collection is 2120-0056. Public reporting for this collection of information is estimated to be approximately 5 minutes per response, including the time for reviewing instructions, completing and reviewing the collection of information. All responses to this collection of information are mandatory. Comments concerning the accuracy of this burden and suggestions for reducing the burden should be directed to the FAA at: 800 Independence Ave., SW., Washington, DC 20591, Attn: Information Collection Clearance Officer, AES-200.</P>
              <P>(4)<E T="03">Special Flight Permits:</E>Special flight permits may be issued in accordance with sections 21.197 and 21.199 of the Federal Aviation Regulations (14 CFR 21.197 and 21.199) to operate the airplane to a location where the requirements of paragraphs (g), (h), (i), (j), (k), and (l) of this AD can be done if the following conditions are met:</P>
              <P>(i) The initial inspection required by paragraph (g) of this AD must be accomplished.</P>
              <P>(ii) If a crack indication is less than or equal to 12.5 mm (0.49 inch), the Manager, International Branch, ANM-116, concurs with issuance of the special flight permits.</P>
              <HD SOURCE="HD1">Related Information</HD>
              <P>(p) Refer to MCAI EASA Airworthiness Directive 2009-0194R1, dated March 10, 2011, corrected March 22, 2011, and the service bulletins listed in table 2 of this AD, for related information.</P>
              <GPOTABLE CDEF="s100,12,xs72" COLS="3" OPTS="L2,i1">
                <TTITLE>Table 2—Related Service Bulletins</TTITLE>
                <BOXHD>
                  <CHED H="1">Service Bulletin</CHED>
                  <CHED H="1">Revision</CHED>
                  <CHED H="1">Date</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328-57-037</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328J-57-015</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Service Bulletin SB-328-57-481</ENT>
                  <ENT>1</ENT>
                  <ENT>October 15, 2009.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services GmbH Service Bulletin SB-328J-57-230</ENT>
                  <ENT>1</ENT>
                  <ENT>October 15, 2009.</ENT>
                </ROW>
              </GPOTABLE>
              <HD SOURCE="HD1">Material Incorporated by Reference</HD>

              <P>(q) You must use the service information contained in table 3 of this AD to do the actions required by this AD, as applicable, unless the AD specifies otherwise.<PRTPAGE P="58098"/>
              </P>
              <GPOTABLE CDEF="s100,12,xs72" COLS="3" OPTS="L2,i1">
                <TTITLE>Table 3—All Material Incorporated by Reference</TTITLE>
                <BOXHD>
                  <CHED H="1">Service Bulletin</CHED>
                  <CHED H="1">Revision</CHED>
                  <CHED H="1">Date</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328-57-037</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Alert Service Bulletin ASB-328J-57-015</ENT>
                  <ENT>2</ENT>
                  <ENT>May 20, 2008.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services Service Bulletin SB-328-57-481</ENT>
                  <ENT>1</ENT>
                  <ENT>October 15, 2009.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">328 Support Services GmbH Service Bulletin SB-328J-57-230</ENT>
                  <ENT>1</ENT>
                  <ENT>October 15, 2009.</ENT>
                </ROW>
              </GPOTABLE>
              <P>(1) The Director of the Federal Register approved the incorporation by reference of this service information under 5 U.S.C. 552(a) and 1 CFR part 51.</P>

              <P>(2) For service information identified in this AD, contact 328 Support Services GmbH, Global Support Center, P.O. Box 1252, D-82231 Wessling, Federal Republic of Germany; telephone +49 8153 88111 6666; fax +49 8153 88111 6565; e-mail<E T="03">gsc.op@328support.de;</E>Internet<E T="03">http://www.328support.de.</E>
              </P>
              <P>(3) You may review copies of the service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>

              <P>(4) You may also review copies of the service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
              </P>
            </EXTRACT>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Renton, Washington, on August 19, 2011.</DATED>
          <NAME>Ali Bahrami,</NAME>
          <TITLE>Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-22032 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2011-0221; Directorate Identifier 2010-NM-120-AD; Amendment 39-16805; AD 2011-18-23]</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>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are adopting a new airworthiness directive (AD) for all The Boeing Company Model DC-8-11, DC-8-12, DC-8-21, DC-8-31, DC-8-32, DC-8-33, DC-8-41, DC-8-42, and DC-8-43 airplanes; Model DC-8-50 series airplanes; Model DC-8F-54 and DC-8F-55 airplanes; Model DC-8-60 series airplanes; Model DC-8-60F series airplanes; Model DC-8-70 series airplanes; and Model DC-8-70F series airplanes. This AD requires repetitive high frequency eddy current or repetitive low frequency eddy current inspections for cracks on the area around certain fasteners of the access opening doubler on the left and right wing center spar lower cap, and repair, if necessary. This AD was prompted by reports that cracks in the center spar lower cap and, in some cases, the web of the spar, have been found at stations Xrs = 168.00, Xrs = 251.00, and Xrs = 358.00. We are issuing this AD to detect and correct cracks in the area around certain fasteners of the access opening doubler on the left and right wing center spar lower cap, which could compromise the structural integrity of the wing structure.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This AD is effective October 25, 2011.</P>
          <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in the AD as of October 25, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, 3855 Lakewood Boulevard, MC D800-0019, Long Beach, California 90846-0001; telephone 206-544-5000, extension 2; fax 206-766-5683; e-mail<E T="03">dse.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 AD, the regulatory evaluation, any comments received, and other information. The address for the Docket Office (phone: 800-647-5527) is Document Management Facility, U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Dara Albouyeh, Aerospace Engineer, Airframe Branch, ANM-120L, FAA, Los Angeles Aircraft Certification Office (ACO), 3960 Paramount Boulevard, Lakewood, California 90712-4137; phone: (562) 627-5222; fax: (562) 627-5210; e-mail:<E T="03">dara.albouyeh@faa.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Discussion</HD>

        <P>We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to include an airworthiness directive (AD) that would apply to the specified products. That NPRM published in the<E T="04">Federal Register</E>on March 15, 2011 (76 FR 13926). That NPRM proposed to require repetitive high frequency eddy current or repetitive low frequency eddy current inspections for cracks on the area around certain fasteners of the access opening doubler on the left and right wing center spar lower cap, and repair, if necessary.</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to participate in developing this AD. The following presents the comment received on the proposal and the FAA's response to each comment.</P>
        <HD SOURCE="HD1">Request To Revise Paragraph (h)(3) of the NPRM</HD>
        <P>Boeing requested that we revise paragraph (h)(3) of the NPRM (76 FR 13926, March 15, 2011) to refer to “Method 101 and 104,” instead of “Method 101 or 104.” Boeing explained that Methods 101 and 104 should be used when using Section 57-10-16 of the McDonnell Douglas DC-8 Supplemental Inspection Document (SID) Report L26-011, Volume II, Revision 8, dated January 2005. Boeing stated that “Method 101 and 104” is correctly referenced in the service information.</P>

        <P>We agree. We have clarified the reference as “Methods 101 and 104” in paragraph (h)(3) of the final rule for the reasons stated by Boeing.<PRTPAGE P="58099"/>
        </P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>We reviewed the relevant data, considered the comment received, and determined that air safety and the public interest require adopting the AD with the change described previously.</P>
        <P>We also determined that this change will not increase the economic burden on any operator or increase the scope of the AD.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this AD would affect 41 airplanes of U.S. registry. We also estimate that it will take 12 work-hours per product to comply with this AD. The average labor rate is $85 per work-hour. Based on these figures, we estimate the cost of this AD to the U.S. operators to be $41,820, or $1,020 per product.</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>For the reasons discussed above, I certify that this AD:</P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
        <P>(3) Will not affect intrastate aviation in Alaska, and</P>
        <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
        <REGTEXT PART="39" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="39" TITLE="14">
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</AMDPAR>
          
          <EXTRACT>
            <FP SOURCE="FP-2">
              <E T="04">2011-18-23The Boeing Company:</E>Amendment 39-16805; Docket No. FAA-2011-0221; Directorate Identifier 2010-NM-120-AD.</FP>
            <HD SOURCE="HD1">Effective Date</HD>
            <P>(a) This AD is effective October 25, 2011.</P>
            <HD SOURCE="HD1">Affected ADs</HD>
            <P>(b) This AD affects certain requirements of AD 2008-25-05, Amendment 39-15763 (73 FR 78936, December 24, 2008).</P>
            <HD SOURCE="HD1">Applicability</HD>
            <P>(c) This AD applies to all The Boeing Company Model DC-8-11, DC-8-12, DC-8-21, DC-8-31, DC-8-32, DC-8-33, DC-8-41, DC-8-42, DC-8-43, DC-8-51, DC-8-52, DC-8-53, DC-8-55, DC-8F-54, DC-8F-55, DC-8-61, DC-8-62, DC-8-63, DC-8-61F, DC-8-62F, DC-8-63F, DC-8-71, DC-8-72, DC-8-73, DC-8-71F, DC-8-72F, and DC-8-73F airplanes, certificated in any category.</P>
            <HD SOURCE="HD1">Subject</HD>
            <P>(d) Air Transport Association (ATA) of America Code 57: Wings.</P>
            <HD SOURCE="HD1">Unsafe Condition</HD>
            <P>(e) This AD was prompted by reports that cracks in the center spar lower cap and, in some cases, the web of the spar, have been found at stations Xrs = 168.00, Xrs = 251.00, and Xrs = 358.00. The Federal Aviation Administration is issuing this AD to detect and correct cracks in the area around certain fasteners of the access opening doubler on the left and right wing center spar lower cap, which could compromise the structural integrity of the wing structure.</P>
            <HD SOURCE="HD1">Compliance</HD>
            <P>(f) You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
            <HD SOURCE="HD1">Inspection</HD>
            <P>(g) Before the accumulation of 20,000 total flight cycles, or within 3,000 flight cycles after the effective date of this AD, whichever occurs later, do a high frequency eddy current (HFEC) or low frequency eddy current (LFEC) inspection for cracks on the area around certain fasteners of the access opening doubler on the left and right wing center spar lower cap, in accordance with the Accomplishment Instructions of Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010. If no crack is found, repeat the inspection thereafter at the applicable interval specified in paragraph 1.E., “Compliance” of Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010.</P>
            <HD SOURCE="HD1">Repair</HD>
            <P>(h) If any crack is found during any inspection required by paragraph (g) of this AD, do the actions specified in paragraphs (h)(1), (h)(2), and (h)(3) of this AD.</P>
            <P>(1) Before further flight, repair the crack in accordance with Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010.</P>
            <P>(2) Within 6,000 flight cycles after doing the most recent HFEC inspection, or within 1,750 flight cycles after doing the most recent LFEC inspection; as applicable; do the inspection specified in paragraph (g) of this AD of the non-repaired area, and repeat the inspection of the non-repaired area thereafter at the applicable time in paragraph 1.E. “Compliance,” of Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010.</P>
            <P>(3) Within the applicable times specified in paragraph 1.E. “Compliance,” of Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010, do the inspections of the repaired area, using the inspection defined in Method 101 of Section 57-10-06, “Lower Center Space Cap Flanges (FWD &amp; AFT) from STA Xrs = 100 to 290,” or Methods 101 and 104 of Section 57-10-16, “Lower Center Space Cap Flanges (FWD &amp; AFT) from STA Xrs = 100 to 290,” of the McDonnell Douglas DC-8 Supplemental Inspection Document (SID), Report L26-011, Volume II, Revision 8, dated January 2005, as applicable. Repeat the inspection thereafter at the applicable intervals specified in paragraph 1.E., “Compliance,” of Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010. If any crack is found, before further flight, repair the crack using a method approved in accordance with the procedures specified in paragraph (j) of this AD.</P>
            <P>(i) The inspections required by paragraph (h)(3) of this AD constitute compliance with paragraph (j) of AD 2008-25-05 for the repaired area. All requirements of AD 2008-25-05 that are not specifically referenced in this paragraph remain fully applicable and require compliance.</P>
            <HD SOURCE="HD1">Alternative Methods of Compliance (AMOCs)</HD>

            <P>(j)(1) The Manager, Los Angeles Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD.<PRTPAGE P="58100"/>
            </P>
            <P>(2) To request a different method of compliance or a different compliance time for this AD, follow the procedures in 14 CFR 39.19. 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. The AMOC approval letter must specifically reference this AD.</P>
            <P>(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Los Angeles ACO to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane and 14 CFR 25.571, Amendment 45, and the approval must specifically refer to this AD.</P>
            <HD SOURCE="HD1">Related Information</HD>

            <P>(k) For more information about this AD, contact Dara Albouyeh, Aerospace Engineer, Airframe Branch, ANM-120L, FAA, Los Angeles ACO, 3960 Paramount Boulevard, Lakewood, California 90712-4137; phone: (562) 627-5222; fax: (562) 627-5210; e-mail:<E T="03">dara.albouyeh@faa.gov.</E>
            </P>
            <HD SOURCE="HD1">Material Incorporated by Reference</HD>
            <P>(l) You must use Boeing Alert Service Bulletin DC8-57A103, dated May 5, 2010; and McDonnell Douglas DC-8 Supplemental Inspection Document (SID), Report L26-011, Volume II, Revision 8, dated January 2005; as applicable; to do the actions required by this AD, unless the AD specifies otherwise. The current revision of the McDonnell Douglas DC-8 SID, Report L26-011, Volume II, Revision 8, dated January 2005, is specified on only the title page and List of Effective Pages of the document; the cover page of this document does not specify a revision of date.</P>
            <P>(1) The Director of the Federal Register approved the incorporation by reference of this service information under 5 U.S.C. 552(a) and 1 CFR part 51.</P>

            <P>(2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, 3855 Lakewood Boulevard, MC D800-0019, Long Beach, California 90846-0001; telephone 206-544-5000, extension 2; fax 206-766-5683; e-mail<E T="03">dse.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>
            </P>
            <P>(3) You may review copies of the service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>

            <P>(4) You may also review copies of the service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at an NARA facility, call 202-741-6030, or go to<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
            </P>
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Renton, Washington, on August 25, 2011.</DATED>
          <NAME>Ali Bahrami,</NAME>
          <TITLE>Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23709 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
        <CFR>17 CFR parts 200, 232, 240 and 249</CFR>
        <DEPDOC>[Release Nos. 33-9259; 34-65343; IC-29788; File No. S7-10-09]</DEPDOC>
        <RIN>RIN 3235-AK27</RIN>
        <SUBJECT>Facilitating Shareholder Director Nominations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Securities and Exchange Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; notice of effective date.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This release provides notice of the effective date of the amendment to Exchange Act Rule 14a-8, the shareholder proposal rule, which will require companies to include in their proxy materials, under certain circumstances, shareholder proposals that seek to establish a procedure in the company's governing documents for the inclusion of one or more shareholder director nominees in the company's proxy materials. This release also provides notice of the effective date of related rule changes adopted concurrently with the amendment to Rule 14a-8.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The effective date of the additions of § 200.82a, § 240.14a-18, § 240.14n-1 through § 240.14n-3, and § 240.14n-101, and the amendments to § 232.13, § 240.13a-11, § 240.13d-1, § 240.14a-2, § 240.14a-4, § 240.14a-5, § 240.14a-6, § 240.14a-8, § 240.14a-9, § 240.14a-12, § 240.15d-11, § 240.13d-102, § 240.14a-101, and § 249.308, published on September 16, 2010 (75 FR 56668), is September 20, 2011. Section 240.14a-11 was vacated by the United States Court of Appeals for the District of Columbia Circuit (No. 10-1305, July 22, 2011) and therefore is not effective.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Tamara Brightwell, Lillian Brown, or Ted Yu, Division of Corporation Finance, at (202) 551-3200, U.S. Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>By order dated October 4, 2010 (Release No. 33-9149, 34-63031, IC-29456), the Securities and Exchange Commission stayed from November 15, 2010 until the resolution of the petition for review of Exchange Act Rule 14a-11 in<E T="03">Business Roundtable et al.</E>v.<E T="03">Securities and Exchange Commission,</E>No. 10-1305 (D.C. Cir., filed Sept. 29, 2010), the effective and compliance dates of amendments to the Federal proxy and related rules that the Commission adopted to facilitate the effective exercise of shareholders' traditional state law rights to nominate and elect directors to company boards of directors. On October 20, 2010, a notice of the stay was published in the<E T="04">Federal Register</E>(75 FR 64641). That announcement stated that a notice of the effective and compliance dates of the final rules would be published in the<E T="04">Federal Register</E>following the resolution of the petition for review. On July 22, 2011, the United States Court of Appeals for the District of Columbia Circuit issued an order vacating Rule 14a-11 and on September 14, 2011, the Court issued its mandate. Because the mandate concludes the litigation in the Court of Appeals, the stay expired by its terms. The Court's order did not affect the amendment to Rule 14a-8, which was not challenged in the litigation, or the related rules and amendments adopted concurrently with Rule14a-11 and the amendment to Rule 14a-8. Accordingly, those rules and amendments are effective upon publication of this notice in the<E T="04">Federal Register</E>.</P>

        <P>As discussed in the preamble above, the final rules noted in the<E T="02">DATES</E>section of this document and published on September 16, 2010 (75 FR 56668) amending Title 17, Chapter II of the Code of Federal Regulations, are effective September 20, 2011, with the exception, as noted, of Rule 14a-11 (17 CFR 240.14a-11).</P>
        <SIG>
          <DATED>Dated: September 15, 2011.</DATED>
          <NAME>Elizabeth M. Murphy,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24118 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8011-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <PRTPAGE P="58101"/>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <CFR>18 CFR Part 40</CFR>
        <DEPDOC>[Docket No. RM10-29-000; Order No. 753]</DEPDOC>
        <SUBJECT>Electric Reliability Organization Interpretation of Transmission Operations Reliability Standard</SUBJECT>
        <DATE>September 15, 2011.</DATE>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Energy Regulatory Commission.</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 (FPA), the Federal Energy Regulatory Commission approves the North American Electric Reliability Corporation's proposed interpretation of Reliability Standard, TOP-001-1, Requirement R8, which pertains to the restoration of real and reactive power during a system emergency.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule will become effective November 21, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P/>
          <FP SOURCE="FP-1">Robert T. Stroh (Legal Information),Office of the General Counsel,Federal Energy Regulatory Commission,888 First Street, NE.,Washington, DC 20426,Telephone: (202) 502-8473.</FP>
          <FP SOURCE="FP-1">Eugene Blick (Technical Information), Office of Electric Reliability, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, Telephone: (202) 502-8066.</FP>
          <FP SOURCE="FP-1">David O'Connor (Technical Information),Office of Electric Reliability,Federal Energy Regulatory Commission,888 First Street, NE.,Washington, DC 20426,Telephone: (202) 502-6695.</FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Before Commissioners: Jon Wellinghoff, Chairman;Marc Spitzer, Philip D. Moeller,John R. Norris, and Cheryl A. LaFleur.</P>
        <HD SOURCE="HD1">Final Rule</HD>
        <P>1. Under section 215 of the Federal Power Act (FPA),<SU>1</SU>
          <FTREF/>the Federal Energy Regulatory Commission approves the North American Electric Reliability Corporation's (NERC) proposed interpretation of Requirement R8 in Commission-approved NERC Reliability Standard TOP-001-1—Reliability Responsibilities and Authorities.</P>
        <FTNT>
          <P>
            <SU>1</SU>16 U.S.C. 824o (2006).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Background</HD>
        <P>2. Section 215 of the FPA requires a Commission-certified Electric Reliability Organization (ERO) to develop mandatory and enforceable Reliability Standards, which are subject to Commission review and approval. Approved Reliability Standards are enforced by the ERO, subject to Commission oversight, or by the Commission independently.</P>
        <P>3. Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO<SU>2</SU>
          <FTREF/>and, subsequently, certified NERC as the ERO.<SU>3</SU>
          <FTREF/>On March 16, 2007, the Commission issued Order No. 693, approving 83 of the 107 Reliability Standards filed by NERC, including Reliability Standard TOP-001-1.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">Rules Concerning Certification of the Electric Reliability Organization; and Procedures for the Establishment, Approval and Enforcement of Electric Reliability Standards,</E>Order No. 672, FERC Stats. &amp; Regs. ¶ 31,204, order on reh'g, Order No. 672-A, FERC Stats. &amp; Regs. ¶ 31,212 (2006).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">North American Electric Reliability Corp.,</E>116 FERC ¶ 61,062,<E T="03">order on reh'g &amp; 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>4</SU>
            <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242,<E T="03">order on reh'g,</E>Order No. 693-A, 120 FERC ¶ 61,053 (2007).</P>
        </FTNT>
        <P>4. NERC's Rules of Procedure provide that a person that is “directly and materially affected” by Bulk-Power System reliability may request an interpretation of a Reliability Standard.<SU>5</SU>
          <FTREF/>The ERO's “standards process manager” will assemble a team with relevant expertise to address the requested interpretation and also form a ballot pool. NERC's Rules provide that, within 45 days, the team will draft an interpretation of the Reliability Standard, with subsequent balloting. If approved by ballot, the interpretation is appended to the Reliability Standard and filed with the applicable regulatory authority for regulatory approval.</P>
        <FTNT>
          <P>
            <SU>5</SU>NERC Rules of Procedure, Appendix 3A, Reliability Standards Development Procedure, Version 6.1, at 27-29 (2010).</P>
        </FTNT>
        <HD SOURCE="HD2">A. Reliability Standard TOP-001-1</HD>
        <P>5. Reliability Standard TOP-001-1 (Reliability Responsibilities and Authorities) centers on the responsibilities of balancing authorities and transmission operators during a system emergency. Specifically, the stated purpose of Reliability Standard TOP-001-1 is to ensure reliability entities have clear decision-making authority and capabilities to take appropriate actions or direct the actions of others to return the transmission system to normal conditions during an emergency. Requirement R8 of the standard provides:</P>
        <EXTRACT>
          
          <P>During a system emergency, the Balancing Authority and Transmission Operator shall immediately take action to restore the Real and Reactive Power Balance. If the Balancing Authority or Transmission Operator is unable to restore Real and Reactive Power Balance it shall request emergency assistance from the Reliability Coordinator. If corrective action or emergency assistance is not adequate to mitigate the Real and Reactive Power Balance, then the Reliability Coordinator, Balancing Authority, and Transmission Operator shall implement firm load shedding.<SU>6</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>6</SU>Reliability Standard TOP-001-1, Requirement R8.</P>
        </FTNT>
        <HD SOURCE="HD2">B. NERC Proposed Interpretation</HD>
        <P>6. On July 16, 2010, NERC submitted its petition for approval for an interpretation of Requirement R8 in Commission-approved Reliability Standard TOP-001-1. The Petition explains that NERC received a request from Florida Municipal Power Pool (FMPP) seeking an interpretation of Reliability Standard TOP-001-1, Requirement R8. Specifically, FMPP requested clarification on several aspects of Requirement R8. FMPP asked the following:</P>
        
        <EXTRACT>
          <P>Balancing real power is not a function of a [Transmission Operator] and balancing reactive power is not a function of a [Balancing Authority]. For Requirement R8 is the Balancing Authority responsibility to immediately take corrective action to restore Real Power Balance and is the [Transmission Operator] responsibility to immediately take corrective action to restore Reactive Power Balance?<SU>7</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>7</SU>NERC Petition at 5.</P>
        </FTNT>
        
        <P>7. Consistent with the NERC Rules of Procedure, NERC stated that it assembled a team to respond to the request for interpretation and presented the proposed interpretation to industry ballot, using a process similar to the process it uses for the development of Reliability Standards.<SU>8</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>8</SU>NERC Reliability Standards Development Procedure at 27-29.</P>
        </FTNT>
        <P>8. In response to FMPP's interpretation request, NERC provided the following:</P>
        <EXTRACT>
          

          <P>The answer to both questions is yes. According to the NERC Glossary of Terms Used in Reliability Standards, the Transmission Operator is responsible for the reliability of its “local” transmission system, and operates or directs the operations of the transmission facilities. Similarly, the Balancing Authority is responsible for maintaining load-interchange-generation balance, i.e., real power balance. In the context of this requirement, the Transmission Operator is the functional entity that balances reactive power. Reactive power balancing can be accomplished by issuing instructions to the Balancing Authority or Generator Operators to alter reactive power injection. Based on NERC Reliability Standard BAL-005-1b Requirement R6, the Transmission Operator has no requirement to<PRTPAGE P="58102"/>compute an Area Control Error (ACE) signal or to balance real power. Based on NERC Reliability Standard VAR-001-1 Requirement R8, the Balancing Authority is not required to resolve reactive power balance issues. According toTOP-001-1/Requirement R3, the Balancing Authority is only required to complywith Transmission Operator or Reliability Coordinator instructions to change injections of reactive power.<SU>9</SU>
            <FTREF/>
          </P>
        </EXTRACT>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">Id.</E>at 5-6.</P>
        </FTNT>
        
        <P>NERC stated that the interpretation was developed and approved by industry stakeholders and approved by the NERC Board of Trustees (Board).</P>

        <P>9. The NERC petition explained that the interpretation is consistent with the stated purpose of the Reliability Standard, which is to ensure reliability entities have clear decision-making authority and capabilities to take appropriate actions or direct the actions of others to return the transmission system to normal conditions during an emergency. NERC added that the interpretation clarifies the responsibilities of balancing authorities and transmission operators during a system emergency by referencing the<E T="03">NERC Glossary of Terms Used in Reliability Standards</E>as well as other relevant Reliability Standards.<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">Id.</E>at 6.</P>
        </FTNT>
        <P>10. On February 14, 2011, NERC made a supplemental filing in response to a Commission staff data request.<SU>11</SU>
          <FTREF/>With regard to whether Requirement R8 obligates a joint response in a system emergency, NERC explained that Requirement R8 does not use the word “joint” or otherwise infer joint responsibility during system emergencies. Rather, NERC responded that the balancing authority and transmission operator have separate responsibilities to restore real and reactive power balance during system emergencies. NERC also stated that the use of “and” between the two entities should not construe communication or coordination. NERC added that the Blackout Report<SU>12</SU>
          <FTREF/>correctly identifies communication and coordination issues as reliability issues and that communication and coordination are addressed in the Communications (COM) Reliability Standards.<SU>13</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>11</SU>Response of the North American Electric Reliability Corporation to Request for Additional Information Regarding Interpretation to Reliability Standard TOP-001-1, Requirement R8 (NERC Response).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">Final Report on the August 14, 2003 Blackout in the United States and Canada</E>(Blackout Report).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>NERC Response at 4-7.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Notice of Proposed Rulemaking</HD>
        <P>11. On April 21, 2011, the Commission issued a Notice of Proposed Rulemaking (NOPR) proposing to approve NERC's interpretation of Reliability Standard TOP-001-1, Requirement R8.<SU>14</SU>
          <FTREF/>In the NOPR, the Commission stated that it believed that the ERO has presented a reasonable interpretation consistent with the language of the Reliability Standard. In addition, the NOPR noted that a balancing authority and transmission operator each have coordination and communication functions that are necessary for maintaining real and reactive power balance.</P>
        <FTNT>
          <P>
            <SU>14</SU>
            <E T="03">Electric Reliability Organization Interpretation of Transmission Operations Reliability Standard,</E>Notice of Proposed Rulemaking, 76 FR 23222 (Apr. 26, 2011), FERC Stats. &amp; Regs. ¶ 32,674 (2011) (NOPR).</P>
        </FTNT>
        <P>12. In response to the NOPR, NERC filed comments supporting the Commission's proposed approval of the interpretation. No comments were filed opposing the Commission's proposal to approve NERC's interpretation.</P>
        <HD SOURCE="HD1">III. Commission Determination</HD>
        <P>13. The Commission adopts the NOPR proposal and approves the interpretation of TOP-001-1, Requirement R8. The Commission finds that NERC's interpretation is just, reasonable, not unduly discriminatory or preferential, and in the public interest.</P>
        <P>14. The interpretation supports the stated purpose of the Reliability Standard, i.e., ensuring that reliability entities have clear decision-making authority and capabilities to take appropriate actions or direct the actions of others to return the transmission system to normal conditions during an emergency.<SU>15</SU>
          <FTREF/>The interpretation also clarifies the responsibilities of a balancing authority and transmission operator during a system emergency. Further, the language is consistent with the language of the requirement. Accordingly, the Commission approves the ERO's interpretation of TOP-001-1, Requirement R8.</P>
        <FTNT>
          <P>
            <SU>15</SU>
            <E T="03">Id.</E>at 6.</P>
        </FTNT>
        <P>15. We agree, as discussed in the interpretation, that the balancing authority is responsible for restoring real power balance during a system emergency and the transmission operator is responsible for restoring reactive power balance during a system emergency. However, during a system emergency, communication and coordination between the transmission operator and balancing authority can be essential to restore real and reactive power balance. For example, during an emergency, the balancing authority may rely on the real power output of a generator to fulfill its responsibility, while the transmission operator may expect the same generator unit to reduce real power to generate greater reactive power output.<SU>16</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>16</SU>The Blackout Report described such a scenario, explaining that a generator unit tripped because the unit's protection system detected the VAR output, i.e., reactive power, exceeded the unit's capability. Blackout Report at 27. The Blackout Report also explained that no generator units were asked to reduce their real power output to produce more reactive power.<E T="03">Id.</E>at 47.</P>
        </FTNT>
        <P>16. NERC acknowledges the need for such communication and coordination.<SU>17</SU>
          <FTREF/>NERC maintains that this coordination and communication is required through two currently-effective Communication Reliability Standards: (1) COM-001-1.1—Telecommunications and (2) COM-002-2—Communication and Coordination.<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>17</SU>NERC Response at 6-7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>NERC Response at 6-7. NERC also identifies several ongoing Reliability Standards projects that are intended to strengthen the requirements pertaining to communication and coordination between entities.</P>
        </FTNT>
        <P>17. We agree with NERC that the currently effective COM Reliability Standards provide for such communication and coordination. For example, Reliability Standard COM-002-2, Requirement R1 provides that transmission operators, balancing authorities and generator operators must have communication links with one another and must be staffed to address a real-time emergency. Reliability Standard EOP-001-0, Requirements R3, R4.3, and R7 also contain provisions relevant to the need for communication and coordination in emergencies.<SU>19</SU>
          <FTREF/>These provisions require balancing authorities and transmission operators to develop plans to mitigate operating emergencies including coordination among adjacent transmission operators and balancing authorities.</P>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">See</E>NOPR, FERC Stats. &amp; Regs. ¶ 32,674 at P 14. On July 13, 2011, the Commission approved EOP-001-2 Reliability Standard, replacing EOP-001-0 effective July 1, 2013.<E T="03">Mandatory Reliability Standards for Interconnection Reliability Operating Limits; System Restoration Reliability Standards,</E>136 FERC ¶ 61,030 (2011). The applicable Requirements in EOP-001-2 relevant to the need for communication and coordination in emergencies are Requirements R2, R3.3, and R6.</P>
        </FTNT>
        <P>18. Accordingly, for the reasons discussed above, we approve NERC's proposed interpretation of TOP-001-1, Requirement R8.</P>
        <HD SOURCE="HD1">IV. Information Collection Statement</HD>
        <P>19. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting and recordkeeping requirements (collections of information) imposed by an agency.<SU>20</SU>
          <FTREF/>The information contained here is also<PRTPAGE P="58103"/>subject to review under section 3507(d) of the Paperwork Reduction Act of 1995.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>20</SU>5 CFR 1320.11.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>44 U.S.C. 3507(d).</P>
        </FTNT>
        <P>20. As stated above, the Commission approved, in Order No. 693, Reliability Standard TOP-001-1 that is the subject of the current rulemaking. This Final Rule approves the interpretation of the previously approved Reliability Standard, which was developed by NERC as the ERO. The interpretation, as clarified, relates to an existing Reliability Standard, and the Commission does not expect it to affect entities' current reporting burden.<SU>22</SU>
          <FTREF/>Accordingly, we will submit this Final Rule to OMB for informational purposes only.</P>
        <FTNT>
          <P>
            <SU>22</SU>
            <E T="03">See</E>Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1901-1907.</P>
        </FTNT>

        <P>21. 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, e-mail:<E T="03">DataClearance@ferc.gov,</E>Phone: (202) 502-8663, fax: (202) 273-0873].</P>
        <HD SOURCE="HD1">V. Environmental Analysis</HD>
        <P>22. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.<SU>23</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>24</SU>
          <FTREF/>The actions proposed herein fall within this categorical exclusion in the Commission's regulations.</P>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">Regulations Implementing the National Environmental Policy Act</E>of 1969, Order No. 486, 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs. Preambles 1986-1990 ¶ 30,783 (1987).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>24</SU>18 CFR 380.4(a)(2)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">VI. Regulatory Flexibility Act</HD>
        <P>23. The Regulatory Flexibility Act of 1980 (RFA)<SU>25</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 final 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>26</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>27</SU>
          <FTREF/>The RFA is not implicated by this Final Rule because the interpretations discussed herein will not have a significant economic impact on a substantial number of small entities.</P>
        <FTNT>
          <P>
            <SU>25</SU>5 U.S.C. 601-612.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>13 CFR 121.101.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>27</SU>13 CFR 121.201, Section 22, Utilities, &amp; n.1.</P>
        </FTNT>
        <P>24. The Commission approved Reliability Standard TOP-001-1 in 2007 in Order No. 693. The Final Rule in the immediate docket addresses an interpretation of Requirement R8 of previously-approved TOP-001-1. The interpretation clarifies current compliance obligations of balancing authorities and transmission operators and therefore, does not create an additional regulatory impact on small entities.</P>
        <HD SOURCE="HD1">VII. Document Availability</HD>

        <P>25. 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>26. 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>27. User assistance is available for eLibrary and the FERC's website during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or e-mail at<E T="03">ferconlinesupport@ferc.gov,</E>or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. E-mail the Public Reference Room at<E T="03">public.referenceroom@ferc.gov.</E>
        </P>
        <HD SOURCE="HD1">VIII. Effective Date and Congressional Notification</HD>
        <P>28. These regulations are effective November 21, 2011. 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>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24088 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID: DoD-2011-OS-0004]</DEPDOC>
        <CFR>32 CFR Part 311</CFR>
        <SUBJECT>Privacy Act of 1974; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Office of the Secretary of Defense is exempting those records contained in DMDC 14 DoD, entitled “Defense Clearance and Investigations Index (DCII)”, pertaining to investigatory material compiled for law enforcement purposes to enable OSD components to conduct certain investigations and relay law enforcement information without compromise of the information, protect investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence. The exemption will allow DoD to provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources' identity would be held in confidence. Further,<PRTPAGE P="58104"/>requiring OSD to grant access to records and agency rules for access and amendment of records would unfairly impede the investigation of allegations of unlawful activities. To require OSD to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.</P>
          <P>This direct final rule makes nonsubstantive changes to the Office of the Secretary Privacy Program rules. These changes will allow the Department to add an exemption rule to the Office of the Secretary of Defense Privacy Program rules that will exempt applicable Department records and/or material from certain portions of the Privacy Act. This change will allow the Department to move part of the Department's personnel security program records from the Defense Security Service Privacy Program to the Office of the Secretary of Defense Privacy Program. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the applicable records and/or material when the purposes underlying the exemption(s) are valid and necessary.</P>
          <P>This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The rule will be effective on November 29, 2011 unless comments are received that would result in a contrary determination. Comments will be accepted on or before November 21, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 1160 Defense Pentagon, Washington, DC 20301-1160.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Cindy Allard at (703) 588-6830.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This direct final rule is consistent with the rule currently published at 32 CFR part 321.13(h) and another rule is being published to remove and reserve 321.13(h).</P>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will withdraw this direct final rule by publishing a notice in the<E T="04">Federal Register</E>. A significant adverse comment is one that explains: (1) Why the direct final rule is inappropriate, including challenges to the rule's underlying premise or approach; or (2) why the direct final rule will be ineffective or unacceptable without a change. In determining whether a comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or Tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense does not have significant economic impact on a substantial number of small entities because it is concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 95-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that this Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and Tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do 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>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 311</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 311 is amended as follows:</P>
        <REGTEXT PART="311" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 311—OFFICE OF THE SECRETARY OF DEFENSE AND JOINT STAFF PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 311 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 522a).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="311" TITLE="32">
          <AMDPAR>2. Section 311.8 is amended by adding paragraph (c)(20) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 311.8</SECTNO>
            <SUBJECT>Procedures for exemptions.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(20) System identifier and name: DMDC 14 DoD, Defense Clearance and Investigations Index.</P>
            <P>(i)<E T="03">Exemptions:</E>Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled<PRTPAGE P="58105"/>by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source. Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2) may be exempt from the following subjections of 5 U.S.C. 552a(c)(3); (d); (e)(1); (e)(4)(G), (H), and (I) and (f).</P>
            <P>(ii)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2).</P>
            <P>(iii)<E T="03">Reasons:</E>(A) From subsection (c)(3) because it will enable OSD components to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
            <P>(B) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
            <P>(C) From subsections (d) and (f) because requiring OSD to grant access to records and agency rules for access and amendment of records would unfairly impede the investigation of allegations of unlawful activities. To require OSD to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: August 24, 2011.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23758 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket No. USCG-2011-0857]</DEPDOC>
        <RIN>RIN 1625-AA11</RIN>
        <SUBJECT>Regulated Navigation Area; Saugus River, Lynn, MA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a Regulated Navigation Area (RNA) on the navigable waters of the Saugus River in Lynn, Massachusetts. This temporary rule allows the Coast Guard to suspend all vessel traffic within the regulated area to allow for stabilization operations that could pose a safety hazard to vessels operating in the area. This temporary rule is necessary to enhance vessel safety, marine environmental protection, and provide for the safety of life on the navigable waters during the removal of a damaged section of the Energy Systems Pipeline Bridge at Mile 2.3 of the Saugus River.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective in the CFR on September 20, 2011 until 5 p.m. on November 9, 2011. This rule is effective with actual notice for purposes of enforcement from 8 a.m. on September 12, 2011 until 5 p.m. on November 9, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2011-0857 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2011-0857 in the “Keyword” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or e-mail Mr. Mark Cutter, U.S. Coast Guard Sector Boston Waterways Management Division, Coast Guard; telephone 617-223-4000, e-mail<E T="03">Mark.E.Cutter@uscg.mil,</E>or Lieutenant Junior Grade Isaac Slavitt, Coast Guard First District Waterways Management Branch, telephone 617-223-8385, e-mail<E T="03">Isaac.M.Slavitt@uscg.mil.</E>If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>
        <P>The Coast Guard is issuing this temporary rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedures Act (APA), 5 U.S.C. 553(b). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule; notice and comment is impracticable because immediate action is necessary to ensure the safety of the public in the vicinity of construction operations being conducted in the Saugus River.</P>
        <P>Serious damage to this pipeline bridge was caused during Tropical Storm Irene, which passed through Boston on 28 August, 2011. Currently, the pipeline is leaning over precariously and is in danger of collapsing. Two phases of work are needed for this pipeline: stabilization (which may include removal of the damaged segment), and then full removal at a later date. This rule addresses only emergency stabilization efforts. A separate rule will be promulgated with normal notice and comment periods for the longer term full repair project.</P>

        <P>On September 1, 2011, General Electric, the pipeline operators, advised that the Energy Systems Pipeline bridge demolition project would require periodic closures of the Saugus River at mile 2.3 to remove the damaged piping support structure. The hazard that the damaged portion of the Energy Systems Pipeline bridge poses to the navigational channel necessitates that all mariners comply with this RNA. Immediate action is needed to control vessels operating in the restricted waterway in order to facilitate repairs and to protect the maritime public from the hazards associated with the stabilization of this damaged structure. Publishing a NPRM and waiting 30 days for comment would be contrary to the public interest since immediate action is needed to restrict<PRTPAGE P="58106"/>vessel traffic to effect repairs and to protect the maritime public from the hazards associated with removal of the damaged section of the structure, including falling debris and the use of heavy machinery.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective fewer than 30 days after publication in the<E T="04">Federal Register</E>. Any delay would be both impracticable and contrary to the public interest. Immediate action is necessary for the reasons discussed above, supporting good cause under 5 U.S.C. 553(b)(B).</P>
        <HD SOURCE="HD1">Basis and Purpose</HD>
        <P>Under the Ports and Waterways Safety Act, the Coast Guard has the authority to establish RNAs in defined water areas that are determined to have hazardous conditions and in which vessel traffic can be regulated in the interest of safety. See 33 U.S.C. 1231 and Department of Homeland Security Delegation No. 0170.1.</P>
        <P>The purpose of this temporary rule is to facilitate the removal of the damaged piping support structure for the Energy Systems Pipeline Bridge located at approximately mile 2.3 of the Saugus River in Lynn, MA. Establishing this temporary rule will allow the necessary stabilization work to be completed and will protect the maritime public from the hazards associated with the demolition of this damaged structure. This structure is in danger of collapse and its stabilization allows for the future safe transit of vessels in the area.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>This action is intended to prohibit vessel traffic on a portion of the Saugus River, when necessary for the safety of navigation, while work is done on the Energy Systems Pipeline Bridge on the Saugus River in Lynn, MA. The regulated area encompasses all waters within 100 yards of either side of the Energy Systems Pipeline Bridge. The Coast Guard may close the area described in this rule to all vessel traffic during any circumstance, planned or unforeseen, that poses a threat to waterway users operating in the area. Complete waterway closures will be made with as much advance notice as possible.</P>
        <P>The project consists of stabilization, cutting and removal of damaged abandoned pipeline and associated steel support structure. Demolition operations will temporarily block the navigable channel due to positioning of a barged-based lifting crane, a deck barge, and an associated towing vessel.</P>
        <P>Entry into this RNA during a closure is prohibited unless authorized by the Sector Boston Captain of the Port (COTP). In the event of an emergency, all construction equipment shall be removed from the channel to allow for emergency vessels to pass. Any violation of this rule is punishable by, among others, civil and criminal penalties, in rem liability against the offending vessel, and the initiation of suspension or revocation proceedings against Coast Guard-issued merchant-mariner credentials.</P>
        <P>The Captain of the Port (COTP) Boston will cause notice of enforcement, suspension of enforcement, or closure of the waterway to be made by all appropriate means for the widest distribution among the affected segments of the public. Such means of notification may include, but are not limited to, Broadcast Notice to Mariners and Local Notice to Mariners.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this temporary final rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD2">Executive Order 12866 and Executive Order 13563</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order.</P>

        <P>The economic impact of this rule will be severely limited for the following reasons: (1) The actual waterway restriction imposed by this RNA is expected to last no longer than 12 hours at a time; (2) demolition work that restricts the navigational channel will be scheduled when there is limited demand for this navigational channel; and (3) advance notification will be made to the maritime community via Local Notice to Mariners, Broadcast Notice to Mariners, and on the Internet at<E T="03">http://homeport.uscg.mil/boston.</E>
        </P>
        <HD SOURCE="HD2">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: the owners or operators of vessels intending to transit in a portion of the Saugus River during periods of construction until the Energy Systems Pipeline bridge has been structurally stabilized. Several small marinas up-river from the damaged pipeline may also be affected.</P>
        <P>This rule will not have a significant economic impact on a substantial number of small entities for the following reasons: although the regulated navigation area will apply to the entire width of the Saugus River navigational channel, restriction of vessel traffic will be limited to not more than 12 hours at a time and response to traffic demand will be coordinated in advance by the Captain of the Port Boston in consultation with the harbormaster of Lynn, MA. Before the effective period, we will issue maritime advisories widely available to users of the waterway. Additionally, because of the dangerous and unstable nature of the damaged pipeline, many vessel operators may have independently reached the conclusion that it is too dangerous to pass underneath. Therefore, the inherent danger of the damaged pipeline is probably already preventing vessel operators from passing through.</P>

        <P>If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see<E T="02">ADDRESSES</E>) explaining why you think it qualifies and how and to what degree this rule would economically affect it.</P>
        <HD SOURCE="HD2">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>

        <P>Small businesses may send comments on the actions of federal employees who enforce, or otherwise determine compliance with, federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The<PRTPAGE P="58107"/>Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD2">Collection of Information</HD>
        <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD2">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
        <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD2">Technical Standards</HD>

        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (<E T="03">e.g.,</E>specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(g), of the Instruction. This rule involves the establishment of a RNA. An environmental analysis checklist and a categorical exclusion determination will be available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1226, 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T01-0857 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T01-0857</SECTNO>
            <SUBJECT>Regulated Navigation Area; Saugus River, Lynn MA.</SUBJECT>
            <P>(a)<E T="03">Regulated Area.</E>The following area is a regulated navigation area: all waters within 100 yards of either side of the Energy Systems Pipeline Bridge at approximately mile 2.3 of the Saugus River in position 42°26′56″ N, 070° 58′31″ W, in Lynn, MA. All geographic coordinates are North American Datum of 1983 (NAD 83).</P>
            <P>(b)<E T="03">Regulations.</E>
            </P>
            <P>(1) The general regulations contained in 33 CFR 165.13 apply.</P>
            <P>(2) No vessel may enter or transit through the regulated area during enforcement periods without the express permission of the Captain of the Port (COTP) Boston.</P>
            <P>(3) Vessels transiting through the RNA with COTP permission are required to do so at reduced speed so as to produce no wake. Vessels transiting through the RNA with COTP permission must still remain at least 150 feet away from all demolition equipment.</P>
            <P>(c)<E T="03">Effective Period.</E>This rule is effective from 8 a.m. on September 12, 2011 until 5 p.m. on November 9, 2011.</P>
            <P>(d)<E T="03">Enforcement Period.</E>This rule will be enforced when necessary for construction operations. The COTP Boston will cause notice of enforcement periods to be made by reasonable means, which may include but are not limited to a Broadcast Notice to Mariners.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <PRTPAGE P="58108"/>
          <DATED>Dated: September 9, 2011.</DATED>
          <NAME>D. A. Neptun,</NAME>
          <TITLE>Rear Admiral, U.S. Coast Guard, Commander, First Coast Guard District.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24051 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket No. USCG-2011-0847]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; Ryder Cup Captain's Duel Golf Shot, Chicago River, Chicago, IL</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary safety zone on the Chicago River near Chicago, Illinois. This zone is intended to restrict vessels from a portion of the Chicago River during a golfing event that will involve hitting golf balls from land onto a stationary barge in the river. This temporary safety zone is necessary to protect the public and their vessels from the hazards associated with golf balls being hit from land onto a stationary barge in the river.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This regulation is effective from 4 p.m. until 5 p.m. on September 26, 2011.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Comments and material received from the public, as well as documents mentioned in this preamble as being available in the docket, are part of docket USCG-2011-0847 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2011-0847 in the “Keyword” box, and then clicking “Search.” This material is also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, contact or e-mail BM1 Adam Kraft, U.S. Coast Guard Sector Lake Michigan, at (414) 747-7148 or<E T="03">Adam.D.Kraft@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone (202) 366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Regulatory Information</HD>
        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when an agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because notice of this golfing event was not received in sufficient time for the Coast Guard to solicit public comments before the start of the event. Thus, waiting for a notice and comment period to run would be impracticable and contrary to the public interest in that it would prevent the Coast Guard from protecting the public and vessels on navigable waters from the hazards associated with golf balls being hit from land onto a stationary barge in the river.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. For the same reasons discussed in the preceding paragraph, a 30-day notice period would also be impracticable and contrary to the public interest.</P>
        <HD SOURCE="HD1">Background and Purpose</HD>
        <P>The Ryder Cup Captain's Duel Golf Shot event takes place on the Chicago River near Chicago, Illinois from 4 p.m. to 5 p.m. on September 26, 2011. The Captain of the Port, Sector Lake Michigan has determined that this event may present significant hazards to public safety and property due to the fact that six golf balls will be hit from the 16th floor of the Trump Tower, onto a stationary barge located in the middle of the Chicago River.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>Because of the aforesaid hazards, the Captain of the Port, Sector Lake Michigan has determined that a temporary safety zone is necessary to ensure the safety of spectators and vessels during the golfing event. The safety zone will encompass all waters of the Chicago River, near Chicago, Illinois, between the North Columbus Drive Bascule Bridge, located at approximate position 41°53′19″ N, 087°37′13″ W and the Michigan Avenue bridge, located at approximate position 41°53′21″ N, 087°37′28″ W. (NAD 83).</P>
        <P>All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port, Sector Lake Michigan, or his or her designated representative. Entry into, transiting, or anchoring within the safety zone is prohibited unless authorized by the Captain of the Port, Sector Lake Michigan, or his or her designated representative. The Captain of the Port, Sector Lake Michigan, or his or her designated representative may be contacted via VHF Channel 16.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this temporary rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD2">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under that those Orders.</P>
        <P>We conclude that this rule is not a significant regulatory action because we anticipate that it will have minimal impact on the economy, will not interfere with other agencies, will not adversely alter the budget of any grant or loan recipients, and will not raise any novel legal or policy issues.</P>
        <HD SOURCE="HD2">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>

        <P>This rule will affect the following entities, some of which might be small entities: the owners or operators of vessels intending to transit or anchor in a portion of the Chicago River, Chicago, IL between 4 p.m. and 5 p.m. on September 26, 2011.<PRTPAGE P="58109"/>
        </P>
        <P>This safety zone will not have a significant economic impact on a substantial number of small entities for the following reasons: the safety zone will only be in effect for one hour on a single day and vessels will be allowed to pass through the safety zone when no conditions exist. In the event that this temporary safety zone affects shipping, commercial vessels may request permission from the Captain of The Port, Sector Lake Michigan, to transit through the safety zone. The Coast Guard will give notice to the public via a Broadcast to Mariners that the regulation is in effect.</P>
        <HD SOURCE="HD2">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD2">Collection of Information</HD>
        <P>This temporary rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD2">Federalism</HD>
        <P>A temporary rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
        <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this temporary rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">Taking of Private Property</HD>
        <P>This rule will not affect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD2">Technical Standards</HD>

        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (<E T="03">e.g.,</E>specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">Environment</HD>
        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(g), of the Instruction because this rule involves the establishment of a safety zone.</P>

        <P>A final environmental analysis checklist and categorical exclusion determination are available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="165" TITLE="33">
          <PRTPAGE P="58110"/>
          <AMDPAR>2. Add § 165.T09-0847 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T09-0847</SECTNO>
            <SUBJECT>Safety Zone; Ryder Cup Captain's Duel Golf Shot, Chicago River, Chicago, Illinois.</SUBJECT>
            <P>(a)<E T="03">Location.</E>The safety zone will encompass all waters of the Chicago River, near Chicago, Illinois, between the North Columbus Drive Bascule Bridge, located at approximate position 41°53′19″ N, 087°37′13″ W and the Michigan Avenue bridge, located at approximate position 41°53′21″ N, 087°37′28″ W. (NAD 83).</P>
            <P>(b)<E T="03">Effective and enforcement period.</E>This regulation is effective and will be enforced from 4 p.m. until 5 p.m. on September 26, 2011. The Captain of the Port, Sector Lake Michigan, or his or her designated representative may terminate the enforcement of this safety zone at any time before the 5 p.m. on September 26, 2011.</P>
            <P>(c)<E T="03">Regulations.</E>(1) In accordance with the general regulations in § 165.23 of this part, entry into, transiting, or anchoring within this safety zone is prohibited unless authorized by the Captain of the Port, Sector Lake Michigan, or his or her designated representative.</P>
            <P>(2) This safety zone is closed to all vessel traffic, except as may be permitted by the Captain of the Port, Sector Lake Michigan, or his or her designated representative.</P>
            <P>(3) The “designated representative” of the Captain of the Port, Sector Lake Michigan, is any Coast Guard commissioned, warrant or petty officer who has been designated by the Captain of the Port, Sector Lake Michigan, to act on his or her behalf. The designated representative of the Captain of the Port, Sector Lake Michigan, will be on the Trump Tower with event participants and will have constant radio communication with the Safety and Patrol vessels which will be provided by the Chicago Police Marine Unit.</P>
            <P>(4) Vessel operators desiring to enter or operate within the safety zone shall contact the Captain of the Port, Sector Lake Michigan, or his or her designated representative to obtain permission to do so. The Captain of the Port, Sector Lake Michigan, or his or her designated representative may be contacted via VHF Channel 16. Vessel operators given permission to enter or operate in the safety zone must comply with all directions given to them by the Captain of the Port, Sector Lake Michigan, or his or her designated representative.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: September 8, 2011.</DATED>
          <NAME>M. W. Sibley,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Sector Lake Michigan.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24142 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket No. USCG-2011-0721]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; Giannangeli Wedding Fireworks, Lake St. Clair, Harrison Township, MI</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary safety zone on Lake St. Clair, Harrison Township, MI. This zone is intended to restrict vessels from a portion of Lake St. Clair during the Giannangeli Wedding Fireworks.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective and will be enforced from 10 p.m. through 10:30 p.m. on September 24, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2011-0721 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2011-0721 in the “Keyword” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or e-mail Lt. Adrian Palomeque, Prevention Department, Sector Detroit, Coast Guard; telephone (313) 568-9508, e-mail<E T="03">Adrian.F.Palomeque@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>
        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule. Notice of this fireworks display was not received in sufficient time for the Coast Guard to solicit public comments before the start of the event. Thus, waiting for a notice and comment period to run would be impracticable and contrary to the public interest because it would inhibit the Coast Guard's ability to protect the public from the hazards associated with maritime fireworks displays.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. For the same reasons discussed in the preceding paragraph, waiting for a 30 day notice period to run would be impracticable and contrary to the public interest.</P>
        <HD SOURCE="HD1">Background and Purpose</HD>
        <P>On September 24, 2011, a private party is holding a land based wedding that will include fireworks launched from a point on Lake St. Clair. The fireworks display will occur between 10 p.m. and 10:30 p.m., September 24, 2011. The Captain of the Port Detroit has determined that fireworks displays launched on or in the vicinity of navigable waters pose hazards to the boating public. Such hazards include obstructions to the waterway that may cause marine casualties, explosive danger of fireworks, and debris falling into the water that may cause death or serious bodily harm and property damage.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>Because of the aforementioned hazards, the Captain of the Port Detroit has determined that this temporary safety zone is necessary to ensure the safety of spectators and vessels during the setup, loading, and launching of the Giannangeli Wedding Fireworks Display. The safety zone will encompass all waters on Lake St. Clair within a 420 foot radius of the fireworks barge launch site located off the shore of Harrison Township, MI at position 42°36′31″ N, 082°48′2″ W from 10 p.m. until 10:30 p.m. on September 24, 2011. All geographic coordinates are North American Datum of 1983 (NAD 83).</P>

        <P>All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port or the designated on<PRTPAGE P="58111"/>scene patrol personnel. Entry into, transiting, or anchoring within the safety zone is prohibited unless authorized by the Captain of the Port Detroit or his designated on scene representative. The Captain of the Port or his designated on scene representative may be contacted via VHF Channel 16.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD2">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under that those Orders.</P>
        <P>We conclude that this rule is not a significant regulatory action because we anticipate that it will have minimal impact on the economy, will not interfere with other agencies, will not adversely alter the budget of any grant or loan recipients, and will not raise any novel legal or policy issues. The safety zone around the launch platform will be relatively small and exist for only a minimal time. Thus, restrictions on vessel movement within any particular area of Lake St. Clair are expected to be minimal. Under certain conditions, moreover, vessels may still transit through the safety zone when permitted by the Captain of the Port.</P>
        <HD SOURCE="HD2">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <P>This rule will affect the following entities, some of which may be small entities: The owners and operators of vessels intending to transit or anchor in this portion of Lake St. Clair between 10 p.m. through 10:30 p.m. on September 24, 2011.</P>
        <P>This safety zone will not have a significant economic impact on a substantial number of small entities because vessels can easily transit around the zone. The Coast Guard will give notice to the public via a Broadcast Notice to Mariners that the regulation is in effect.</P>
        <HD SOURCE="HD2">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD2">Collection of Information</HD>
        <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD2">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
        <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD2">Technical Standards</HD>

        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of<PRTPAGE P="58112"/>Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (<E T="03">e.g.,</E>specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(g) of the Instruction because it involves the establishment of a temporary safety zone. An environmental analysis checklist and a categorical exclusion determination will be available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine Safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T09-0721 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T09-0721</SECTNO>
            <SUBJECT>Safety zone; Giannangeli Wedding Fireworks, Lake St. Clair, Harrison Township, MI.</SUBJECT>
            <P>(a)<E T="03">Location.</E>The safety zone will encompass all U. S. navigable waters on Lake St. Clair within a 420 foot radius of Harrison Township, MI at position 42°36′31″ N, 082°48′2″ W. All geographic coordinates are North American Datum of 1983 (NAD 83).</P>
            <P>(b)<E T="03">Effective and Enforcement Period.</E>This rule is effective and will be enforced from 10 p.m. through 10:30 p.m. on September 24, 2011.</P>
            <P>(c)<E T="03">Regulations.</E>
            </P>
            <P>(1) In accordance with the general regulations in Section 165.23 of this part, entry into, transiting, or anchoring within this safety zone is prohibited unless authorized by the Captain of the Port Detroit, or his designated on-scene representative.</P>
            <P>(2) This safety zone is closed to all vessel traffic, except as may be permitted by the Captain of the Port Detroit or his designated on-scene representative.</P>
            <P>(3) The “on-scene representative” of the Captain of the Port is any Coast Guard commissioned, warrant, or petty officer who has been designated by the Captain of the Port to act on his behalf. The on-scene representative of the Captain of the Port will be aboard either a Coast Guard or Coast Guard Auxiliary vessel. The Captain of the Port or his designated on scene representative may be contacted via VHF Channel 16.</P>
            <P>(4) Vessel operators desiring to enter or operate within the safety zone shall contact the Captain of the Port Detroit or his on-scene representative to obtain permission to do so.</P>
            <P>(5) Vessel operators given permission to enter or operate in the safety zone must comply with all directions given to them by the Captain of the Port or his on-scene representative.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: September 6, 2011.</DATED>
          <NAME>E.J. Marohn,</NAME>
          <TITLE>Commander, U.S. Coast Guard, Acting Captain of the Port Detroit.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24143 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket No. USCG-2010-0939 ]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zone; M/V DAVY CROCKETT, Columbia River</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The U.S. Coast Guard is extending the enforcement period of a safety zone established on the waters of the Columbia River surrounding the remaining cofferdam at the M/V DAVY CROCKETT removal sight at approximate river mile 117. The original safety zone was established on January 28, 2011. The safety zone is necessary to help ensure the safety of the response workers and maritime public from the hazards associated with the ongoing worksite cleanup operations. All persons and vessels are prohibited from entering or remaining in the safety zone unless authorized by the Captain of the Port, Columbia River or his designated representative.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective in the CFR from September 20, 2011 through October 31, 2011. This rule is effective with actual notice for purposes of enforcement on September 1, 2011. This rule will remain in effect through October 31, 2011.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2010-0939 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2010-0939 in the “Keyword” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or e-mail BM1 Silvestre Suga, Waterways Management Division, Marine Safety Unit Portland, Coast Guard; telephone 503-240-9319, e-mail<E T="03">Silvestre.G.Suga@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>

        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because to do so would be contrary to public interest. The safety zone is immediately<PRTPAGE P="58113"/>necessary to help ensure the safety of the response workers and the maritime public due to the ongoing worksite cleanup operations.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>because the safety zone is immediately necessary to help ensure the safety of the response workers and the maritime public due to the ongoing worksite cleanup operations.</P>
        <HD SOURCE="HD1">Background and Purpose</HD>
        <P>The remaining cofferdam at the M/V DAVY CROCKETT removal sight is located on the Washington State side of the Columbia River at approximately river mile 117. The Coast Guard, other state and federal agencies, and federal contractors are continuing a worksite cleanup following the removal of M/V DAVY CROCKETT. The cleanup operations require a minimal wake in the vicinity of the cofferdam to help ensure the safety of response workers. Only authorized persons and/or vessels can be safely allowed in the worksite cleanup area.</P>
        <P>A 300 ft safety zone is necessary to keep vessels clear of the ongoing worksite cleanup in and around the cofferdam. The previous 300 ft safety zone will expire on August 31, 2011.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>The Coast Guard is extending the enforcement of the safety zone created by this rule until October 31, 2011. The safety zone will cover all waters of the Columbia River encompassed within the following four points: Point one at 45°34′59.74″ N/122°28′35.00″ W on the Washington bank of the Columbia River then proceeding into the river to point two at 45°34′51.42″ N/122°28′35.47″ W, then proceeding upriver to the third point at 45°34′51.02″ N/122°28′07.32″ W, then proceeding to the shoreline to the fourth point on the Washington Bank at 45°34′56.06″ N/122°28′07.36″ W, then back along the shoreline to point one. Geographically this encompasses all the waters within an area starting at approximately 300 ft upriver from the cofferdam cleanup site extending to 300 ft abreast of the cofferdam cleanup site and then ending 300 ft down river of the cofferdam cleanup site.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under that those Orders.</P>
        <P>The Coast Guard has made this determination based on the fact that the safety zones created by this rule will not significantly affect the maritime public because the areas covered are limited in size and/or have little commercial or recreational activity. In addition, vessels may enter the safety zones with the permission of the Captain of the Port, Columbia River or his designated representative.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule may affect the following entities some of which may be small entities: The owners and operators of vessels intending to operate in the areas covered by the safety zones created in this rule. The safety zones will not have a significant economic impact on a substantial number of small entities because the areas covered are limited in size. In addition, vessels may enter the safety zones with the permission of the Captain of the Port, Columbia River or his designated representative.</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminates ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>

        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not<PRTPAGE P="58114"/>an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>

        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (<E T="03">e.g.,</E>specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(g), of the Instruction. This rule involves the creation of safety zones. An environmental analysis checklist and a categorical exclusion determination will be available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T13-175 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T13-175</SECTNO>
            <SUBJECT>Safety Zone; M/V DAVY CROCKETT Cleanup site, Columbia River.</SUBJECT>
            <P>(a)<E T="03">Location:</E>The following area is a safety zone:</P>
            <P>(1) All waters of the Columbia River encompassed within the following four points: Point one at 45°34′59.74″ N/122°28′35.00″ W on the Washington bank of the Columbia River then proceeding into the river to point two at 45°34′51.42″ N/122°28′35.47″ W, then proceeding upriver to the third point at 45°34′51.02″ N/122°28′07.32″ W, then proceeding to the shoreline to the fourth point on the Washington Bank at 45°34′56.06″ N/122°28′07.36″ W, then back along the shoreline to point one. Geographically this encompasses all the waters within an area starting at approximately 300 ft upriver from the cofferdam cleanup site extending to 300 ft abreast of the cofferdam cleanup site and then ending 300 ft down river of the cofferdam cleanup site.</P>
            <P>(2) [Reserved]</P>
            <P>(b)<E T="03">Regulations.</E>In accordance with the general regulations in 33 CFR Part 165, Subpart C, no person may enter or remain in the safety zone created in this section or bring, cause to be brought, or allow to remain in the safety zone created in this section any vehicle, vessel, or object unless authorized by the Captain of the Port, Columbia River or his designated representative.</P>
            <P>(c)<E T="03">Enforcement Period.</E>The safety zone created in this section will be in effect from September 1, 2011 through October 31, 2011 unless cancelled sooner by the Captain of the Port, Columbia River.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: August 30, 2011.</DATED>
          <NAME>B.C. Jones,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Columbia River.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24146 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R03-OAR-2011-0288; FRL-9468-4]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Pennsylvania; Control of Particulate Matter Emissions From the Operation of Outdoor Wood-Fired Boilers</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is approving a State Implementation Plan (SIP) revision submitted by the Commonwealth of Pennsylvania. This SIP revision pertains to the control of particulate matter emissions from the operation of outdoor wood-fired boilers (OWBs). EPA is approving this revision to reduce particular matter emissions from the operation of outdoor wood-fired boilers in accordance with the requirements of the Clean Air Act (CAA).</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This final rule is effective on October 20, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID Number EPA-R03-OAR-2011-0288. All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>Web site. Although listed in the electronic docket, some information is not publicly available,<E T="03">i.e.,</E>confidential business information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically through<E T="03">http://www.regulations.gov</E>or in hard copy for public inspection during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania<PRTPAGE P="58115"/>19103. Copies of the State submittal are available at the Pennsylvania Department of Environmental Protection, Bureau of Air Quality Control, P.O. Box 8468, 400 Market Street, Harrisburg, Pennsylvania 17105.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Rose Quinto, (215) 814-2182, or by e-mail at<E T="03">quinto.rose@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On July 15, 2011 (76 FR 41742), EPA published a notice of proposed rulemaking (NPR) for the Commonwealth of Pennsylvania. The NPR proposed approval for the control of particulate matter emissions from the operation of OWBs. The formal SIP revision was submitted by the Pennsylvania Department of the Environmental Protection (PADEP) on October 20, 2010. No public comments were received on the NPR.</P>
        <HD SOURCE="HD1">II. Summary of SIP Revision</HD>
        <P>The SIP revision adds definitions and terms to Title 25 of the Pennsylvania Code (25 Pa. Code) Chapter 121.1, relating to definitions, used in the substantive provision of this SIP revision. In addition, the SIP revision adds a new regulation to 25 Pa. Code Chapter 123 (Standards for Contaminants) Particulate Matter Emissions, Section 123.14 (Outdoor Wood-Fired Boilers). The emissions standard established in this SIP revision is the Phase 2 emissions standard described in the EPA voluntary OWB program. The SIP revision is also based on the Northeast States for Coordinated Air Use Management (NESCAUM) model rule.</P>
        <P>The new regulation (Section 123.14) applies to the following: (1) To a person, manufacturer, supplier or distributor who sells, offers for sale, leases or distributes an outdoor wood-fired boiler for use; (2) a person who installs an outdoor wood-fired boiler; and (3) a person who purchases, receives, leases, owns, uses or operate an outdoor wood-fired boiler. The new regulation consists of the following: (1) Exemptions for a non-Phase 2 OWB; (2) Phase 2 OWB provisions; (3) setback requirements for new Phase 2 OWBs; (4) stack height requirements for new Phase 2 OWBs; (5) allowed fuels; (6) prohibited fuels; and (7) applicable laws and regulatory requirements. Other specific requirements for the control of particulate matter emissions from the operation of OWBs and the rationale for EPA's proposed action are explained in the NPR and will not be restated here.</P>
        <HD SOURCE="HD1">III. Final Action</HD>
        <P>EPA is approving 25 Pa. Code Chapter 121.1, relating to definitions used in the substantive provision of this SIP revision and the new regulation pertaining to 25 Pa. Code Chapter 123 (Standards for Contaminants) Particulate Matter Emissions, Section 123.14 (Outdoor Wood-Fired Boilers) as revisions to the Pennsylvania SIP.</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
        <HD SOURCE="HD2">A. General Requirements</HD>
        <P>Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the CAA and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by State law. For that reason, this action:</P>
        <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
        <P>• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have Tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on Tribal governments or preempt Tribal law.</P>
        <HD SOURCE="HD2">B. Submission to Congress and the Comptroller General</HD>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action 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>. A major rule cannot take effect until 60 days after it is published 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>
        <HD SOURCE="HD2">C. Petitions for Judicial Review</HD>
        <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by November 21, 2011. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action, pertaining to Pennsylvania's control of particulate matter emissions from the operation of outdoor wood-fired boilers, may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Particulate matter, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: August 31, 2011.</DATED>
          <NAME>W.C. Early,</NAME>
          <TITLE>Acting, Regional Administrator, Region III.</TITLE>
        </SIG>
        <P>40 CFR part 52 is amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <PRTPAGE P="58116"/>
            <HD SOURCE="HED">PART 52—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart NN—Pennsylvania</HD>
          </SUBPART>
          <AMDPAR>2. In §52.2020, the table in paragraph (c)(1) is amended by:</AMDPAR>
          <AMDPAR>a. Revising entry for Section 121.1.</AMDPAR>
          <AMDPAR>b. Adding entry for Section 123.14 after the existing entry for Section 123.13(a) through (c).</AMDPAR>
          <P>The amendments read as follows:</P>
          <SECTION>
            <SECTNO>§52.2020</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(1) * * *</P>
            <GPOTABLE CDEF="s50,r50,xs60,r100,r100" COLS="5" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">State citation</CHED>
                <CHED H="1">Title/subject</CHED>
                <CHED H="1">State<LI>effective date</LI>
                </CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Additional<LI>explanation/</LI>
                  <LI>§ 52.2063 citation</LI>
                </CHED>
              </BOXHD>
              <ROW EXPSTB="04">
                <ENT I="21">
                  <E T="02">Title 25—Environmental Protection</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="04">
                <ENT I="21">
                  <E T="02">Article III—Air Resources</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="04" RUL="s">
                <ENT I="21">
                  <E T="02">Chapter 121General Provisions</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="01">Section 121.1</ENT>
                <ENT>Definitions</ENT>
                <ENT>12/18/10</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
                <ENT>Added new definitions and terms. The State effective date is 10/2/10.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW EXPSTB="04" RUL="s">
                <ENT I="21">
                  <E T="02">Chapter 123—Standard for Contaminants</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW EXPSTB="04" RUL="s">
                <ENT I="21">
                  <E T="02">Particulate Matter Emissions</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*********</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Section 123.14</ENT>
                <ENT>Outdoor wood-fired boilers</ENT>
                <ENT>10/2/10</ENT>
                <ENT>9/20/11 [<E T="03">Insert page number where the document begins</E>]</ENT>
                <ENT>New section.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24099 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R03-OAR-2010-0475; FRL- 9466-6]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans;District of Columbia, Maryland, and Virginia; 2002 Base Year Emission Inventory, Reasonable Further Progress Plan, Contingency Measures, Reasonably Available Control Measures, and Transportation Conformity Budgets for the Washington, DC 1997 8-Hour Moderate Ozone Nonattainment Area</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is approving State Implementation Plan (SIP) revisions submitted by the District of Columbia, the State of Maryland, and the Commonwealth of Virginia (the States). These revisions pertain to the 2002 base year emissions inventory, the reasonable further progress (RFP) plan, RFP contingency measure, and reasonably available control measure (RACM) requirements of the Clean Air Act (CAA) for the Washington, DC-MD-VA moderate 1997 8-hour ozone nonattainment area (the Washington Area). EPA is also approving the 2008 transportation conformity motor vehicle emissions budgets (MVEBs) associated with this revision. EPA is approving the SIP revisions because they satisfy the emission inventory, RFP, RACM, RFP contingency measures, and transportation conformity requirements for areas classified as moderate nonattainment for the 1997 8-hour ozone national ambient air quality standard (NAAQS) and demonstrate further progress in reducing ozone precursors. This action is being taken under the CAA.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This final rule is effective on October 20, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID Number EPA-R03-OAR-2010-0475. All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>Web site. Although listed in the electronic docket, some information is not publicly available,<E T="03">i.e.,</E>confidential business information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically through<E T="03">http://www.regulations.gov</E>or in hard copy for public inspection during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. Copies of the State submittal are available at the District of Columbia. Department of the Environment, Air Quality Division, 1200 1st Street, NE., 5th floor, Washington, DC 20002; the Maryland Department of the Environment, 1800 Washington Boulevard, Suite 705, Baltimore, Maryland 21230; and the Virginia Department of Environmental Quality, 629 East Main Street, Richmond, Virginia 23219.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Maria A. Pino, (215) 814-2181, or by e-mail at<E T="03">pino.maria@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>

        <P>On June 30, 2011 (76 FR 38334), EPA published a notice of proposed rulemaking (NPR) for the District of Columbia, the State of Maryland, and the Commonwealth of Virginia. The NPR proposed approval of the 2002 base year emissions inventory, the RFP plan, RFP contingency measure, and RACM analysis for the Washington, DC-MD-VA moderate 1997 8-hour ozone<PRTPAGE P="58117"/>nonattainment area. These SIP elements were part of the “Plan to Improve Air Quality in the Washington, DC-MD-VA Region, State Implementation Plan (SIP) for 8-Hour Ozone Standard, Moderate Area SIP” (the Washington Area 8-hour ozone plan), which the District of Columbia Department of the Environment (DDOE), the Maryland Department of the Environment (MDE), and the Virginia Department of Environmental Quality (VADEQ) developed jointly. The Washington Area 8-hour ozone plan was formally submitted to EPA as a SIP revision by DDOE on June 12, 2007, by MDE on June 4, 2007, and by VADEQ on June 12, 2007. The NPR also proposed approval of the transportation conformity 2008 MVEBs associated with this revision.</P>
        <HD SOURCE="HD1">II. Summary of SIP Revision</HD>
        <P>The SIP revision addresses emissions inventory, RACM, RFP, and RFP contingency measures requirements for the 1997 8-hour ozone NAAQS for the Washington, DC-MD-VA 1997 8-hour moderate ozone nonattainment area. The SIP revision also establishes MVEBs for 2008. Other specific requirements of the Washington Area 8-hour ozone plan and the rationale for EPA's proposed action are explained in the NPR and will not be restated here. No public comments were received on the NPR.</P>
        <HD SOURCE="HD1">III. General Information Pertaining to SIP Submittals From the Commonwealth of Virginia</HD>
        <P>In 1995, Virginia adopted legislation that provides, subject to certain conditions, for an environmental assessment (audit) “privilege” for voluntary compliance evaluations performed by a regulated entity. The legislation further addresses the relative burden of proof for parties either asserting the privilege or seeking disclosure of documents for which the privilege is claimed. Virginia's legislation also provides, subject to certain conditions, for a penalty waiver for violations of environmental laws when a regulated entity discovers such violations pursuant to a voluntary compliance evaluation and voluntarily discloses such violations to the Commonwealth and takes prompt and appropriate measures to remedy the violations. Virginia's Voluntary Environmental Assessment Privilege Law, Va. Code Sec. 10.1-1198, provides a privilege that protects from disclosure documents and information about the content of those documents that are the product of a voluntary environmental assessment. The Privilege Law does not extend to documents or information (1) That are generated or developed before the commencement of a voluntary environmental assessment; (2) that are prepared independently of the assessment process; (3) that demonstrate a clear, imminent and substantial danger to the public health or environment; or (4) that are required by law.</P>
        <P>On January 12, 1998, the Commonwealth of Virginia Office of the Attorney General provided a legal opinion that states that the Privilege law, Va. Code Sec. 10.1-1198, precludes granting a privilege to documents and information “required by law,” including documents and information “required by Federal law to maintain program delegation, authorization or approval,” since Virginia must “enforce Federally authorized environmental programs in a manner that is no less stringent than their Federal counterparts.* * *” The opinion concludes that “[r]egarding § 10.1-1198, therefore, documents or other information needed for civil or criminal enforcement under one of these programs could not be privileged because such documents and information are essential to pursuing enforcement in a manner required by Federal law to maintain program delegation, authorization or approval.”</P>
        <P>Virginia's Immunity law, Va. Code Sec. 10.1-1199, provides that “[t]o the extent consistent with requirements imposed by Federal law,” any person making a voluntary disclosure of information to a State agency regarding a violation of an environmental statute, regulation, permit, or administrative order is granted immunity from administrative or civil penalty. The Attorney General's January 12, 1998 opinion states that the quoted language renders this statute inapplicable to enforcement of any Federally authorized programs, since “no immunity could be afforded from administrative, civil, or criminal penalties because granting such immunity would not be consistent with Federal law, which is one of the criteria for immunity.”</P>
        <P>Therefore, EPA has determined that Virginia's Privilege and Immunity statutes will not preclude the Commonwealth from enforcing its program consistent with the Federal requirements. In any event, because EPA has also determined that a state audit privilege and immunity law can affect only state enforcement and cannot have any impact on Federal enforcement authorities, EPA may at any time invoke its authority under the CAA, including, for example, sections 113, 167, 205, 211 or 213, to enforce the requirements or prohibitions of the state plan, independently of any state enforcement effort. In addition, citizen enforcement under section 304 of the CAA is likewise unaffected by this, or any, state audit privilege or immunity law.</P>
        <HD SOURCE="HD1">III. Final Action</HD>
        <P>EPA is approving the 2002 base year emissions inventory; the 2008 ozone projected emission inventory; the 2008 RFP plan; RFP contingency measures; RACM analysis; and 2008 transportation conformity budgets for the Washington, DC-MD-VA 1997 8-hour moderate ozone nonattainment area, and the Washington Area 8-hour ozone plan, which were submitted to EPA as a SIP revision by DDOE on June 12, 2007, by MDE on June 4, 2007, and by VADEQ onJune 12, 2007. The SIP revision satisfies the requirements for 1997 8-hour ozone NAAQS nonattainment areas classified as moderate and demonstrates further progress in reducing ozone precursors.</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
        <HD SOURCE="HD2">A. General Requirements</HD>
        <P>Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the CAA and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this action:</P>
        <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>

        <P>• Is not an economically significant regulatory action based on health or<PRTPAGE P="58118"/>safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
        <P>• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</P>
        <HD SOURCE="HD2">B. Submission to Congress and the Comptroller General</HD>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action 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>. A major rule cannot take effect until 60 days after it is published 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>
        <HD SOURCE="HD2">C. Petitions for Judicial Review</HD>
        <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by November 21, 2011. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action, pertaining to the 2002 base year emissions inventory, the 2008 ozone projected emission inventory, the 2008 RFP plan; RFP contingency measures, RACM analysis, and 2008 transportation conformity budgets for the Washington, DC-MD-VA 1997 8-hour moderate ozone nonattainment area, may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: August 31, 2011.</DATED>
          <NAME>W.C. Early,</NAME>
          <TITLE>Acting, Regional Administrator,Region III.</TITLE>
        </SIG>
        <P>40 CFR part 52 is amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart J—District of Columbia</HD>
          </SUBPART>

          <AMDPAR>2. In § 52.470, the table in paragraph (e) is amended by adding at the end of the table, the entries for Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures and Contingency Measures; 2002 Base Year Inventory for VOC, NO<E T="52">X</E>and CO; and 2008 RFP Transportation Conformity Budgets for the Washington DC-MD-VA 1997 8-hour Ozone Moderate Nonattainment Area. The amendments read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.470</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(e) * * *</P>
            <GPOTABLE CDEF="s50,r50,12,r50,xs50" COLS="5" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">Name of non-regulatory<LI>SIP revision</LI>
                </CHED>
                <CHED H="1">Applicable geographic area</CHED>
                <CHED H="1">State submittal date</CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Additional<LI>explanation</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures, and Contingency Measures</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2002 Base Year Inventory for VOC, NO<E T="52">X</E>, and CO</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2008 RFP Transportation Conformity Budgets</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>3. Section 52.474 is amended by revising the section heading and by adding paragraph (d) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.474</SECTNO>
            <SUBJECT>Base Year Emissions Inventory.</SUBJECT>
            <STARS/>

            <P>(d) EPA approves as a revision to the District of Columbia State Implementation Plan the 2002 base year emissions inventories for the Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Acting Director of the District of Columbia Department of the Environment on June 12, 2007. This submittal consists of the 2002 base year point, area, non-road mobile, and on-road mobile source inventories in area for the following pollutants: volatile organic compounds (VOC), carbon monoxide (CO) and nitrogen oxides (NO<E T="52">X</E>).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>4. Section 52.476 is amended by adding paragraphs (e) and (f) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.476</SECTNO>
            <SUBJECT>Control strategy: ozone.</SUBJECT>
            <STARS/>
            <P>(e) EPA approves revisions to the District of Columbia State Implementation Plan consisting of the 2008 reasonable further progress (RFP) plan, reasonably available control measures, and contingency measures for the Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Acting Director of the District of Columbia Department of the Environment on June 12, 2007.</P>

            <P>(f) EPA approves the following 2008 RFP motor vehicle emissions budgets (MVEBs) for the Washington, DC-MD-<PRTPAGE P="58119"/>VA 1997 8-hour ozone moderate nonattainment area submitted by the Director of the Virginia Department of Environment Quality on June 12, 2007:</P>
            <GPOTABLE CDEF="s50,12C,12C,12C,r50" COLS="5" OPTS="L2,i1">
              <TTITLE>Transportation Conformity Emissions Budgets for the Washington, DC-MD-VA Area</TTITLE>
              <BOXHD>
                <CHED H="1">Type of control strategy SIP</CHED>
                <CHED H="1">Year</CHED>
                <CHED H="1">VOC<LI>(TPD)</LI>
                </CHED>
                <CHED H="1">NO<E T="52">X</E>
                  <LI>(TPD)</LI>
                </CHED>
                <CHED H="1">Effective date of adequacy determination or SIP approval</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Rate of Progress Plan</ENT>
                <ENT>2008</ENT>
                <ENT>70.8</ENT>
                <ENT>159.8</ENT>
                <ENT>September 21, 2009 (74 FR 45853), published September 4, 2009.</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart V—Maryland</HD>
          </SUBPART>

          <AMDPAR>5. In § 52.1070, the table in paragraph (e) is amended by adding at the end of the table, the entries for Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures and Contingency Measures; 2002 Base Year Inventory for VOC, NO<E T="52">X</E>and CO; and 2008 RFP Transportation Conformity Budgets for the Washington DC-MD-VA 1997 8-hour Ozone Moderate Nonattainment Area. The amendments read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1070</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(e)* * *</P>
            <GPOTABLE CDEF="s50,r50,12,r50,xs50" COLS="5" OPTS="L1,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">Name of non-regulatory<LI>SIP revision</LI>
                </CHED>
                <CHED H="1">Applicable geographic area</CHED>
                <CHED H="1">State submittal date</CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Additional<LI>explanation</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures, and Contingency Measures</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins].</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2002 Base Year Inventory for VOC, NO<E T="52">X</E>, and CO</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2008 RFP Transportation Conformity Budgets</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>6. Section 52.1075 is amended by adding paragraph (k) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1075</SECTNO>
            <SUBJECT>Base Year Emissions Inventory.</SUBJECT>
            <STARS/>

            <P>(k) EPA approves as a revision to the Maryland State Implementation Plan the 2002 base year emissions inventories for the Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Secretary of the Maryland Department of the Environment on June 4, 2007. This submittal consists of the 2002 base year point, area, non-road mobile, and on-road mobile source inventories in area for the following pollutants: volatile organic compounds (VOC), carbon monoxide (CO) and nitrogen oxides (NO<E T="52">X</E>).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>7. Section 52.1076 is amended by adding paragraphs (u) and (v) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1076</SECTNO>
            <SUBJECT>Control strategy plans for attainment and rate-of-progress: Ozone.</SUBJECT>
            <STARS/>
            <P>(u) EPA approves revisions to the Maryland State Implementation Plan consisting of the 2008 reasonable further progress (RFP) plan, reasonably available control measures, and contingency measures for the Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Secretary of the Maryland Department of the Environment on June 4, 2007.</P>
            <P>(v) EPA approves the following 2008 RFP motor vehicle emissions budgets (MVEBs) for the Washington, DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Director of the Virginia Department of Environment Quality on June 12, 2007:</P>
            <GPOTABLE CDEF="s50,12C,12C,12C,r50" COLS="5" OPTS="L2,i1">
              <TTITLE>Transportation Conformity Emissions Budgets for the Washington, DC-MD-VA Area</TTITLE>
              <BOXHD>
                <CHED H="1">Type of control<LI>strategy SIP</LI>
                </CHED>
                <CHED H="1">Year</CHED>
                <CHED H="1">VOC<LI>(TPD)</LI>
                </CHED>
                <CHED H="1">NO<E T="52">X</E>
                  <LI>(TPD)</LI>
                </CHED>
                <CHED H="1">Effective date of adequacy<LI>determination or</LI>
                  <LI>SIP approval</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Rate of Progress Plan</ENT>
                <ENT>2008</ENT>
                <ENT>70.8</ENT>
                <ENT>159.8</ENT>
                <ENT>September 21, 2009 (74 FR 45853), published September 4, 2009.</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart VV—Virginia</HD>
          </SUBPART>

          <AMDPAR>8. In § 52.2420, the table in paragraph (e) is amended by adding at the end of the table, the entries for Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures and Contingency Measures; 2002 Base Year Inventory for VOC, NO<E T="52">x</E>and CO; and 2008 RFP Transportation Conformity Budgets for the Washington DC-MD-VA 1997 8-hour Ozone Moderate Nonattainment Area. The amendments read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.2420</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(e)* * *<PRTPAGE P="58120"/>
            </P>
            <GPOTABLE CDEF="s50,r50,12,r50,xs50" COLS="5" OPTS="L1,tp0,i1">
              <TTITLE/>
              <BOXHD>
                <CHED H="1">Name of non-regulatory<LI>SIP revision</LI>
                </CHED>
                <CHED H="1">Applicable geographic area</CHED>
                <CHED H="1">State submittal date</CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Additional<LI>explanation</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Reasonable Further Progress Plan (RFP), Reasonably Available Control Measures, and Contingency Measures</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2002 Base Year Inventory for VOC, NOx, and CO</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2008 RFP Transportation Conformity Budgets</ENT>
                <ENT>Washington DC-MD-VA 1997 8-hour ozone moderate nonattainment area</ENT>
                <ENT>6/12/07</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>9. Section 52.2425 is amended by revising the section heading and by adding paragraph (e) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.2425</SECTNO>
            <SUBJECT>Base Year Emissions Inventory.</SUBJECT>
            <STARS/>

            <P>(e) EPA approves as a revision to the Virginia State Implementation Plan the 2002 base year emissions inventories for the Washington, DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Director of the Virginia Department of Environment Quality on June 12, 2007. This submittal consists of the 2002 base year point, area, non-road mobile, and on-road mobile source inventories in area for the following pollutants: volatile organic compounds (VOC), carbon monoxide (CO) and nitrogen oxides (NO<E T="52">X</E>).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>10. Section 52.2428 is amended by adding paragraphs (f) and (g) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.2428</SECTNO>
            <SUBJECT>Control Strategy: Carbon monoxide and ozone.</SUBJECT>
            <STARS/>
            <P>(f) EPA approves revisions to the Virginia State Implementation Plan consisting of the 2008 reasonable further progress (RFP) plan, reasonably available control measures, and contingency measures for the Washington, DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Director of the Virginia Department of Environment Quality on June 12, 2007.</P>
            <P>(g) EPA approves the following 2008 RFP motor vehicle emissions budgets (MVEBs) for the Washington, DC-MD-VA 1997 8-hour ozone moderate nonattainment area submitted by the Director of the Virginia Department of Environment Quality on June 12, 2007:</P>
            <GPOTABLE CDEF="s50,12C,12C,12C,r50" COLS="5" OPTS="L2,i1">
              <TTITLE>Transportation Conformity Emissions Budgets for the Washington, DC-MD-VA Area</TTITLE>
              <BOXHD>
                <CHED H="1">Type of control strategy<LI>SIP</LI>
                </CHED>
                <CHED H="1">Year</CHED>
                <CHED H="1">VOC<LI>(TPD)</LI>
                </CHED>
                <CHED H="1">NO<E T="52">X</E>
                  <LI>(TPD)</LI>
                </CHED>
                <CHED H="1">Effective date<LI>of adequacy</LI>
                  <LI>determination or</LI>
                  <LI>SIP approval</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Rate of Progress Plan</ENT>
                <ENT>2008</ENT>
                <ENT>70.8</ENT>
                <ENT>159.8</ENT>
                <ENT>September 21, 2009 (74 FR 45853), published September 4, 2009.</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23967 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R03-OAR-2010-0770; FRL-9466-5]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Delaware; Requirements for Preconstruction Review, Prevention of Significant Deterioration</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>EPA is approving a State Implementation Plan (SIP) revision submitted by the State of Delaware. The revision establishes and requires the addition of nitrogen oxides (NO<E T="52">X</E>) as a precursor to ozone in the Delaware SIP. EPA is approving this revision to include NO<E T="52">X</E>as a precursor to ozone in the requirements for preconstruction review for prevention of significant deterioration (PSD) areas in Delaware in accordance with the requirements of the Clean Air Act (CAA).</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This final rule is effective on October 20, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID Number EPA-R03-OAR-2010-0770. All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>website. Although listed in the electronic docket, some information is not publicly available,<E T="03">i.e.,</E>confidential business information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically through<E T="03">http://www.regulations.gov</E>or in hard copy for public inspection during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. Copies of the State submittal are available at the Delaware Department of Natural Resources and Environmental Control, 89 Kings Highway, P.O. Box 1401, Dover, Delaware 19903.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Sharon McCauley, (215) 814-3376, or by e-mail at<E T="03">mccauley.sharon@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>

        <P>Throughout this document, whenever “we,” “us,” or “our” is used, we mean EPA. On May 9, 2011 (76 FR 26679), EPA published a notice of proposed rulemaking (NPR) for the State of Delaware. The NPR proposed approval of NO<E T="52">X</E>as a precursor to ozone in the requirements for preconstruction review for PSD areas in Delaware. The formal SIP revision was submitted by Delaware on April 1, 2010.<PRTPAGE P="58121"/>
        </P>

        <P>This SIP revision approval will add the current regulations found in Regulation 1125, section 3.0, Requirements for Preconstruction Review, Prevention of Significant Deterioration (Regulation 1125, section 3.0) as of April 11, 2010 which established NO<E T="52">X</E>as a precursor to ozone, but will keep intact the formally approved Delaware SIP increments for NO<E T="52">X</E>found in the<E T="04">Federal Register</E>notice for Delaware dated July 27, 1993 (58 FR 40065) for permitting and the construction of new major stationary sources and the significant modification of existing major stationary sources of air pollutants in areas designated attainment or non-classifiable for the National Ambient Air Quality Standards (NAAQS).</P>
        <HD SOURCE="HD1">II. Summary of SIP Revision</HD>

        <P>As required by 40 CFR part 51, Subpart I—“Review of New Sources and Modifications,” this rule adopts criteria and procedures for the prevention of significant deterioration of air quality that are consistent with the governing Federal regulation at 40 CFR 51.166. Promulgation of this rule by the State Legislature was necessary for the State to fulfill its responsibilities under 40 CFR part 51 and the CAA, as amended. Revisions to the State's rule were also necessary to ensure that the SIP provides for the attainment and maintenance of the NAAQS. This SIP approval action addresses changes needed in the part C PSD permit program. This SIP submission also corrects deficiencies identified by EPA in the March 27, 2008<E T="04">Federal Register</E>action entitled, “Completeness Findings for section 110(a) State Implementation Plans for the 8-hour Ozone National Ambient Air Quality Standards (1997 Ozone NAAQS)” (73 FR 16205). EPA's approval of this SIP submission addresses Delaware's compliance with the portion of CAA section 110(a)(2)(C) &amp; (J) relating to the CAA's part C permit program for the 1997 Ozone NAAQS, because this approval action will establish NO<E T="52">X</E>as a precursor to ozone in Delaware's SIP in accordance with the<E T="04">Federal Register</E>action dated November 29, 2005 (70 FR 71612) that finalized the NO<E T="52">x</E>as a precursor for ozone regulations set forth at 40 CFR 51.166 and in 40 CFR 52.21. As such, this approval action will add NO<E T="52">x</E>as a precursor to ozone in the Delaware SIP and Delaware will be in compliance with the portion of CAA section 110(a)(2)(C) and (J) relating to the CAA's part C permit program for the 1997 ozone NAAQS.</P>
        <P>Other specific requirements of NO<E T="52">x</E>as a precursor to ozone and the rationale for EPA's proposed action are explained in the NPR and will not be restated here. No public comments were received on the NPR.</P>
        <HD SOURCE="HD1">III. Final Action</HD>
        <P>EPA is approving the addition of nitrogen oxides (NO<E T="52">X</E>) as a precursor to ozone for PSD as a revision to the Delaware SIP and is making a determination that Delaware is in compliance with the portion of CAA section 110(a)(2)(C) and (J) relating to the CAA's part C permit program for the 1997 ozone NAAQS.</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
        <HD SOURCE="HD2">A. General Requirements</HD>
        <P>Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the CAA and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this action:</P>
        <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Is not subject to requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
        <P>• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</P>
        <HD SOURCE="HD2">B. Submission to Congress and the Comptroller General</HD>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action 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>. A major rule cannot take effect until 60 days after it is published 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>
        <HD SOURCE="HD2">C. Petitions for Judicial Review</HD>

        <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by November 21, 2011. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action to add nitrogen oxides (NO<E T="52">X</E>) as a precursor to ozone into the Delaware SIP may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Environmental protection, Air pollution control, Carbon monoxide, Incorporation by reference, Intergovernmental relations, Lead, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements, Sulfur oxides, Volatile organic compounds.</P>
        </LSTSUB>
        <SIG>
          <PRTPAGE P="58122"/>
          <DATED>Dated: August 31, 2011.</DATED>
          <NAME>W.C. Early,</NAME>
          <TITLE>Acting Regional Administrator, Region III.</TITLE>
        </SIG>
        
        <P>40 CFR part 52 is amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart I—Delaware</HD>
          </SUBPART>
          <AMDPAR>2. In § 52.420, the table in paragraph (c) is amended by revising the entry for Regulation 1125, Section 3.0 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.420</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <GPOTABLE CDEF="s50,r50,x640,r100,r100" COLS="5" OPTS="L1,i1">
              <TTITLE>EPA-Approved Regulations in the Delaware SIP</TTITLE>
              <BOXHD>
                <CHED H="1">State regulation<LI>(7 DNREC 1100)</LI>
                </CHED>
                <CHED H="1">Title/subject</CHED>
                <CHED H="1">State effective date</CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Additional explanation</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW RUL="s">
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW EXPSTB="04" RUL="">
                <ENT I="21">
                  <E T="02">1125REQUIREMENTS FOR PRECONSTRUCTION REVIEW</E>
                </ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="01">Section 3.0</ENT>
                <ENT>Prevention of Significant Deterioration of Air Quality</ENT>
                <ENT>4/11/10</ENT>
                <ENT>9/20/11 [Insert page number where the document begins]</ENT>
                <ENT>Modified to include NO<E T="52">X</E>as precursor to ozone. Previous SIP-approved revisions to Section 3.1 for nitrogen dioxide increments and Section 3.9A (now designated as Section 3.10.1) for air quality models remain part of the SIP.</ENT>
              </ROW>
              <ROW RUL="">
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23984 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Chapter 2</CFR>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Material Inspection and Receiving Report (DFARS Case 2009-D023)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS), Appendix F, Material Inspection and Receiving Report, to incorporate new procedures for using the electronic Wide Area WorkFlow (WAWF) Receiving Report.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Julian Thrash, telephone 703-602-0310.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DoD published a proposed rule in the<E T="04">Federal Register</E>(75 FR 56961) on September 17, 2010, to amend DFARS Appendix F, Material Inspection and Receiving Report, to provide new coverage on the use, preparation, and distribution of the electronic WAWF receiving report, which is the primary method for documenting acceptance of supplies and services and for electronic invoicing. The rule also addressed WAWF capability to provide the following:</P>
        <P>• Item Unique Identification (IUID). When the clause at DFARS 252.211-7003, Item Identification and Valuation, is used in the contract and requires reporting of IUID data, WAWF captures the IUID data and forwards the data to the IUID registry after acceptance. WAWF may be used to report Unique Item Identifiers (UIIs) at the line item level and also UIIs embedded at the line item level.</P>
        <P>• Radio Frequency Identification (RFID). When the clause at DFARS 252.211-7006, Radio Frequency Identification, is used in the contract, WAWF will capture the RFID information and forward the data to the receiving location.</P>
        <P>Using WAWF is the only way a contractor can comply with the clause to furnish RFID data via an Advance Shipping Notice. Insertion of the new WAWF coverage into Appendix F necessitates relocating and renumbering existing coverage for use, preparation, and distribution of the DD Form 250 Material Inspection and Receiving Report, and the DD Form 250-1 Tanker/Barge Material Inspection and Receiving Report.</P>
        <HD SOURCE="HD1">II. Discussion and Analysis</HD>
        <P>In response to the proposed rule, DoD received comments from five respondents. A discussion of the comments follows.</P>
        <HD SOURCE="HD2">A. Revise F-103, WAWF RR and DD Form 250</HD>
        <P>
          <E T="03">Comment:</E>Two respondents suggested changing the text at F-103(b)(2) for the transfer of Government property using the property transfer function. Another respondent recommended adding where training for the preparation of document types is available.</P>
        <P>
          <E T="03">Response:</E>These recommendations are incorporated into the final rule.</P>
        <HD SOURCE="HD2">B. Limitation on the Quantity of Embedded Items in WAWF</HD>
        <P>
          <E T="03">Comment:</E>A respondent asked if there was a limit on the quantity of embedded items at the line item level that may be reported in WAWF.</P>
        <P>
          <E T="03">Response:</E>A quantity limit of 100 embedded items currently exists in the software capability, however, this limit<PRTPAGE P="58123"/>is subject to change in future versions of WAWF.</P>
        <HD SOURCE="HD2">C. F-103(e)(2), Radio Frequency Identification (RFID)</HD>
        <P>
          <E T="03">Comment:</E>A respondent suggested adding clarification on the use of RFID information.</P>
        <P>
          <E T="03">Response:</E>As suggested, paragraph F-103(e)(2) is revised to clarify that the RFID information can be added either at submission or via the “WAWF Pack Later” functionality.</P>
        <HD SOURCE="HD2">D. F-104, Application</HD>
        <P>
          <E T="03">Comment:</E>A respondent asked about the meaning of “consigned to” at F-104(a)(4) and for clarification regarding use of a continuation sheet. The respondent stated that they have no control over how the continuation sheet appears or prints from WAWF.</P>
        <P>
          <E T="03">Response:</E>The phrase “consigned to” is the one to whom a line item is given, transferred, or delivered for control. In regard to use of a continuation sheet, the format printed out from WAWF will suffice as long as the required contractor information is entered.</P>
        <HD SOURCE="HD2">E. F-301, Preparation Instructions—General Comments</HD>
        <P>
          <E T="03">Comment:</E>Two respondents suggested, at paragraph F-301(a)(1), replacing “contractor” with “vendor” to be consistent with the label used on the training Web site provided in the proposed rule. A respondent suggested: (1) Revising F-301(a)(2) to reflect the creation of an extension to the prime Commercial and Government Entity (CAGE); (2) replacing, at paragraph F-301(a)(4), “official DoD sites” with “DoD definitive sources”; (3). adding text at paragraph F-301(b)(1)(iii) to clarify that comments in the miscellaneous information tab will appear in the comments section of the printed WAWF receiving report; (4). changing, at paragraph F-301(b)(1)(iv), “DoD contract number” to “DoD contract number and delivery order number”; and, (5) updating paragraph F-301(b)(3) to correctly refer to the data field as “Estimated” and reflect that data entry is a drop-down box.</P>
        <P>
          <E T="03">Response:</E>The final rule is revised to incorporate these recommendations.</P>
        <HD SOURCE="HD2">F. Inclusion of Shipping Documents</HD>
        <P>
          <E T="03">Comment:</E>A respondent requested at paragraph F-301(b)(2)(i), SHIPMENT NO., that contractors must always provide packaging documentation in their shipment containers. If contractors choose to provide their own packaging documentation they must ensure their documentation includes their shipment number data. The respondent recommended the addition of a statement that any document utilized as a packing list must include the shipment number information. Additionally, the respondent suggested revising the text with an example to clarify that the shipment number format requires first three data positions to be alpha, fourth position alpha-numeric and last three positions are numeric<E T="03">e.g.,</E>DFAR001 or DAR0001.</P>
        <P>
          <E T="03">Response:</E>The recommendations are incorporated into the final rule.</P>
        <P>
          <E T="03">Comment:</E>A respondent requested at paragraph F-301(b)(3), Date Shipped, that a “MIRR clause does not identify electronic data submission timeline.” The respondent recommended the DFARS MIRR language include the statement that the contractor will submit the completed MIRR via WAWF within one business day of material shipment. The respondent stated that material shipments missing shipment numbered data causes manual research in order to process the receipt acceptance.</P>
        <P>
          <E T="03">Response:</E>The MIRR is completed at the time of delivery of goods or services and, for both WAWF and paper DD form 250s, copies of the MIRR accompany the shipment. Paragraph F-301(b)(3) is revised to add a reference to “see F-303).”</P>
        <P>
          <E T="03">Comment:</E>A respondent requested at paragraph F-305, Invoice instructions, adding a statement that contractors should ensure the packaging documentation includes a Government signed receiving report when the contract requires origin inspection and acceptance. The respondent further stated that contractors must include the signed document indicating material receipt acceptance has occurred in the container with the exception of material shipments that are approved for Alternate Release Procedures.</P>
        <P>
          <E T="03">Response:</E>The final rule is revised to incorporate the recommendations.</P>
        <HD SOURCE="HD2">G. F-301(b)(4)—Bill of Lading Information</HD>
        <P>
          <E T="03">Comment:</E>A respondent stated, at paragraph F-301(b)(4)(i), that bills of lading are obtained when an item is being scheduled to ship, and thus may not be available until after the item has been source inspected/accepted. The respondent recommended clearly stating that the field is not required prior to source inspection and acceptance, nor, in their opinion, should a receiving report correction be issued only for adding a bill of lading after it has been obtained. Further, the respondent suggested revising F-301(b)(4), to enter the commercial or Government bill of lading number after “BL.”</P>
        <P>
          <E T="03">Response:</E>Currently, the “Bill of Lading Number” field is not a mandatory field in WAWF. Additional changes to the Bill of Lading functionality may be made later on.</P>
        <HD SOURCE="HD2">H. Line Haul Information Changes</HD>
        <P>
          <E T="03">Comment:</E>One respondent suggested at paragraph F-301(b)(5), Line Haul Mode, that this is an item that may not be stated accurately until after signature, when the item is scheduled for shipment, and recommended that this field not be required prior to source inspection/acceptance.</P>
        <P>
          <E T="03">Response:</E>There is flexibility in WAWF regarding this entry as “Line Haul Mode” field is not a mandatory field.</P>
        <HD SOURCE="HD2">I. Allow for WAWF Acceptance at “Other” Using Code “D”</HD>
        <P>
          <E T="03">Comment:</E>Two respondents suggested that paragraph F-301(b)(6), Inspection and Acceptance Point, be changed from “WAWF allows acceptance at Other” to “WAWF allows acceptance at Other (O).” Two respondents suggested adding, that for purposes of conforming to contract, “0” is equivalent to “D”.</P>
        <P>
          <E T="03">Response:</E>The final rule is revised to incorporate the recommendations.</P>
        <HD SOURCE="HD2">J. Marked for Codes</HD>
        <P>
          <E T="03">Comment:</E>A respondent suggested at paragraphs F-301(b)(7), Prime Contractor/Code, F-301(b)(9), Shipped From/Code, and F-301(b)(11), Payment Will Be Made By/Code, that these codes must match the contract, however, the street address is not required to match the contract. The respondents further opined that WAWF does not require the entry of an address code in either WAWF 4.2 or 5.0, and concluded that the requirement of an address should be clarified.</P>
        <P>
          <E T="03">Response:</E>No clarification is needed in the rule. Contractors can fulfill contracts with shipments from their location or from subsidiaries or subcontractors. Therefore, the shipped from code doesn't necessarily need to match the contract. Further, the receiving report is used for services as well as supplies where there will be no ship-from code.</P>
        <P>
          <E T="03">Comment:</E>One respondent requested clarification at paragraph F-301(b)(13), Marked For/Code, concerning the “Marked For Address.” Previously, textual marking information associated with the “Marked For DoDAAC” was placed in the address lines of the “Marked For DoDAAC.” Now that DoD is moving away from paper documents, the respondent wanted confirmation to<PRTPAGE P="58124"/>use the data fields as labeled using the code area for the “Marked For DoDAAC” and address only, and the “Mark For Rep” and “Mark For Secondary” fields used for the text information.</P>
        <P>
          <E T="03">Response:</E>The respondent is correct concerning use of these fields. No change to the rule is required.</P>
        <HD SOURCE="HD2">K. Marked for Codes</HD>
        <P>
          <E T="03">Comment:</E>A respondent requested revisions at paragraph F-301(b)(13) to reflect that a “Marked For Code” cannot be a CAGE code, only a DoDAAC or Military Assistance Program Address Codes.</P>
        <P>
          <E T="03">Response:</E>No revision is required in response to this comment since a CAGE code can be entered in the “Mark For Code” field.</P>
        <HD SOURCE="HD2">L. National Stock Number Entry Requirements</HD>
        <P>
          <E T="03">Comment:</E>A respondent recommended at paragraph F-301(b)(15)(1)(A) clarifying that in the “Type” drop-down field, that the user is to select the corresponding type for the data entered, and that if no National Stock Number or other valid “Type” is available, the word “None” may be entered for the Stock/Part Number, with a corresponding “Type” of any value other than the National Stock Number selected from the drop-down box. Another respondent stated that if the contract contains NSNs as well as other identification (<E T="03">e.g.,</E>part numbers), a contractor should place the NSN information in the Stock Part Number field and the remaining numbers in the line item description field.</P>
        <P>
          <E T="03">Response:</E>The paragraph is revised accordingly to incorporate the first recommendation. In regards to the second comment concerning NSNs as well as other identifying information, the respondent is correct in how this process works. The text is revised to ensure this meaning is understood.</P>
        <HD SOURCE="HD2">M. The “Description” Field Length and Use</HD>
        <P>
          <E T="03">Comment:</E>A respondent asked whether or not at paragraph F-301(b)(15)(ii), if exceeding 20 characters in the description field is a cause for the rejection of a receiving report. Further, the respondent requested clarification on whether or not the description refers to what is defined in the payment system as a “service” line item as opposed to a “supply” line item. A WAWF RR for a repair is for acceptance of the repair and not of the item repaired. However, repair line items are frequently defined as “supply” line items and therefore the ship-to location is the actual ship-to of the repaired item.</P>
        <P>
          <E T="03">Response:</E>Exceeding 20 characters in the description is not a cause for rejection of a receiving report. In response to the second comment, the respondent is correct that the description refers to the designation in the payment system as a “service” line item as opposed to a “supply” line item.</P>
        <HD SOURCE="HD2">N. GFP Drop-Down Box</HD>
        <P>
          <E T="03">Comment:</E>A respondent suggested that clarification at paragraph F-301(b)(15)(iv)(E) is required for how the text relates to the GFE drop-down box, and whether or not the drop-down box is insufficient for this situation. The correct use of GFE drop-down box needs to be fully explained. If it is not the same as the entry of “GFP” in the description text, the differences must be clarified.</P>
        <P>
          <E T="03">Response:</E>The drop-down GFE box is not related to this section. It is obsolete and no longer used and will be deleted in a future version of WAWF. The GFP drop-down box is sufficient for use of GFP.</P>
        <HD SOURCE="HD2">O. F-301—General Comments Regarding Unit Price</HD>
        <P>
          <E T="03">Comment:</E>Two respondents stated that at paragraph F-301(b)(18), the proposed text is identical to that used in the current Appendix F for unit price (see F-301, block 19, on current Appendix F). They further stated that this document will never be used as an invoice; thus, in their opinion, there should not be a requirement to fill in a unit price, except in the cases listed. Further, one respondent recommended at paragraph F-301(b)(18)(i) the addition of the text to clarify the handling of unit prices and property transfer. Another respondent had a concern with unit prices that were as little as twenty cents and not being accepted by the Government agency. This respondent also noted that an estimated price can be entered in the description field, but the Government contracting office expects the price entered in the price field, even though WAWF does not accept the entry the way the agency had requested. The respondent went on to state that the DFARS does not address the electronic aspect of WAWF and billing.</P>
        <P>
          <E T="03">Response:</E>The unit price is required. In regard to the intent of the paragraph on the WAWF initiated property transfer, the purpose is to alert the contractor that a property transfer will be generated as a result of the completion of the WAWF RR. In regard to the unit price, it is required when the clause at DFARS 252.211-7003, Item Identification and Valuation, is used; otherwise the use of the field is optional and at the discretion of the vendor. When used for item unique identification, the unit price does not necessarily reflect the billing price on the contract. The DFARS addresses electronic billing at 252.232.7003, Electronic Submission of Payment Requests and Receiving Reports. No change in the rule is required in response to these comments.</P>
        <HD SOURCE="HD2">P. F-301—General Comments Regarding Contract Quality Assurance</HD>
        <P>
          <E T="03">Comment:</E>One respondent suggested at paragraph F-301(b)(20)(ii), that the term “execute” is misleading and will cause confusion. The respondent also stated that removing the quotation marks will ensure a clear direction. The respondent further suggested at paragraphs F-301(b)(20)(iv)(A)(3) and (v) the steps described should match the actual step taken in WAWF to electronically sign the document and recommended the text be revised.</P>
        <P>
          <E T="03">Response:</E>The quotation marks used for the term “execute” are removed. In regard to the electronic signatures, the text has been revised accordingly to match the actual steps taken in WAWF.</P>
        <HD SOURCE="HD2">Q. Comment Regarding F-301(b)(21)</HD>
        <P>
          <E T="03">Comment:</E>One respondent suggested paragraph F-301(b)(21) should be referenced as the COMMENTS block and/or MISC INFO tab.</P>
        <P>
          <E T="03">Response:</E>The title is revised to incorporate “MISC. INFO” as suggested.</P>
        <HD SOURCE="HD2">R. Printed Documents</HD>
        <P>
          <E T="03">Comment:</E>One respondent recommended at paragraph F-306(b), that the text be revised to clarify that if a signed copy is required by the contractor, the contractor will print the WAWF RR only after a signature is applied by the Government Inspector or Acceptor in WAWF.</P>
        <P>
          <E T="03">Response:</E>This text is revised accordingly to incorporate the suggestion.</P>
        <HD SOURCE="HD2">S. Part 4—General Comments</HD>
        <P>
          <E T="03">Comment:</E>One respondent stated that in Part 4 there are multiple references to section F-301 and recommended, where appropriate, the references be updated to the corresponding F-401 reference. The respondent also suggested that at paragraph F-401(b)(2), “Starting over with 0001” cannot be used in an electronic world, and that the DD Form 250 needs to conform to the same requirement (F-301(b)(2)) as the WAWF RR.</P>
        <P>
          <E T="03">Response:</E>Part 4 references in the final rule are updated as required. In<PRTPAGE P="58125"/>regard to shipment numbering, the system will not allow the shipment number to start over with 0001 as any duplication of the combined contract number, delivery order number, and shipment number results a duplication error. In these cases, WAWF requires a change in the shipment number prefix. While on a paper DD Form 250, it is possible to start over with 0001 when the series is completely used, a change in the shipment number prefix should be required for consistency. The text at F-401(b)(2) is revised to clarify this process.</P>
        <HD SOURCE="HD2">T. Part 5 Comments</HD>
        <P>
          <E T="03">Comment:</E>A respondent commented on Part 5 concerning the “alternate” release procedure. The respondent noted that all other references in the document are to “alternative” release procedure, and would like to know which is correct.</P>
        <P>
          <E T="03">Response:</E>The final rule is revised in Part 5 to refer to “alternative” in lieu of “alternate.”</P>
        <HD SOURCE="HD2">U. WAWF Versions</HD>
        <P>
          <E T="03">Comment:</E>A respondent stated there are a number of changes incorporated in the latest WAWF release that impact MIRR data entry. The respondent noted that changes include removal of “other” as an acceptance point and replacing it with more specific data entries for inspection, acceptance, and ship to DoDAAC codes.</P>
        <P>
          <E T="03">Response:</E>There is no need to change paragraph F-301(b)(6) as “Other” will remain an option for the inspection and acceptance point. DoD adopted business rules regarding the inspection, acceptance, and ship-to fields but kept the source, destination, and other inspection and acceptance points. Therefore, no change is necessary.</P>
        <HD SOURCE="HD2">V. General Comments</HD>
        <P>
          <E T="03">Comment:</E>One respondent stated that Appendix F addresses the use of the MIRR in WAWF, yet multiple types of receiving and performance transactions exist. Examples include:</P>
        <P>○ Receiving Report.</P>
        <P>○ Receiving Report—COMBO.</P>
        <P>○ Invoice 2-in-1 (Services Only).</P>
        <P>
          <E T="03">Response:</E>Appendix F only provides instruction for use of the MIRR. Invoice 2-in-1 (services only) is used to document acceptance of services when a MIRR is not required. The COMBO transaction in WAWF allows for the vendor to do one set of data entry that is split in the system into both a receiving report, identical to the non-COMBO receiving report, and an invoice. The instructions for the data entry in the COMBO are the same as the data fields for the receiving report.</P>
        <P>
          <E T="03">Comment:</E>A respondent suggested at paragraph F-301 rewording to state that Electronic Document Access (EDA) will automatically populate all available and applicable contract data.</P>
        <P>
          <E T="03">Response:</E>This change is incorporated at F-301(a)(3) in the final rule.</P>
        <P>
          <E T="03">Comment:</E>A respondent stated that they had received multiple rejections of receiving reports due to a formatting issue. In one case, the receiving report was rejected due to a dash being dropped out of the line item stock number upon loading to WAWF. In the respondent's opinion, the missing dash should not be a reason for rejection. The respondent requested adding specific language to F-301(b)(15) to indicate that missing dashes are acceptable in the line item stock number.</P>
        <P>
          <E T="03">Response:</E>The respondent indicates a dash was missing from the part number. This changes the item identification significantly. There are no known concerns with the National Stock Number functionality.</P>
        <HD SOURCE="HD1">III. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, was not subject to review under section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>

        <P>DoD does not expect this final rule to have a significant economic impact on 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>The final rule provides guidance on the preparation and use of the electronic WAWF Receiving Report which is now required for use in most contracts. Additionally, the rule addresses the WAWF capability and instructions to comply with reporting requirements for IUID and RFID data submissions. DoD has prepared a Final Regulatory Flexibility Analysis, which is summarized as follows:</P>
        <P>The objective of the rule is to facilitate maximum use of WAWF by providing detailed guidance. DFARS Subpart 232.70, Electronic Submission and Processing of Payment Requests and Receiving Reports, prescribes policies for submitting and processing payment requests in electronic form to comply with 10 U.S.C. 2227, Electronic Submission and Processing of Claims for Contract Payments. WAWF is the DoD system for contractors to submit payment and receiving reports in an electronic format. This final rule affects all DoD contractors who are not exempt from using WAWF. Exempt classes of contracts are those that are listed under the seven categories of contracts at DFARS 232.7002, Policy. Record keeping required is limited to that necessary to properly invoice and record shipping and receiving information under Government contracts. The preparation of these records requires clerical and analytic skills to create the documents and input them into the electronic WAWF system.</P>
        <P>The rule does not duplicate, overlap, or conflict with any other Federal rules. There are no known significant alternatives to the rule that would meet the requirements of 10 U.S.C. 2227, Electronic Submission and Processing of Claims for Contract Payments. Any impact on small business is expected to be beneficial by providing detailed use, preparation and distribution guidance for electronic submission in lieu of preparing and submitting paper invoices and receiving records.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
        <P>The Paperwork Reduction Act (44 U.S.C. chapter 35) applies. The Appendix F information collection requirements in this rule are approved under Office of Management and Budget Control Number 0704-0248, DFARS Appendix F, Material Inspection and Receiving Report. The current approval took into consideration use of the automated WAWF system, so inclusion of the WAWF guidance into Appendix F adds no new information collection requirements.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Appendix F to Chapter 2</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>

        <P>Therefore, 48 CFR chapter 2 is amended by revising appendix F to read as follows:<PRTPAGE P="58126"/>
        </P>
        <HD SOURCE="HD1">Appendix F to Chapter 2—Material Inspection and Receiving Report</HD>
        <CONTENTS>
          <SECHD>Sec.</SECHD>
          <HD SOURCE="HD1">Part 1—Introduction</HD>
          <SECTNO>F-101</SECTNO>
          <SUBJECT>General.</SUBJECT>
          <SECTNO>F-102</SECTNO>
          <SUBJECT>Applicability.</SUBJECT>
          <SECTNO>F-103</SECTNO>
          <SUBJECT>Use.</SUBJECT>
          <SECTNO>F-104</SECTNO>
          <SUBJECT>Application.</SUBJECT>
          <HD SOURCE="HD1">Part 2—Contract Quality Assurance On Shipments Between Contractors</HD>
          <SECTNO>F-201</SECTNO>
          <SUBJECT>Procedures.</SUBJECT>
          <HD SOURCE="HD1">Part 3—Preparation of the Wide Area Workflow Receiving Report (WAWF RR)</HD>
          <SECTNO>F-301</SECTNO>
          <SUBJECT>Preparation instructions.</SUBJECT>
          <SECTNO>F-302</SECTNO>
          <SUBJECT>Mode/method of shipment codes.</SUBJECT>
          <SECTNO>F-303</SECTNO>
          <SUBJECT>Consolidated shipments.</SUBJECT>
          <SECTNO>F-304</SECTNO>
          <SUBJECT>Correction instructions.</SUBJECT>
          <SECTNO>F-305</SECTNO>
          <SUBJECT>Invoice instructions.</SUBJECT>
          <SECTNO>F-306</SECTNO>
          <SUBJECT>Packing list instructions.</SUBJECT>
          <SECTNO>F-307</SECTNO>
          <SUBJECT>Receiving instructions.</SUBJECT>
          <HD SOURCE="HD1">Part 4—Preparation of the DD Form 250 and DD Form 250C</HD>
          <SECTNO>F-401</SECTNO>
          <SUBJECT>Preparation instructions.</SUBJECT>
          <SECTNO>F-402</SECTNO>
          <SUBJECT>Mode/method of shipment codes.</SUBJECT>
          <SECTNO>F-403</SECTNO>
          <SUBJECT>Consolidated shipments.</SUBJECT>
          <SECTNO>F-404</SECTNO>
          <SUBJECT>Multiple consignee instructions.</SUBJECT>
          <SECTNO>F-405</SECTNO>
          <SUBJECT>Correction instructions.</SUBJECT>
          <SECTNO>F-406</SECTNO>
          <SUBJECT>Invoice instructions.</SUBJECT>
          <SECTNO>F-407</SECTNO>
          <SUBJECT>Packing list instructions.</SUBJECT>
          <SECTNO>F-408</SECTNO>
          <SUBJECT>Receiving instructions.</SUBJECT>
          <HD SOURCE="HD1">Part 5—Distribution of Wide Area Workflow Receiving Report (WAWF RR), DD Form 250 and DD Form 250C</HD>
          <SECTNO>F-501</SECTNO>
          <SUBJECT>Distribution of WAWF RR.</SUBJECT>
          <SECTNO>F-502</SECTNO>
          <SUBJECT>Distribution of DD Form 250 and DD Form 250C.</SUBJECT>
          <HD SOURCE="HD1">Part 6—Preparation of the DD Form 250-1 (Loading Report)</HD>
          <SECTNO>F-601</SECTNO>
          <SUBJECT>Instructions.</SUBJECT>
          <HD SOURCE="HD1">Part 7—Preparation of the DD Form 250-1 (Discharge Report)</HD>
          <SECTNO>F-701</SECTNO>
          <SUBJECT>Instructions.</SUBJECT>
          <HD SOURCE="HD1">Part 8—Distribution of the DD Form 250-1</HD>
          <SECTNO>F-801</SECTNO>
          <SUBJECT>Distribution.F-802 Corrected DD Form 250-1.</SUBJECT>
          <SECTNO>F-802</SECTNO>
          <SUBJECT>Corrected DD Form 250-1.</SUBJECT>
        </CONTENTS>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
        </AUTH>
        <EXTRACT>
          <HD SOURCE="HD1">Part 1—Introduction</HD>
          <HD SOURCE="HD2">F-101General.</HD>
          <P>(a) This appendix contains procedures and instructions for the use, preparation, and distribution of the Wide Area WorkFlow Receiving Report (WAWF RR), the DD Form 250, Material Inspection and Receiving Report (MIRR) and (DD Form 250 series equivalents) and commercial shipping/packing lists used to document Government contract quality assurance.</P>
          <P>(b) The use of the DD Form 250 is on an exception basis (see DFARS 232.7003(a)) because use of the WAWF RR is now required by most DoD contracts. WAWF provides for electronic preparation and documentation of acceptance of supplies and services, and electronic invoicing. In addition WAWF allows the printing of a RR that can be used as a packing list or when a signed copy is required.</P>
          <HD SOURCE="HD2">F-102Applicability.</HD>
          <P>(a) DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports, requires payment requests and receiving reports using WAWF in nearly all cases.</P>
          <P>(b) The provisions of this appendix also apply to supplies or services acquired by DoD when the clause at DFARS 252.246-7000, Material Inspection and Receiving Report, is included in the contract.</P>
          <P>(c) When DoD provides quality assurance or acceptance services for non-DoD activities, prepare a MIRR using the instructions in this appendix, unless otherwise specified in the contract.</P>
          <HD SOURCE="HD2">F-103Use.</HD>
          <P>(a) The WAWF RR and the DD Form 250 are multipurpose reports used—</P>
          <P>(1) To provide evidence of Government contract quality assurance at origin or destination;</P>
          <P>(2) To provide evidence of acceptance at origin, destination, or other;</P>
          <P>(3) For packing lists;</P>
          <P>(4) For receiving;</P>
          <P>(5) For shipping;</P>
          <P>(6) As a contractor invoice (the WAWF RR or DD Form 250 alone cannot be used as an invoice, however the option exists to create an invoice from the Receiving Report or a Combo (Invoice and Receiving Report) both of which minimize data entry); and</P>
          <P>(7) As commercial invoice support.</P>
          <P>(b) Do not use the WAWF RR or the DD Form 250 for shipments—</P>
          <P>(1) By subcontractors, unless the subcontractor is shipping directly to the Government; or</P>

          <P>(2) Of contract inventory. The WAWF Property Transfer document should be used for this type of shipment. Training for the preparation of this document type is available at<E T="03">https://wawftraining.eb.mil</E>, under the Property Transfer and Receipt section.</P>
          <P>(c) The contractor prepares the WAWF RR or the DD Form 250, except for entries that an authorized Government representative is required to complete. When using a paper DD Form 250, the contractor shall furnish sufficient copies of the completed form, as directed by the Government representative.</P>
          <P>(d) Use the DD Form 250-1:</P>
          <P>(1) For bulk movements of petroleum products by tanker or barge to cover—</P>
          <P>(i) Origin or destination acceptance of cargo; or</P>
          <P>(ii) Shipment or receipt of Government owned products.</P>
          <P>(2) To send quality data to the point of acceptance in the case of origin inspection on FOB destination deliveries or preinspection at product source. Annotate the forms with the words “INSPECTED FOR QUALITY ONLY.”</P>
          <P>(e) In addition to the above uses, the WAWF RR provides additional functionality, not provided by the paper DD Form 250 that complies with the following requirements:</P>
          <P>(1) Item Unique Identification (IUID), when the clause at DFARS 252.211-7003, Item Identification and Valuation, is used in the contract, reporting of IUID data is required. WAWF captures the IUID data and forwards the data to the IUID registry after acceptance. WAWF can be used to report Unique Item Identifiers (UIIs) at the line item level and also UIIs embedded at the line item level.</P>
          <P>(2) Radio Frequency Identification (RFID), when the clause at DFARS 252.211-7006, Radio Frequency Identification, is used in the contract, WAWF will capture the RFID information and forward the data to the receiving location. Using WAWF is the only way a contractor can comply with the clause to furnish RFID data via an Advance Shipping Notice (ASN). The RFID information may be added at time of submission, or via the WAWF Pack Later functionality after acceptance.</P>
          <HD SOURCE="HD2">F-104Application.</HD>
          <P>(a)<E T="03">WAWF RR and DD Form 250.</E>
          </P>
          <P>(1) Use the WAWF RR or DD Form 250 for delivery of contract line, subline, exhibit line, or exhibit subline items. Do not use the WAWF RR or DD Form 250 for those exhibit line or exhibit subline items on a DD Form 1423, Contract Data Requirements List, which indicate no DD Form 250 is required.</P>
          <P>(2) If the shipped to, marked for, shipped from, mode of shipment, contract quality assurance and acceptance data are the same for more than one shipment made on the same day under the same contract, contractors may prepare one WAWF RR or DD Form 250 to cover all such shipments.</P>
          <P>(3) If the volume of the shipment precludes the use of a single car, truck, or other vehicle, prepare a separate WAWF RR or DD Form 250 for the contents of each vehicle.</P>
          <P>(4) When a shipment is consigned to an Air Force activity and the shipment includes items of more than one Federal supply class (FSC) or material management code (MMC), prepare a separate WAWF RR or DD Form 250 for items of each of the FSCs or MMCs in the shipment. However, the cognizant Government representative may authorize a single WAWF RR or DD Form 250, listing each of the FSCs or MMCs included in the shipment on a separate continuation sheet. The MMC appears as a suffix to the national stock number applicable to the item.</P>
          <P>(5)<E T="03">Consolidation of Petroleum Shipments on a Single WAWF RR or DD Form 250.</E>
          </P>
          <P>(i)<E T="03">Contiguous United States.</E>Contractors may consolidate multiple car or truck load shipments of petroleum made on the same day, to the same destination, against the same contract line item, on one WAWF RR or DD Form 250. To permit verification of motor deliveries, assign each load a load number which can be identified to the shipment number in Block 2 of the DD Form 250. Include a shipping document (commercial or Government) with each individual load showing as a minimum—</P>
          <P>(A) The shipper;</P>
          <P>(B) Shipping point;</P>
          <P>(C) Consignee;</P>
          <P>(D) Contract and line item number;</P>
          <P>(E) Product identification;</P>
          <P>(F) Gross gallons (bulk only);</P>
          <P>(G) Loading temperature (bulk only);</P>

          <P>(H) American Petroleum Institute gravity (bulk only);<PRTPAGE P="58127"/>
          </P>
          <P>(I) Identification of carrier's equipment;</P>
          <P>(J) Serial number of all seals applied; and</P>
          <P>(K) Signature of supplier's representative.</P>
          
          <FP>When acceptance is at destination, the receiving activity retains the shipping document(s) to verify the entries on the consignee copy of the DD Form 250 forwarded by the contractor (reference F-401, Table 1) before signing Block 21b.</FP>
          <P>(ii)<E T="03">Overseas.</E>The same criteria as for contiguous United States applies, except the consolidation period may be extended, if acceptable to the receiving activity, shipping activity, Government finance office, and the authorized Government representative having cognizance at the contractor's facility. In addition, the contractor may include more than one contract line item in each WAWF RR or DD Form 250 if the shipped to, marked for, shipped from, mode of shipment, contract quality assurance, and acceptance data are the same for all line items.</P>
          <P>(6)<E T="03">Consolidation of Coal Shipments on a Single WAWF RR or DD 250.</E>Contractors may consolidate multiple railcar or truck shipments of coal made on the same day, to the same destination, against the same contract line items, on one WAWF RR or DD 250. To permit verification of truck deliveries, assign each load a load number which can be identified to the shipment number in Block 2 of the DD Form 250 and the analytical test report. Include a commercial shipping document with each individual truck load showing as a minimum—</P>
          <P>(i) The shipper;</P>
          <P>(ii) The name or names;</P>
          <P>(iii) Location and shipping point of the mine or mines from which the coal originates;</P>
          <P>(iv) The contract number;</P>
          <P>(v) The exact size of the coal shipped; and</P>
          <P>(vi) A certified weighmaster's certification of weight for the truckload.</P>
          
          <P>Include a waybill with each rail shipment showing the identical information. To permit verification of rail deliveries, identify each railcar number comprising the shipment to the shipment number in Block 2 of the DD Form 250 and the analytical test report. When acceptance is at destination, the receiving activity must retain the shipping document(s) to verify the entries on the consignee copy of the DD Form 250.</P>
          <P>(b)<E T="03">DD Form 250-1.</E>
          </P>
          <P>(1) Use a separate form for each tanker or barge cargo loaded.</P>
          <P>(2) The contractor may report more than one barge in the same tow on a single form if on the same contract and consigned to the same destination.</P>
          <P>(3) When liftings involve more than one contract, prepare separate forms to cover the portion of cargo loaded on each contract.</P>
          <P>(4) Prepare a separate form for each product or grade of product loaded.</P>
          <P>(5) Use a separate document for each tanker or barge cargo and each grade of product discharged.</P>
          <P>(6) For discharge, the contractor may report more than one barge in the same tow on a single form if from the same loading source.</P>
          <HD SOURCE="HD1">Part 2—Contract Quality Assurance on Shipments Between Contractors</HD>
          <HD SOURCE="HD2">F-201Procedures</HD>
          <P>Follow the procedures at PGI F-201 for evidence of required Government contract quality assurance at a subcontractor's facility.</P>
          <HD SOURCE="HD2">Part 3—Preparation of the Wide Area Workflow Receiving Report (WAWF RR)</HD>
          <HD SOURCE="HD2">F-301Preparation instructions.</HD>
          <P>(a)<E T="03">General.</E>
          </P>

          <P>(1) Preparation instructions and training for the WAWF RR are available at<E T="03">https://wawftraining.eb.mil.</E>The instructions on preparing a WAWF RR are part of the Vendor Training section.</P>
          <P>(2) Prime contractors can direct subcontractors to prepare and submit documents in WAWF by giving their subcontractors access to WAWF via the creation of a Commercial and Government Entity (CAGE) extension to the prime CAGE.</P>
          <P>(3) If the contract is in Electronic Document Access (EDA) (DoD's contract repository), then the WAWF system will automatically populate all available and applicable contract data.</P>
          <P>(i) When source acceptance is required, WAWF will populate the “Inspect By” with the “Admin by” Department of Defense Activity Address Code (DoDAAC). The vendor shall change the DoDAAC if Government Source Inspection (GSI) is performed at other than the “Admin By.”</P>
          <P>(ii) Any fields that have been pre-filled may be changed.</P>
          <P>(iii) WAWF will also verify that CAGE codes are valid and active in the CCR (Central Contractor Registration), and that DoDAACs and Military Assistance Program Address Codes (MAPACs) are valid in Defense Automatic Addressing System (DAAS).</P>
          <P>(4) WAWF will populate the address information for CAGE codes, DODAACs, and MAPACs from CCR and DAAS. These sites are the DoD definitive sources for address information. Any fields that have been pre-filled may be changed or additional information added.</P>
          <P>(5) Do not include classified information in WAWF.</P>
          <P>(b)<E T="03">Completion instructions.</E>
          </P>
          <P>(1) Contract no/delivery order No.</P>
          <P>(i) Enter the 13-position alpha-numeric basic Procurement Instrument Identification Number (PIIN) of the contract. When applicable, enter the four-position alpha-numeric call/order serial number that is supplementary to the 13-position basic PIIN. This number is also referred to as the Supplementary Procurement Instrument Identification Number (SPIIN). Use SPIINs for (also see Subpart 204.70)—</P>
          <P>(A) Delivery orders under indefinite-delivery type contracts;</P>
          <P>(B) Orders under basic ordering agreements; and</P>
          <P>(C) Calls under blanket purchase agreements.</P>
          <P>(ii) Except as indicated in paragraph (b)(1)(iii) of this appendix, do not enter supplementary numbers used in conjunction with basic PIINs to identify—</P>
          <P>(A) Modifications of contracts and agreements;</P>
          <P>(B) Modifications to calls or orders; or</P>
          <P>(C) Document numbers representing contracts written between contractors.</P>
          <P>(iii) When shipping instructions are furnished and shipment is made before receipt of the confirming contract modification (SF 30, Amendment of Solicitation/Modification of Contract), enter a comment in the Misc. Info Tab to this effect. This will appear in the Comments section of the printed WAWF RR.</P>
          <P>(iv) For DoD delivery orders on non-DoD contracts, enter the non-DoD contract number in the contract number field and enter the DoD contract number and, when applicable, delivery order number in the delivery order field.</P>
          <P>(2) Shipment No.</P>

          <P>(i) The shipment number format requires first three data positions to be alpha, fourth position alpha-numeric and last three positions numeric,<E T="03">e.g.,</E>DFAR001 or DAR0001. Any document used as a packing list must include the shipment number information.</P>
          <P>(A) The prime contractor shall control and assign the shipment number prefix. The shipment number shall consist of three alphabetic characters for each “Shipped From” address. The shipment number prefix shall be different for each “Shipped From” address and shall remain constant throughout the life of the contract. The prime contractor may assign separate prefixes when shipments are made from different locations within a facility identified by one “Shipped From” address.</P>
          <P>(B) Number the first shipment 0001 for shipments made under the contract or contract and order number from each “Shipped From” address, or shipping location within the “Shipped From” address. Consecutively number all subsequent shipments with the identical shipment number prefix. While shipments should be created sequentially they can be released and accepted out of sequence.</P>
          <P>
            <E T="03">(1)</E>Use alpha-numeric serial numbers when more than 9,999 numbers are required. Serially assign alpha-numeric numbers with the alpha in the first position (the letters I and O shall not be used) followed by the three-position numeric serial number. Use the following alpha-numeric sequence:</P>
          
          <FP SOURCE="FP-1">A000 through A999 (10,000 through 10,999)</FP>
          <FP SOURCE="FP-1">B000 through B999 (11,000 through 11,999)</FP>
          <FP SOURCE="FP-1">Z000 through Z999 (34,000 through 34,999)</FP>
          
          <P>
            <E T="03">(2)</E>When this series is completely used, the shipment number prefix will have to be changed when the series is completely used. WAWF will not allow duplicate shipment numbers to be created against a contract or contract and delivery order.</P>
          <P>(ii) Reassign the shipment number of the initial shipment where a “Replacement Shipment” is involved (see paragraph (b)(16)(iv)(F) of this appendix).</P>
          <P>(iii) The prime contractor shall control deliveries and on the final shipment of the contract shall end the shipment number with a “Z.” Where the final shipment is from other than the prime contractor's plant, the prime contractor may elect either to—</P>

          <P>(A) Direct the subcontractor making the final shipment to end that shipment number with a “Z”; or<PRTPAGE P="58128"/>
          </P>
          <P>(B) Upon determination that all subcontractors have completed their shipments, to correct the DD Form 250 (see F-304) covering the final shipment made from the prime contractor's plant by addition of a “Z” to that shipment number.</P>
          <P>(iv) Contractors follow the procedures in F-305 to use commercial invoices.</P>
          <P>(3) Date shipped. Enter the date the shipment is released to the carrier or the date the services are completed. If the shipment will be released after the date of contract quality assurance and/or acceptance, enter the estimated date of release. When the date is estimated, enter an “E” or select an “E” from the drop down menu in the “Estimated” block after the date. Do not delay submission of the WAWF RR for lack of entry of the actual shipping date. Correction of the WAWF RR is not required to show the actual shipping date (see F-303). Once the document is submitted the shipment date cannot be changed.</P>
          <P>(4) B/L TCN. When applicable, enter—</P>
          <P>(i) The commercial or Government bill of lading number after “B/L;” WAWF provides the capability to separately and correctly identify the Government Bill of Lading (GBL) from a Commercial Bill of Lading (CBL). An authorized user will select whether the entered bill of lading number is either a GBL number or a CBL number.</P>
          <P>(ii) The transportation control number must be a 17 alpha/numeric digit min/max field, and WAWF provides the capability to enter two secondary transportation tracking numbers.</P>
          <P>(5) Line haul mode. Select the Line Haul Mode of Shipment code from a drop down menu in WAWF.</P>
          <P>(6) Inspection and acceptance point. Enter an “S” for Origin or “D” for Destination. In addition to “S” and “D,” WAWF allows acceptance at Other (O). For purposes of conforming to contract, “O” is equivalent to “D”. In WAWF, destination acceptance is performed by the “Ship to” DODAAC organization and “Other” permits the acceptance of destination documents at a location other than the “Ship to.” The goods or services will be shipped to one location and the paperwork will be routed to another location for the actual acceptance.</P>
          <P>(7) Prime contractor/code. Enter the prime CAGE code to which the contract was awarded.</P>
          <P>(8) Administered by/code. Enter the DoDAAC code of the contract administration office cited in the contract.</P>
          <P>(9) Shipped from/code.</P>
          <P>(i) Enter the CAGE or DoDAAC code of the “Shipped From” location. If it is the same as the CAGE code leave blank.</P>
          <P>(ii) For performance of services line items which do not require delivery of items upon completion of services, enter the code of the location at which the services were performed. As mentioned in (i) above, if identical to the prime CAGE code leave blank.</P>
          <P>(10) FOB. Enter an “S” for Origin or “D” for Destination as specified in the contract. Enter an alphabetic “O” if the “FOB” point cited in the contract is other than origin or destination.</P>
          <P>(11) Payment will be made by/code. Enter the DoDAAC code of the payment office cited in the contract.</P>
          <P>(12) Shipped to/code. Enter the DoDAAC, MAPAC, or CAGE code from the contract or shipping instructions.</P>
          <P>(13) Marked for/code. Enter the code from the contract or shipping instructions. Only valid DoDAACs, MAPACs, or CAGE codes can be entered. Vendors should use the WAWF “Mark for Rep” and “Mark for Secondary” fields for textual marking information specified in the contract.</P>
          <P>(14) Item No. Enter the item number used in the contract. Use a valid 4 or 6 character line item number under the Uniform Contract Line Item Numbering System (see 204.71). Line item numbers with 6 characters with numbers in the final two positions are not deliverable or billable.</P>
          <P>(15) Stock/part number/description.</P>
          <P>(i) Enter the following for each line item:</P>

          <P>(A) The national stock number (NSN) or noncatalog number. If the contract contains NSNs as well as other identification (<E T="03">e.g.,</E>part numbers) the contractor should place the NSN information in the Stock Part Number field and the remaining numbers in the line item description field. The data entered in the NSN field must reflect the NSN of the material item being shipped and should be a valid NSN, 13 positions in length. In the “Type” drop-down field, select the corresponding type for the data entered. If no National Stock Number (NSN) or other valid “Type” is available, the word “NONE” may be entered for the Stock/Part Number, with a corresponding “Type” of any value other than NSN selected from the drop-down box.</P>
          <P>(B) In the description field, if required by the contract for control purposes, enter: The make, model, serial number, lot, batch, hazard indicator, or similar description.</P>
          <P>(C) The Military Standard Requisitioning and Issue Procedures (MILSTRIP) must be placed on the MILSTRIP Tab, not in the line item description field. Enter the MILSTRIP data for each CLIN when MILSTRIP data is identified in the contract.</P>
          <P>(ii) For service line items, select SV for “SERVICE” in the type field followed by as short a description as is possible in the description field. Some examples of service line items are maintenance, repair, alteration, rehabilitation, engineering, research, development, training, and testing. The “Ship To” code and the “Unit” will have to be filled out. The “Shipped To” code is the destination Service Acceptor Code for WAWF. If source inspected and accepted enter the service performance location as the “Ship To” code.</P>
          <P>(iii) For all contracts administered by the Defense Contract Management Agency, with the exception of fast pay procedures, enter the gross weight of the shipment.</P>
          <P>(iv) In the description field enter the following as appropriate (entries may be extended through Block 20).</P>
          <P>(A) Enter in capital letters any special handling instructions/limits for material environmental control, such as temperature, humidity, aging, freezing, shock, etc.</P>

          <P>(B) When a shipment is chargeable to Navy appropriation 17X4911, enter the appropriation, bureau control number (BCN), and authorization accounting activity (AAA) number (<E T="03">e.g.,</E>17X4911-14003-104).</P>
          <P>(C) When the Navy transaction type code (TC), “2T” or “7T” is included in the appropriation data, enter “TC 2T” or “TC 7T.”</P>
          <P>(D) When an NSN is required by but not cited in a contract and has not been furnished by the Government, the contractor may make shipment without the NSN at the direction of the contracting officer. Enter the authority for such shipment.</P>
          <P>(E) When Government furnished property (GFP) is included with or incorporated into the line item, enter the letters “GFP.”</P>

          <P>(F) On shipments of Government furnished aeronautical equipment (GFAE) under Air Force contracts, enter the assignment AERNO control number,<E T="03">e.g.,</E>“AERNO 60-6354.”</P>
          <P>(G) For items shipped with missing components, enter and complete the following:</P>
          
          <FP>“Item(s) shipped short of the following component(s): NSN or comparable identification ____, Quantity ____, Estimated Value ____, Authority ____”</FP>
          <P>(H) When shipment is made of components which were short on a prior shipment, enter and complete the following:</P>
          <P>“These components were listed as shortages on shipment number ____, date shipped ____”</P>
          <P>(I) When shipments involve drums, cylinders, reels, containers, skids, etc., designated as returnable under contract provisions, enter and complete the following:</P>
          <P>“Return to ____, Quantity ____, Item ____, Ownership (Government/contractor).”</P>
          <P>(J) Enter the total number of shipping containers, the type of containers, and the container number(s) assigned for the shipment.</P>
          <P>(K) On foreign military sales (FMS) shipments, enter the special markings, and FMS case identifier from the contract. Also enter the gross weight.</P>
          <P>(L) When test/evaluation results are a condition of acceptance and are not available prior to shipment, the following note shall be entered if the shipment is approved by the contracting officer:</P>
          <P>“Note: Acceptance and payment are contingent upon receipt of approved test/evaluation results.”</P>
          <P>The contracting officer will advise—</P>
          <P>
            <E T="03">(1)</E>The consignee of the results (approval/disapproval); and</P>
          <P>
            <E T="03">(2)</E>The contractor to withhold invoicing pending attachment of the approved test/evaluation results.</P>
          <P>(M) For clothing and textile contracts containing a bailment clause, enter the words “GFP UNIT VALUE.”</P>
          <P>(N) When the initial unit incorporating an approved value engineering change proposal (VECP) is shipped, enter the following statement:</P>
          
          <FP>This is the initial unit delivered which incorporates VECP No. ____, Contract Modification No. ____, dated ____</FP>
          <P>(16) Quantity shipped/received.</P>

          <P>(i) Enter the quantity shipped, using the unit of measure in the contract for payment. When a second unit of measure is used for<PRTPAGE P="58129"/>purposes other than payment, enter the appropriate quantity in the description field.</P>
          <P>(ii) On the final shipment of a line item of a contract containing a clause permitting a variation of quantity and an underrun condition exists, the prime contractor shall choose the Ship Advice Code “Z”. Where the final shipment is from other than the prime contractor's plant and an underrun condition exists, the prime contractor may elect to direct the subcontractor making the final shipment to choose the Ship Advice Code “Z”;</P>
          <P>(iii) When the Government is performing destination acceptance the acceptor should enter actual quantity received in apparent good condition in the “Qty. Accepted” field of the Acceptor Line Item Tab.</P>
          <P>(17) Unit of measure. Enter the abbreviation of the unit measure as indicated in the contract for payment. Where a second unit of measure is indicated in the contract for purposes other than payment or used for shipping purposes, enter the second unit of measure in the description field. Authorized abbreviations are listed in MIL-STD-129, Marking for Shipping and Storage and in the WAWF Unit of Measure Table Link. For example, LB for pound, SH for sheet.</P>
          <P>(18) Unit price. The contractor may, at its option, enter unit prices on all WAWF RR copies, except as a minimum:</P>
          <P>(i) The contractor shall enter unit prices for each item of property fabricated or acquired for the Government and delivered to a contractor as Government furnished property (GFP). Get the unit price from Section B of the contract. If the unit price is not available, use an estimate. The estimated price should be the contractor's estimate of what the items will cost the Government. When the price is estimated, enter “Estimated Unit Price” in the description field. However, if the contract has Item Unique Identification (IUID) requirements and the receiving report is being processed in WAWF the unit price represents the acquisition cost that will be passed to the IUID registry. Therefore, the unit price is required (see the clause at DFARS 252.211-7003, Item Identification and Valuation). When delivering GFP via WAWF to another contractor, WAWF will initiate a property transfer if the vendor who is initiating the WAWF RR is also registered as a vendor property shipper in WAWF and the vendor receiving the property is also a vendor property receiver in WAWF.</P>
          <P>(ii) For clothing and textile contracts containing a bailment clause, enter the cited Government furnished property unit value as “GFP UNIT VALUE” in the description field.</P>
          <P>(19) Amount. WAWF will calculate and populate the amount by multiplying the unit price times the quantity.</P>
          <P>(20) Contract Quality Assurance (CQA).</P>
          <P>(i) The words “conform to contract” contained in the text above the signature block in the WAWF RR Header Tab relate to quality and to the quantity of the items on the report. Enter notes taking exception in Misc. Info Tab comment field or on attached supporting documents with an appropriate block cross-reference.</P>
          <P>(ii) When a shipment is authorized under an alternative release procedure, contractors will execute the alternative release procedure in WAWF by including the appropriate indicator in the electronic transaction rather than through inclusion or attachment of the text of the certificate. The alternative release procedure only provides for release of shipment; Government acceptance must still be indicated by a Government official's signature on the WAWF RR.</P>
          <P>(iii) When contract terms provide for use of Certificate of Conformance and shipment is made under these terms, contractors will execute Certificates in WAWF by including the appropriate indicator in the electronic transaction rather than through inclusion or attachment of the text of the certificate. Government acceptance must still be indicated by a Government official's signature on the WAWF RR.</P>
          <P>(iv) Origin.</P>
          <P>(A) The authorized Government representative must:—</P>
          <P>
            <E T="03">(1)</E>Place an “X” in the appropriate CQA and/or acceptance box(es) to show origin CQA and/or acceptance; and</P>
          <P>
            <E T="03">(2)</E>Sign and date.</P>
          <P>WAWF will enter the typed, stamped, or printed name, title, email address, and commercial telephone number.</P>
          <P>(B) When fast pay procedures apply, the contractor or subcontractor shall select “FAST PAY” when creating the WAWF RR. When CQA is required, the authorized Government representative shall execute the block as required by paragraph (A).</P>
          <P>(v) Destination. When CQA and acceptance or acceptance is at destination, the authorized Government representative must—</P>
          <P>(A) Place an “X” in the appropriate box(es); and</P>
          <P>(B) Sign and date.</P>
          <P>WAWF will enter the typed, stamped, or printed name, title, email address, and commercial telephone number.</P>
          <P>(21) Contractor use only. MISC. INFO. Self explanatory.</P>
          <HD SOURCE="HD2">F-302Mode/method of shipment codes.</HD>
          <GPOTABLE CDEF="xls20,r100" COLS="2" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Code</CHED>
              <CHED H="1">Description</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">A</ENT>
              <ENT>Motor, truckload.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">B</ENT>
              <ENT>Motor, less than truckload.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">C</ENT>
              <ENT>Van (unpacked, uncrated personal or Government property).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">D</ENT>
              <ENT>Driveaway, truckaway, towaway.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">E</ENT>
              <ENT>Bus.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">F</ENT>
              <ENT>Air Mobility Command (Channel and Special Assignment Airlift Mission).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">G</ENT>
              <ENT>Surface parcel post.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">H</ENT>
              <ENT>Air parcel post.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">I</ENT>
              <ENT>Government trucks, for shipment outside local delivery area.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">J</ENT>
              <ENT>Air, small package carrier.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">K</ENT>
              <ENT>Rail, carload.<SU>1</SU>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="01">L</ENT>
              <ENT>Rail, less than carload.<SU>1</SU>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="01">M</ENT>
              <ENT>Surface, freight forwarder.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">N</ENT>
              <ENT>LOGAIR.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">O</ENT>
              <ENT>Organic military air (including aircraft of foreign governments).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">P</ENT>
              <ENT>Through Government Bill of Lading (TGBL).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Q</ENT>
              <ENT>Commercial air freight (includes regular and expedited service provided by major airlines; charters and air taxis).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">R</ENT>
              <ENT>European Distribution System or Pacific Distribution System.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">S</ENT>
              <ENT>Scheduled Truck Service (STS) (applies to contract carriage, guaranteed traffic routings and/or scheduled service).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">T</ENT>
              <ENT>Air freight forwarder.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">U</ENT>
              <ENT>QUICKTRANS.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">V</ENT>
              <ENT>SEAVAN.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">W</ENT>
              <ENT>Water, river, lake, coastal (commercial).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">X</ENT>
              <ENT>Bearer, walk-thru (customer pickup of material).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Y</ENT>
              <ENT>Military Intratheater Airlift Service.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Z</ENT>
              <ENT>Military Sealift Command (MSC) (controlled contract or arranged space).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">2</ENT>
              <ENT>Government watercraft, barge, lighter.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">3</ENT>
              <ENT>Roll-on Roll-off (RORO) service.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">4</ENT>
              <ENT>Armed Forces Courier Service (ARFCOS).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5</ENT>
              <ENT>Surface, small package carrier.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">6</ENT>
              <ENT>Military official mail (MOM).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">7</ENT>
              <ENT>Express mail.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">8</ENT>
              <ENT>Pipeline.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">9</ENT>
              <ENT>Local delivery by Government or commercial truck (includes on base transfers; deliveries between air, water, or motor terminals; and adjacent activities). Local delivery areas are identified in commercial carriers' tariffs which are filed and approved by regulatory authorities.</ENT>
            </ROW>
            <TNOTE>
              <SU>1</SU>Includes trailer/container-on-flat-car (excluding SEAVAN).</TNOTE>
          </GPOTABLE>
          <HD SOURCE="HD2">F-303Consolidated shipments.</HD>
          <P>When individual shipments are held at the contractor's plant for authorized transportation consolidation to a single bill of lading, the contractor may prepare the WAWF RR at the time of CQA or acceptance prior to the time of actual shipment.</P>
          <HD SOURCE="HD2">F-304Correction instructions.</HD>

          <P>Functionality for correcting a WAWF RR is being developed. Preparation instructions and training for corrections will be available at<E T="03">https://wawftraining.eb.mil</E>once the functionality is deployed. The instructions will be part of the vendor training.</P>
          <HD SOURCE="HD2">F-305Invoice instructions.</HD>

          <P>Contractors shall submit payment requests and receiving reports in electronic form, unless an exception in DFARS 232.7002 applies. Contractor submission of the material inspection and receiving information required by this appendix by using the WAWF electronic form (see paragraph (b) of the clause at DFARS 252.232-7003) fulfills the requirement for a DD Form 250 MIRR. Contractors should ensure the packaging documentation includes a Government signed receiving report when the contract requires origin inspection and acceptance. Contractors must include a signed document indicating material receipt and acceptance has occurred in the container with the exception of material shipments that are approved for Alternative Release Procedures (ARP).<PRTPAGE P="58130"/>
          </P>
          <HD SOURCE="HD2">F-306Packing list instructions.</HD>
          <P>Contractors may also use a WAWF processed RR as a packing list. WAWF provides options to print the RR. These printed RRs may also be used if a signed copy is required.</P>
          <P>(a) WAWF provides a print capability for its RR. The WAWF printed RR can be identified by its distinctive format and by the text “Please look in WAWF for signed copy” underneath the “RECEIVING REPORT” title at the top of each printed page. This printed copy can be used as a packing list. If needed, the signature can be verified by reviewing the signed RR in WAWF.</P>
          <P>(b) Contractors can also print a RR from their systems (not WAWF). If such a signed copy is required by the contractor, the contractor will print the WAWF RR only after a signature is applied by the Government Inspector or Acceptor in WAWF. Copies printed will be annotated with “\\original signed in WAWF\\” in lieu of the inspector/acceptor's signature.</P>
          <HD SOURCE="HD2">F-307Receiving instructions.</HD>
          <P>If CQA and acceptance or acceptance of supplies is required upon arrival at destination, see F-301(b)(20)(v) for instructions.</P>
          <HD SOURCE="HD1">Part 4—Preparation of the DD Form 250 and DD Form 250C</HD>
          <HD SOURCE="HD2">F-401Preparation instructions.</HD>
          <P>(a)<E T="03">General.</E>
          </P>
          <P>(1) Dates must use nine spaces consisting of the four digits of the year, three-position alphabetic month abbreviation, and two digits for the day. For example, 2000AUG07, 2000SEP24.</P>
          <P>(2) Addresses must consist of the name, street address/P.O. box, city, state, and ZIP code.</P>
          <P>(3) Enter to the right of and on the same line as the word “Code” in Blocks 9 through 12 and in Block 14—</P>
          <P>(i) The Commercial and Government Entity Handbook (H4/H8) code;</P>
          <P>(ii) The DoD activity address code (DoDAAC) as it appears in the DoD Activity Address Directory (DoDAAD), DoD 4000.25-6-M; or</P>
          <P>(iii) The Military Assistance Program Address Directory (MAPAD) code.</P>
          <P>(4) Enter the DoDAAC, CAGE (H4/H8), or MAPAD code in Block 13.</P>
          <P>(5) The data entered in the blocks at the top of the DD Form 250c must be identical to the comparable entries in Blocks 1, 2, 3, and 6 of the DD Form 250.</P>
          <P>(6) Enter overflow data from the DD Form 250 in Block 16 or in the body of the DD Form 250c with an appropriate cross-reference. Do not number or distribute additional DD Form 250c sheets, solely for continuation of Block 23 data as part of the MIRR.</P>
          <P>(7) Do not include classified information in the MIRR. MIRRs must not be classified.</P>
          <P>(b)<E T="03">Completion instructions.</E>
          </P>
          <P>(1) Block 1—Procurement instrument identification (Contract) NO. See paragraph F-301(b)(1).</P>
          <P>(2) Block 2—Shipment no. See F-301(b)(2), Shipment no. When the series is completely used, change the shipment number prefix and start with 0001.</P>
          <P>(3) Block 3—Date shipped. Enter the date the shipment is released to the carrier or the date the services are completed. If the shipment will be released after the date of CQA and/or acceptance, enter the estimated date of release. When the date is estimated, enter an “E” after the date. Do not delay distribution of the MIRR for entry of the actual shipping date. Reissuance of the MIRR is not required to show the actual shipping date (see F-403).</P>
          <P>(4) Block 4—B/L TCN. When applicable, enter—</P>
          <P>(i) The commercial or Government bill of lading number after “B/L;”</P>
          <P>(ii) The transportation control number after “TCN” (when a TCN is assigned for each line item on the DD Form 250 under Block 16 instructions, insert “See Block 16”); and</P>
          <P>(iii) The initial (line haul) mode of shipment code in the lower right corner of the block (see F-402).</P>
          <P>(5) Block 5—Discount terms.</P>
          <P>(i) The contractor may enter the discount in terms of percentages on all copies of the MIRR.</P>
          <P>(ii) Use the procedures in F-406 when the MIRR is used as an invoice.</P>
          <P>(6) Block 6—Invoice no./date.</P>
          <P>(i) The contractor may enter the invoice number and actual or estimated date of invoice submission on all copies of the MIRR. When the date is estimated, enter an “E” after the date. Do not correct MIRRs other than invoice copies to reflect the actual date of invoice submission.</P>
          <P>(ii) Use the procedures in F-406 when the MIRR is used as an invoice.</P>
          <P>(7) Block 7—Page/of. Consecutively number the pages of the MIRR. On each page enter the total number of pages of the MIRR.</P>
          <P>(8) Block 8—Acceptance point. Enter an “S” for Origin or “D” for destination.</P>
          <P>(9) Block 9—Prime contractor/code. Enter the code and address.</P>
          <P>(10) Block 10—Administered by/code. Enter the code and address of the contract administration office cited in the contract.</P>
          <P>(11) Block 11—Shipped from/code/fob.</P>
          <P>(i) Enter the code and address of the “Shipped From” location. If identical to Block 9, enter “See Block 9.”</P>
          <P>(ii) For performance of services line items which do not require delivery of items upon completion of services, enter the code and address of the location at which the services were performed. If the DD Form 250 covers performance at multiple locations, or if identical to Block 9, enter “See Block 9.”</P>
          <P>(iii) Enter on the same line and to the right of “FOB” an “S” for Origin or “D” for Destination as specified in the contract. Enter an alphabetic “O” if the “FOB” point cited in the contract is other than origin or destination.</P>
          <P>(iv) For destination or origin acceptance shipments involving discount terms, enter “DISCOUNT EXPEDITE” in at least one-half inch outline-type style letters across Blocks 11 and 12. Do not obliterate other information in these blocks.</P>
          <P>(12) Block 12—Payment will be made by/code. Enter the code and address of the payment office cited in the contract.</P>
          <P>(13) Block 13—Shipped to/code. Enter the code and address from the contract or shipping instructions.</P>
          <P>(14) Block 14—Marked for/code. Enter the code and address from the contract or shipping instructions. When three-character project codes are provided in the contract or shipping instructions, enter the code in the body of the block, prefixed by “Proj”; do not enter in the Code block.</P>
          <P>(15) Block 15—Item No. See paragraph F-301(b)(14) with the exception to F301(b)(2)(B)2 that line item numbers not in accordance with the Uniform Contract Line Item Numbering System may be entered without regard to positioning.</P>
          <P>(16) Block 16—Stock/part No./description.</P>
          <P>(i) Use single or double spacing between line items when there are less than four line items. Use double spacing when there are four or more line items. Enter the following for each line item:</P>
          <P>(A) The national stock number (NSN) or noncatalog number. Where applicable, include a prefix or suffix. If a number is not provided, or it is necessary to supplement the number, include other identification such as the manufacturer's name or Federal supply code (as published in Cataloging Handbook H4-1), and the part number. Show additional part numbers in parentheses or slashes. Show the descriptive noun of the item nomenclature and if provided, the Government assigned management/material control code. The contractor may use the following technique in the case of equal kind supply items. The first entry shall be the description without regard to kind. For example, “Shoe-Low Quarter-Black,” “Resistor,” “Vacuum Tube,” etc. Below this description, enter the contract line item number in Block 15 and Stock/Part number followed by the size or type in Block 16.</P>
          <P>(B) On the next printing line, if required by the contract for control purposes, enter: The make, model, serial number, lot, batch, hazard indicator, or similar description.</P>
          <P>(C) On the next printing lines enter—</P>
          <P>
            <E T="03">(1)</E>The MIPR number prefixed by “MIPR” or the MILSTRIP requisition number(s) when provided in the contract; or</P>
          <P>
            <E T="03">(2)</E>Shipping instructions followed on the same line (when more than one requisition is entered) by the unit for payment and the quantity shipped against each requisition.</P>
          <P>Example:</P>
          
          <FP>V04696-185-750XY19059A—EA 5</FP>
          <FP>N0018801776038XY3211BA—EA 200</FP>
          <FP>AT650803050051AAT6391J—EA 1000</FP>
          
          <P>(D) When a TCN is assigned for each line item, enter on the next line the transportation control number prefixed by “TCN.”</P>
          <P>(ii) For service line items, enter the word “SERVICE” followed by as short a description as is possible in no more than 20 additional characters. Some examples of service line items are maintenance, repair, alteration, rehabilitation, engineering, research, development, training, and testing. Do not complete Blocks 4, 13, and 14 when there is no shipment of material.</P>
          <P>(iii) For all contracts administered by the Defense Contract Management Agency, with the exception of fast pay procedures, enter and complete the following:</P>
          <FP>Gross Shipping Wt.<PRTPAGE P="58131"/>
          </FP>
          <FP>____________</FP>
          <FP>State weight in pounds only.</FP>
          <P>(iv) Starting with the next line, enter the following as appropriate (entries may be extended through Block 20). When entries apply to more than one line item in the MIRR, enter them only once after the last line item entry. Reference applicable line item numbers.</P>
          <P>(A) Enter in capital letters any special handling instructions/limits for material environmental control, such as temperature, humidity, aging, freezing, shock, etc.</P>

          <P>(B) When a shipment is chargeable to Navy appropriation 17X4911, enter the appropriation, bureau control number (BCN), and authorization accounting activity (AAA) number (<E T="03">e.g.,</E>17X4911-14003-104).</P>
          <P>(C) When the Navy transaction type code (TC), “2T” or “7T” is included in the appropriation data, enter “TC 2T” or “TC 7T.”</P>
          <P>(D) When an NSN is required by but not cited in a contract and has not been furnished by the Government, the contractor may make shipment without the NSN at the direction of the contracting officer. Enter the authority for such shipment.</P>
          <P>(E) When Government furnished property (GFP) is included with or incorporated into the line item, enter the letters “GFP.”</P>
          <P>(F) When shipment consists of replacements for supplies previously furnished, enter in capital letters “REPLACEMENT SHIPMENT.” (See F-401, Block 17, for replacement indicators.)</P>

          <P>(G) On shipments of Government furnished aeronautical equipment (GFAE) under Air Force contracts, enter the assignment AERNO control number,<E T="03">e.g.,</E>“AERNO 60-6354.”</P>
          <P>(H) For items shipped with missing components, enter and complete the following:</P>
          
          <FP>“Item(s) shipped short of the following component(s):</FP>
          <FP SOURCE="FP1-2">NSN or comparable identification ____, Quantity ____, Estimated Value ____, Authority ____”</FP>
          <FP>(I) When shipment is made of components which were short on a prior shipment, enter and complete the following:</FP>
          
          <FP>“These components were listed as shortages on shipment number ____, date shipped ____”</FP>
          <P>(J) When shipments involve drums, cylinders, reels, containers, skids, etc., designated as returnable under contract provisions, enter and complete the following:</P>
          
          <FP>“Return to ____, Quantity ____, Item ____, Ownership (Government/contractor).”</FP>
          <P>(K) Enter the total number of shipping containers, the type of containers, and the container number(s) assigned for the shipment.</P>
          <P>(L) On foreign military sales (FMS) shipments, enter the special markings, and FMS case identifier from the contract. Also enter the gross weight.</P>
          <P>(M) When test/evaluation results are a condition of acceptance and are not available prior to shipment, the following note shall be entered if the shipment is approved by the contracting officer:</P>
          
          <P>“Note: Acceptance and payment are contingent upon receipt of approved test/evaluation results.”</P>
          <P>The contracting officer will advise—</P>
          <P>
            <E T="03">(1)</E>The consignee of the results (approval/disapproval); and</P>
          <P>
            <E T="03">(2)</E>The contractor to withhold invoicing pending attachment of the approved test/evaluation results.</P>
          <P>(N) The copy of the DD Form 250 required to support payment for destination acceptance (top copy of those with shipment) or ARP origin acceptance shall be identified as follows: enter “PAYMENT COPY” in approximately one-half inch outline type style letters with “FORWARD TO BLOCK 12 ADDRESS” in approximately one-quarter inch letters immediately below. Do not obliterate any other entries.</P>
          <P>(O) For clothing and textile contracts containing a bailment clause, enter the words “GFP UNIT VALUE.”</P>
          <P>(P) When the initial unit incorporating an approved value engineering change proposal (VECP) is shipped, enter the following statement:</P>
          
          <FP>This is the initial unit delivered which incorporates VECP No. ____,  Contract Modification No. ____, dated ____</FP>
          <P>(17) Block 17—Quantity shipped/received.</P>
          <P>(i) Enter the quantity shipped, using the unit of measure in the contract for payment. When a second unit of measure is used for purposes other than payment, enter the appropriate quantity directly below in parentheses.</P>
          <P>(ii) On the final shipment of a line item of a contract containing a clause permitting a variation of quantity and an underrun condition exists, the prime contractor shall enter a “Z” below the last digit of the quantity. Where the final shipment is from other than the prime contractor's plant and an underrun condition exists, the prime contractor may elect either to—</P>
          <P>(A) Direct the subcontractor making the final shipment to enter a “Z” below the quantity; or</P>
          <P>(B) Upon determination that all subcontractors have completed their shipments, correct the DD Form 250 (see F-405) coving the final shipment of the line item from the prime contractor's plant by addition of a “Z” below the quantity. Do not use the “Z” on deliveries which equal or exceed the contract line item quantity.</P>
          <P>(iii) For replacement shipments, enter “A” below the last digit of the quantity, to designate first replacement, “B” for second replacement, etc. Do not use the final shipment indicator “Z” on underrun deliveries when a final line item shipment is replaced.</P>
          
          <GPOTABLE CDEF="s160" COLS="1" OPTS="L0,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1"/>
            </BOXHD>
            <ROW>
              <ENT I="21">17. QUANTITY</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
            <ROW>
              <ENT I="22"/>
            </ROW>
          </GPOTABLE>
          <FP>SHIP/REC'D</FP>
          
          <FP>1000</FP>
          
          <FP>(10)</FP>
          
          <FP>Z</FP>
          <P>(iv) If the quantity received is the same quantity shipped and all items are in apparent good condition, enter by a check mark. If different, enter actual quantity received in apparent good condition below quantity shipped and circle. The receiving activity will annotate the DD Form 250 stating the reason for the difference.</P>
          <P>(18) Block 18—Unit. Enter the abbreviation of the unit measure as indicated in the contract for payment. Where a second unit of measure is indicated in the contract for purposes other than payment or used for shipping purposes, enter the second unit of measure directly below in parentheses. Authorized abbreviations are listed in MIL-STD-129, Marking for Shipping and Storage. For example, LB for pound, SH for sheet.</P>
          <GPOTABLE CDEF="s160" COLS="1" OPTS="L0,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1"/>
            </BOXHD>
            <ROW>
              <ENT I="21">18. UNIT</ENT>
            </ROW>
            
            <ROW>
              <ENT I="01">LB</ENT>
            </ROW>
            
            <ROW>
              <ENT I="01">(SH)</ENT>
            </ROW>
            
          </GPOTABLE>
          <P>(19) Block 19—Unit price. The contractor may, at its option, enter unit prices on all MIRR copies, except as a minimum:</P>
          <P>(i) The contractor shall enter unit prices on all MIRR copies for each item of property fabricated or acquired for the Government and delivered to a contractor as Government furnished property (GFP). Get the unit price from Section B of the contract. If the unit price is not available, use an estimate. The estimated price should be the contractor's estimate of what the items will cost the Government. When the price is estimated, enter an “E” after the unit price.</P>
          <P>(ii) Use the procedures in F-406 when the MIRR is used as an invoice.</P>
          <P>(iii) For clothing and textile contracts containing a bailment clause, enter the cited Government furnished property unit value opposite “GFP UNIT VALUE” entry in Block 16.</P>
          <P>(iv) Price all copies of DD Forms 250 for FMS shipments with actual prices, if available. If actual price are not available, use estimated prices. When the price is estimated, enter an “E” after the price.</P>
          <P>(20) Block 20—AMOUNT. Enter the extended amount when the unit price is entered in Block 19.</P>
          <P>(21) Block 21—Contract quality assurance (CQA).</P>
          <P>(i) The words “conform to contract” contained in the printed statements in Blocks 21a and 21b relate to quality and to the quantity of the items on the report. Do not modify the statements. Enter notes taking exception in Block 16 or on attached supporting documents with an appropriate block cross-reference.</P>
          <P>(ii) When a shipment is authorized under alternative release procedure, attach or include the appropriate contractor signed certificate on the top copy of the DD Form 250 copies distributed to the payment office or attach or include the appropriate contractor certificate on the contract administration office copy when contract administration (Block 10 of the DD Form 250) is performed by the Defense Contract Management Agency.</P>

          <P>(iii) When contract terms provide for use of Certificate of Conformance and shipment is made under these terms, the contractor<PRTPAGE P="58132"/>shall enter in capital letters “CERTIFICATE OF CONFORMANCE” in Block 21a on the next line following the CQA and acceptance statements. Attach or include the appropriate contractor signed certificate on the top copy of the DD Form 250 copies distributed to the payment office or attach or include the appropriate certificate on the contract administration office copy when contract administration (Block 10 of the DD Form 250) is performed by the Defense Contract Management Agency. In addition, attach a copy of the signed certificate to, or enter on, copies of the MIRR sent with shipment.</P>
          <P>(iv) Origin.</P>
          <P>(A) The authorized Government representative must—</P>
          <P>
            <E T="03">(1)</E>Place an “X” in the appropriate CQA and/or acceptance box(es) to show origin CQA and/or acceptance. When the contract requires CQA at destination in addition to origin CQA, enter an asterisk at the end of the statement and an explanatory note in Block 16;</P>
          <P>
            <E T="03">(2)</E>Sign and date;</P>
          <P>
            <E T="03">(3)</E>Enter the typed, stamped, or printed name, title, mailing address, and commercial telephone number.</P>
          <P>(B) When alternative release procedures apply—</P>
          <P>
            <E T="03">(1)</E>The contractor or subcontractor shall complete the entries required under paragraph (A) and enter in capital letters “ALTERNATIVE RELEASE PROCEDURE” on the next line following the printed CQA/acceptance statement.</P>
          <P>
            <E T="03">(2)</E>When acceptance is at origin and contract administration is performed by an office other than the Defense Contract Management Agency, the contractor shall furnish the four payment office copies of the MIRR to the authorized Government representative for dating and signing of one copy and forwarding of all copies to the payment office.</P>
          <P>
            <E T="03">(3)</E>When acceptance is at origin and contract administration is performed by the Defense Contract Management Agency, furnish the contract administration office copy of the MIRR to the authorized Government representative for dating and signing and forwarding to the contract administration office (see F-501, Table 1).</P>
          <P>(C) When fast pay procedures apply, the contractor or subcontractor shall enter in capital letters “FAST PAY” on the next line following the printed CQA/acceptance statement. When CQA is required, the authorized Government representative shall execute the block as required by paragraph (A).</P>
          <P>(D) When Certificate of Conformance procedures apply, inspection or inspection and acceptance are at source, and the contractor's Certificate of Conformance is required, the contractor shall enter in capital letters “CERTIFICATE OF CONFORMANCE” as required by paragraph (b)(21)(iii) of this appendix.</P>
          <P>
            <E T="03">(1)</E>For contracts administered by an office other than the Defense Contract Management Agency, furnish the four payment office copies of the MIRR to the authorized Government representative for dating and signing of one copy, and forwarding of all copies to the payment office.</P>
          <P>
            <E T="03">(2)</E>For contracts administered by the Defense Contract Management Agency, furnish the contract administration office copy of the MIRR to the authorized Government representative for dating and signing and forwarding to the contract administration office (see F-401, Table 1).</P>
          <P>
            <E T="03">(3)</E>When acceptance is at destination, no entry shall be made other than “CERTIFICATE OF CONFORMANCE.”</P>
          <P>(v) Destination.</P>
          <P>(A) When acceptance at origin is indicated in Block 21a, make no entries in Block 21b.</P>
          <P>(B) When CQA and acceptance or acceptance is at destination, the authorized Government representative must—</P>
          <P>
            <E T="03">(1)</E>Place an “X” in the appropriate box(es);</P>
          <P>
            <E T="03">(2)</E>Sign and date; and</P>
          <P>
            <E T="03">(3)</E>Enter typed, stamped, or printed name, title, mailing address, and commercial telephone number.</P>
          <P>(C) When “ALTERNATIVE RELEASE PROCEDURE” is entered in Block 21a and acceptance is at destination, the authorized Government representative must complete the entries required by paragraph (b)(21)(v)(B) of this appendix.</P>
          <P>(D) Forward the executed payment copy or MILSCAP format identifier PKN or PKP to the payment office cited in Block 12 within four work days (five days when MILSCAP Format is used) after delivery and acceptance of the shipment by the receiving activity. Forward one executed copy of the final DD Form 250 to the contract administration office cited in Block 10 for implementing contract closeout procedures.</P>
          <P>(E) When “FAST PAY” is entered in Block 21a, make no entries in this block.</P>
          <P>(22) Block 22—Receiver's use. The authorized representative of the receiving activity (Government or contractor) must use this block to show receipt, quantity, and condition. The authorized representative must—</P>
          <P>(i) Enter the date the supplies arrived. For example, when off-loading or in-checking occurs subsequent to the day of arrival of the carrier at the installation, the date of the carrier's arrival is the date received for purposes of this block;</P>
          <P>(ii) Sign; and</P>
          <P>(iii) Enter typed, stamped, or printed name, title, mailing address, and commercial telephone number.</P>
          <P>(23) Block 23—Contractor use only. Self explanatory.</P>
          <HD SOURCE="HD2">F-402Mode/method of shipment codes.</HD>
          <P>See paragraph F-302.</P>
          <HD SOURCE="HD2">F-403Consolidated shipments.</HD>
          <P>When individual shipments are held at the contractor's plant for authorized transportation consolidation to a single bill of lading, the contractor may prepare the DD Forms 250 at the time of CQA or acceptance prior to the time of actual shipment (see Block 3).</P>
          <HD SOURCE="HD2">F-404Multiple consignee instructions.</HD>
          <P>The contractor may prepare one MIRR when the identical line item(s) of a contract are to be shipped to more than one consignee, with the same or varying quantities, and the shipment requires origin acceptance. Prepare the MIRR using the procedures in this appendix with the following changes:</P>
          <P>(a) Blocks 2, 4, 13, and, if applicable, 14—Enter “See Attached Distribution List.”</P>
          <P>(b) Block 15—The contractor may group item numbers for identical stock/part number and description.</P>
          <P>(c) Block 17—Enter the “total” quantity shipped by line item or, if applicable, grouped identical line items.</P>
          <P>(d) Use the DD Form 250c to list each individual “Shipped To” and “Marked For” with—</P>
          <P>(1) Code(s) and complete shipping address and a sequential shipment number for each;</P>
          <P>(2) Line item number(s);</P>
          <P>(3) Quantity;</P>
          <P>(4) MIPR number(s), preceded by “MIPR,” or the MILSTRIP requisition number, and quantity for each when provided in the contract or shipping instructions; and</P>
          <P>(5) If applicable, bill of lading number, TCN, and mode of shipment code.</P>
          <P>(e) The contractor may omit those distribution list pages of the DD Form 250c that are not applicable to the consignee. Provide a complete MIRR for all other distribution.</P>
          <HD SOURCE="HD2">F-405Correction instructions.</HD>
          <P>Make a new revised MIRR or correct the original when, because of errors or omissions, it is necessary to correct the MIRR after distribution has been made. Use data identical to that of the original MIRR. Do not correct MIRRs for Blocks 19 and 20 entries. Make the corrections as follows—</P>
          <P>(a) Circle the error and place the corrected information in the same block; if space is limited, enter the corrected information in Block 16 referencing the error page and block. Enter omissions in Block 16 referencing omission page and block. For example—</P>
          <GPOTABLE CDEF="xl50,r50" COLS="2" OPTS="L0,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1" O="L">2. SHIPMENT NO.</CHED>
              <CHED H="1" O="L">17. QUANTITY</CHED>
            </BOXHD>
            <ROW>
              <ENT I="22"/>
              <ENT>SHIP/REC'D</ENT>
            </ROW>
            
            <ROW>
              <ENT I="01">(AAA0001)</ENT>
              <ENT/>
            </ROW>
            
            <ROW>
              <ENT I="22"/>
              <ENT>19</ENT>
            </ROW>
            
            <ROW>
              <ENT I="05">See Block 16</ENT>
              <ENT>(17)</ENT>
            </ROW>
            
            <ROW RUL="s">
              <ENT I="05">__________</ENT>
              <ENT>__________</ENT>
            </ROW>
            
            <TNOTE>16. STOCK/PART NO. DESCRIPTION</TNOTE>
            
            <TNOTE>CORRECTIONS:</TNOTE>
            
            <TNOTE>Refer Block 2: Change shipment No. AAA001 to AAA0010 on all pages of the MIRR.</TNOTE>
            
            <TNOTE>Refer Blocks 15, 16, 17, and 18, page 2: Delete in entirety Line Item No. 0006. This item was not shipped.</TNOTE>
          </GPOTABLE>
          <P>(b) When corrections have been made to entries for line items (Block 15) or quantity (Block 17), enter the words “CORRECTIONS HAVE BEEN VERIFIED” on page 1. The authorized Government representative will date and sign immediately below the statement. This verification statement and signature are not required for other corrections.</P>

          <P>(c) Clearly mark the pages of the MIRR requiring correction with the words “CORRECTED COPY.” Avoid obliterating any other entries. Where corrections are<PRTPAGE P="58133"/>made only on continuation sheets, also mark page number 1 with the words “CORRECTED COPY.”</P>
          <P>(d) Page 1 and only those continuation pages marked “CORRECTED COPY” shall be distributed to the initial distribution. A complete MIRR with corrections shall be distributed to new addressee(s) created by error corrections.</P>
          <HD SOURCE="HD2">F-406Invoice instructions.</HD>
          <P>(a) Contractors shall submit payment requests and receiving reports in electronic form, unless an exception in DFARS 232.7002 applies. Contractor submission of the material inspection and receiving information required by this appendix by using the WAWF electronic form (see paragraph (b) of the clause at DFARS 252.232-7003) fulfills the requirement for an MIRR.</P>
          <P>(b) If the contracting officer authorizes the contractor to submit an invoice in paper form, the Government encourages, but does not require, the contractor to use the MIRR as an invoice, in lieu of a commercial form. If commercial forms are used, identify the related MIRR shipment number(s) on the form. If using the MIRR as an invoice, prepare the MIRR and forward the required number of copies to the payment office as follows:</P>
          <P>(1) Complete Blocks 5, 6, 19, and 20. Block 6 shall contain the invoice number and date. Column 20 shall be totaled.</P>

          <P>(2) Mark in letters approximately one inch high, first copy: “ORIGINAL INVOICE,” for all invoice submissions; and three copies: “INVOICE COPY,” when the payment office requires four copies. Questions regarding the appropriate number of copies (<E T="03">i.e.,</E>one or four) should be directed to the applicable payment office.</P>
          <P>(3) Forward the appropriate number of copies to the payment office (Block 12 address), except when acceptance is at destination and a Navy finance office will make payment, forward to destination.</P>
          <P>(4) Separate the copies of the MIRR used as an invoice from the copies of the MIRR used as a receiving report.</P>
          <HD SOURCE="HD2">F-407Packing list instructions.</HD>
          <P>Contractors may use copies of the MIRR as a packing list. The packing list copies are in addition to the copies of the MIRR required for standard distribution (see F-501). Mark them “PACKING LIST.”</P>
          <HD SOURCE="HD2">F-408Receiving instructions.</HD>
          <P>When the MIRR is used for receiving purposes, local directives shall prescribe procedures. If CQA and acceptance or acceptance of supplies is required upon arrival at destination, see F-401(b)(21)(v) for instructions.</P>
          <HD SOURCE="HD1">PART 5—Distribution of Wide Area Workflow Receiving Report (WAWF RR), DD Form 250 and DD Form 250C</HD>
          <HD SOURCE="HD2">F-501Distribution of WAWF RR.</HD>
          <P>Use of the WAWF electronic form satisfies the distribution requirements of this section, except for the copies required to accompany shipment.</P>
          <HD SOURCE="HD2">F-502Distribution of DD FORM 250 AND DD FORM 250C.</HD>
          <P>(a) The contractor is responsible for distributing the DD Form 250, Material Inspection and Receiving Report (MIRR) including mailing and payment of postage.</P>
          <P>(b) Contractors shall distribute MIRRs using the instructions in Tables 1 and 2.</P>
          <P>(c) Contractors shall distribute MIRRs on non-DoD contracts using this appendix as amended by the contract.</P>
          <P>(d) Contractors shall make distribution promptly, but no later than the close of business of the work day following—</P>
          <P>(1) Signing of the DD Form 250 (Block 21a) by the authorized Government representative; or</P>
          <P>(2) Shipment when authorized under terms of alternative release, certificate of conformance, or fast pay procedures; or</P>
          <P>(3) Shipment when CQA and acceptance are to be performed at destination.</P>
          <P>(e) Do not send the consignee copies (via mail) on overseas shipments to port of embarkation (POE). Send them to consignee at APO/FPO address.</P>
          <P>(f) Copies of the MIRR forwarded to a location for more than one recipient shall clearly identify each recipient.</P>
          <HD SOURCE="HD1">Material Inspection And Receiving Report</HD>
          <GPOTABLE CDEF="s200,10" COLS="2" OPTS="L2,p1,8/9,i1">
            <TTITLE>Table 1—Standard Distribution</TTITLE>
            <BOXHD>
              <CHED H="1"/>
              <CHED H="1"/>
            </BOXHD>
            <ROW>
              <ENT I="01">With Shipment*</ENT>
              <ENT>2</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Consignee (via mail)</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(For Navy procurement, include unit price)</ENT>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(For foreign military sales, consignee copies are not required)</ENT>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="01">Contract Administration Office (CAO)</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(Forward direct to address in Block 10 except when addressee is a Defense Contract Management Agency (DCMA) office and a certificate of conformance or the alternative release procedures (see F-301, Block 21) is involved, and acceptance is at origin; then, forward through the authorized Government representative.)</ENT>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="01" O="xl">Purchasing Office</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Payment Office **</ENT>
              <ENT>2</ENT>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(Forward direct to address in Block 12 except—</ENT>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="05" O="xl">(i) When address in Block 10 is a DCMA office and payment office in Block 12 is the Defense Finance and Accounting Service, Columbus Center, do not make distribution to the Block 12 addressee;</ENT>
            </ROW>
            <ROW>
              <ENT I="05" O="xl">(ii) When address in Block 12 is the Defense Finance and Accounting Service, Columbus Center/Albuquerque Office (DFAS-CO/ALQ), Kirtland AFB, NM, attach only one copy to the required number of copies of the contractor's invoice;</ENT>
            </ROW>
            <ROW>
              <ENT I="05" O="xl">(iii) When acceptance is at destination and a Navy finance office will make payment, forward to destination; and</ENT>
            </ROW>
            <ROW>
              <ENT I="05" O="xl">(iv) When a certificate of conformance or the alternative release procedures (see F-301, Block 21) are involved and acceptance is at origin, forward the copies through the authorized Government representative.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">ADP Point for CAO (applicable to Air Force only)</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(When DFAS-CO/ALQ is the payment office in Block 12, send one copy to DFAS-CO/ALQ immediately after signature. If submission of delivery data is made electronically, distribution of this hard copy need not be made to DFAS-CO/ALQ.)</ENT>
              <ENT O="xl"/>
            </ROW>
            <ROW>
              <ENT I="01">CAO of Contractor Receiving GFP</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="03" O="xl">(For items fabricated or acquired for the Government and shipped to a contractor as Government furnished property, send one copy directly to the CAO cognizant of the receiving contractor, ATTN: Property Administrator (see DoD 4105.59-H).)</ENT>
              <ENT O="xl"/>
            </ROW>
            <TNOTE>* Attach as follows:</TNOTE>
            <TNOTE>** Payment by Defense Finance and Accounting Service, Columbus Center will be based on the source acceptance copies of DD Forms 250 forwarded to the contract administration office.</TNOTE>
          </GPOTABLE>
          <GPOTABLE CDEF="s100,r100" COLS="2" OPTS="L2,tp0,i1">
            <BOXHD>
              <CHED H="1">Type of shipment</CHED>
              <CHED H="1">Location</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Carload or truckload</ENT>
              <ENT>Affix to the shipment where it will be readily visible and available upon receipt.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Less than carload or truckload</ENT>
              <ENT>Affix to container number one or container truckload bearing lowest number.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mail, including parcel post</ENT>
              <ENT>Attach to outside or include in the package. Include a copy in each additional package of multi-package shipments.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="58134"/>
              <ENT I="01">Pipeline, tank car, or railroad cars for coal movements</ENT>
              <ENT>Forward with consignee copies.</ENT>
            </ROW>
          </GPOTABLE>
          <GPOTABLE CDEF="s100,r100,14" COLS="3" OPTS="L2,i1">
            <TTITLE>Material Inspection and Receiving Report Table 2—Special Distribution</TTITLE>
            <BOXHD>
              <CHED H="1">As required</CHED>
              <CHED H="1">Address</CHED>
              <CHED H="1">Number of<LI>copies</LI>
              </CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Each: Navy Status Control Activity, Army, Air Force, DLA Inventory Control Manager</ENT>
              <ENT>Address specified in contract</ENT>
              <ENT>* 1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Quality Assurance Representative</ENT>
              <ENT>Address specified by the assigned quality assurance representative</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Transportation Office issuing GBL (attach to GBL memorandum copy)</ENT>
              <ENT>CAO address unless otherwise specified in the contract</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Purchasing Office other than office issuing contract</ENT>
              <ENT>Address specified in the contract</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Foreign Military Sales Representative</ENT>
              <ENT>Address specified in the contract</ENT>
              <ENT>8</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Military Assistance Advisory Group (Grant Aid shipments)</ENT>
              <ENT>U.S. Military Advisory Group, Military Attache, Mission, or other designated agency address as specified in the contract</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Army Foreign Military Sales</ENT>
              <ENT>Commander, U.S. Army Security Assistance Command, ATTN: AMSAC-OL, 54 “M” Avenue, Suite 1, New Cumberland, PA 17070-5096</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Air Force On shipments of new production of aircraft and missiles, class 1410 missiles, 1510 aircraft (fixed wing, all types), 1520 aircraft (rotary wing), 1540 gliders, 1550 target drones</ENT>
              <ENT>HQ Air Force Materiel Command, LGX-AVDO, Area A, Building 262, Room N142, 4375 Chidlaw Road, Wright-Patterson AFB, OH 45433-5006</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">When above items are delivered to aircraft modification centers</ENT>
              <ENT>DCMA</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Foreign Military Sales/Military Assistance Program (Grant Aid) shipments to Canada</ENT>
              <ENT>National Defence Headquarters, Ottawa, Ontario Canada, K1A OK4 ATTN: DPSUPS3</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Other than Canada</ENT>
              <ENT>Address in the contract</ENT>
              <ENT>1</ENT>
            </ROW>
            <ROW>
              <ENT I="01">When consignee is an Air National Guard Activity</ENT>
              <ENT>Consignee address (Block 13), ATTN: Property Officer</ENT>
              <ENT>3</ENT>
            </ROW>
            <ROW>
              <ENT I="21">Navy</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Navy Foreign Military Sales</ENT>
              <ENT>Naval Inventory Control Point Deputy Commander for International Programs (NAVICP Code P761), 700 Robbins Avenue, Philadelphia, PA 19111-5095</ENT>
              <ENT>2</ENT>
            </ROW>
            <ROW>
              <ENT I="01">When typed code (TC) 2T or 7T is shown in Block 16, or when shipment is consigned to another contractor's plant for a Government representative or when Block 16 indicates shipment includes GFP</ENT>
              <ENT>Naval Inventory Control Point (Code 0142) for aviation type material, 700 Robbins Avenue, Philadelphia, PA 19111-5098 and<LI>Naval Inventory Control Point (Code 0143) for all other material 5450 Carlisle Pike, PO Box 2020, Mechanicsburg, PA 17055-0788</LI>
              </ENT>
              <ENT>2</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bulk Petroleum Shipments</ENT>
              <ENT>Cognizant Defense Fuel Region (see Table 4)</ENT>
              <ENT>1</ENT>
            </ROW>
            <TNOTE>* Each addressee.</TNOTE>
          </GPOTABLE>
          <HD SOURCE="HD1">Part 6—Preparation of the DD Form 250-1 (Loading Report)</HD>
          <P>
            <E T="03">F-601 Instructions.</E>
          </P>
          <P>Prepare the DD Form 250-1 using the following instructions when applied to a tanker or barge cargo lifting. If space is limited, use abbreviations. The block numbers correspond to those on the form.</P>
          <P>(a) Block 1—Tanker/barge. Line out “TANKER” or “BARGE” as appropriate and place an “X” to indicate loading report.</P>
          <P>(b) Block 2—Inspection office. Enter the name and location of the Government office conducting the inspection.</P>
          <P>(c) Block 3—Report No. Number each form consecutively, starting with number 1, to correspond to the number of shipments made against the contract. If shipment is made from more than one location against the same contract, use this numbering system at each location.</P>
          <P>(d) Block 4—Agency placing order on shipper, city, state and/or local address (loading). Enter the applicable Government activity.</P>
          <P>(e) Block 5—Department. Enter military department owning product being shipped.</P>
          <P>(f) Block 6—Prime contract or P.O. No. Enter the contract or purchase order number.</P>
          <P>(g) Block 7—Name of prime contractor, city, state and/or local address (loading). Enter the name and address of the contractor as shown in the contract.</P>
          <P>(h) Block 8—Storage contract. Enter storage contract number if applicable.</P>
          <P>(i) Block 9—Terminal or refinery shipped from, city, state and/or local address. Enter the name and location of the contractor facility from which shipment is made. Also enter delivery point in this space as either “FOB Origin” or “FOB Destination.”</P>
          <P>(j) Block 10—Order No. on supplier. Enter number of the delivery order, purchase order, subcontract or suborder placed on the supplier.</P>
          <P>(k) Block 11—Shipped to: (receiving activity, city, state and/or local address). Enter the name and geographical address of the consignee as shown on the shipping order.</P>
          <P>(l) Block 12—B/L number. If applicable, enter the initials and number of the bill of lading. If a commercial bill of lading is later authorized to be converted to a Government bill of lading, show “Com. B/L to GB/L.”</P>
          <P>(m) Block 13—Reqn. or request No. Enter number and date from the shipping instructions.</P>
          <P>(n) Block 14—Cargo No. Enter the cargo number furnished by the ordering office.</P>
          <P>(o) Block 15—Vessel. Enter the name of tanker or barge.</P>
          <P>(p) Block 16—Draft arrival. Enter the vessel's draft on arrival.</P>
          <P>(q) Block 17—Draft sailing. Enter the vessel's draft on completion of loading.</P>
          <P>(r) Block 18—Previous two cargoes. Enter the type of product constituting previous two cargoes.</P>
          <P>(s) Block 19—Prior inspection. Leave blank.</P>
          <P>(t) Block 20—Condition of shore pipeline. Enter condition of line (full or empty) before and after loading.</P>

          <P>(u) Block 21—Appropriation (loading). Enter the appropriation number shown on the contract, purchase order or distribution plan. If the shipment is made from departmentally owned stock, show “Army,<PRTPAGE P="58135"/>Navy, or Air Force (as appropriate) owned stock.”</P>
          <P>(v) Block 22—Contract item no. Enter the contract item number applicable to the shipment.</P>
          <P>(w) Block 23—Product. Enter the product nomenclature and grade as shown in the contract or specification, the stock or class number, and the NATO symbol.</P>
          <P>(x) Block 24—Specifications. Enter the specification and amendment number shown in the contract.</P>
          <P>(y) Block 25—Statement of quantity. Enter in the “LOADED” column, the net barrels, net gallons, and long tons for the cargo loaded. NOTE: If more than<FR>1/2</FR>of 1 percent difference exists between the ship and shore quantity figures, the contractor shall immediately investigate to determine the cause of the difference. If necessary, prepare corrected documents; otherwise, put a statement in Block 28 as to the probable or actual cause of the difference.</P>
          <P>(z) Block 26—Statement of quality.</P>
          <P>(1) Under the heading “TESTS” list all inspection acceptance tests of the specification and any other quality requirements of the contract.</P>
          <P>(2) Under the heading “SPECIFICATION LIMITS” list the limits or requirements as stated in the specification or contract directly opposite each entry in the “TESTS” column. List waivers to technical requirements.</P>
          <P>(3) Under the heading “TEST RESULTS” list the test results applicable to the storage tank or tanks from which the cargo was lifted. If more than one storage tank is involved, list the tests applicable to each tank in separate columns headed by the tank number, the date the product in the tank was approved, and the quantity loaded from the tank. Each column shall also list such product characteristics as amount and type of corrosion inhibitor, etc.</P>

          <P>(aa) Block 27—Time statement. Line out “DISCHARGE” and “DISCHARGING.” Complete all applicable entries of the time statement using local time. Take these dates and times from either the vessel or shore facility log. The Government representative shall ensure that the logs are in agreement on those entries used. If the vessel and shore facility logs are not in agreement, the Government representative will explain the reasons in Block 28—REMARKS. Do not enter the date and time the vessel left berth on documents placed aboard the vessel. The date and time shall appear on all other copies. Express all dates in sequence of day, month, and year with the month spelled out or abbreviated (<E T="03">e.g.,</E>10 Sept. 67). The term FINISHED BALLAST DISCHARGE is meant to include all times needed to complete deballasting and mopping/drying of ship's tanks. The inspection of ship's tanks for loading is normally performed immediately upon completion of drying tanks.</P>
          <P>(bb) Block 28—Remarks. Use this space for reporting:</P>
          <P>(1) All delays, their cause and responsible party (vessel, shore facility, Government representative, or other).</P>
          <P>(2) Details of loading abnormalities such as product losses due to overflow, leaks, delivery of product from low level in shore tanks, etc.</P>
          <P>(3) In the case of multiple consignees, enter each consignee, the amount consigned to each, and if applicable, the storage contract numbers appearing on the delivery order.</P>
          <P>(4) When product title is vested in the U.S. Government, insert in capital letters “U.S. GOVERNMENT OWNED CARGO.” If title to the product remains with the contractor and inspection is performed at source with acceptance at destination, insert in capital letters “CONTRACTOR OWNED CARGO.”</P>
          <P>(5) Seal numbers and location of seals. If space is not adequate, place this information on the ullage report or an attached supplemental sheet.</P>
          <P>(cc) Block 29—Company or receiving terminal. Line out “OR RECEIVING TERMINAL” and get the signature of the supplier's representative.</P>
          <P>(dd) Block 30—Certification by government representative. Line out “discharged.” The Government representative shall date and sign the form to certify inspection and acceptance, as applicable, by the Government. The name of the individual signing this certification, as well as the names applied in Blocks 29 and 31, shall be typed or hand lettered. The signature in Block 30 must agree with the typed or lettered name to be acceptable to the paying office.</P>
          <P>(ee) Block 31—Certification by master or agent. Obtain the signature of the master of the vessel or its agent.</P>
          <HD SOURCE="HD1">Part 7—Preparation of the DD Form 250-1 (Discharge Report)</HD>
          <HD SOURCE="HD2">F-701Instructions.</HD>
          <P>Prepare the DD Form 250-1 using the following instructions when applied to a tanker or barge discharge. If space is limited, use abbreviations. The block numbers correspond to those on the form.</P>
          <P>(a) Block 1—Tanker/barge. Line out “TANKER” or “BARGE” as applicable and place an “X” to enter discharge report.</P>
          <P>(b) Block 2—Inspection office. Enter Government activity performing inspection on the cargo received.</P>
          <P>(c) Block 3—Report No. Leave blank.</P>
          <P>(d) Block 4—Agency placing order on shipper, city, state and/or local address (loading). Enter Government agency shown on loading report.</P>
          <P>(e) Block 5—Department. Enter Department owning product being received.</P>
          <P>(f) Block 6—Prime contract or P.O. No. Enter the contract or purchase order number shown on the loading report.</P>
          <P>(g) Block 7—Name of prime contractor, city, state and/or local address (loading). Enter the name and location of contractor who loaded the cargo.</P>
          <P>(h) Block 8—Storage contract. Enter the number of the contract under which material is placed in commercial storage where applicable.</P>
          <P>(i) Block 9—Terminal or refinery shipped from, city, state and/or local address. Enter source of cargo.</P>
          <P>(j) Block 10—Order No. on supplier. Make same entry appearing on loading report.</P>
          <P>(k) Block 11—Shipped to: (RECEIVING ACTIVITY, CITY, STATE AND/OR LOCAL ADDRESS). Enter receiving activity's name and location.</P>
          <P>(l) Block 12—B/L number. Enter as appears on loading report.</P>
          <P>(m) Block 13—Reqn. or request No. Leave blank.</P>
          <P>(n) Block 14—Cargo No. Enter cargo number shown on loading report.</P>
          <P>(o) Block 15—Vessel. Enter name of tanker or barge discharging cargo.</P>
          <P>(p) Block 16—Draft arrival. Enter draft of vessel upon arrival at dock.</P>
          <P>(q) Block 17—Draft sailing. Enter draft of vessel after discharging.</P>
          <P>(r) Block 18—Previous two cargoes. Leave blank.</P>
          <P>(s) Block 19—Prior inspection. Enter the name and location of the Government office which inspected the cargo loading.</P>
          <P>(t) Block 20—Condition of shore pipeline. Enter condition of line (full or empty) before and after discharging.</P>
          <P>(u) Block 21—Appropriation (loading). Leave blank.</P>
          <P>(v) Block 22—Contract item No. Enter the item number shown on the loading report.</P>
          <P>(w) Block 23—Product. Enter information appearing in Block 23 of the loading report.</P>
          <P>(x) Block 24—Specifications. Enter information appearing in Block 24 of the loading report.</P>
          <P>(y) Block 25—Statement of quantity. Enter applicable data in proper columns.</P>
          <P>(1) Take “LOADED” figures from the loading report.</P>
          <P>(2) Determine quantities discharged from shore tank gauges at destination.</P>
          <P>(3) If a grade of product is discharged at more than one point, calculate the loss or gain for that product by the final discharge point.</P>
          <P>Report amounts previously discharged on discharge reports prepared by the previous discharge points. Transmit volume figures by routine message to the final discharge point in advance of mailed documents to expedite the loss or gain calculation and provide proration data when more than one department is involved.</P>
          <P>(4) The loss or gain percentage shall be entered in the “PERCENT” column followed by “LOSS” or “GAIN,” as applicable.</P>
          <P>(5) On destination acceptance shipments, accomplish the “DISCHARGED” column only, unless instructed to the contrary.</P>
          <P>(z) Block 26—Statement of quality.</P>
          <P>(1) Under the heading “TESTS” enter the verification tests performed on the cargo preparatory to discharge.</P>
          <P>(2) Under “SPECIFICATION LIMITS” enter the limits, including authorized departures (if any) appearing on the loading report, for the tests performed.</P>
          <P>(3) Enter the results of tests performed under the heading “TEST RESULTS.”</P>

          <P>(aa) Block 27—Time statement. Line out “LOAD” and “LOADING.” Complete all applicable entries of the time statement using local time. Take the dates and times from either the vessel or shore facility log. The Government representative shall ensure that these logs are in agreement with entries used. If the vessel and shore facility logs are not in agreement, the Government representative will explain the reason(s) in Block 28—REMARKS. Do not enter the date and time the vessel left berth on documents placed aboard the vessel. The date and time shall<PRTPAGE P="58136"/>appear on all other copies. Express all dates in sequence of day, month, and year with the month spelled out or abbreviated (<E T="03">e.g.,</E>10 Sept. 67).</P>
          <P>(bb) Block 28—Remarks. Use this space for reporting important facts such as:</P>
          <P>(1) Delays, their cause, and responsible party (vessel, shore facility, Government representative, or others).</P>
          <P>(2) Abnormal individual losses contributing to the total loss. Enter the cause of such losses as well as actual or estimated volumes involved. Such losses shall include, but not be restricted to, product remaining aboard (enter tanks in which contained), spillages, line breaks, etc. Note where gravity group change of receiving tank contents results in a fictitious loss or gain. Note irregularities observed on comparing vessel ullages obtained at loading point with those at the discharge point if they indicate an abnormal transportation loss or contamination.</P>
          <P>(cc) Block 29—Company or receiving terminal. Line out “COMPANY OR.” Secure the signature of a representative of the receiving terminal.</P>
          <P>(dd) Block 30—Certification by government representative. Line out “loaded.” The Government representative shall date and sign the form to certify inspection and acceptance, as applicable, by the Government. The name of the individual signing the certification as well as the names applied in Blocks 29 and 31 shall be typed or hand lettered on the master or all copies of the form. The signature in Block 30 must agree with the typed or lettered name to be acceptable to the paying office.</P>
          <P>(ee) Block 31—Certification by master or agent. Obtain the signature of the master of the vessel or the vessel's agent.</P>
          <HD SOURCE="HD1">Part 8—Distribution of the DD Form 250-1</HD>
          <HD SOURCE="HD2">
            <E T="03">F-801Distribution.</E>
          </HD>
          <P>Follow the procedures at PGI F-801 for distribution of DD Form 250-1.</P>
          <HD SOURCE="HD2">
            <E T="03">F-802Corrected DD Form 250-1.</E>
          </HD>
          <P>Follow the procedures at PGI F-802 when corrections to DD Form 250-1 are needed.</P>
          
        </EXTRACT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23958 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Part 201</CFR>
        <RIN>RIN 0750-AH35</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Designation of a Contracting Officer's Representative (DFARS Case 2011-D037)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System; Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to clarify that a contracting officer's representative must be an employee, military or civilian, of the U.S. Government, a foreign government, or a North Atlantic Treaty Organization (NATO)/coalition partner, and that contractor personnel shall not serve as contracting officer's representatives.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Manuel Quinones, telephone 703-602-8383.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>This rule is based on a request from Headquarters NATO Training Mission—Afghanistan (NTM-A) to permit the designation of non-U.S. Government employees as contracting officer's representatives (CORs) in support of the NTM-A's efforts to train the Afghan National Security Force (ANSF). The NTM-A supports the growth of the ANSF through numerous activities including the contracting of civilian mentoring services. These contracts for mentoring services to the ANSF require the contractor to deploy teams throughout the joint area of operations and interact with non-U.S. coalition partners exclusively. To provide assurance that contractual requirements are being met, it is crucial that contract performance information be submitted to the contracting officer by those coalition units with insight of contractor activities.</P>
        <P>Contracting officers supporting contingency operations abroad require the flexibility to ensure the proper oversight of contract performance, such as at locations where there is no U.S. presence or the designation of a U.S. Government COR is not viable. This rule provides that flexibility by clarifying at DFARS 201.602-2 that a COR must be an employee, military or civilian, of the U.S. Government, a foreign government, or a NATO/coalition partner. CORs must meet all training and experience qualifications commensurate with the delegated responsibilities per DFARS 201.602-2(2)(ii). In addition, the rule makes clear that contractor personnel may not serve as CORs. Contractor personnel may, however, continue to perform technical oversight functions on behalf of the contracting officer, excluding those that are inherently governmental (see FAR 7.5).</P>
        <P>DoD has issued this rule as a final rule because this rule does not have a significant effect beyond the internal operating procedures of DoD and does not have a significant cost or administrative impact on contractors or offerors. Therefore, public comment is not required in accordance with 41 US.C. 1707.</P>
        <HD SOURCE="HD1">II. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders 12866 and 13563 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 is not a significant regulatory action and, therefore, was not subject to review under Section 6(b) of Executive Order 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act does not apply to this rule. This final rule does not constitute a significant DFARS revision within the meaning of FAR 1.501, and public comment is not required in accordance with 41. U.S.C. 1707.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>The final rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Part 201</HD>
          <P>Government Procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR part 201 is amended as follows:</P>
        <REGTEXT PART="201" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 201—FEDERAL ACQUISITION REGULATIONS SYSTEM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 48 CFR part 201 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="201" TITLE="48">
          <AMDPAR>2. Section 201.602-2 is amended to revise paragraph (2)(i) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>201.602-2</SECTNO>
            <SUBJECT>Responsibilities.</SUBJECT>
            <STARS/>
            <P>(2)  * * *<PRTPAGE P="58137"/>
            </P>
            <P>(i) Must be an employee, military or civilian, of the U.S. Government, a foreign government, or a North Atlantic Treaty Organization/coalition partner. In no case shall contractor personnel serve as CORs;</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23950 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 201, 209, 212, 215, 219, 232, 237, 243, 252, and Appendix I to Chapter 2</CFR>
        <RIN>RIN 0750-AG38</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Positive Law Codification of Title 41 U.S.C. (DFARS Case 2011-D036)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to conform references throughout the DFARS to the new Codification of Title 41, United States Code, “Public Contracts.”</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Amy Williams, 703-602-0328.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On January 4, 2011, Public Law 111-350 enacted a new codified version of Title 41, United States Code (U.S.C.), entitled “Public Contracts.” The purpose of this final rule is to update all references to Title 41 in the DFARS to conform to the recodification.</P>
        <P>DoD has issued a final rule because this rule does not have a significant effect beyond the internal operating procedures of DoD and does not have a significant cost or administrative impact on contractors or offerors. Therefore public comment is not required in accordance with 41 U.S.C. 1303.</P>
        <HD SOURCE="HD1">II. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders 12866 and 13563 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 is not a significant regulatory action and, therefore, was not subject to review under Section 6(b) of Executive Order 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act does not apply to this rule. This final rule does not constitute a significant DFARS revision within the meaning of FAR 1.501 and public comment is not required in accordance with 41 U.S.C. 1707.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>The rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 201, 209, 212, 215, 219, 232, 237, 243, 252, and Appendix I to Chapter 2</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 201, 209, 212, 215, 219, 232, 237, 243, 252 and appendix I to chapter II are amended as follows:</P>
        <REGTEXT PART="201" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 201, 209, 212, 215, 219, 232, 237, 243, 252, and appendix I to chapter II continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
          <PART>
            <HD SOURCE="HED">PART 201—FEDERAL ACQUISITION REGULATIONS SYSTEM</HD>
            <SECTION>
              <SECTNO>201.107</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>2. Amend section 201.107 by—</AMDPAR>
          <AMDPAR>(a) Removing “Section” from the introductory text and adding in its place “section”; and</AMDPAR>
          <AMDPAR>(b) Removing “425” from the introductory text and adding in its place “1304”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="201" TITLE="48">
          <SECTION>
            <SECTNO>201.304</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>3. Amend section 201.304(2) by—</AMDPAR>
          <AMDPAR>(a) Removing “Section” and adding in its place “section”; and</AMDPAR>
          <AMDPAR>(b) Removing “425” and adding in its place “1304”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="209" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 209—CONTRACTOR QUALIFICATIONS</HD>
            <SECTION>
              <SECTNO>209.406-2</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>4. Amend section 209.406-2(2) by—</AMDPAR>
          <AMDPAR>(a) Removing “Section” and adding in its place “section”;</AMDPAR>
          <AMDPAR>(b) Removing “(Pub. L. 110-181)”; and</AMDPAR>
          <AMDPAR>(c) Removing “423(e)(3)(A)(iii)” and adding in its place “2105(c)(1)(C)”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="212" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 212—ACQUISITION OF COMMERCIAL ITEMS</HD>
            <SECTION>
              <SECTNO>212.207</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>5. Amend section 212.207—</AMDPAR>
          <AMDPAR>(a) In paragraph (b)(i) by removing “403(12)(E)” and adding in its place “103”; and</AMDPAR>
          <AMDPAR>(b) In paragraph (b)(iii)(A) by removing “403(12)(F)” and adding in its place “103”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="215" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 215—CONTRACTING BY NEGOTIATION</HD>
          </PART>
          <AMDPAR>6. Revise the heading of section 215.403-1 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>215.403-1</SECTNO>
            <SUBJECT>Prohibition on obtaining cost or pricing data (10 U.S.C. 2306a and 41 U.S.C. chapter 35).</SUBJECT>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="219" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 219—SMALL BUSINESS PROGRAMS</HD>
            <SECTION>
              <SECTNO>219.703</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>7. Amend section 219.703(a) introductory text by—</AMDPAR>
          <AMDPAR>(a) Removing “46-48” and adding in its place “8502-8504”; and</AMDPAR>
          <AMDPAR>(b) Removing “Section” and adding in its place “section”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="232" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 232—CONTRACT FINANCING</HD>
            <SECTION>
              <SECTNO>232.803</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>8. Amend section 232.803(d) by removing “Section 3737(e) of the Revised Statutes (41 U.S.C. 15)” and adding in its place “41 U.S.C. 6305”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="237" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 237—SERVICE CONTRACTING</HD>
            <SECTION>
              <SECTNO>237.102-71</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>9. Amend section 237.102-71(a)(2) by removing “357(b)” and adding in its place “6701”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="243" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 243—CONTRACT MODIFICATIONS</HD>
            <SECTION>
              <SECTNO>243.204-71</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>10. Amend section 242.204-71(c) by removing “605(c)” and adding in its place “7103”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <PART>
            <PRTPAGE P="58138"/>
            <HD SOURCE="HED">PART 252—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
            <SECTION>
              <SECTNO>252.203-7000</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>11. Amend section 252.203-7000 by—</AMDPAR>
          <AMDPAR>(a) Removing the clause date of “(JAN 2009)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(b) In paragraph (a)(2)(i) introductory text, removing “403(16)” and adding in its place “131”; and</AMDPAR>
          <AMDPAR>(c) In paragraph (c), removing “423(e)(3)” and adding in its place “2105(c)”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <SECTION>
            <SECTNO>252.212-7001</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>12. Amend section 252.212-7001 by—</AMDPAR>
          <AMDPAR>(a) Removing the clause date of “(AUG 2011)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(b) In paragraph (b)(2) removing “Section” and adding in its place “section”;</AMDPAR>
          <AMDPAR>(c) In paragraph (b)(2) removing the word “note”.</AMDPAR>
          <SECTION>
            <SECTNO>252.219-7003</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>13. Amend section 252.219-7003 by—</AMDPAR>
          <AMDPAR>(a) Removing the clause date of “(OCT 2010)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(b) In paragraph (d), removing “46-48” and adding in its place “8502-8504”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <SECTION>
            <SECTNO>252.225-7001</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>14. Amend section 252.225-7001 by—</AMDPAR>
          <AMDPAR>(a) Removing the clause date of “(JAN 2009)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(b) In paragraph (b), removing “Section 10a-d” and adding in its place “chapter 83”; and</AMDPAR>
          <AMDPAR>(c) In paragraph (b) removing “431” and adding in its place “1907”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <SECTION>
            <SECTNO>252.227-7037</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>15. Amend section 252.227-7037 by—</AMDPAR>
          <AMDPAR>(a) Removing the clause date “(SEP 1999)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(b) In paragraph (e)(3), removing “601,<E T="03">et seq.”</E>and adding in its place “7101”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <HD SOURCE="HD1">APPENDIX I TO CHAPTER 2—[Amended]</HD>
          <AMDPAR>16. Amend section I-101.4 by removing “46” and adding in its place “8502”.</AMDPAR>
          
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23951 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE ;P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 204, 212, and 252</CFR>
        <RIN>RIN 0750-AH02</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement (DFARS); Alternative Line Item Structure (DFARS Case 2010-D017)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to establish a standard procedure for offerors to propose an alternative line item structure that reflects the offeror's business practices for selling and billing commercial items and initial provisioning spares for weapon systems</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Julian E. Thrash, 703-602-0310.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DoD published a proposed rule in the<E T="04">Federal Register</E>at 76 FR 21847 on April 19, 2011, to add DFARS language that provides offerors the opportunity to propose an alternative line item structure in solicitations for commercial items and initial provisioning spares. This DFARS change will allow offerors to provide information about their products that may not have been known to the Government prior to issuance of the solicitation. No public comments were received regarding the proposed rule.</P>
        <P>DoD identified the need to propose an alternative line item structure during process reviews and working group sessions that assessed destination-acceptance procedures. The process reviews performed by DoD cross-service working groups, which were chartered by the Defense Finance and Accounting System, examined issues causing problems in the receipt and acceptance phase for contract deliverables and payments.</P>

        <P>This group determined that the level of detail in the requirements description and line item structure is not always sufficient for delivery, payment, and subsequent inventory management of the items delivered. For example, the contract line item may be for a desktop computer, but the actual items delivered, invoiced, and inventoried may reflect a separate monitor, keyboard, and central processing unit. The resultant misalignment of transaction detail (<E T="03">i.e.,</E>contract line item, invoiced unit, delivery and inventory unit) is the cause of failures in the electronic processes of the DoD's business enterprise requiring manual intervention with potential delays in contractor payment.</P>
        <P>To address this recurring problem, this rule establishes and standardizes a process to enable offerors to propose changes in their offer to the solicitation's line item structure. Establishing such a process is a first step towards managing variation in these transactions by eliminating or reducing manual intervention.</P>
        <HD SOURCE="HD1">II. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, was not subject to review under section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>

        <P>DoD certifies that this final rule will not have a significant economic impact on 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>because the rule does not impose any additional requirements on small businesses. Further, this change does not add to, or delete from existing requirements or authorities for entities to include alternative line item structures in their offers. This rule is formalizing a process to facilitate offerors' ability to request changes to the line item structure.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>The rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <PRTPAGE P="58139"/>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 204, 212, and 252</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 204, 212, and 252 are amended as follows:</P>
        <REGTEXT PART="204" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 204, 212, and 252 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="204" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 204—ADMINISTRATIVE MATTERS</HD>
          </PART>
          <AMDPAR>2. Amend section 204.7103 by adding a new paragraph (g) to read as follows:</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="204" TITLE="48">
          <SECTION>
            <SECTNO>204.7103-1</SECTNO>
            <SUBJECT>Criteria for establishing.</SUBJECT>
            <STARS/>
            <P>(g) Certain commercial items and initial provisioning spares for weapons systems are requested and subsequently solicited using units of measure such as kit, set, or lot. However, there are times when individual items within that kit, set, or lot are not grouped and delivered in a single shipment. This creates potential contract administration issues with inspection, acceptance, and payment. In such cases, solicitations should be structured to allow offerors to provide information about products that may not have been known to the Government prior to solicitation and propose an alternate line item structure as long as the alternate is consistent with the requirements of 204.71, which provides explicit guidance on the use of contract line items and subline items, and with PGI 204.71.</P>
          </SECTION>
          <AMDPAR>3. Revise section 204.7109 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>204.7109</SECTNO>
            <SUBJECT>Solicitation provision and contract clause.</SUBJECT>
            <P>(a) Use the clause at 252.204-7006, Billing Instructions, in solicitations and contracts if Section G includes—</P>
            <P>(1) Any of the standard payment instructions at PGI 204.7108(d)(1) through (6); or</P>
            <P>(2) Other payment instructions, in accordance with PGI 204.7108(d)(12), that require contractor identification of the contract line item(s) on the payment request.</P>
            <P>(b) Use the provision at 252.204-7011, Alternative Line Item Structure, in solicitations for commercial items and initial provisioning spares.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="212" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 212—ACQUISITION OF COMMERCIAL ITEMS</HD>
          </PART>
          <AMDPAR>4. Amend section 212.301 by revising paragraph (f)(iv) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>212.301</SECTNO>
            <SUBJECT>Solicitation provisions and contract clauses for the acquisition of commercial items.</SUBJECT>
            <P>(f) * * *</P>
            <P>(iv) Use the provisions and clauses prescribed elsewhere in DFARS as follows:</P>
            <P>(A) Use the provision at 252.204-7011, Alternative Line Item Structure, as prescribed in 204.7109(b).</P>
          </SECTION>
        </REGTEXT>
        <P>(B) Use the provision at 252.209-7001, Disclosure of Ownership or Control by the Government of a Terrorist Country, as prescribed in 209.104-70(a).</P>
        <P>(C) Use the clause at 252.211-7003, Item Identification and Valuation, as prescribed in 211.274-4.</P>
        <P>(D) Use the clause at 252.211-7006, Radio Frequency Identification, as prescribed in 211.275-3.</P>
        <P>(E) Use the provision at 252.225-7010, Commercial Derivative Military Article—Specialty Metals Compliance Certificate, as prescribed in 225.7003-5(b).</P>
        <P>(F) Use the clause at 252.225-7040, Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States, as prescribed in 225.7402-4.</P>
        <P>(G) Use the clause at 252.225-7043, Antiterrorism/Force Protection Policy for Defense Contractors Outside the United States, in solicitations and contracts that include the clause at 252.225-7040.</P>
        <P>(H) Use the clause at 252.232-7009, Mandatory Payment by Governmentwide Commercial Purchase Card, as prescribed in 232.1110.</P>
        <P>(I) Use the clause at 252.232-7010, Levies on Contract Payments, as prescribed in 232.7102.</P>
        <P>(J) Use the clause at 252.232-7011, Payments in Support of Emergencies and Contingency Operations, as prescribed in 232.908.</P>
        <P>(K) Use the clause at 252.246-7003, Notification of Potential Safety Issues, as prescribed in 246.371.</P>
        <P>(L) Use the provision at 252.247-7026, Evaluation Preference for Use of Domestic Shipyards—Applicable to Acquisition of Carriage by Vessel for DoD Cargo in the Coastwise or Noncontiguous Trade, as prescribed in 247.574(e).]</P>
        <P>(M) Use the clause at 252.247-7027, Riding Gang Member Requirements, as prescribed in 247.574(f).</P>
        <STARS/>
        <REGTEXT PART="252" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 252—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
          </PART>
          <AMDPAR>5. Add section 252.204-7011 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.204-7011</SECTNO>
            <SUBJECT>Alternative Line Item Structure.</SUBJECT>
            <P>As prescribed in 204.7109(b), insert the following provision:</P>
            
            <EXTRACT>
              <HD SOURCE="HD1">ALTERNATIVE LINE-ITEM STRUCTURE (SEP 2011)</HD>
              <P>(a) Line items are the basic structural elements in a solicitation or contract that provide for the organization of contract requirements to facilitate pricing, delivery, inspection, acceptance and payment. Line items are organized into contract line items, subline items, and exhibit line items. Separate line items should be established to account for separate pricing, identification (see section 211.274 of the Defense Federal Acquisition Regulation Supplement), deliveries, or funding. The Government recognizes that the line item structure in this solicitation may not conform to every offeror's practices. Failure to correct these issues can result in difficulties in accounting for deliveries and processing payments. Therefore, offerors are invited to propose an alternative line item structure for items on which bids, proposals, or quotes are requested in this solicitation to ensure that the resulting contract structure is economically and administratively advantageous to the Government and the Contractor.</P>
              <P>(b) If an alternative line item structure is proposed, the structure must be consistent with subpart 204.71 of the Defense Federal Acquisition Regulation Supplement and PGI 204.71. A sample solicitation line-item structure and a corresponding offer of a proposed alternative line-item structure follow.</P>
              <P>Solicitation:</P>
              <GPOTABLE CDEF="s50,r100,10C,10,xs24,xs24" COLS="6" OPTS="L2,tp0,i1">
                <TTITLE/>
                <BOXHD>
                  <CHED H="1">Item No.</CHED>
                  <CHED H="1">Supplies/Service</CHED>
                  <CHED H="1">Quantity</CHED>
                  <CHED H="1">Unit</CHED>
                  <CHED H="1">Unit price</CHED>
                  <CHED H="1">Amount</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">0001</ENT>
                  <ENT>Computer, Desktop with CPU, Monitor, Keyboard and Mouse</ENT>
                  <ENT>20</ENT>
                  <ENT>EA</ENT>
                  <ENT/>
                  <ENT/>
                </ROW>
              </GPOTABLE>

              <P>Alternative line-item structure offer where monitors are shipped separately:<PRTPAGE P="58140"/>
              </P>
              <GPOTABLE CDEF="s50,r100,10C,10,xs24,xs24" COLS="6" OPTS="L2,tp0,i1">
                <TTITLE/>
                <BOXHD>
                  <CHED H="1">Item No.</CHED>
                  <CHED H="1">Supplies/Service</CHED>
                  <CHED H="1">Quantity</CHED>
                  <CHED H="1">Unit</CHED>
                  <CHED H="1">Unit Price</CHED>
                  <CHED H="1">Amount</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">0001</ENT>
                  <ENT>Computer, Desktop with CPU, Keyboard and Mouse</ENT>
                  <ENT>20</ENT>
                  <ENT>EA</ENT>
                  <ENT/>
                  <ENT/>
                </ROW>
                <ROW>
                  <ENT I="01">0002</ENT>
                  <ENT>Monitor</ENT>
                  <ENT>20</ENT>
                  <ENT>EA</ENT>
                  <ENT/>
                  <ENT/>
                </ROW>
              </GPOTABLE>
              <FP>(End of provision)</FP>
            </EXTRACT>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23953 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 204 and 252</CFR>
        <RIN>RIN 0750-AG39</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Annual Representations and Certifications (DFARS Case 2009-D011)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to conform it to higher-level changes in the Code of Federal Regulation relating to annual representations and certifications.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P/>
          <P SOURCE="NPAR">Mr. Julian Thrash, 703-602-0310.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DFARS 204.1202 prescribes use of DFARS provision 252.204-7007, Alternate A, Annual Representations and Certifications, in contracts that also incorporate Federal Acquisition Regulation (FAR) provision 52.204-8, Annual Representations and Certifications. FAR 52.204-8 was changed to add a new paragraph (c), which lists the applicable representations and certifications in the Online Representations and Certifications Application (ORCA). This FAR change necessitated a similar modification of DFARS 252.204-7007.</P>
        <P>DoD published a proposed rule in the<E T="04">Federal Register</E>at 75 FR 71646, on November 24, 2010, to update DFARS 204.1202 and 252.204-7007. The public comment period closed January 24, 2011. Two respondents submitted comments on the proposed rule. A discussion of the comments is provided below.</P>
        <HD SOURCE="HD1">II. Discussion and Analysis</HD>
        <HD SOURCE="HD2">A. Applicability</HD>
        <P>
          <E T="03">Comment:</E>A respondent recommended DFARS 252.212-7000, Offeror Representations and Certifications—Commercial Items, be retained in the list of representations and certification at 204.1202(2) that are not to be included in the solicitation when using the provision DFARS 252.204-7007, because that provision is to be used in non-commercial solicitations only. Another respondent recommended that DFARS 204.1202(2) include provisions that are applicable to solicitations, rather than those not applicable, similar to FAR 52.204-8.</P>
        <P>
          <E T="03">Response:</E>The first respondent is correct that DFARS provision 252.212-7000 is for commercial solicitations only and will not be included in solicitations that include DFARS 252.204-7007, because that provision is used when FAR 52.204-8 is included, and that FAR provision is not used in solicitations issued under FAR part 12 for acquisition of commercial items. However, inclusion of DFARS 252.212-7000 on the list at DFARS 204.1202(2) is not appropriate, because the list at DFARS 204.1202(2) should include only provisions that are listed in 252.204-7007, Alternate A, Annual Representations and Certifications. Therefore, the final rule does not retain 252.212-7000 on the list at 204.1202(2). Further, DFARS 204.1202(2) introductory text was amended to clarify that the listed provisions will not be included separately in the solicitation, because the appropriate representations and certifications will be covered by inclusion of DFARS 252.204-7007 in the solicitation.</P>
        <P>
          <E T="03">Comment:</E>A respondent recommended the representations at DFARS 252.216-7003 and DFARS 252.239-7011 be retained in the list of representations and certifications at DFARS 252.204-7007 because the Contractor is asked to make a representation about itself.</P>
        <P>
          <E T="03">Response:</E>DFARS 252.216-7003 will be retained in the list. DFARS 252.239-7011, however, will not be included because the clause requires contractors to make certain representations during contract performance concerning reimbursement of special construction and equipment costs. According to DFARS 239.7408-1(a), “special construction normally involves a common carrier giving a special service or facility related to the performance of the basic telecommunications service requirements.” Since these are costs that occur during contract performance, the contractor would not be able to make a proper representation prior to award.</P>
        <HD SOURCE="HD2">B. Clarification</HD>
        <P>
          <E T="03">Comment:</E>A respondent recommended modifying the second sentence of DFARS 252.204.7007(e) by removing “as indicated in (d) and (e) of this provision” and adding “as well as those in (d) above” after “posted electronically.”</P>
        <P>
          <E T="03">Response:</E>When using the alternate at DFARS 252.204-7007, paragraphs (d) and (e) replace paragraph (d) of FAR 52.204-8. DFARS 252.204-7007(e) provides that by submission of an offer, the offeror verifies that the FAR 52.204-8(c) representations and certifications and the DFARS 252.204-7007(d) representations and certifications are up to date in ORCA. Accordingly, the language in paragraph (e) was changed to include the statement “as indicated in FAR 52.204-8(c) and paragraph (d) of this provision.”</P>
        <P>
          <E T="03">Comment:</E>A respondent commented that the second to last line of 252.204-7007(e) should say “provision number” instead of “clause number.”</P>
        <P>
          <E T="03">Response:</E>The term “clause number” was changed to “provision number” in the second to last line of 252.204-7007(e) and in the first block of the table provided.</P>
        <HD SOURCE="HD2">C. Additional Changes</HD>
        <P>DFARS 252.209-7001, Disclosure of Ownership or Control by the Government of a Terrorist Country, which was inadvertently omitted from the listing of provisions, has been added to 204.1202(2)(i) and 252.204-7007(d)(1)(i). The Alternates for 252.225-7020, Trade Agreements Certificate, and 252.225-7035, Buy American Act-Free Trade Agreements-Balance of Payments Program Certificate, were added to 252.204-7007(d)(2)(iii), and (vi), respectively.</P>

        <P>Additionally, to further clarify applicability of the various provisions, 252.204-7007(d) was reformatted into two sections to separately list the DFARS provisions that the contracting officer may individually select if one of the provisions applies for a particular<PRTPAGE P="58141"/>procurement. Additionally, the prescription for use of 252.204-7007 was reformatted to include it as a lead in to the provision rather than being a part of the provision.</P>
        <HD SOURCE="HD1">III. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders 12866 and 13563 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 is not a significant regulatory action and, therefore, was not subject to review under Section 6(b) of Executive Order 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>

        <P>DoD certifies that this final rule will not have a significant economic impact on a substantial number of small entities within the meaning for the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.,</E>because the rule does not impose any additional requirements on small businesses.</P>
        <P>A proposed rule published in the<E T="04">Federal Register</E>at 75 FR 73997, on November 30, 2010, invited comments from small businesses and other interested parties. No comments were received from small entities on the affected DFARS subpart with regard to small businesses.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
        <P>The rule does not impose any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 204 and 252</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 204 and 252 are amended as follows:</P>
        <REGTEXT PART="204" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 204 and 252 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="204" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 204—ADMINISTRATIVE MATTERS</HD>
          </PART>
          <AMDPAR>2. Section 204.1202 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>204.1202</SECTNO>
            <SUBJECT>Solicitation provision.</SUBJECT>
          </SECTION>
        </REGTEXT>
        <P>When using the provision at FAR 52.204-8, Annual Representations and Certifications—</P>
        <P>(1) Use the provision with 252.204-7007, Alternate A, Annual Representations and Certifications; and</P>
        <P>(2) Do not include separately in the solicitation the following provisions, which are included in DFARS 252.204-7007:</P>
        <P>(i) 252.209-7001, Disclosure of Ownership or Control by the Government of a Terrorist Country.</P>
        <P>(ii) 252.209-7005, Reserve Officer Training Corps and Military Recruiting on Campus.</P>
        <P>(iii) 252.209-7002, Disclosure of Ownership or Control by a Foreign Government.</P>
        <P>(iv) 252.216-7003, Economic Price Adjustment—Wage Rates or Material Prices Controlled by a Foreign Government.</P>
        <P>(v) 252.225-7000, Buy American Act—Balance of Payments Program Certificate.</P>
        <P>(vi) 252.225-7020, Trade Agreements Certificate.</P>
        <P>(vii) 252.225-7022, Trade Agreements Certificate—Inclusion of Iraqi End Products.</P>
        <P>(viii) 252.225-7031, Secondary Arab Boycott of Israel.</P>
        <P>(ix) 252.225-7035, Buy American Act—Free Trade Agreements—Balance of Payments Program Certificate.</P>
        <P>(x) 252.225-7042, Authorization to Perform.</P>
        <P>(xi) 252.229-7003, Tax Exemptions (Italy).</P>
        <P>(xii) 252.229-7005, Tax Exemptions (Spain).</P>
        <P>(xiii) 252.247-7022, Representation of Extent of Transportation by Sea.</P>
        <REGTEXT PART="252" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 252—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
          </PART>
          <AMDPAR>3. Section 252.204-7007 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.204-7007</SECTNO>
            <SUBJECT>Alternate A, Annual Representations and Certifications.</SUBJECT>
            <P>As prescribed in 204.1202, use the following provision:</P>
            
            <EXTRACT>
              <HD SOURCE="HD1">Alternate A, Annual Representations and Certifications (Sep 2011)</HD>
              <P>Substitute the following paragraphs (d) and (e) for paragraph (d) of the provision at FAR 52.204-8:</P>
              <P>(d)(1) The following representations or certifications in ORCA are applicable to this solicitation as indicated:</P>
              <P>(i) 252.209-7001, Disclosure of Ownership or Control by the Government of a Terrorist Country. Applies to all solicitations expected to result in contracts of $150,000 or more.</P>
              <P>(ii) 252.209-7005, Reserve Officer Training Corps and Military Recruiting on Campus. Applies to all solicitations and contracts with institutions of higher education.</P>
              <P>(iii) 252.216-7003, Economic Price Adjustment-Wage Rates or Material Prices Controlled by a Foreign Government. Applies to fixed-price supply and service contracts when the contract is to be performed wholly or in part in a foreign country, and a foreign government controls wage rates or material prices and may during contract performance impose a mandatory change in wages or prices of materials.</P>
              <P>(iv) 252.225-7042, Authorization to Perform. Applies to all solicitations when performance will be wholly or in part in a foreign country.</P>
              <P>(v) 252.229-7003, Tax Exemptions (Italy). Applies to solicitations and contracts when contract performance will be in Italy.</P>
              <P>(vi) 252.229-7005, Tax Exemptions (Spain). Applies to solicitations and contracts when contract performance will be in Spain.</P>
              <P>(vii) 252.247-7022, Representation of Extent of Transportation by Sea. Applies to all solicitations except those for direct purchase of ocean transportation services or those with an anticipated value at or below the simplified acquisition threshold.</P>

              <P>(2) The following representations or certifications in ORCA are applicable to this solicitation as indicated by the Contracting Officer: [<E T="03">Contracting Officer check as appropriate.</E>]</P>
              <P>__(i) 252.209-7002, Disclosure of Ownership or Control by a Foreign Government.</P>
              <P>__(ii) 252.225-7000, Buy American Act—Balance of Payments Program Certificate.</P>
              <P>__(iii) 252.225-7020, Trade Agreements Certificate.</P>
              <P>__Use with Alternate I.</P>
              <P>__(iv) 252.225-7022, Trade Agreements Certificate—Inclusion of Iraqi End Products.</P>
              <P>__(v) 252.225-7031, Secondary Arab Boycott of Israel.</P>
              <P>__(vi) 252.225-7035, Buy American Act—Free Trade Agreements—Balance of Payments Program Certificate.</P>
              <P>__Use with Alternate I.</P>
              <P>__Use with Alternate II.</P>
              <P>__Use with Alternate III.</P>

              <P>(e) The offeror has completed the annual representations and certifications electronically via the Online Representations and Certifications Application (ORCA) Web site at<E T="03">https://orca.bpn.gov/</E>. After reviewing the ORCA database information, the offeror verifies by submission of the offer that the representations and certifications currently posted electronically that apply to this solicitation as indicated in FAR 52.204-8(c) and paragraph (d) of this provision have been entered or updated within the last 12 months, are current, accurate, complete, and applicable to this solicitation (including the business size standard applicable to the<PRTPAGE P="58142"/>NAICS code referenced for this solicitation), as of the date of this offer, and are incorporated in this offer by reference (see FAR 4.1201); except for the changes identified below [<E T="03">offeror to insert changes, identifying change by provision number, title, date].</E>These amended representation(s) and/or certification(s) are also incorporated in this offer and are current, accurate, and complete as of the date of this offer.</P>
              <GPOTABLE CDEF="xl50,xl50,14,14" COLS="4" OPTS="L2,tp0,i1">
                <TTITLE/>
                <BOXHD>
                  <CHED H="1">FAR/DFARS provision No.</CHED>
                  <CHED H="1">Title</CHED>
                  <CHED H="1">Date</CHED>
                  <CHED H="1">Change</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="22"/>
                </ROW>
              </GPOTABLE>
              <P>Any changes provided by the offeror are applicable to this solicitation only, and do not result in an update to the representations and certifications posted on ORCA.</P>
              <FP>(End of provision)</FP>
            </EXTRACT>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23947 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 211 and 252</CFR>
        <RIN>RIN 0750-AH05</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Passive Radio Frequency Identification (DFARS Case 2010-D014)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to update requirements relating to the use of passive radio frequency identification (RFID).</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>September 20, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dustin Pitsch, telephone 703-602-0289.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DoD published a proposed rule in the<E T="04">Federal Register</E>at 76 FR 9714 on February 26, 2011, in response to a request of the Office of Logistics and Materiel Readiness of the Office of the Secretary of Defense (Acquisition, Technology, and Logistics) to update requirements relating to the use of passive radio frequency identification (RFID).</P>
        <HD SOURCE="HD1">II. Discussion and Analysis</HD>
        <P>DoD received comments from two respondents in response to the proposed rule. One respondent expressed general support for the rule.</P>
        <P>
          <E T="03">Comment:</E>A respondent stated that RFID tags will play an expanded role in inventory management and asset protection for the DoD and expanded use should occur soon.</P>
        <P>
          <E T="03">Response:</E>DoD agrees that RFID use in inventory management is expanding and will continue to expand.</P>
        <P>
          <E T="03">Comment:</E>A respondent stated that RFID tracking is not the current industry standard for inventory management of pharmaceuticals and that adding this requirement would cost the suppliers and DoD a significant amount of time and money to implement. This respondent believes that the current use of 2D barcodes is sufficient for tracking pharmaceuticals and that the DoD should not require the use of passive RFID.</P>
        <P>
          <E T="03">Response:</E>DoD agrees and the final rule does not include a requirement for passive RFID use for pharmaceuticals.</P>
        <HD SOURCE="HD1">III. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is a significant regulatory action and, therefore, was subject to review under section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>

        <P>DoD has prepared a Final Regulatory Flexibility Analysis (FRFA) consistent with the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.</E>The FRFA is summarized as follows.</P>
        <P>The DFARS previously listed approximately 20 specific DoD activity addresses and provides the authority for using other ship-to locations “outside the contiguous United States” under certain circumstances. However, the Defense Logistics Agency and the Navy proposed adding more than 200 additional sites, making it impracticable to list all DoD passive RFID addresses in the DFARS text or its associated clause. Instead, this rule adds a Web site for contractors to find the RFID Identifier for each specific DoD ship-to address that uses RFID technology. Including the Web site in the DFARS has the added benefit of enabling the addition of new ship-to addresses in the future as necessary without the need to revise the DFARS in each case. This final rule amends the revised, shortened list of ship-to addresses at DFARS 211.275-2(a)(2) to allow contracting officers to add tagging requirements to contract deliverables shipping to DoDAACs not specifically included in the list as they deem necessary.</P>
        <P>The current OMB information collection justification for the clause associated with the current DFARS, 252.211-7006, entitled “Radio Frequency Identification,” lists the number of contractors impacted by the RFID requirement as 25,500. While each contractor has multiple submissions (one for each shipment), it takes only 1.12 seconds per response. The rule changes impact, if any, should decrease the response time and not increase it.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
        <P>There are information collection requirements associated with the use of RFIDs. However, there will be no substantive change to the existing information collection requirements currently approved under OMB Information Control Number 0704-0434, DFARS; Radio Frequency Identification Advance Shipment Notices. Therefore, DoD has determined that the final rule has no material impact on the approved collection.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 211 and 252</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 211 and 252 are amended as follows:</P>
        <REGTEXT PART="211" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 211 and 252 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="211" TITLE="48">
          <PART>
            <PRTPAGE P="58143"/>
            <HD SOURCE="HED">PART 211—DESCRIBING AGENCY NEEDS</HD>
          </PART>
          <AMDPAR>2. The section heading for section 211.275 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>211.275</SECTNO>
            <SUBJECT>Passive radio frequency identification.</SUBJECT>
          </SECTION>
          <SECTION>
            <SECTNO>211.275-1</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="211" TITLE="48">
          <AMDPAR>3. Section 211.275-1 is amended to add the word “Passive” before the phrase “Radio Frequency Identification”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="211" TITLE="48">
          <AMDPAR>4. Section 211.275-2 is amended to—</AMDPAR>
          <AMDPAR>a. Revise paragraph (a) introductory text; and</AMDPAR>
          <AMDPAR>b. Revise paragraph (a)(2).</AMDPAR>
          <P>The revisions read as follows:</P>
          <SECTION>
            <SECTNO>211.275-2</SECTNO>
            <SUBJECT>Policy.</SUBJECT>
            <P>(a) Except as provided in paragraph (b) of this section, radio frequency identification (RFID), in the form of a passive RFID tag, is required for cases and palletized unit loads packaging levels and any additional consolidation level(s) deemed necessary by the requiring activity for shipments of items that—</P>
            <STARS/>
            <P>(2) Will be shipped to one of the locations listed at<E T="03">http://www.acq.osd.mil/log/rfid/</E>or to—</P>
            <P>(i) A location outside the contiguous United States when the shipment has been assigned Transportation Priority 1; or</P>
            <P>(ii) Any additional location(s) deemed necessary by the requiring activity.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="211" TITLE="48">
          <STARS/>
          <AMDPAR>5. Section 211.275-3 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>211.275-3</SECTNO>
            <SUBJECT>Contract clause.</SUBJECT>
            <P>Use the clause at<E T="03">252.211-7006,</E>Passive Radio Frequency Identification, in solicitations and contracts that will require shipment of items meeting the criteria at<E T="03">211.275-2,</E>and complete paragraph (b)(1)(ii) of the clause at 252.211-7006 as appropriate.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 252—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
          </PART>
          <AMDPAR>6. Section 252.211-7006 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.211-7006</SECTNO>
            <SUBJECT>Passive Radio Frequency Identification.</SUBJECT>
            <P>As prescribed in<E T="03">211.275-3</E>, use the following clause:</P>
            <EXTRACT>
              <HD SOURCE="HD1">Passive Radio Frequency Identification (SEP 2011)</HD>
              <P>(a)<E T="03">Definitions.</E>As used in this clause—</P>
              <P>
                <E T="03">Advance shipment notice</E>means an electronic notification used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as passive radio frequency identification (RFID) or item unique identification (IUID) information, order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.</P>
              <P>
                <E T="03">Bulk commodities</E>means the following commodities, when shipped in rail tank cars, tanker trucks, trailers, other bulk wheeled conveyances, or pipelines:</P>
              <P>(1) Sand.</P>
              <P>(2) Gravel.</P>
              <P>(3) Bulk liquids (water, chemicals, or petroleum products).</P>
              <P>(4) Ready-mix concrete or similar construction materials.</P>
              <P>(5) Coal or combustibles such as firewood.</P>
              <P>(6) Agricultural products such as seeds, grains, or animal feed.</P>
              <P>
                <E T="03">Case</E>means either a MIL-STD-129 defined exterior container within a palletized unit load or a MIL-STD-129 defined individual shipping container.</P>
              <P>
                <E T="03">Electronic Product Code<SU>TM</SU>(EPC®)</E>means an identification scheme for universally identifying physical objects via RFID tags and other means. The standardized EPC<SU>TM</SU>data consists of an EPC<SU>TM</SU>(or EPC<SU>TM</SU>identifier) that uniquely identifies an individual object, as well as an optional filter value when judged to be necessary to enable effective and efficient reading of the EPC<SU>TM</SU>tags. In addition to this standardized data, certain classes of EPC<SU>TM</SU>tags will allow user-defined data. The EPC<SU>TM</SU>Tag Data Standards will define the length and position of this data, without defining its content.</P>
              <P>
                <E T="03">EPCglobal®</E>means a subscriber-driven organization comprised of industry leaders and organizations focused on creating global standards for the adoption of passive RFID technology.</P>
              <P>
                <E T="03">Exterior container</E>means a MIL-STD-129 defined container, bundle, or assembly that is sufficient by reason of material, design, and construction to protect unit packs and intermediate containers and their contents during shipment and storage. It can be a unit pack or a container with a combination of unit packs or intermediate containers. An exterior container may or may not be used as a shipping container.</P>
              <P>
                <E T="03">Palletized unit load</E>means a MIL-STD-129 defined quantity of items, packed or unpacked, arranged on a pallet in a specified manner and secured, strapped, or fastened on the pallet so that the whole palletized load is handled as a single unit. A palletized or skidded load is not considered to be a shipping container. A loaded 463L System pallet is not considered to be a palletized unit load. Refer to the Defense Transportation Regulation, DoD 4500.9-R, Part II, Chapter 203, for marking of 463L System pallets.</P>
              <P>
                <E T="03">Passive RFID tag</E>means a tag that reflects energy from the reader/interrogator or that receives and temporarily stores a small amount of energy from the reader/interrogator signal in order to generate the tag response. The only acceptable tags are EPC Class 1 passive RFID tags that meet the EPCglobal<SU>TM</SU>Class 1 Generation 2 standard.</P>
              <P>
                <E T="03">Radio frequency identification (RFID)</E>means an automatic identification and data capture technology comprising one or more reader/interrogators and one or more radio frequency transponders in which data transfer is achieved by means of suitably modulated inductive or radiating electromagnetic carriers.</P>
              <P>
                <E T="03">Shipping container</E>means a MIL-STD-129 defined exterior container that meets carrier regulations and is of sufficient strength, by reason of material, design, and construction, to be shipped safely without further packing (<E T="03">e.g.,</E>wooden boxes or crates, fiber and metal drums, and corrugated and solid fiberboard boxes).</P>
              <P>(b)(1) Except as provided in paragraph (b)(2) of this clause, the Contractor shall affix passive RFID tags, at the case- and palletized- unit-load packaging levels, for shipments of items that—</P>
              <P>(i) Are in any of the following classes of supply, as defined in DoD 4140.1-R, DoD Supply Chain Materiel Management Regulation, AP1.1.11:</P>
              <P>(A) Subclass of Class I—Packaged operational rations.</P>
              <P>(B) Class II—Clothing, individual equipment, tentage, organizational tool kits, hand tools, and administrative and housekeeping supplies and equipment.</P>
              <P>(C) Class IIIP—Packaged petroleum, lubricants, oils, preservatives, chemicals, and additives.</P>
              <P>(D) Class IV—Construction and barrier materials.</P>
              <P>(E) Class VI—Personal demand items (non-military sales items).</P>
              <P>(F) Subclass of Class VIII—Medical materials (excluding pharmaceuticals, biologicals, and reagents—suppliers should limit the mixing of excluded and non-excluded materials).</P>
              <P>(G) Class IX—Repair parts and components including kits, assemblies and subassemblies, reparable and consumable items required for maintenance support of all equipment, excluding medical-peculiar repair parts; and</P>

              <P>(ii) Are being shipped to one of the locations listed at<E T="03">http://www.acq.osd.mil/log/rfid/</E>or to—</P>
              <P>(A) A location outside the contiguous United States when the shipment has been assigned Transportation Priority 1, or to—</P>

              <P>(B) The following location(s) deemed necessary by the requiring activity:<PRTPAGE P="58144"/>
              </P>
              <GPOTABLE CDEF="xl40,xl40,xl40,xl40,xl40" COLS="5" OPTS="L2,tp0,i1">
                <TTITLE/>
                <BOXHD>
                  <CHED H="1">Contract line, subline, or exhibit line item number</CHED>
                  <CHED H="1">Location name</CHED>
                  <CHED H="1">City</CHED>
                  <CHED H="1">State</CHED>
                  <CHED H="1">DoDAAC</CHED>
                </BOXHD>
                <ROW RUL="s">
                  <ENT I="22"/>
                </ROW>
                <ROW>
                  <ENT I="22"/>
                </ROW>
              </GPOTABLE>
              <P>(2) The following are excluded from the requirements of paragraph (b)(1) of this clause:</P>
              <P>(i) Shipments of bulk commodities.</P>
              <P>(ii) Shipments to locations other than Defense Distribution Depots when the contract includes the clause at FAR 52.213-1, Fast Payment Procedures.</P>
              <P>(c) The Contractor shall—</P>

              <P>(1) Ensure that the data encoded on each passive RFID tag are globally unique (<E T="03">i.e.,</E>the tag ID is never repeated across two or more RFID tags) and conforms to the requirements in paragraph (d) of this clause;</P>
              <P>(2) Use passive tags that are readable; and</P>
              <P>(3) Ensure that the passive tag is affixed at the appropriate location on the specific level of packaging, in accordance with MIL-STD-129 (Section 4.9.2) tag placement specifications.</P>
              <P>(d)<E T="03">Data syntax and standards.</E>The Contractor shall encode an approved RFID tag using the instructions provided in the EPC<SU>TM</SU>Tag Data Standards in effect at the time of contract award. The EPC<SU>TM</SU>Tag Data Standards are available at<E T="03">http://www.epcglobalinc.org/standards/</E>.</P>
              <P>(1) If the Contractor is an EPCglobal<SU>TM</SU>subscriber and possesses a unique EPC<SU>TM</SU>company prefix, the Contractor may use any of the identifiers and encoding instructions described in the most recent EPC<SU>TM</SU>Tag Data Standards document to encode tags.</P>

              <P>(2) If the Contractor chooses to employ the DoD identifier, the Contractor shall use its previously assigned Commercial and Government Entity (CAGE) code and shall encode the tags in accordance with the tag identifier details located at<E T="03">http://www.acq.osd.mil/log/rfid/tag_data.htm.</E>If the Contractor uses a third-party packaging house to encode its tags, the CAGE code of the third-party packaging house is acceptable.</P>
              <P>(3) Regardless of the selected encoding scheme, the Contractor with which the Department holds the contract is responsible for ensuring that the tag ID encoded on each passive RFID tag is globally unique, per the requirements in paragraph (c)(1) of this clause.</P>
              <P>(e)<E T="03">Advance shipment notice.</E>The Contractor shall use Wide Area WorkFlow (WAWF), as required by DFARS 252.232-7003, Electronic Submission of Payment Requests, to electronically submit advance shipment notice(s) with the RFID tag ID(s) (specified in paragraph (d) of this clause) in advance of the shipment in accordance with the procedures at<E T="03">https://wawf.eb.mil/</E>.</P>
              
              <FP>(End of clause)</FP>
            </EXTRACT>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23945 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 212, 227, and 252</CFR>
        <RIN>RIN 0750-AF84</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Presumption of Development Exclusively at Private Expense (DFARS Case 2007-D003)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule to amend the Defense Federal Acquisition Regulation Supplement to implement sections of the Fiscal Year (FY) 2007 and 2008 National Defense Authorization Act, including special requirements and procedures related to the validation of a contractor's or subcontractor's asserted restrictions on technical data and computer software.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Manuel Quinones, 703-602-8383.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>This final rule amends the Defense Federal Acquisition Regulation Supplement (DFARS) to implement section 802(b) of the FY 2007 National Defense Authorization Act (NDAA) (Pub. L. 109-364) and section 815 of the FY 2008 NDAA (Pub. L. 110-181). Section 802(b) modified 10 U.S.C. 2321(f)(2) with regard to the presumption of development at private expense for major systems. Section 815 revised 10 U.S.C. 2321(f)(2) to exempt commercially available off-the-shelf items from the requirements that section 802(b) established for major systems.</P>
        <P>This final rule implements special requirements and procedures related to the validation of a contractor's or subcontractor's asserted restrictions on technical data and computer software. More specifically, the final rule affects these validation procedures in the context of two special categories of items: Commercial items (including commercially available off-the-shelf items), which may be referred to as the “Commercial Rule;” and major systems (including subsystems and components of major systems), which may be referred to as the “Major Systems Rule.”</P>

        <P>DoD published a proposed rule with a request for comments in the<E T="04">Federal Register</E>on May 7, 2010 (75 FR 25161). Two respondents provided comments.</P>
        <HD SOURCE="HD1">II. Discussion and Analysis of the Public Comments</HD>
        <P>A discussion of the comments and the changes made to the rule as a result of those comments are provided as follows.</P>
        <HD SOURCE="HD2">A. Prescribing a Noncommercial Clause for Technical Data Related to a Commercial Item</HD>
        <P>
          <E T="03">Comment:</E>Two respondents described the prescriptions at DFARS 227.7102-3(b) and 227.7103-6(a) as new requirements that exceed the changes necessary to implement the statute.</P>
        <P>
          <E T="03">Response:</E>The operative elements of the clause prescription at DFARS 227.7102-3(b) were a part of the last major revision of Part 227 in 1995. The substance of the prescription has not changed in the proposed rule; the requirement was redesignated as DFARS 227.7102-(4)(b) and revised to cross-reference the prescription added to DFARS 227.7103-6(a). This follows DFARS drafting principles to use only a single prescription for each clause, using cross-references when necessary. As such, the prescription at DFARS 227.7103-6(a) serves as the primary source for prescribing all uses of the clause at DFARS 252.227-7013, with a cross-reference at 227.7102-(4)(b).</P>
        <P>
          <E T="03">Comment:</E>A respondent recommended that the criteria “or will pay any portion of the development costs” should be eliminated because the Government should not receive the benefit of something it may or may not pay for in the future outside of the contract.</P>
        <P>
          <E T="03">Response:</E>The “will pay” criterion has been used since 1995. The term “will” is used to denote an anticipated future action or result, and there is no evidence that this criterion has been or should be interpreted as seeking to be used in a contract when the criteria used to invoke the clause has not, and is not, expected to occur during the contract.<PRTPAGE P="58145"/>
        </P>
        <P>
          <E T="03">Comment:</E>Two respondents outlined specific concerns that prescribing use of the noncommercial clause for technical data related to a commercial item is unnecessarily burdensome with regard to the noncommercial marking requirements. One respondent argued that this could result in the contractor unintentionally forfeiting its intellectual property rights by delivering with commercial markings that do not comply with the DFARS noncommercial marking requirements.</P>
        <P>
          <E T="03">Response:</E>The prescription for the use of the clause at DFARS 252.227-7013 in this scenario already exists. Use of commercial restrictive markings would not directly result in the forfeiture of the contractor's intellectual property rights in cases in which the noncommercial marking rules were used. The restrictive marking required by the clause at DFARS 252.227-7015(d) for technical data related to commercial items should be sufficient to: (1) Preserve the contractor's rights under the noncommercial clause procedures for correcting “nonconforming” markings (see DFARS 252.227-7013(h)(1)) or (2) validate asserted restrictions under DFARS 252.227-7037, which is used regardless of whether the clauses at DFARS 252.227-7013 or 252.227-7015 are included.</P>
        <P>The final rule is amended to address concerns about the desirability of requiring noncommercial markings for the entire technical data package, in cases where the Government may have funded only a small portion of the development. The final rule revises the prescriptions at DFARS 227.7102-4(b) and 227.7103-6(a), to clarify that in cases when the Government “will have paid” for any portion of the development of a commercial item, both the commercial clause at DFARS 252.227-7015 and the noncommercial clause at DFARS 252.227-7013 should be used together. In these cases, the noncommercial clause will apply only to the technical data related to those portions of the commercial item that were developed in some part at Government expense, and the commercial clause will remain applicable to the rest of the data. This preserves the preexisting allocation of rights between the parties, but avoids the necessity of applying noncommercial markings to data related to commercial technologies that were developed exclusively at private expense. In addition, the flowdown requirements of DFARS clause 252.227-7013(k) and clause 252.227-7015(e) are clarified to enable the use of the appropriate clause(s) to lower-tier subcontracts.</P>
        <P>
          <E T="03">Comment:</E>Two respondents commented that the proposed revisions result in a commercial item losing its commercial item status. One of these respondents recommended the elimination of the “developed exclusively at private expense” component of the proposed revisions to the clause at DFARS 252.227-7019, to avoid the application of the noncommercial clauses to commercial technologies.</P>
        <P>
          <E T="03">Response:</E>The prescription for the use of the clause at DFARS 252.227-7013 does not affect the commercial status of an item that otherwise meets the definition of commercial item at FAR 2.101 (based on 41 U.S.C. 403(12), and 10 U.S.C. 2302(3)(I)). If the item still qualifies as a commercial item, then it is a commercial item. If that commercial item was not developed exclusively at private expense, then the rules apply that govern the treatment of technical data deliverables and associated license rights related to that commercial item.</P>
        <P>
          <E T="03">Comment:</E>Two respondents identified several ways in which the prescribed use of the clause at DFARS 252.227-7013, instead of 252.227-7015, appears to be inconsistent with FAR and DFARS policies regarding data deliverables and data rights in commercial technologies. The respondents noted that DFARS 227.7102-1 states DoD's basic policy that DoD shall acquire only the technical data deliverables that are customarily provided to the public, with a few exceptions.</P>
        <P>
          <E T="03">Response:</E>The prescription for the use of the clause at DFARS 252.227-7013, when the item has been developed in part at Government expense but the item still qualifies as commercial, does not change the applicability of this policy statement. The policy provides exceptions, one of which allows the Government to require the delivery of technical data that describes modifications made at Government expense even if such data is not typically provided to the public (see DFARS 227.7102-1(a)(3)).</P>
        <P>
          <E T="03">Comment:</E>A respondent recommended the elimination of the “developed exclusively at private expense” component of the proposed revisions to the clause at DFARS 252.227-7019, to avoid the application of the noncommercial clauses to commercial technologies.</P>
        <P>
          <E T="03">Response:</E>The respondent's basis for concern is unclear in view of the limited applicability of the clause at DFARS 252.227-7019 to only noncommercial computer software, and the proposed revisions address only the noncommercial aspects of the Major Systems Rule. Accordingly, the proposed revisions to the validation procedures for noncommercial computer software at DFARS 227.7203-13 and 252.227-7019 are retained in the final rule.</P>
        <P>
          <E T="03">Comment:</E>One respondent noted that DFARS 227.7202-1 states the basic policy governing commercial computer software and computer software documentation is that the Government acquires the licenses customarily provided to the public unless such licenses are inconsistent with Federal procurement law or do not otherwise satisfy the agency's needs.</P>
        <P>
          <E T="03">Response:</E>The proposed rule creates no issues or conflicts with this policy since there are no changes proposed for any DFARS coverage related to commercial computer software or documentation.</P>
        <HD SOURCE="HD2">B. Applying Data Rights Clauses to Subcontracts for Commercial Items</HD>
        <P>
          <E T="03">Comment:</E>Two respondents recommended that 10 U.S.C. 2320 and 10 U.S.C. 2321 not be removed from the list of statutes set forth in DFARS 212.504(a), which prohibits their application to subcontracts for commercial items. One respondent concluded that removing these statutes from the list appears to “unilaterally overturn the express intent of Congress and the FAR Council” and that the proposed rule did not explain the basis for the decision to remove the statutes from the list.</P>
        <P>
          <E T="03">Response:</E>The proposed rule explains the basis for this determination. The decision to remove these statutes from the list is based on the appropriate statutory determinations that doing so is in the best interest of the Government. The proposed revisions to DFARS 212.504(a) are retained in the final rule.</P>
        <HD SOURCE="HD2">C. Application of Statutory Technical Data Rules to Computer Software</HD>
        <P>
          <E T="03">Comment:</E>A respondent argued that the proposed rule should not make any changes to the validation procedures for computer software; in particular, the clause at DFARS 252.227-7019, “Validation of Asserted Restrictions—Computer Software,” should not be amended to include the proposed new paragraph (f) that implements the “Major Systems Rule.” In addition, a respondent contended that the decision to cover software was flawed because: (1) There is no statutory basis for the change and (2) not all rights determinations are “black and white.”</P>
        <P>
          <E T="03">Response:</E>(1) Although 10 U.S.C. 2320 and 2321 apply only to technical data and not to computer software, it is longstanding DoD policy and practice to<PRTPAGE P="58146"/>apply the same or analogous requirements to computer software, whenever appropriate. Accordingly, the proposed rule implements revisions to the validation procedures for computer software only to the extent that those procedures are based on the technical data validation procedures that are affected by the statutory changes. The result is that it is only the Major Systems Rule that is adapted for application only to noncommercial computer software. (2) The new Major Systems Rule is applicable only to challenges of contractor assertions that development was exclusively at private expense. Thus, the proposed adaptation of the new Major Systems Rule to noncommercial software validation also is not applicable to assertions based on mixed funds, and does not in any way restrict the ability to segregate mixed-funding development into its privately-funded and Government-funded portions.</P>
        <HD SOURCE="HD2">D. Two Separate Standards for Civilian and DoD Agencies</HD>
        <P>
          <E T="03">Comment:</E>One respondent stated that the proposed rule creates two separate standards for civilian and DoD agencies in that “the practical result could be that an item will be treated as commercial for purposes of intellectual property rights by civilian agencies, and as non-commercial by the agencies of DoD.”</P>
        <P>
          <E T="03">Response:</E>Without analyzing the required treatment under the FAR of a commercial item by a civilian agency when the Government has paid a portion of the development costs, the proposed rule has not changed the criteria for whether an item is a commercial item (<E T="03">i.e.,</E>under the definition at FAR 2.101). Since 1995, DFARS 227.7102-3(b) has required the use of the noncommercial clause at 252.227-7013 in lieu of the commercial clause at 252.227-7015 if the Government will pay any portion of the development costs of the commercial item. Although the proposed revision of the DoD validation scheme to include a “Commercial Rule” and a “Major Systems Rule” may have no equivalent in the civilian validation scheme, DoD's process is driven by the changes to 10 U.S.C. 2321, for which there is no equivalent in the civilian agency statute (41 U.S.C. 253d). No revisions are necessary.</P>
        <HD SOURCE="HD2">E. Administrative, Technical and Typographical Issues</HD>
        <P>
          <E T="03">Comment:</E>A respondent identified a citation error, which seeks to remove and reserve 212.504 paragraphs (a)(v) 10 U.S.C. 2324, Allowable Costs Under Defense Contracts and (a)(vi) 10 U.S.C. 2327, Reporting Requirements Regarding Dealings with Terrorist Countries, when it appears that the intent is to remove paragraphs (a)(iii) 10 U.S.C. 2320, Rights in Technical Data and (iv) 10 U.S.C. 2321, Validation of Proprietary Data Restrictions.</P>
        <P>
          <E T="03">Response:</E>The respondent is correct. This change is reflected in the final rule.</P>
        <P>
          <E T="03">Comment:</E>A respondent recommended changing the cross-reference in the second sentence of DFARS 252.227-7037(c) from paragraph (b) to (b)(1) for further clarification.</P>
        <P>
          <E T="03">Response:</E>The respondent is correct. This change is reflected in the final rule.</P>
        <HD SOURCE="HD2">F. Changes to Rule Resulting From the Public Comments</HD>
        <P>Changes made in the final rule based on the public comments received, include the following:</P>
        <P>• Removed DFARS 212.504 paragraphs (a)(iii) 10 U.S.C. 2320, Rights in Technical Data, and (a)(iv) 10 U.S.C. 2321, Validation of Proprietary Data Restrictions, instead of DFARS 212.504 paragraphs (a)(v) 10 U.S.C. 2324, Allowable Costs Under Defense Contracts and (a)(vi) 10 U.S.C. 2327, Reporting Requirements Regarding Dealings with Terrorist Countries.</P>
        <P>• Revised the prescriptions at DFARS 227.7102-4(b) and 227.7103-6(a) to clarify that in cases when the Government “will have paid” for any portion of the development of a commercial item, both the commercial clause at DFARS 252.227-7015 and the noncommercial clause at DFARS 252.227-7013 shall be used together.</P>
        <P>• Revised 252.212-7001(b) to add 252.227-7013 and 252.227-7037 to be used, as applicable.</P>
        <P>• Revised 252.212-7001(c) to add 252.227-7013, 252.227-7015 and 252.227-7037 to be flowed down to subcontractors, as applicable.</P>
        <P>• Revised the clause flowdown requirements of DFARS 252.227-7013(k) and 252.227-7015(e) to enable the use of the appropriate clause(s) to lower tier subcontracts.</P>
        <P>• Changed the cross reference in the second sentence of the clause at DFARS 252.227-7037(c) from paragraph (b) to (b)(1).</P>
        <P>• Revised 252.244-7000 to add 252.227-7015 and 252.227-7037 to be flowed down to subcontractors, as applicable.</P>
        <HD SOURCE="HD1">III. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is a significant regulatory action and, therefore, was subject to review under Section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>

        <P>DoD certifies that this final rule will not have significant economic impact on a substantial number of small entities within the meaning for the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.,</E>because major systems or subsystems are generally not developed by small businesses. The rule only applies in the limited circumstances that there is a challenge to a use or release restriction for a major system or subsystem that the contractor or subcontractor claims was developed exclusively at private expense.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
        <P>The rule does not impose any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 212, 227, and 252</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 212, 227, and 252 are amended as follows:</P>
        <REGTEXT PART="212" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 212, 227, and 252 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="212" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 212—ACQUISITION OF COMMERCIAL ITEMS</HD>
            <SECTION>
              <SECTNO>212.504</SECTNO>
              <SUBJECT>[Amended]</SUBJECT>
            </SECTION>
          </PART>
          <AMDPAR>2. Section 212.504 is amended as follows:</AMDPAR>
          <AMDPAR>(a) By removing paragraphs (a)(iii) and (iv); and</AMDPAR>
          <AMDPAR>(b) Redesignating paragraphs (a)(v) through (xix) as (a)(iii) through (xvii), respectively.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <PART>
            <PRTPAGE P="58147"/>
            <HD SOURCE="HED">PART 227—PATENTS, DATA, AND COPYRIGHTS</HD>
          </PART>
          <AMDPAR>3. Amend section 227.7102 by removing the text, and republishing the section heading to read as follows:</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <SECTION>
            <SECTNO>227.7102</SECTNO>
            <SUBJECT>Commercial items, components, or processes.</SUBJECT>
          </SECTION>
          <AMDPAR>4. Redesignate section 227.7102-3 as 227.7102-4.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <AMDPAR>5. Add new section 227.7102-3 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>227.7102-3</SECTNO>
            <SUBJECT>Government right to review, verify, challenge and validate asserted restrictions.</SUBJECT>
            <P>Follow the procedures at 227.7103-13 and the clause at 252.227-7037, Validation of Restrictive Markings on Technical Data, regarding the validation of asserted restrictions on technical data related to commercial items.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <AMDPAR>6. Revise the newly redesignated section 227.7102-4 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>227.7102-4</SECTNO>
            <SUBJECT>Contract clauses.</SUBJECT>
            <P>(a)(1) Except as provided in paragraph (b) of this subsection, use the clause at 252.227-7015, Technical Data-Commercial Items, in all solicitations and contracts when the Contractor will be required to deliver technical data pertaining to commercial items, components, or processes.</P>
            <P>(2) Use the clause at 252.227-7015 with its Alternate I in contracts for the development or delivery of a vessel design or any useful article embodying a vessel design.</P>
            <P>(b) In accordance with the clause prescription at 227.7103-6(a), use the clause at 252.227-7013, Rights in Technical Data-Noncommercial Items, in addition to the clause at 252.227-7015, if the Government will have paid for any portion of the development costs of a commercial item. The clause at 252.227-7013 will govern the technical data pertaining to any portion of a commercial item that was developed in any part at Government expense, and the clause at 252.227-7015 will govern the technical data pertaining to any portion of a commercial item that was developed exclusively at private expense.</P>
            <P>(c) Use the clause at 252.227-7037, Validation of Restrictive Markings on Technical Data, in all solicitations and contracts for commercial items that include the clause at 252.227-7015 or the clause at 252.227-7013.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <AMDPAR>6. Amend section 227.7103-6 to revise paragraph (a) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>227.7103-6</SECTNO>
            <SUBJECT>Contract clauses.</SUBJECT>
            <P>(a) Use the clause at 252.227-7013, Rights in Technical Data-Noncommercial Items, in solicitations and contracts when the successful offeror(s) will be required to deliver to the Government technical data pertaining to noncommercial items, or pertaining to commercial items for which the Government will have paid for any portion of the development costs (in which case the clause at 252.227-7013 will govern the technical data pertaining to any portion of a commercial item that was developed in any part at Government expense, and the clause at 252.227-7015 will govern the technical data pertaining to any portion of a commercial item that was developed exclusively at private expense). Do not use the clause when the only deliverable items are computer software or computer software documentation (see 227.72), commercial items developed exclusively at private expense (see 227.7102-4), existing works (see 227.7105), special works (see 227.7106), or when contracting under the Small Business Innovation Research Program (see 227.7104). Except as provided in 227.7107-2, do not use the clause in architect-engineer and construction contracts.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <AMDPAR>7. Amend section 227.7103-13 by:</AMDPAR>
          <AMDPAR>(a) Redesignating paragraph (c) as paragraph (d);</AMDPAR>
          <AMDPAR>(b) Adding a new paragraph (c); and</AMDPAR>
          <AMDPAR>(c) Amending redesignated paragraph (d) by revising the introductory text and paragraphs (d)(2)(i) and (d)(4).</AMDPAR>
          <P>The additions and revisions read as follows.</P>
          <SECTION>
            <SECTNO>227.7103-13</SECTNO>
            <SUBJECT>Government right to review, verify, challenge and validate asserted restrictions.</SUBJECT>
            <STARS/>
            <P>(c)<E T="03">Challenge considerations and presumption.</E>
            </P>
            <P>(1)<E T="03">Requirements to initiate a challenge.</E>Contracting officers shall have reasonable grounds to challenge the validity of an asserted restriction. Before issuing a challenge to an asserted restriction, carefully consider all available information pertaining to the assertion. The contracting officer shall not challenge a contractor's assertion that a commercial item, component, or process was developed exclusively at private expense unless the Government can demonstrate that it contributed to development of the item, component or process.</P>
            <P>(2)<E T="03">Presumption regarding development exclusively at private expense.</E>10 U.S.C. 2320(b)(1) and 2321(f) establish a presumption and procedures regarding validation of asserted restrictions for technical data related to commercial items, and to major systems, on the basis of development exclusively at private expense.</P>
            <P>(i)<E T="03">Commercial items.</E>For commercially available off-the-shelf items (defined at 41 U.S.C. 431(c)[104]) in all cases, and for all other commercial items except as provided in paragraph (c)(2)(ii) of this subsection, contracting officers shall presume that the items were developed exclusively at private expense whether or not a contractor submits a justification in response to a challenge notice. When a challenge is warranted, a contractor's or subcontractor's failure to respond to the challenge notice cannot be the sole basis for issuing a final decision denying the validity of an asserted restriction.</P>
            <P>(ii)<E T="03">Major systems.</E>The presumption of development exclusively at private expense does not apply to major systems or subsystems or components thereof, except for commercially available off-the-shelf items (which are governed by paragraph (c)(2)(i) of this subsection). When the contracting officer challenges an asserted restriction regarding technical data for a major system or a subsystem or component thereof on the basis that the technology was not developed exclusively at private expense, the contracting officer shall sustain the challenge unless information provided by the contractor or subcontractor demonstrates that the item was developed exclusively at private expense.</P>
            <P>(d)<E T="03">Challenge and validation.</E>All challenges shall be made in accordance with the provisions of the clause at 252.227-7037, Validation of Restrictive Markings on Technical Data.</P>
            <STARS/>
            <P>(2)<E T="03">Pre-challenge requests for information.</E>
            </P>
            <P>(i) After consideration of the situations described in paragraph (d)(3) of this subsection, contracting officers may request the person asserting a restriction to furnish a written explanation of the facts and supporting documentation for the assertion in sufficient detail to enable the contracting officer to ascertain the basis of the restrictive markings. Additional supporting documentation may be requested when the explanation provided by the person making the assertion does not, in the contracting officer's opinion, establish the validity of the assertion.</P>
            <STARS/>
            <P>(4)<E T="03">Challenge notice.</E>The contracting officer shall not issue a challenge notice unless there are reasonable grounds to question the validity of an assertion. The contracting officer may challenge<PRTPAGE P="58148"/>an assertion whether or not supporting documentation was requested under paragraph (d)(2) of this subsection. Challenge notices shall be in writing and issued to the contractor or, after consideration of the situations described in paragraph (d)(3) of this subsection, the person asserting the restriction. The challenge notice shall include the information in paragraph (e) of the clause at 252.227-7037.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="227" TITLE="48">
          <AMDPAR>8. Amend section 227.7203-13 by:</AMDPAR>
          <AMDPAR>(a) Redesignating paragraphs (d) through (f) as (e) through (g), respectively; and</AMDPAR>
          <AMDPAR>(b) Adding a new paragraph (d) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>227.7203-13</SECTNO>
            <SUBJECT>Government right to review, verify, challenge and validate asserted restrictions.</SUBJECT>
            <STARS/>
            <P>(d)<E T="03">Major systems.</E>When the contracting officer challenges an asserted restriction regarding noncommercial computer software for a major system or a subsystem or component thereof on the basis that the computer software was not developed exclusively at private expense, the contracting officer shall sustain the challenge unless information provided by the contractor or subcontractor demonstrates that the computer software was developed exclusively at private expense.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 252—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
          </PART>
          <AMDPAR>9. Amend section 252.212-7001 by—</AMDPAR>
          <AMDPAR>(a) Revising the introductory text;</AMDPAR>
          <AMDPAR>(b) Amending the clause date by removing “(AUG 2011)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(c) Redesignating paragraphs (b)(19) through (b)(28) as paragraphs (b)(20) through (b)(29);</AMDPAR>
          <AMDPAR>(d) Adding new paragraph (b)(19);</AMDPAR>
          <AMDPAR>(e) Amending newly redesignated paragraph (b)(20) by removing “(MAR 2011)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(f) Amending newly redesignated paragraph (b)(21) by removing “(SEP 1999)” and adding in its place “(SEP 2011), if applicable (see 227.7102-4(c)).”;</AMDPAR>
          <AMDPAR>(g) Redesignating paragraphs (c)(2) through (c)(6) as paragraphs (c)(5) through (c)(9), respectively; and</AMDPAR>
          <AMDPAR>(h) Adding new paragraphs (c)(2) through (c)(4).</AMDPAR>
          <P>The additions and revisions read as follows:</P>
          <SECTION>
            <SECTNO>252.212-7001</SECTNO>
            <SUBJECT>Contract Terms and Conditions Required to Implement Statues or Executive Orders Applicable to Defense Acquisitions of Commercial Items.</SUBJECT>
            <P>As prescribed in 212.301(f)(iii) and 227.7103-6(a) and (e), use the following clauses as applicable:</P>
            <STARS/>
            <P>(b) * * *</P>
            <P>(19)  252.227-7013, Rights in Technical Data—Noncommercial Items (SEP 2011), if applicable (see 227.7103-6(a)).</P>
            <STARS/>
            <P>(c) * * *</P>
            <P>(2) 252.227-7013, Rights in Technical Data—Noncommercial Items (SEP 2011), if applicable (see 227.7103-6(a)).</P>
            <P>(3) 252.227-7015, Technical Data—Commercial Items (SEP 2011), if applicable (see 227.7102-4(a)).</P>
            <P>(4) 252.227-7037, Validation of Restrictive Markings on Technical Data (SEP 2011), if applicable (see 227.7102-4(c)).</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>10. Amend section 252.227-7013 by—</AMDPAR>
          <AMDPAR>(a) Amending the clause date by removing “(MAR 2011)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(b) Revising paragraph (k)(2) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.227-7013</SECTNO>
            <SUBJECT>Rights in technical data-Noncommercial items.</SUBJECT>
            <STARS/>
            <P>(k) * * *</P>
            <P>(2) Whenever any technical data for noncommercial items, or for commercial items developed in any part at Government expense, is to be obtained from a subcontractor or supplier for delivery to the Government under this contract, the Contractor shall use this same clause in the subcontract or other contractual instrument, and require its subcontractors or suppliers to do so, without alteration, except to identify the parties. This clause will govern the technical data pertaining to noncommercial items or to any portion of a commercial item that was developed in any part at Government expense, and the clause at 252.227-7015 will govern the technical data pertaining to any portion of a commercial item that was developed exclusively at private expense. No other clause shall be used to enlarge or diminish the Government's, the Contractor's, or a higher-tier subcontractor's or supplier's rights in a subcontractor's or supplier's technical data.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>11. Amend section 252.227-7015 by—</AMDPAR>
          <AMDPAR>(a) Amending the clause date by removing “(MAR 2011)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(b) Adding new paragraph (e) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.227-7015</SECTNO>
            <SUBJECT>Technical data-Commercial items.</SUBJECT>
            <STARS/>
            <P>(e)<E T="03">Applicability to subcontractors or suppliers.</E>
            </P>
            <P>(1) The Contractor shall recognize and protect the rights afforded its subcontractors and suppliers under 10 U.S.C. 2320 and 10 U.S.C. 2321.</P>
            <P>(2) Whenever any technical data related to commercial items developed in any part at private expense will be obtained from a subcontractor or supplier for delivery to the Government under this contract, the Contractor shall use this same clause in the subcontract or other contractual instrument, and require its subcontractors or suppliers to do so, without alteration, except to identify the parties. This clause will govern the technical data pertaining to any portion of a commercial item that was developed exclusively at private expense, and the clause at 252.227-7013 will govern the technical data pertaining to any portion of a commercial item that was developed in any part at Government expense.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>12. Amend section 252.227-7019 by—</AMDPAR>
          <AMDPAR>(a) Amending the clause date by removing “(JUN 1995)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(b) Redesignating paragraphs (f) through (i) as paragraphs (g) through (j), respectively;</AMDPAR>
          <AMDPAR>(c) Adding new paragraph (f);</AMDPAR>
          <AMDPAR>(d) Revising the newly redesignated paragraph (g)(5);</AMDPAR>
          <AMDPAR>(e) Amending the newly redesignated paragraph (h)(1) introductory text by removing “(g)(3)”, and adding in its place “(h)(3)”; and</AMDPAR>
          <AMDPAR>(f) Amending the newly redesignated paragraph h)(3) by removing “(g)(1)”, and adding in its place “(h)(1)”.</AMDPAR>
          <P>The additions and revisions read as follows:</P>
          <SECTION>
            <SECTNO>252.227-7019</SECTNO>
            <SUBJECT>Validation of asserted restrictions-Computer software.</SUBJECT>
            <STARS/>
            <P>(f)<E T="03">Major systems.</E>When the Contracting Officer challenges an asserted restriction regarding noncommercial computer software for a major system or a subsystem or component thereof on the basis that the computer software was not developed exclusively at private expense, the Contracting Officer will sustain the challenge unless information provided by the Contractor or subcontractor demonstrates that the computer software was developed exclusively at private expense.<PRTPAGE P="58149"/>
            </P>
            <P>(g) * * *</P>
            <P>(5) If the Contractor fails to respond to the Contracting Officer's request for information or additional information under paragraph (g)(1) of this clause, the Contracting Officer will issue a final decision, in accordance with paragraph (f) of this clause and the Disputes clause of this contract, pertaining to the validity of the asserted restriction.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>13. Amend 252.227-7037 by—</AMDPAR>
          <AMDPAR>(a) Amending the introductory text by removing “227.7102-3(c)” and adding in its place “227.7102-4(c)”;</AMDPAR>
          <AMDPAR>(b) Amending the clause date by removing “(SEP 1999)” and adding in its place “(SEP 2011)”; and</AMDPAR>
          <AMDPAR>(c) Revising paragraphs (b), (c), (f), and (l) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.227-7037</SECTNO>
            <SUBJECT>Validation of restrictive markings on technical data.</SUBJECT>
            <STARS/>
            <P>(b)<E T="03">Presumption regarding development exclusively at private expense.</E>
            </P>
            <P>(1)<E T="03">Commercial items.</E>For commercially available off-the-shelf items (defined at 41 U.S.C. 104) in all cases, and for all other commercial items except as provided in paragraph (b)(2) of this clause, the Contracting Officer will presume that a Contractor's asserted use or release restrictions are justified on the basis that the item, component, or process was developed exclusively at private expense. The Contracting Officer shall not challenge such assertions unless the Contracting Officer has information that demonstrates that the item, component, or process was not developed exclusively at private expense.</P>
            <P>(2)<E T="03">Major systems.</E>The presumption of development exclusively at private expense does not apply to major systems or subsystems or components thereof, except for commercially available off-the-shelf items (which are governed by paragraph (b)(1) of this clause). When the Contracting Officer challenges an asserted restriction regarding technical data for a major system or a subsystem or component thereof on the basis that the item, component, or process was not developed exclusively at private expense, the Contracting Officer will sustain the challenge unless information provided by the Contractor or subcontractor demonstrates that the item, component, or process was developed exclusively at private expense.</P>
            <P>(c)<E T="03">Justification.</E>The Contractor or subcontractor at any tier is responsible for maintaining records sufficient to justify the validity of its markings that impose restrictions on the Government and others to use, duplicate, or disclose technical data delivered or required to be delivered under the contract or subcontract. Except as provided in paragraph (b)(1) of this clause, the Contractor or subcontractor shall be prepared to furnish to the Contracting Officer a written justification for such restrictive markings in response to a challenge under paragraph (e) of this clause.</P>
            <STARS/>
            <P>(f)<E T="03">Final decision when Contractor or subcontractor fails to respond.</E>Upon a failure of a Contractor or subcontractor to submit any response to the challenge notice the Contracting Officer will issue a final decision to the Contractor or subcontractor in accordance with paragraph (b) of this clause and the Disputes clause of this contract pertaining to the validity of the asserted restriction. This final decision shall be issued as soon as possible after the expiration of the time period of paragraph (e)(1)(ii) or (e)(2) of this clause. Following issuance of the final decision, the Contracting Officer will comply with the procedures in paragraphs (g)(2)(ii) through (iv) of this clause.</P>
            <STARS/>
            <P>(l)<E T="03">Flowdown.</E>The Contractor or subcontractor agrees to insert this clause in contractual instruments with its subcontractors or suppliers at any tier requiring the delivery of technical data.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="252" TITLE="48">
          <AMDPAR>14. Amend section 252.244-7000 by—</AMDPAR>
          <AMDPAR>(a) Amending the clause date by removing “(AUG 2011)” and adding in its place “(SEP 2011)”;</AMDPAR>
          <AMDPAR>(b) Redesignating paragraphs (c) through (h) as (e) through (j), respectively; and</AMDPAR>
          <AMDPAR>(c) Adding new paragraphs (c) and (d) as follows:</AMDPAR>
          <SECTION>
            <SECTNO>252.244-7000</SECTNO>
            <SUBJECT>Subcontracts for commercial items and commercial components (DoD contracts).</SUBJECT>
            <STARS/>
            <P>(c) 252.227-7015, Technical Data—Commercial Items (SEP 2011), if applicable (see 227.7102-4(a)).</P>
            <P>(d) 252.227-7037, Validation of Restrictive Markings on Technical Data (SEP 2011), if applicable (see 227.7102-4(c)).</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23956 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Part 213</CFR>
        <RIN>RIN 0750-AH07</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Ships Bunkers Easy Acquisition (SEA) Card® and Aircraft Ground Services (DFARS Case 2009-D019)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement to allow the use of U.S. Government fuel cards in lieu of a Purchase Order-Invoice-Voucher for fuel, oil, and refueling-related items for purchases not exceeding the simplified acquisition threshold.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Dustin Pitsch, telephone 703-602-0289.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DoD published a proposed rule in the<E T="04">Federal register</E>at 76 FR 21849 on April 19, 2011, to add language to Defense Federal Acquisition Regulation Supplement (DFARS) 213.306(a)(1)(A) to include purchases of marine fuel, oil, and refueling-related items up to the simplified acquisition threshold using the Ships Bunkers Easy Acquisition (SEA) Card® in lieu of the SF 44, Purchase Order-Invoice-Voucher. Additionally, this section is revised to include additional ground refueling-related services when using the AIR Card®. These changes for use of the AIR Card® and SEA Card® will improve the refueling capability of aircraft and smaller vessels at non-contract locations. No public comments were received in response to the proposed rule.</P>
        <HD SOURCE="HD1">II. 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 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<PRTPAGE P="58150"/>equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, was not subject to review under Section 6(b) of Executive Order 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>

        <P>A final regulatory flexibility analysis has been prepared consistent with the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.,</E>and is summarized as follows:</P>
        <P>This is a final rule to revise the Defense Federal Acquisition Regulation Supplement (DFARS) at 213 to permit the use of U.S. Government fuel cards in lieu of an SF 44, Purchase Order-Invoice-Voucher, for fuel, oil, and refueling-related items for purchases not exceeding the simplified acquisition threshold. The objective of this rule is to amend DFARS 213.306(a)(1)(A) to (1) Permit the purchase of marine fuel using the Ships' bunkers Easy Acquisition (SEA) Card® in lieu of the SF44, Purchase Order-Invoice-Voucher, up to the simplified acquisition threshold and (2) provide additional ground refueling-related services when using the AIR Card®. The legal basis is 41 U.S.C. 1303 and 48 CFR chapter 1.</P>
        <P>Purchases of aviation fuel are on-the-spot, over the counter transactions (“gas and go”), but generally exceed the micro-purchase threshold due to the price of aviation fuel and oil fuel tank capacities. Previously, the threshold for SF44/AIR Card® purchases of fuel and oil was set at the simplified acquisition threshold at DFARS 213.306(a)(1)(A)) under DFARS Case 2007-D017 (see final rule published at 72 FR 6484 on February 12, 2007).</P>
        <P>The military services and the U.S. Coast Guard have small vessels that fulfill valid mission needs in direct support of national security. Unlike larger vessels, small vessels' movements and needs are often unpredictable. These small vessels must procure fuel away from their home stations, but because of their smaller size and unique mission requirements are unable to use the Defense Logistics Agency energy bunkers contracts available at major seaports. Due to port restrictions, bunkering merchants do not typically provide support to smaller vessels. Instead, these smaller vessels frequent non-contract merchants or “marina-type merchants” that otherwise serve civilian recreational watercraft and similar needs.</P>
        <P>No public comments were received in response to the initial regulatory flexibility analysis.</P>
        <P>Approximately 80% of “marina-type merchants” are considered small businesses. Marina-type merchants accepting the SEA Card® will pay a normal fee to the banking institution or processing center, similar to VISA charges these merchants incur from other credit card clients. In addition, merchants are expected to benefit from accelerated payments, since they will be paid by the banking institution in accordance with their merchant agreement. The rule facilitates open market purchases, benefits merchants by making it much easier for merchants to do business with the military and will not have a significant cost or administrative impact on contractors, subcontractors, or offerors.</P>

        <P>DoD does not expect this rule to have a significant economic impact on 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>because the rule does not have a significant effect beyond DoD's internal operating procedures, substituting the use of a fuel card (AIR Card® and SEA Card®) in lieu of the SF44, Purchase Order-Invoice-Voucher.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>This rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Part 213</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR part 213 is amended as follows:</P>
        <REGTEXT PART="213" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 213—SIMPLIFIED ACQUISITION PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for 48 CFR part 213 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="213" TITLE="48">
          <AMDPAR>2. Section 213.306 is amended to revise paragraph (a)(1)(A) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>213.306</SECTNO>
            <SUBJECT>SF 44, Purchase Order-Invoice-Voucher.</SUBJECT>
            <P>(a)(1) * * *</P>
            <P>(A)<E T="03">Fuel and oil.</E>U.S. Government fuel cards may be used in lieu of an SF 44 for fuel, oil, and authorized refueling-related items (see PGI 213.306 for procedures on use of fuel cards);</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23944 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Part 215</CFR>
        <RIN>RIN 0750-AG82</RIN>
        <SUBJECT>Defense Federal Acquisition Regulations Supplement; Discussions Prior to Contract Award (DFARS Case 2010-D013)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is amending the Defense Federal Acquisition Regulation Supplement (DFARS) to strongly encourage discussions prior to award for source selections of procurements estimated at $100 million or more.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Dustin Pitsch, telephone 703-602-0289.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>DoD published a proposed rule at 75 FR 71647 on November 24, 2010, to implement the recommendation of the DoD Source Selection Joint Analysis Team (JAT) to strongly encourage the use of discussions in all competitive negotiated procurements over $100 million. The period for public comment closed on January 24, 2011, and three respondents provided comments.</P>
        <P>The rule proposed to amend DFARS part 215 to strongly recommend, for acquisitions of more than $100 million, that contracting officers hold discussions rather than use the authority at FAR 52.215-1 to award on initial offers without discussions.</P>
        <HD SOURCE="HD1">II. Discussion and Analysis</HD>
        <HD SOURCE="HD2">A. Proposed rule is excessive</HD>
        <P>
          <E T="03">Comment:</E>One respondent said that the proposed rule is “overkill.”</P>
        <P>
          <E T="03">Response:</E>No change was made in the final rule in response to this comment. The JAT advises that data shows that the number of protests filed against the award of competitive negotiated contracts and orders over $100 million is substantially higher when discussions are not held. A preference for holding<PRTPAGE P="58151"/>discussions is recognition of a best practice.</P>
        <HD SOURCE="HD2">B. Negative effects possible</HD>
        <P>
          <E T="03">Comment:</E>One respondent wrote that requiring discussions could have negative effects, such as added Government and industry cost due to the significant increase in the source selection schedule and reduced solicitation and proposal quality due to a mindset that problems can be fixed during discussions.</P>
        <P>
          <E T="03">Response:</E>The JAT data demonstrates that procurement lead time is significantly extended when protests occurred. The second concern raised by the respondent, that proposals will be of lower quality, is unrealistic because the offeror that chooses to submit an inferior proposal always runs the risk of not making the competitive range and therefore not being considered for award.</P>
        <HD SOURCE="HD2">C. Change reference</HD>
        <P>
          <E T="03">Comment:</E>A respondent wanted to change the reference from 215.203-71 to 215.306(d) because the latter deals with discussions, which are covered at FAR 15.306(d).</P>
        <P>
          <E T="03">Response:</E>DoD agrees with the recommendation. The statement about holding discussions for actions of $100 million or more is relocated in the final rule to DFARS subpart 215.306(c) from 215.2.</P>
        <HD SOURCE="HD2">D. Remove “competitive range” limitation</HD>
        <P>
          <E T="03">Comment:</E>A respondent proposed deleting the phrase “with offerors in the competitive range” at the end of the sentence “(F)or source selections when the procurement is $100 million or more, contracting officers should conduct discussions with offerors in the competitive range.” The respondent noted that FAR 15.306(c)(1) and (d), read together, require the conduct of discussions with all offerors in the competitive range in every case.</P>
        <P>
          <E T="03">Response:</E>DoD agrees with respondent that the FAR already mandates discussions with all offerors whose proposals have been selected for the competitive range. The intent of this rule is to expand the situations in which discussions are held beyond those situations where they may be already mandated. The language in the proposed rule at DFARS 215.203-71 is relocated to 215.306(c)(1) in the final rule and revised to state “For source selections, when the procurement is $100 million or more, contracting officers should conduct discussions. Follow the procedures at FAR 15.306(c) and (d).”</P>
        <HD SOURCE="HD1">III. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is a significant regulatory action and, therefore, was subject to review under Section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>
        <P>DoD does not expect that this final rule will not have a significant economic impact on a substantial number of small entities within the meaning of the Regulatory Flexibility Act, 5 U.S.C. 601, et seq., because the final rule does not add to or delete existing regulations on discussions for DoD procurements under $100 million, the majority of DoD procurements. For procurements of at least $100 million, any increase in discussions is anticipated to benefit all offerors, including small businesses, by providing them an opportunity to explain details of the offer and address their particular capabilities.</P>
        <P>A final regulatory flexibility analysis was performed and is summarized as follows. This rule was initiated at the request of the Director, Defense Procurement and Acquisition Policy, to implement a recommendation of the Department of Defense (DoD) Source Selection Joint Analysis Team (JAT). The JAT, which was tasked to revise the DoD Source Selection Procedures, determined that there is a significant positive correlation between high-dollar source selections conducted without discussions and the number of protests sustained. In order to improve the quality of high-dollar, complex source selections, and reduce turbulence and inefficiency resulting from sustained protests, the policy is changed to strongly encourage discussions prior to the award of source selections estimated at $100 million or more.</P>
        <P>DoD research has indicated that meaningful discussions with industry prior to contract award on high-dollar, complex requirements improves both industry's understanding of solicitation requirements and the Government's understanding of industry issues. By identifying and discussing these issues prior to submission of final proposals, the Government is often able to issue clarifying language. The modified requirements documentation allows industry to tailor proposals and better describe the offeror's intended approach, increases the probability that the offeror's proposal satisfies the Government requirements, and often results in better contract performance. Asking contracting officers to conduct discussions with industry provides a reasonable approach to recognizing and addressing valid industry concerns and a constructive alternative to protests resulting from industry frustration over misunderstood requirements. The legal basis is 41 U.S.C. 1303 and 48 CFR chapter 1.</P>
        <P>Data were reviewed for the most recent year available, Fiscal Year 2009. While there is no data source available that tabulates the number of offers received from small businesses, DoD determined that 620 new contracts and 252 new task orders or delivery orders of $100 million or more were awarded to small businesses during Fiscal Year 2009. Therefore, DoD estimates that at least 872 small businesses could benefit from this policy change.</P>
        <P>There is no reporting, recordkeeping, or other compliance requirement associated with the proposed rule. Therefore, there is no impact, positive or negative, on small businesses in this area. Thus, there are no additional professional skills necessary on the part of small businesses in this area. There are no direct costs to small business firms to comply with this rule. Conversely, small businesses that might have previously filed a protest against an award when discussions were not held may now be able to avoid the costs associated with protesting.</P>
        <P>The rule does not duplicate, overlap, or conflict with any other Federal rules.</P>

        <P>There are no practical alternatives that will accomplish the objectives of the proposed rule. When a solicitation includes the provision at FAR 52.215-1, Instructions to Offerors—Competitive Acquisitions, paragraph (f)(4) of the clause states that the “Government intends to evaluate proposals and award a contract without discussions.” If, however, the solicitation includes FAR 52.215-1 with its Alternate I, then the revised paragraph (f)(4) states that the “Government intends to evaluate proposals and award a contract after conducting discussions with offerors whose proposals have been determined to be within the competitive range.” Use of the clause without Alternate I will not accomplish the stated objectives;<PRTPAGE P="58152"/>only the clause with its Alternate I will accomplish the purpose of this case.</P>
        <P>No comments were received from small entities on this rule.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act.</HD>
        <P>The final rule does not contain any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Part 215</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR part 215 is amended as follows:</P>
        <REGTEXT PART="215" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 215—CONTRACTING BY NEGOTIATION</HD>
          </PART>
          <AMDPAR>1. The authority citation for 48 CFR part 215 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="215" TITLE="48">
          <AMDPAR>2. Section 215.209 is added as follows:</AMDPAR>
          <SECTION>
            <SECTNO>215.209</SECTNO>
            <SUBJECT>Solicitation provisions and contract clauses.</SUBJECT>
            <P>(a) For source selections when the procurement is $100 million or more, contracting officers should use the provision at FAR 52.215-1, Instructions to Offerors—Competitive Acquisition, with its Alternate I.</P>
          </SECTION>
          <AMDPAR>3. Section 215.306 is added as follows:</AMDPAR>
          <SECTION>
            <SECTNO>215.306</SECTNO>
            <SUBJECT>Exchanges with offerors after receipt of proposals.</SUBJECT>
            <P>(c)<E T="03">Competitive range.</E>
            </P>
            <P>(1) For acquisitions with an estimated value of $100 million or more, contracting officers should conduct discussions. Follow the procedures at FAR 15.306(c) and (d).</P>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23949 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Parts 217 and 241</CFR>
        <RIN>RIN 0750-AG89</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Multiyear Contracting (DFARS Case 2009-D026)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to update and clarify the requirements for multiyear contracting.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Manuel Quinones, telephone (703) 602-8383.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>This DFARS case was initiated by DoD to perform a comprehensive review of DFARS subpart 217.1, Multiyear Contracting. On March 2, 2011, the DoD published a proposed rule to update and clarify the requirements relating to multiyear contracting. This final rule reorganizes and updates existing coverage for multiyear acquisitions.</P>
        <P>A minor editorial change was made to the final rule at DFARS 217.170 to remove the redundant introductory sentence that had been proposed at 217.170(a) and to revert to the original paragraph numbering of this section. At DFARS 217.172(f)(1), the references to 217.172(g)(4) and (5) were corrected to refer to 217.172(g)(3) and (4). Coverage at 217.175 was renumbered to 217.174 to follow in sequence, and this required a reference citation change at 241.103. No changes to existing DoD policy, including implementation of any statutorily mandated acquisition-related thresholds, are being made in this rule.</P>
        <HD SOURCE="HD1">II. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, is not subject to review under section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>

        <P>DoD certifies that this rule will not have a 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>because the rule does not change the existing requirements of subpart 217.1. Furthermore, these requirements are primarily internal procedures for DoD. No comments were received from small entities concerning the existing regulations in subparts affected by this rule in accordance with 5 U.S.C. 610.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>This rule does not impose any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 48 CFR Parts 217 and 241:</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        
        <P>Therefore, 48 CFR parts 217 and 241 are amended as follows:</P>
        <REGTEXT PART="217" TITLE="48">
          <AMDPAR>1. The authority citation for 48 CFR parts 217 and 241 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 217—SPECIAL CONTRACTING METHODS</HD>
          </PART>
          <AMDPAR>2. Section 217.170 is amended by—</AMDPAR>
          <AMDPAR>a. Amending paragraph (a), by removing “Section” and adding in its place “section” and removing “Public Law 105-56” and adding in its place “Pub. L. 105-56,”;</AMDPAR>
          <AMDPAR>b. Amending paragraph (b), by removing “217.172(f)(2)” and adding in its place “217.172(g)(2)”;</AMDPAR>
          <AMDPAR>c. Amending paragraph (c) by removing “Section” and adding in its place “section” and removing “Public Law 105-56” and adding in its place “Pub. L. 105-56,”;</AMDPAR>
          <AMDPAR>d. Amending paragraph (c) by removing in the listing of references “;” in two places and adding in its place “,”; and</AMDPAR>
          <AMDPAR>e. Revising paragraph (e) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>217.170</SECTNO>
            <SUBJECT>General.</SUBJECT>
            <STARS/>
            <P>(e)(1) DoD must provide notification to the congressional defense committees at least 30 days before entering into a multiyear contract for certain procurements, including those expected to—</P>

            <P>(i) Employ an unfunded contingent liability in excess of $20 million (see 10 U.S.C. 2306b(l)(1)(B)(i)(II), 10 U.S.C. 2306c(d)(1), and section 8008(a) of Pub. L. 105-56 and similar sections in subsequent DoD appropriations acts);<PRTPAGE P="58153"/>
            </P>
            <P>(ii) Employ economic order quantity procurement in excess of $20 million in any one year of the contract (10 U.S.C. 2306b(l)(1)(B)(i)(I));</P>
            <P>(iii) Involve a contract for advance procurement leading to a multiyear contract that employs economic order quantity procurement in excess of $20 million in any one year (see 10 U.S.C. 306b(l)(1)(B)(ii) and section 8008(a) of Pub. L. 105-56 and similar sections in subsequent DoD appropriations acts); or</P>
            <P>(iv) Include a cancellation ceiling in excess of $100 million (see 10 U.S.C. 2306c(d)(4), 10 U.S.C. 2306b(g), and section 8008(a) of Pub. L. 105-56 and similar sections in subsequent DoD appropriations acts).</P>
            <P>(2) A DoD component must submit a request for authority to enter into a multiyear contract described in paragraphs (e)(1)(i) through (iv) of this section as part of the component's budget submission for the fiscal year in which the multiyear contract will be initiated. DoD will include the request, for each candidate it supports, as part of the President's budget for that year and in the Appendix to that budget as part of proposed legislative language for the appropriations bill for that year (section 8008(b) of Pub. L. 105-56).</P>
            <P>(3) If the advisability of using a multiyear contract becomes apparent too late to satisfy the requirements in paragraph (e)(2) of this section, the request for authority to enter into a multiyear contract must be—</P>
            <P>(i) Formally submitted by the President as a budget amendment; or</P>
            <P>(ii) Made by the Secretary of Defense, in writing, to the congressional defense committees (see section 8008(b) of Pub. L. 105-56).</P>
            <P>(4) Agencies must establish reporting procedures to meet the congressional notification requirements of paragraph (e)(1) of this section. The head of the agency must submit a copy of each notice to the Director of Defense Procurement and Acquisition Policy, Office of the Under Secretary of Defense (Acquisition, Technology, and Logistics) (OUSD(AT&amp;L)DPAP), and to the Deputy Under Secretary of Defense (Comptroller) (Program/Budget) (OUSD(C)(P/B)).</P>
            <P>(5) If the budget for a contract that contains a cancellation ceiling in excess of $100 million does not include proposed funding for the costs of contract cancellation up to the cancellation ceiling established in the contract—</P>
            <P>(i) The notification required by paragraph (e)(1) of this section shall include—</P>
            <P>(A) The cancellation ceiling amounts planned for each program year in the proposed multiyear contract, together with the reasons for the amounts planned;</P>
            <P>(B) The extent to which costs of contract cancellation are not included in the budget for the contract; and</P>
            <P>(C) A financial risk assessment of not including budgeting for costs of contract cancellation (10 U.S.C. 2306b(g) and 10 U.S.C. 2306c(d)); and</P>
            <P>(ii) The head of the agency shall provide copies of the notification to the Office of Management and Budget at least 14 days before contract award.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <AMDPAR>3. Amend section 217.171 by—</AMDPAR>
          <AMDPAR>(a) Removing paragraphs (a)(4) through (a)(6) and paragraph (b);</AMDPAR>
          <AMDPAR>(c) Redesignating paragraphs (a)(2), (a)(2)(i), (a)(2)(ii), and (a)(2)(iii) as paragraphs (b), (b)(1), (b)(2), and (b)(3), respectively;</AMDPAR>
          <AMDPAR>(d) Redesignating paragraphs (a)(3), (a)(3)(i), (a)(3)(ii), (a)(3)(ii)(A), (a)(3)(ii)(B) and (a)(3)(iii) as paragraphs (c), (c)(1), (c)(2), (C)(2)(i), (c)(2)(ii) and (c)(3), respectively; and</AMDPAR>
          <AMDPAR>(f) Revising paragraph (a) as set forth below.The revision reads as follows:</AMDPAR>
          <SECTION>
            <SECTNO>217.171</SECTNO>
            <SUBJECT>Multiyear contracts for services.</SUBJECT>
            <P>(a) The head of the agency may enter into a multiyear contract for a period of not more than 5 years for the following types of services (and items of supply relating to such services), even though funds are limited by statute to obligation only during the fiscal year for which they were appropriated (10 U.S.C. 2306c). Covered services are—</P>
            <P>(1) Operation, maintenance, and support of facilities and installations;</P>
            <P>(2) Maintenance or modification of aircraft, ships, vehicles, and other highly complex military equipment;</P>

            <P>(3) Specialized training requiring high-quality instructor skills (<E T="03">e.g.,</E>training for pilots and aircrew members or foreign language training);</P>
            <P>(4) Base services (<E T="03">e.g.,</E>ground maintenance, in-plane refueling, bus transportation, and refuse collection and disposal); and</P>
            <P>(5) Environmental remediation services for—</P>
            <P>(i) An active military installation;</P>
            <P>(ii) A military installation being closed or realigned under a base closure law as defined in 10 U.S.C. 2667(h)(2); or</P>
            <P>(iii) A site formerly used by DoD.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <AMDPAR>4. Section 217.172 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>217.172</SECTNO>
            <SUBJECT>Multiyear contracts for supplies.</SUBJECT>
            <P>(a) This section applies to all multiyear contracts for supplies, including weapon systems and other multiyear acquisitions specifically authorized by law (10 U.S.C. 2306b).</P>
            <P>(b) The head of the agency may enter into a multiyear contract for supplies if, in addition to the conditions listed in FAR 17.105-1(b), the use of such a contract will promote the national security of the United States (10 U.S.C. 2306b(a)(6)).</P>
            <P>(c) Multiyear contracts in amounts exceeding $500 million must be specifically authorized by law (10 U.S.C. 2306b and 10 U.S.C. 2306c). A multiyear supply contract may be authorized by an appropriations act or a law other than an appropriations act (10 U.S.C. 2306b(i)(3) and (l)(3)).</P>
            <P>(d) The head of the agency shall not enter into a multiyear contract unless—</P>
            <P>(1) The Secretary of Defense has submitted to Congress a budget request for full funding of units to be procured through the contract; and</P>
            <P>(2) In the case of a contract for procurement of aircraft, the budget request includes full funding of procurement funds for production beyond advance procurement activities of aircraft units to be produced in the fiscal year covered by the budget.</P>
            <P>(e)(1) The head of the agency must not enter into or extend a multiyear contract that exceeds $500 million (when entered into or extended until the Secretary of Defense identifies the contract and any extension in a report submitted to the congressional defense committees (10 U.S.C. 2306b(1)(5)).</P>
            <P>(2) In addition, for contracts equal to or greater than $500 million, the head of the contracting activity must determine that the conditions required by paragraph (g)(2)(i) through (vii) of this section will be met by such contract, in accordance with the Secretary's certification and determination required by paragraph (g)(2) of this section (10 U.S.C. 2306b(a)(1)(7)).</P>
            <P>(f) The head of the agency may enter into a multiyear contract for—</P>
            <P>(1) A weapon system and associated items, services, and logistics support for a weapon system; and</P>

            <P>(2) Advance procurement of components, parts, and materials necessary to manufacture a weapon system, including advance procurement to achieve economic lot purchases or more efficient production rates (see 217.172(g)(3) and (4) regarding economic order quantity procurements). Before initiating an advance procurement, the contracting officer must verify that it is consistent with DoD policy (<E T="03">e.g.,</E>the full funding policy in Volume 2A, chapter 1, of DoD 7000.14-R, Financial Management Regulation).<PRTPAGE P="58154"/>
            </P>
            <P>(g) The head of the agency shall ensure that the following conditions are satisfied before awarding a multiyear contract under the authority described in paragraph (b) of this section:</P>
            <P>(1) The multiyear exhibits required by DoD 7000.14-R, Financial Management Regulation, are included in the agency's budget estimate submission and the President's budget request.</P>
            <P>(2) The Secretary of Defense certifies to Congress in writing, by no later than March 1 of the year in which the Secretary requests legislative authority to enter into such contracts, that each of the conditions in paragraphs (g)(2)(i) through (vii) of this section is are satisfied (10 U.S.C. 2306b(i)(1)(A) through (G)).</P>
            <P>(i) The Secretary has determined that each of the requirements in FAR 17.105, paragraphs (b)(1) through (5) will be met by such contract and has provided the basis for such determination to the congressional defense committees (10 U.S.C. 2306b(i)(1)(A)).</P>
            <P>(ii) The Secretary's determination under paragraph (g)(2)(i) of this section was made after the completion of a cost analysis performed by the Defense Cost and Resource Center of the Department of Defense and such analysis supports the findings (10 U.S.C. 2306b(i)(1)(B)).</P>
            <P>(iii) The system being acquired pursuant to such contract has not been determined to have experienced cost growth in excess of the critical cost growth threshold pursuant to 10 USC 2433(d) within 5 years prior to the date the Secretary anticipates such contract (or a contract for advance procurement entered into consistent with the authorization for such contract) will be awarded (10 U.S.C. 2306b(i)(1)(C)).</P>
            <P>(iv) A sufficient number of end items of the system being acquired under such contract have been delivered at or within the most current estimates of the program acquisition unit cost or procurement unit cost for such system to determine that current estimates of such unit costs are realistic (10 U.S.C. 2306b(i)(1)(D)).</P>
            <P>(v) Sufficient funds will be available in the fiscal year in which the contract is to be awarded to perform the contract, and the future-years defense program for such fiscal year will include the funding required to execute the program without cancellation (10 U.S.C. 2306b(i)(1)(E)).</P>
            <P>(vi) The contract is a fixed price type contract (10 U.S.C. 2306b(i)(1)(F)).</P>
            <P>(vii) The proposed multiyear contract provides for production at not less than minimum economic rates, given the existing tooling and facilities. The head of the agency shall submit to USD(C)(P/B) information supporting the agency's determination that this requirement has been met (10 U.S.C. 2306b(i)(1)(G)).</P>
            <P>(viii) The head of the agency shall submit information supporting this certification to USD(C)(P/B) for transmission to Congress through the Secretary of Defense.</P>
            <P>(A) The head of the agency shall, as part of this certification, give written notification to the congressional defense committees of—</P>
            <P>
              <E T="03">(1)</E>The cancellation ceiling amounts planned for each program year in the proposed multiyear contract, together with the reasons for the amounts planned;</P>
            <P>
              <E T="03">(2)</E>The extent to which costs of contract cancellation are not included in the budget for the contract; and</P>
            <P>
              <E T="03">(3)</E>A financial risk assessment of not including the budgeting for costs of contract cancellation (10 U.S.C. 2306b(g)); and</P>
            <P>(B) The head of the agency shall provide copies of the notification to the Office of Management and Budget at least 14 days before contract award.</P>
            <P>(3) The contract is for the procurement of a complete and usable end item (10 U.S.C. 2306b(i)(4)(A)).</P>
            <P>(4) Funds appropriated for any fiscal year for advance procurement are obligated only for the procurement of those long-lead items that are necessary in order to meet a planned delivery schedule for complete major end items that are programmed under the contract to be acquired with funds appropriated for a subsequent fiscal year (including an economic order quantity of such long-lead items when authorized by law (10 U.S.C. 2306b(i)(4)(B)).</P>
            <P>(5) The Secretary may make the certification under paragraph (g)(2) of this section notwithstanding the fact that one or more of the conditions of such certification are not met if the Secretary determines that, due to exceptional circumstances, proceeding with a multiyear contract under this section is in the best interest of the Department of Defense and the Secretary provides the basis for such determination with the certification (10 U.S.C. 2306b(i)(5)).</P>
            <P>(6) The Secretary of Defense may not delegate this authority to make the certification under paragraph (g)(2) of this section or the determination under paragraph (g)(5) of this section to an official below the level of the Under Secretary of Defense for Acquisition, Technology, and Logistics (10 U.S.C. 2306b(i)(6)).</P>
            <P>(7) The Secretary of Defense shall send a notification containing the findings of the agency head under FAR 17.105-1(b), and the basis for such findings, 30 days prior to the award of a multiyear contract or a defense acquisition program that has been specifically authorized by law to the congressional defense committees (10 U.S.C. 2306b(i)(7)).</P>
            <P>(8) All other requirements of law are met and there are no other statutory restrictions on using a multiyear contract for the specific system or component (10 U.S.C. 2306b(i)(2)). One such restriction may be the achievement of specified cost savings. If the agency finds, after negotiations with the contractor(s), that the specified savings cannot be achieved, the head of the agency shall assess the savings that, nevertheless, could be achieved by using a multiyear contract. If the savings are substantial, the head of the agency may request relief from the law's specific savings requirement. The request shall—</P>
            <P>(i) Quantify the savings that can be achieved;</P>
            <P>(ii) Explain any other benefits to the Government of using the multiyear contract;</P>
            <P>(iii) Include details regarding the negotiated contract terms and conditions; and</P>
            <P>(iv) Be submitted to OUSD(AT&amp;L)DPAP for transmission to Congress via the Secretary of Defense and the President.</P>
            <P>(h) The Secretary of Defense may instruct the head of the agency proposing a multiyear contract to include in that contract negotiated priced options for varying the quantities of end items to be procured over the life of the contract (10 U.S.C. 2306b(j)).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <AMDPAR>5. Section 217.173 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>217.173</SECTNO>
            <SUBJECT>Multiyear contracts for military family housing.</SUBJECT>
            <P>The head of the agency may enter into multiyear contracts for periods up to 4 years for supplies and services required for management, maintenance, and operation of military family housing and may pay the costs of such contracts for each year from annual appropriations for that year (10 U.S.C. 2829).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <SECTION>
            <SECTNO>217.174</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>6. Section 217.174 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="217" TITLE="48">
          <AMDPAR>7. Section 217.175 is redesignated as 217.174 and the newly redesignated section 217.174 paragraph (b) is revised as set forth below.</AMDPAR>
          <SECTION>
            <SECTNO>217.174</SECTNO>
            <SUBJECT>Multiyear contracts for electricity from renewable energy sources.</SUBJECT>
            <STARS/>
            <P>(b)<E T="03">Limitations.</E>The head of the contracting activity may exercise the authority in paragraph (a) of this section to enter into a contract for a period in<PRTPAGE P="58155"/>excess of 5 years only if the head of the contracting activity determines, on the basis of a business case analysis (see PGI 217.174 for a business case analysis template and guidance) prepared by the requiring activity, that—</P>
            <P>(1) The proposed purchase of electricity under such contract is cost effective; and</P>
            <P>(2) It would not be possible to purchase electricity from the source in an economical manner without the use of a contract for a period in excess of 5 years.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="241" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 241—ACQUISITION OF UTILITY SERVICES</HD>
          </PART>
          <AMDPAR>8. Section 241.103 paragraph (2) is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>241.103</SECTNO>
            <SUBJECT>Statutory and delegated authority.</SUBJECT>
            <STARS/>
            <P>(2) See 217.174 for authority to enter into multiyear contracts for electricity from renewable energy sources.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23963 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Defense Acquisition Regulations System</SUBAGY>
        <CFR>48 CFR Part 236</CFR>
        <RIN>RIN 0750-AG91</RIN>
        <SUBJECT>Defense Federal Acquisition Regulation Supplement; Construction and Architect-Engineer Services Performance Evaluation (DFARS Case 2010-D024)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Acquisition Regulations System, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>DoD is issuing a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to remove the requirement to use DoD-unique forms to prepare contractor performance evaluations for construction and architect-engineer services.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>September 20, 2011.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Manuel Quinones, telephone, (703) 602-8383.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>

        <P>This rule removes the requirement to use DoD-unique forms to document contractor past performance for construction and Architect-Engineer services. On April 19, 2011, DoD published a proposed rule in the<E T="04">Federal Register</E>at 75 FR 21851 to delete outdated procedures and references to obsolete DD forms. No public comments were received in response to the proposed rule.</P>
        <P>One editorial change is being made to the final rule. The references to “A-E” are revised to read “architect-engineer” in sections 236.102, 236.602-70, 236.606-70, and in 236.609-70.</P>
        <HD SOURCE="HD1">II. Executive Orders 12866 and 13563</HD>
        <P>Executive Orders (E.O.s) 12866 and 13563 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). E.O. 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, is not subject to review under section 6(b) of E.O. 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.</P>
        <HD SOURCE="HD1">III. Regulatory Flexibility Act</HD>

        <P>A final regulatory flexibility analysis has been prepared consistent with the Regulatory Flexibility Act, 5 U.S.C. 601,<E T="03">et seq.,</E>and is summarized as follows.</P>
        <P>DoD is amending the DFARS to reflect the current automated process being used by and delete outdated procedures and references to obsolete DD forms. The objective of this rule is to remove the requirement to use DD Form 2626, Performance Evaluation (Construction), and DD Form 2631, Performance Evaluation (Architect-Engineer), to evaluate contractor performance.</P>
        <P>The Contractor Performance Assessment Report System (CPARS) is now the Governmentwide system for electronically collecting past performance data; there is no need to specify separate DoD forms to collect the data. Accordingly, this rule removes the requirement to use DD forms 2626 and 2631 from the DFARS.</P>
        <P>On April 19, 2011, DoD published a proposed rule at 75 FR 21851. The period for public comments closed on June 20, 2011. DoD made no changes to the proposed rule because public comments were not received in response to the initial regulatory flexibility analysis.</P>
        <P>There are no reporting, recordkeeping, or other compliance requirements associated with this rule. Thus, there are no professional skills necessary on the part of small businesses. In a like manner, there are no direct costs to small entities to comply with this rule other than the cost of internet access should small entities choose to comment on their past performance evaluation entered into CPARS by Government personnel.</P>
        <P>There are no known relevant Federal rules that may duplicate, overlap or conflict with this rule. Instead, the rule aligns the DFARS to the Federal Acquisition Regulation (FAR) ensuring that agencies submit past performance reports electronically per FAR 42.15 eliminating the need for paper reports.</P>
        <P>No mitigation steps were taken, since the rule does not have a significant adverse economic impact on small entities.</P>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>This rule does not impose any information collection requirements that require the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of subjects in 48 CFR Part 236</HD>
          <P>Government procurement.</P>
        </LSTSUB>
        <SIG>
          <NAME>Mary Overstreet,</NAME>
          <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
        </SIG>
        <P>Therefore, 48 CFR part 236 is amended as follows:</P>
        <REGTEXT PART="236" TITLE="48">
          <PART>
            <HD SOURCE="HED">PART 236—CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS</HD>
          </PART>
          <AMDPAR>1. The authority citation for 48 CFR part 236 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>41 U.S.C. 1303 and 48 CFR chapter 1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="236" TITLE="48">
          <SECTION>
            <SECTNO>236.102</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Amend section 236.102 by—</AMDPAR>
          <AMDPAR>(a) Removing paragraph designations (1) through (4);</AMDPAR>
          <AMDPAR>(b) Redesignating paragraphs (i) and (ii) in the definitions of “Construction activity” as paragraphs (1) and (2); and</AMDPAR>
          <AMDPAR>(c) Removing the definition of “A-E”.</AMDPAR>
          <SECTION>
            <SECTNO>236.201</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>3. Section 236.201 is removed.</AMDPAR>
          <SECTION>
            <SECTNO>236.602-70</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>4. Amend section 236.602-70 by removing “A-E” and adding in its place “architect-engineer”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="236" TITLE="48">
          <AMDPAR>5. Revise section 236.604 to read as follows:</AMDPAR>
          <SECTION>
            <PRTPAGE P="58156"/>
            <SECTNO>236.604</SECTNO>
            <SUBJECT>Performance evaluation.</SUBJECT>
            <P>Prepare a separate performance evaluation after actual construction of the project. Ordinarily, the evaluating official should be the person most familiar with the architect-engineer contractor's performance.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="236" TITLE="48">
          <SECTION>
            <SECTNO>236.606-70</SECTNO>
            <SUBJECT>Statutory fee limitation. [Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>6. Amend section 236.606-70(a) to remove “A-E” and add in its place “architect-engineer”.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="236" TITLE="48">
          <SECTION>
            <SECTNO>236.609-70</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>7. Amend section 236.609-70 as follows—</AMDPAR>
          <AMDPAR>(a) In paragraph (a)(1) introductory text remove “A-E” and add in its place “architect-engineer”.</AMDPAR>
          <AMDPAR>(b) In paragraph (a)(1)(ii) remove “A-E” and add in its place “architect-engineer contractor”.</AMDPAR>
          <AMDPAR>(c) In paragraph (b) introductory text remove “A-E” and add in its place “architect-engineer”.</AMDPAR>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23952 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-08-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 679</CFR>
        <DEPDOC>[Docket No. 101126522-0640-02]</DEPDOC>
        <RIN>RIN 0648-XA710</RIN>
        <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Pollock in Statistical Area 610 in the Gulf of Alaska</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>Temporary rule; closure.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS is prohibiting directed fishing for pollock in Statistical Area 610 in the Gulf of Alaska (GOA). This action is necessary to prevent exceeding the C season allowance of the 2011 total allowable catch of pollock for Statistical Area 610 in the GOA.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective 1200 hrs, Alaska local time (A.l.t.), September 17, 2011, through 1200 hrs, A.l.t., October 1, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Josh Keaton, 907-586-7228.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>NMFS manages the groundfish fishery in the GOA exclusive economic zone according to the Fishery Management Plan for Groundfish of the Gulf of Alaska (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50 CFR part 600 and 50 CFR part 679.</P>
        <P>The C season allowance of the 2011 total allowable catch (TAC) of pollock in Statistical Area 610 of the GOA is 8,729 metric tons (mt) as established by the final 2011 and 2012 harvest specifications for groundfish of the GOA (76 FR 11111, March 1, 2011). In accordance with § 679.20(a)(5)(iv)(B) the Administrator, Alaska Region, NMFS (Regional Administrator), hereby decreases the C season pollock allowance by 123 mt to reflect the total amount of pollock TAC that has been caught prior to the C season in Statistical Area 610. Therefore, the revised C season allowance of the pollock TAC in Statistical Area 610 is 8,606 mt (8,729 mt minus 123 mt).</P>
        <P>In accordance with § 679.20(d)(1)(i), the Regional Administrator has determined that the C season allowance of the 2011 TAC of pollock in Statistical Area 610 of the GOA will soon be reached. Therefore, the Regional Administrator is establishing a directed fishing allowance of 8,506 mt, and is setting aside the remaining 100 mt as bycatch to support other anticipated groundfish fisheries. In accordance with § 679.20(d)(1)(iii), the Regional Administrator finds that this directed fishing allowance has been reached. Consequently, NMFS is prohibiting directed fishing for pollock in Statistical Area 610 of the GOA.</P>
        <P>After the effective date of this closure the maximum retainable amounts at § 679.20(e) and (f) apply at any time during a trip.</P>
        <HD SOURCE="HD1">Classification</HD>
        <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the closure of pollock in Statistical Area 610 of the GOA. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of September 14, 2011.</P>
        <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
        <P>This action is required by § 679.20 and is exempt from review under Executive Order 12866.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: September 15, 2011.</DATED>
          <NAME>Steven Thur,</NAME>
          <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24104 Filed 9-15-11; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>76</VOL>
  <NO>182</NO>
  <DATE>Tuesday, September 20, 2011</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="58157"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <CFR>9 CFR Parts 416, 417, and 430</CFR>
        <DEPDOC>[Docket No. FSIS-2010-0023]</DEPDOC>
        <SUBJECT>Shiga Toxin-Producing<E T="0714">Escherichia coli</E>in Certain Raw Beef Products</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final determination and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Food Safety and Inspection Service (FSIS) intends to carry out verification procedures, including sampling and testing manufacturing trim and other raw ground beef product components, to ensure control of both<E T="03">Escherichia coli</E>O157:H7 (<E T="03">E. coli</E>O157:H7) and six other serogroups of Shiga toxin-producing<E T="03">E. coli</E>(STEC) (O26, O45, O103, O111, O121, and O145). The Agency intends to implement sampling and testing for the additional STEC. FSIS has determined that they, as well as O157:H7, are adulterants of non-intact raw beef products and product components within the meaning of the Federal Meat Inspection Act (FMIA). The Agency is publishing guidance for use in validating commercial pathogen detection test kits that may be capable of detecting the STEC of concern. Finally, the Agency is planning a comprehensive survey of its field personnel who are stationed in beef slaughtering and processing establishments, similar to the 2007 “checklist” survey, to determine the processing practices that are employed to reduce the likelihood of contamination of intact and non-intact beef products with these STEC.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>To receive full consideration, comments should be received by November 21, 2011.</P>

          <P>FSIS intends to implement routine testing for the six additional STEC discussed in this document beginning March 5, 2012, following its comment period. To allow industry time to implement possible changes to food safety systems, FSIS will generally not regard raw, non-intact beef products or the components of such products found to have these pathogens as adulterated until it begins this routine testing. FSIS will affirm, in an additional<E T="04">Federal Register</E>notice, the date that it plans to implement sampling and testing.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>FSIS invites interested persons to submit comments on this document. Comments may be submitted by either of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>This Web site provides the ability to type short comments directly into the comment field on this Web page or attach a file for lengthier comments. Go to<E T="03">http://www.regulations.gov.</E>Follow the online instructions at that site for submitting comments.</P>
          <P>•<E T="03">Mail, including floppy disks or CD-ROMs, and hand- or courier-delivered items:</E>Send to Docket Clerk, U.S. Department of Agriculture (USDA), FSIS, Docket Clearance Unit, 8-164, Patriots Plaza III, 355 E Street, SW., Washington, DC 20024-3221.</P>
          <P>
            <E T="03">Instructions:</E>All items submitted by mail or electronic mail must include the Agency name and docket number FSIS-2010-0023. Comments received in response to this docket will be made available for public inspection and posted without change, including any personal information, to<E T="03">http://www.regulations.gov.</E>
          </P>
          <P>
            <E T="03">Docket:</E>For access to background documents or comments received, go to the FSIS Docket Room at the address listed above between 8:30 a.m. and 4:30 p.m., Monday through Friday.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Daniel L. Engeljohn, Ph.D., Assistant Administrator, Office of Policy and Program Development, Food Safety and Inspection Service, U.S. Department of Agriculture, (202) 205-0495.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Table of Contents</HD>
        <EXTRACT>
          <FP>Background</FP>
          <FP SOURCE="FP-2">I. Shiga Toxin-Producing<E T="03">E. coli: E. coli</E>O157:H7FSIS and Industry Actions</FP>
          <FP SOURCE="FP-2">II. Non-O157 STEC</FP>
          <FP SOURCE="FP-2">III. Stakeholder Input</FP>
          <FP SOURCE="FP1-2">Petition to Declare All Enterohemorrhagic STEC to be Adulterants</FP>
          <FP SOURCE="FP1-2">Letter to Secretary of Agriculture from American Meat Institute</FP>
          <FP SOURCE="FP-2">IV. STEC Policy Implementation</FP>
          <FP SOURCE="FP1-2">Implementation, Status of Laboratory Methods</FP>
          <FP SOURCE="FP1-2">On-Going Work</FP>
          <FP SOURCE="FP1-2">Expected Industry Response</FP>
          <FP SOURCE="FP1-2">New Checklist</FP>
          <FP SOURCE="FP1-2">State Programs and Foreign Government Programs</FP>
          <FP SOURCE="FP1-2">Time-frame for Complete Enforcement</FP>
          <FP SOURCE="FP1-2">Validation Guidance for Pathogen Detection Test Kits</FP>
          <FP SOURCE="FP-2">V. Anticipated Costs and Benefits Associated With This Policy</FP>
          <FP SOURCE="FP1-2">Costs to the Agency</FP>
          <FP SOURCE="FP1-2">Costs to the Industry</FP>
          <FP SOURCE="FP1-2">Expected Benefits</FP>
          <FP SOURCE="FP1-2">Avoided Recalls</FP>
          <FP SOURCE="FP1-2">Impact on Small Business</FP>
          <FP SOURCE="FP1-2">Summary of Requests for Comment</FP>
          <FP SOURCE="FP1-2">USDA Nondiscrimination Statement</FP>
          <FP SOURCE="FP1-2">Additional Public Notification</FP>
        </EXTRACT>
        <HD SOURCE="HD1">Background</HD>
        <HD SOURCE="HD1">I. Shiga Toxin-Producing E. coli: E. coli O157:H7</HD>
        <P>While most strains of common intestinal bacteria of the<E T="03">E. coli</E>species are harmless, and are not adulterants of raw meat, some strains are highly pathogenic. The Shiga toxin-producing<E T="03">E. coli</E>(STEC) may cause illnesses of varying severity, from diarrhea (often bloody) and abdominal cramps to, rarely, kidney disorders. Shiga toxin is the same toxin as is produced by<E T="03">Shigella,</E>the bacteria that cause dysentery. In some instances, the toxin will bind to tissues in the kidneys and cause hemolytic uremic syndrome (HUS), leading to kidney failure and death. STEC also may cause asymptomatic infections and extraintestinal infections.<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>1</SU>U.S. Centers for Disease Control and Prevention. 2005. Shiga toxin-producing Escherichia coli (STEC). National Notifiable Diseases Surveillance System (NNDSS), 2005 Case Definition.<E T="03">http://www.cdc.gov/ncphi/disss/nndss/casedef/shiga_current.htm,</E>accessed September 11, 2010.</P>
        </FTNT>

        <P>Since the 1990s, FSIS has considered a particular strain of STEC,<E T="03">E. coli</E>O157:H7, to be an adulterant of raw, non-intact beef products and the raw intact components used to manufacture these products. On September 28, 1994, in a speech to the American Meat Institute, then-FSIS Administrator Michael R. Taylor stated, “To clarify an important legal point, we consider raw ground beef that is contaminated with<E T="03">E. coli</E>O157:H7 to be adulterated within the meaning of the [FMIA]. We are prepared to use the Act's enforcement tools, as necessary, to exclude adulterated product from commerce.<PRTPAGE P="58158"/>* * * We plan to conduct targeted sampling and testing of raw ground beef at plants and in the marketplace for possible contamination.” Mr. Taylor further stated, “We know that the ultimate solution to the (<E T="03">E. coli</E>) O157:H7 problem lies not in comprehensive end-product testing but rather in the development and implementation of science-based preventive controls, with product testing to verify process control.”<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>Michael R. Taylor, FSIS Administrator. September 29, 1994. “Change and Opportunity to Improve the Safety of the Food Supply. Speech to American Meat Institute Annual Convention, San Francisco, CA.</P>
        </FTNT>

        <P>FSIS currently conducts verification procedures, including testing of ground beef products, beef manufacturing trimmings, and other raw ground beef product components for the presence of<E T="03">E. coli</E>O157:H7. This pathogen can cause bloody diarrhea and other serious infections, particularly in vulnerable persons—the very young, the immunocompromised, and the elderly. Very few cells of<E T="03">E. coli</E>O157:H7 are necessary to cause illness. While residing on the exterior surfaces of contaminated carcasses and primal and subprimal cuts of meat, the organisms can also contaminate the interior of ground product or other beef products—such as needle-tenderized or vacuum-tumbled product—when the protective surfaces of these products have been penetrated. If these products do not undergo rigorous heat treatment or other effective processing, the organisms can survive to cause human illness.</P>

        <P>FSIS issued a policy statement (64 FR 2803; Jan. 19, 1999) that stated, “* * * [g]iven the low infectious dose of [<E T="03">E. coli</E>O157:H7] associated with foodborne disease outbreaks and the very severe consequences of an [<E T="03">E. coli</E>O157:H7] infection, the Agency believes that the status under the FMIA of beef products contaminated with [<E T="03">E. coli</E>O157:H7] must depend on whether there is adequate assurance that subsequent handling of the product will result in food that is not contaminated when consumed.” FSIS stated that, with the exception of intact cuts of muscle that are to be distributed for consumption as intact cuts, an<E T="03">E. coli</E>O157:H7-contaminated beef product must not be distributed until it has been processed into a ready-to-eat product,<E T="03">i.e.,</E>a food that can be consumed safely without further cooking or other preparation. FSIS therefore deemed adulterated<E T="03">E. coli</E>O157:H7-contaminated non-intact products and intact cuts that are to be further processed into non-intact products before being distributed for consumption.</P>

        <P>In October 2002, FSIS published a rule (67 FR 62325; Oct. 7, 2002) requiring all manufacturers of beef products to reassess their HACCP plans relating to<E T="03">E. coli</E>O157:H7 because the prevalence of the pathogen on cattle brought to slaughter was higher than expected.<SU>3</SU>

          <FTREF/>FSIS issued compliance guidance for establishments on controlling<E T="03">E. coli</E>O157:H7.</P>
        <FTNT>
          <P>

            <SU>3</SU>U.S. Department of Agriculture. Food Safety and Inspection Service.<E T="03">E. coli</E>0157:H7 Contamination of Beef Products. Oct. 7, 2002. 67 FR 62325.</P>
        </FTNT>

        <P>The beef industry held a summit in January 2003 to develop a unified plan and “best practices” for<E T="03">E. coli</E>O157:H7 reduction. The industry introduced several mitigation techniques to reduce the prevalence of<E T="03">E. coli</E>O157:H7 from the slaughterhouse to the grinding establishment. Recommended preventive measures included testing the hides and pre-eviscerated carcasses of cattle in order to benchmark whether and how the sanitary dressing procedures and antimicrobial interventions are effective in reducing bacterial contamination, targeting research on the development of effective interventions and implementing robust microbiological testing schemes. For the production of ground products, the recommendations included stopping the practice of carrying over product from one production day to the next, a practice that had resulted in a major recall of ground beef. The industry continues to use many of these techniques in controlling<E T="03">E. coli</E>O157:H7 and has been focusing increasingly on risk reduction from the farm to the table.</P>
        <HD SOURCE="HD1">II. Non-O157 STEC</HD>
        <P>As mentioned above,<E T="03">E. coli</E>O157:H7 is not the only STEC that can enter the meat supply and cause illness.<SU>4</SU>
          <FTREF/>FSIS is aware that other STEC serogroups may be present in cattle, and can contaminate beef and other meat products and that consumption of products containing certain pathogenic STEC can produce a range of symptoms from mild, non-bloody diarrhea to HUS and death, primarily in very young, elderly, or immunocompromised individuals.</P>
        <FTNT>
          <P>
            <SU>4</SU>There are approximately 300 to 400 known STEC serotypes that carry various Stx alleles and many of these serotypes and some of the Stx alleles have not been implicated in illness. These various STEC serotypes can be found in soil, water, and other foods and have even been reported to be present in the intestinal tracts of healthy humans. However, very few of the 300-400 non-O157 STEC have been conclusively identified as having caused illness due to being in the U.S. meat supply.</P>
        </FTNT>
        <P>The most prevalent pathogenic non-O157 STEC serogroups in the United States are O26, O45, O103, O111, O121, and O145.<SU>5</SU>
          <FTREF/>While more than 50 STEC serogroups have been associated with human illness, U.S. Centers for Disease Control and Prevention (CDC) data shows that over 70 to 83 percent of confirmed, serogrouped non-O157 STEC illnesses are caused by these six STEC serogroups.<SU>6</SU>
          <FTREF/>All of these non-O157 STEC strains can cause hemorrhagic colitis and all except O45 have been shown to cause hemolytic uremic syndrome.<SU>7</SU>
          <FTREF/>We note that the illnesses associated with these strains have not primarily been due to contamination on beef.</P>
        <FTNT>
          <P>

            <SU>5</SU>Brooks, J.T., and E.G. Sewers, J.G. Wells, K.D. Greene, P.M. Griffin, R. M. Hoekstra, and N.A. Strockbine. 2005. Non-O157 Shiga Toxin-Producing<E T="03">Escherichia coli</E>Infections in the United States, 1983-2002. JID 2005:192 (October 15) 1422-1429.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>6</SU>Centers for Disease Control and Prevention. Bacterial Foodborne and Diarrheal Disease National Case Surveillance Annual Reports, 2003-2006. Available at<E T="03">http://www.cdc.gov/nationalsurveillance/case_surveillance.html.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>7</SU>See Table 2 of the DRAFT Risk Profile for Pathogenic Non-O157 Shiga Toxin-Producing<E T="03">Escherichia coli</E>later in this document.</P>
        </FTNT>
        <P>Though limited data are available on dose response, there is evidence that the infectious doses of these non-O157 STEC are relatively low. For example, an investigation of an outbreak of STEC O26 from fermented beef sausage in Denmark yielded an infectious dose of 100 cells.<SU>8</SU>
          <FTREF/>From an outbreak of O111 STEC in beef sausage in Australia, investigators extrapolated a dose range of 1 to 10 organisms, given as few as 1 cell per 10 g of sausage.<SU>9</SU>
          <FTREF/>Using the concentrations of STEC O145 in contaminated ice cream in an outbreak in Belgium, the estimated infective dose was 400 CFU.<SU>10</SU>
          <FTREF/>This is comparable to illness from<E T="03">E. coli</E>O157:H7, which can result from infection with as few as 10 cells.<SU>11</SU>
          <FTREF/>Although some of these outbreaks were attributable to contamination of products other than those the Agency regulates, the information from them shows how virulent these pathogenic STEC can be.</P>
        <FTNT>
          <P>
            <SU>8</SU>Boel, J.,<E T="03">et al.</E>2009.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>Paton AW, Ratcliff RM, Doyle RM, Seymour-Murray J, Davos D, Lanser JA, and Paton JC. 1996. Molecular microbiological investigation of an outbreak of hemolytic-uremic syndrome caused by dry fermented sausage contaminated with Shiga-like toxin-producing Escherichia coli. J Clin Microbiol. 34(7):1622-7.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>Buvens G, Possé B, De Schrijver K, De Zutter L, Piérard D, Lauwers S, and Pierard D. 2011. Virulence Profiling and Quantification of Verocytotoxin-Producing Escherichia coli O145:H28 and O26:H11 Isolated During an Ice Cream-Related Hemolytic Uremic Syndrome Outbreak. Foodborne Pathog Dis. 8(3):1-6.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>11</SU>Tilden J. Jr, Young W., McNamara A.M., Custer, C., Boesel, B., Lambert-Fair, M.A., Majkowski, J., Vugia, D., Werner, S.B., Hollingsworth, J., and Morris, J.G. Jr. 1996. A new route of transmission for<E T="03">Escherichia coli:</E>infection from dry fermented salami. Am J Public Health. 86(8):1142-5.</P>
        </FTNT>
        <PRTPAGE P="58159"/>

        <P>There is also evidence that the thermal resistance of these strains is high enough that they can survive ordinary cooking of ground beef products. A recent study examining thermal resistance of STEC-inoculated non-intact beef revealed that<E T="03">E. coli</E>O157:H7 and non-O157 STEC (a pooled composite of STEC serogroups O45, O103, O111, O121, and O145) had similar thermal inactivation profiles (Luchansky, unpublished data).<SU>12</SU>
          <FTREF/>The recent outbreak in which ground beef was implicated as the vehicle of infection and other evidence shows that STEC O26 survives typical cooking.<SU>13</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>12</SU>Luchansky, J.B. 2010. Unpublished data. Portions of this research were presented at the Annual Meeting of the International Association for Food Protection, August 1-4, 2010, Anaheim, CA.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>13</SU>Duffy G, Walsh C, Blair IS, and McDowell DA. 2006. Survival of antibiotic resistant and antibiotic sensitive strains of<E T="03">E. coli</E>O157 and<E T="03">E. coli</E>O26 in food matrices. Int J Food Microbiol. 109(3):179-86.</P>
        </FTNT>

        <P>Illnesses from person-to-person transmission of STEC serogroups O26, O45, O103, O111, O121, and O145 have been documented, particularly in daycare settings and nursing homes, where there is close contact between persons with immature or compromised immune systems and/or underdeveloped personal hygiene skills. This occurs when an infected, sometimes asymptomatic, person sheds bacteria in feces and subsequent contamination of food or fomites occurs. STEC serogroups O26, O45, O103, O111, O121, and O145 have been isolated from beef carcasses or retail beef in the U.S.<E T="51">14 15 16</E>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>14</SU>Bosilevac JM and M Koohmaraie. 2011. Prevalence nd Characterization of Non-0157 Shiga toxin Producing Escherichia coli Isolated from Commercial Ground Beef in the United States. Appl Environ Microbiol. Published ahead of print on 21 January 2011, doi:10.1128/AEM.02833-10.</P>
          <P>
            <SU>15</SU>Samadpour M. 2011. Prevalence of Toxin containing non-O157 Escherichia coli found in Commercial Ground Beef. In preparation.</P>
          <P>
            <SU>16</SU>Arthur TM, Barkocy-Gallagher GA, Rivera-Betancourt M, and Koohmaraie M. 2002. Prevalence and characterization of non-O157 Shiga toxin-producing Escherichia coli on carcasses in commercial beef cattle processing plants. Appl Environ Microbiol. 68(10):4847-52.</P>
        </FTNT>
        <P>With full consideration of the information described above, FSIS has determined that raw, non-intact beef products that are contaminated with these STEC O26, O45, O103, O111, O121, and O145, are adulterated within the meaning of 21 U.S.C. 601(m)(1). Raw, non-intact beef products that are contaminated with these pathogens are also unhealthful and unwholesome (under 21 U.S.C. 601(m)(3)). FSIS also considers adulterated intact cuts that are contaminated with these serogroups if they are to be further processed into raw, non-intact products before being distributed for consumption.</P>

        <P>FSIS has developed a laboratory methodology for detection and isolation of these serogroups from beef, thereby allowing development of an enforceable policy program targeted to control STECs O26, O45, O103, O111, O121, and O145. FSIS will verify establishment controls for these pathogens and will collect product samples in support of its verification efforts as well as to inform the Agency's regulatory program with regard to the pathogens. Establishments that manufacture raw, non-intact beef products or intact raw beef components of those products will be expected to evaluate whether these non-O157 STEC are hazards reasonably likely to occur in their products. FSIS will generally not regard raw, non-intact beef products or the components of such products found to have these pathogens as adulterated until FSIS implements a routine sampling program that will include, besides<E T="03">E. coli</E>O157:H7, six additional STEC serogroups (O26, O45, O103, O111, O121, and O145). However, if product is associated with an STEC outbreak before that time, such product will be subject to recall, consistent with current FSIS practice.</P>
        <HD SOURCE="HD1">III. Stakeholder Input</HD>
        <P>On October 17, 2007, FSIS, the Food and Drug Administration's Center for Food Safety and Applied Nutrition (FDA, CFSAN), and the CDC held a public meeting to solicit input from industry, consumers, academia, and other public health and regulatory agencies on the issue of whether some non-O157 STEC should be considered adulterants (72 FR 57285).<SU>17</SU>
          <FTREF/>At the public meeting, FSIS indicated that the Agency was considering non-O157 STEC to be adulterants but also discussed the need to conduct further research to address the issues associated with these microorganisms. At the meeting, FSIS also acknowledged the need to develop the laboratory capacity to support policy decisions with respect to non-O157 STEC. The Agency requested public input on these issues.</P>
        <FTNT>
          <P>
            <SU>17</SU>For the transcript and presentations, go to<E T="03">http://www.fsis.usda.gov/News_&amp;_Events/2007_Events/index.asp</E>(accessed Jul. 20, 2010).</P>
        </FTNT>
        <HD SOURCE="HD2">Petition To Declare All Enterohemorrhagic STEC To Be Adulterants</HD>

        <P>On October 5, 2009, Marler Clark, LLP, PS, and other parties petitioned FSIS to issue an interpretive rule declaring all enterohemorrhagic STEC to be adulterants within the meaning of the FMIA. They specifically cited 21 U.S.C. 601(m)(1), under which a meat or meat food product is adulterated if it bears or contains any poisonous or deleterious substance that may render it injurious to health. The petitioners argued that applying the provision to STEC in addition to serogroup O157 is justified because current scientific and medical research demonstrates that the dangers associated with<E T="03">E. coli</E>O157:H7 extend to all pathogenic STEC. They referred to the potential for non-O157 STEC to cause HUS, the prevalence of the non-O157 STEC among foodborne pathogens, cattle as reservoirs of the pathogen, the presence of non-O157 STEC in beef products, and the implication of non-O157 STEC in outbreaks of foodborne illness. Because these non-O157 STEC have the same characteristics as O157 STEC, they argued, these pathogens ought to have the same legal status as O157 STEC.<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">http://www.fsis.usda.gov/PDF/Petition_Marler_100509.pdf</E>(Accessed Nov. 30, 2010).</P>
        </FTNT>
        <P>In an addendum to the petition, filed February 22, 2010, petitioners submitted a copy of a 2007 journal article by FDA scientists detailing a PCR method for identifying isolates that include the six most prevalent non-O157 STEC. The petitioners also provided a study that they commissioned to analyze retail ground beef samples.<SU>19</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">http://www.fsis.usda.gov/PDF/Petition_Marler_Clark_022210.pdf</E>and<E T="03">http://www.fsis.usda.gov/PDF/Petition_Marler_Cover%20Letter.pdf</E>(Accessed Nov. 30, 2010.)</P>
        </FTNT>
        <P>In correspondence with the petitioners, FSIS stated that when the Agency had an appropriate laboratory method for conducting regulatory sampling for some non-O157 STEC and had developed a plan for how it intends to address the issue, it would make the plan available to the public for comment. The Agency would then provide a final response to the petition.<SU>20</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>20</SU>Philip S. Derfler, Assistant Administrator, Office of Policy and Program Development, FSIS/USDA. April 8, 2010. Letter to William Marler, Esq., Marler-Clark, LLP, PS. At:<E T="03">http://www.fsis.usda.gov/PDF/Petition_Marler_Clark_Progress_Response.pdf</E>(Accessed Nov. 30, 2010.)</P>
        </FTNT>

        <P>The petitioners filed a Supplemental Statement of Additional Grounds on May 7, 2010. In their Supplemental Statement, they cited studies of illness outbreaks linked to non-O157 STEC and a paper on the feasibility of testing ground beef and milk for Shiga-like toxin-producing<E T="03">E. coli.</E>
          <SU>21</SU>

          <FTREF/>The petitioners filed a Second Supplemental Statement of Additional Grounds on September 2, 2010, in light of the STEC<PRTPAGE P="58160"/>O26 outbreak, discussed below, that was linked to ground beef. They attached a May 21, 2010, CDC memorandum on Non-O157 STEC outbreaks in the United States. The memorandum, referring to a recent STEC O145 outbreak in romaine lettuce, expressed the opinion that as the ability of clinical laboratories to detect non-O157 STEC has improved, more of the organisms were being detected.</P>
        <FTNT>
          <P>
            <SU>21</SU>Acheson, D.W.K.,<E T="03">et al.</E>1996. Detection of Shiga-like Toxin-Producing Escherichia coli in Ground Beef and Milk by Commercial Enzyme Immunoassay. J. Food Prot. 59:4:344-349.</P>
        </FTNT>
        <HD SOURCE="HD2">Letter to Secretary of Agriculture From American Meat Institute</HD>
        <P>In an August 18, 2010, letter from American Meat Institute (AMI) President and CEO J. Patrick Boyle to Secretary of Agriculture Tom Vilsack, AMI offered to work with the Department on the control of STEC. AMI expressed concern that the designation of non-O157 STEC as adulterants might “result in a misdirected regulatory program that would do more harm than good.” AMI addressed several matters relating to FSIS policy on non-O157 STEC and the extent to which the non-O157 STEC are a health risk. We have considered these concerns and recommendations as we have developed this policy.</P>
        <P>FSIS regards testing of non-intact raw beef products and components of products as just one of several verification methods the Agency uses. These include verification of establishment HACCP systems, Sanitation Standard Operating Procedures (Sanitation SOPs) and other prerequisite programs, comprehensive food safety assessments, and checks on records of purchases from suppliers.</P>
        <P>FSIS actively engages experts and the public in ongoing discussions of public health issues and the science associated with our actions. For example, FSIS held public meetings on non-O157 STEC policy in 2007 and 2008 that involved presentations by domestic and international experts from Government, industry, and academia. Participants discussed the bases for determining non-O157 STEC to be adulterants, epidemiological evidence of increasing incidence of non-O157 STEC, and the importance of barriers and interventions in food production and processing to prevent contamination with STEC. The Agency is planning further evaluations and will use the findings to assess industry compliance and controls for pathogens in raw beef products. FSIS requests comments on whether to hold a technical meeting during the comment period for this document or later.</P>

        <P>FSIS has prepared guidance for the validation of test kits for the detection of pathogens, including both<E T="03">E. coli</E>O157:H7 and non-O157 STEC (see below). This guidance should enable test kit developers to determine the effectiveness of their products. Also, as discussed elsewhere in this document, FSIS is making available its screening and isolation methods for non-O157 STEC. These methods were included in the Agency's Microbiology Laboratory Guidebook.</P>

        <P>FSIS intends to perform a nationwide microbiological baseline survey on beef carcasses in late 2011. This microbiological survey will analyze samples from carcasses for the presence of the pathogens<E T="03">E. coli</E>O157:H7 and the STEC identified in this rule,<E T="03">Salmonella,</E>and indicator bacteria (generic<E T="03">E. coli,</E>coliforms, and Enterobacteriaceae). Regarding the analytical method to be used, FSIS is making its method publicly available and will include it in the Agency's Microbiological Laboratory Guidebook.</P>
        <HD SOURCE="HD1">IV. STEC Policy Implementation</HD>
        <HD SOURCE="HD2">Implementation, Status of Laboratory Methods</HD>

        <P>As noted above, FSIS intends by March 5, 2012, to begin implementing a routine sampling program that will include, besides<E T="03">E. coli</E>O157:H7, six additional STEC serogroups (O26, O45, O103, O111, O121, and O145). FSIS will initially sample raw beef manufacturing trimmings and other ground beef product components produced domestically and imported, and test the samples for these serogroups. When FSIS implements its testing program, the Agency will consider other products, including raw ground beef contaminated with any of the six additional STEC serogroups to be adulterated. The Agency is planning later—as soon as laboratory capacity is available—to expand this program to conduct verification testing of ground beef products for these serogroups. Data gathered from the sampling will enable the Agency to gauge more precisely the level of hazard posed by these STEC. In general, FSIS will review the information and adjust its policies and implementation strategies consistent with direction in Executive Order 13563 to retrospectively analyze rules “that may be outmoded, ineffective, insufficient, or excessively burdensome, and to modify, streamline, expand, or repeal them in accordance with what has been learned.” FSIS will issue a<E T="04">Federal Register</E>document informing stakeholders before expanding its verification testing to include raw beef products other than beef manufacturing trimmings and other ground beef components.</P>

        <P>When FSIS samples trim or other ground beef components, FSIS will now test up to two portions of product (up to 325 g per portion) collected at an establishment to test for<E T="03">E. coli</E>O157:H7 and, upon initiation of the actions outlined in this document, for the additional six non-O157 STEC (serogroups O26, O45, O103, O111, O121, and O145). Also, a single 325-g ground beef sample will now be tested for<E T="03">E. coli</E>O157:H7 upon initiation of the actions outlined in this document.</P>

        <P>FSIS has previously tested five separate 65-g sub-samples of the sample collected at an establishment for<E T="03">E. coli</E>O157:H7. An Agency study showed the new method to be not as sensitive as the old method in detecting the lowest levels (1-4 CFR/325g) of<E T="03">E. coli</E>O157:H7 cells. However, the difference in sensitivity was not statistically significant. Using the new method would permit FSIS to analyze more samples at the same or less laboratory costs than the present method. Because the sensitivity of the new method is comparable, if not actually equal, to that of the present method, FSIS expects the new approach to yield laboratory cost efficiencies with no significant statistical difference in the analytical results.</P>

        <P>The Agency will use the new modified trypticase soy broth with novobiocin plus casaminoacids (mTSB+n) enrichment medium described in the FSIS Microbiology Laboratory Guidebook MLG chapters 5.06 and 5B.01 the preparation step of its procedure for identifying the six non-O157 STEC. Testing for non-O157 STEC with a polymerase-chain-reaction (PCR) test involves a two-stage PCR screening test: the first stage will detect samples positive for<E T="03">stx</E>and<E T="03">eae</E>(intimin). In the second stage, samples will be screened for the presence of one of the six public health-relevant serogroups (O26, O45, O103, O111, O121, and O145). A sample will be identified as “potential positive” when it tests positive for the<E T="03">stx</E>gene and the<E T="03">eae</E>gene and is also positive for one or more of the target O-group genes (on day three of the analysis).</P>

        <P>Samples that are “potential positive” are further analyzed by using immunomagnetic beads to capture the target analyte. The immunomagnetic beads are used to inoculate Rainbow Agar plates. After incubation (day 4 of the analysis), the plates are observed for colonies that have an appearance typical of the target analyte. Typical colonies are tested with latex agglutination reagents specific for the target serogroup, if at least one colony tests positive by latex agglutination, the sample is called “presumptive<PRTPAGE P="58161"/>positive.” This is similar to<E T="03">E. coli</E>O157:H7 analysis; typical colonies are tested using latex agglutination reagents on analytical day 4.</P>

        <P>Samples that screen positive at the first stage of testing (stx+, eae+) for non-O157 STEC but screen negative at the second stage (O-group negative) will<E T="03">not</E>be regarded as potential positive results. FSIS would not consider the results to be evidence of adulteration. However, such screen-positives do indicate the potential presence of an organism capable of producing Shiga toxin (<E T="03">stx</E>) and intimin (<E T="03">eae</E>) and may indicate conditions that allow pathogenic STEC through the system. Therefore, FSIS will use these results to inform its verifications of HACCP system adequacy, in accordance with 9 CFR 417.8.</P>

        <P>In order for a sample to be “confirmed positive,” FSIS will further characterize the isolates by biochemical tests. A confirmed positive sample will be one where an isolate has<E T="03">stx, eae,</E>and one or more of the target O-group genes and has been biochemically confirmed to be<E T="03">E. coli.</E>(By comparison, a sample is confirmed positive for<E T="03">E. coli</E>O157:H7 if biochemical tests identify the isolate as an<E T="03">E. coli,</E>serological or PCR tests identify it as an O157, and serological or PCR tests detect Shiga toxin production, or are positive for the<E T="03">stx</E>gene, or determine the isolate to be “H7.”)</P>

        <P>The detection and isolation methodology for non-O157 STEC is described in chapter MLG 5B.00, or current revision, of the FSIS Microbiology Laboratory Guidebook, available at:<E T="03">http://www.fsis.usda.gov/PDF/Mlg_5B_00.pdf.</E>FSIS will advise the establishment to hold the sampled product and not release it pending negative test results. If test results are positive and product has been released into commerce, FSIS will request that the producing establishment recall that product.</P>
        <P>FSIS estimates that most sampled product will screen negative for non-O157 STEC at the first stage of testing and that the negative results will be available within 48 hours of shipment of the samples to the laboratory. For samples that screen positive, an additional three to five days may be necessary for a confirmed positive or negative result. However, as the Agency gains experience and data, and as the performance of test methods improves, the Agency hopes to reduce the time needed to obtain definitive results.</P>

        <P>For imported products tested at port of entry, if the product tests positive at the second stage and has been not been held at the import establishment, it will be subject to recall. If the product has been held, the product will be refused entry. As always, product subsequently presented for import inspection from the same foreign country and establishment will be held at the official import establishment pending results. The FSIS Office of International Affairs will notify the program officials of the affected exporting country as soon as a positive result is reported, so that they can determine whether the producing establishment has exported any other product from the same production lot to the United States. As in the control of<E T="03">E. coli</E>O157:H7, if the foreign establishment has properly defined the product lot on the basis of specific control factors, and accurately tracked the containerization of product produced under those controls, the establishment can reduce the likelihood that adulterated product will enter commerce, and can more easily recover product if a sample is positive.</P>

        <P>Control factors recommended by FSIS for use in defining the product and container destined for the United States include<E T="03">E. coli</E>sampling programs for distinguishing production subsets; cross-contamination preventions incorporated in Sanitation SOPs; re-work controls; and other prerequisite programs. Other control factors may include sanitary dressing procedures; employee hygiene, processing interventions that limit or reduce<E T="03">E. coli</E>contamination; elimination of “carry over” of manufacturing trimmings, raw beef components, or re-work from one production period to the next; and sanitation of product contact surfaces, including machinery and employee hand tools.</P>
        <P>Generally, FSIS recommends that establishments develop and implement in-plant sampling plans that define production lots or sub-lots that are microbiologically independent of other production lots or sub-lots. Production lots that are so identified may bear distinctive markings on the shipping cartons and—on exported product—foreign health certificates. If a foreign government or establishment does not apply control factors, FSIS may default to defining the product represented by a microbiological sample as all product produced on a particular production day.</P>
        <P>FSIS expects to begin the non-O157 STEC program by analyzing raw beef manufacturing trimmings and other ground beef product components. For imported product, FSIS intends to conduct sampling of imported beef manufacturing trim and ground beef components at official import inspection establishments.</P>
        <P>FSIS believes that, by testing trim samples and other components for the non-O157 STEC, the Agency can offer an immediate measure of public health protection commensurate with the Agency's regulatory requirements. The Agency expects eventually to test ground beef, hamburger, and beef patty products for STEC. In taking a staged approach to the implementation of this new testing program, the Agency should be able to use its resources most effectively.</P>
        <HD SOURCE="HD2">Expected Industry Response</HD>

        <P>The beef industry currently applies a range of sanitary slaughter methods to control<E T="03">E. coli</E>O157:H7 in raw non-intact beef products. These include hide washing, sanitary hide removal, pre-evisceration organic acid rinses, spot cleaning of carcasses with viscera contamination, thermal pasteurization of dressed carcasses to reduce microbial loads, and chilled carcass treatments. These methods are typically applied in a slaughter plant sanitation program to prevent the carry-over of bacterial contamination from the farm or feedlot to the slaughter floor and meat processing areas.</P>

        <P>Many establishments that produce raw non-intact beef products, such as ground beef, incorporate such antimicrobial interventions as organic acid sprays in their processing. These methods should be as effective in controlling non-O157 STEC as they are in controlling<E T="03">E. coli</E>O157:H7. In this respect, the industry would incur no additional processing costs in controlling non-O157 STEC as a result of the policy the Agency is adopting. However, from the experience in controlling<E T="03">E. coli</E>O157:H7, FSIS anticipates that many firms will want to implement their own testing programs and even to conduct the same kind of testing that FSIS plans to carry out. Some firms already test their products for<E T="03">E. coli</E>O157:H7 and provide the further processing, wholesale, or retail businesses they supply with certificates of analysis on the product testing they have conducted. They may want to test for non-O157 STEC and certify to their customers that they have done so.</P>

        <P>FSIS will follow the same procedures with respect to non-O157 STEC as it follows for<E T="03">E. coli</E>O157:H7. A first-stage screen positive (<E T="03">stx</E>and<E T="03">eae</E>) is evidence of the presence of Shiga toxin and intimin and may indicate that an establishment is not adequately addressing hazards reasonably likely to occur. Establishments should reassess their HACCP plans, Sanitation Standard Operating Procedures, or other prerequisite programs on the basis of<PRTPAGE P="58162"/>this evidence. If the reassessment results indicate that pathogenic STEC are reasonably likely to occur in the production process, the establishment's HACCP plan must address them.</P>
        <HD SOURCE="HD2">New Checklist</HD>

        <P>In addition, in the coming months, FSIS plans to conduct a new “checklist” survey of its field inspection personnel who are stationed in beef slaughtering and processing establishments. As they did in 2007 with respect to<E T="03">E. coli</E>O157:H7, inspection personnel at official establishments that slaughter, fabricate, grind, mechanically tenderize, or enhance by tumbling, massaging, or injecting beef products with substances such as marinades will complete an on-line checklist on how the establishments address STEC. This checklist will provide information on this class of establishments regarding the methods they use to prevent product contamination.</P>
        <HD SOURCE="HD2">State Programs and Foreign Government Programs</HD>
        <P>States that have their own meat inspection programs for meat products produced and transported solely within the State are required to have mandatory ante-mortem and post-mortem inspection, reinspection, and sanitation requirements that are at least equal to those in the Federal Meat Inspection Act (21 U.S.C. 661(a)(1)). Therefore, these States' sampling procedures and testing methods for non-O157 STEC in raw beef products must be at least as sensitive as FSIS's procedures and testing methods for non-O157 STEC.</P>
        <P>Foreign countries that are eligible to export meat products to the United States must apply inspection, sanitary, and other standards that are equivalent to those that FSIS applies to those products (21 U.S.C. 620). Thus, in evaluating a foreign country's meat inspection system to determine the country's eligibility to export products to the United States, FSIS will consider whether the testing methods and procedures for non-O157 STEC that the country applies are equivalent to those that FSIS uses.</P>
        <HD SOURCE="HD2">Time-Frame for Complete Enforcement</HD>

        <P>FSIS intends to be able to begin implementing regulatory sampling for the six non-O157 STEC in March 2012. FSIS would take action on positive samples following the same procedures as those currently followed with respect to samples that test positive for<E T="03">E. coli</E>O157:H7.</P>
        <P>In an effort to increase awareness of this policy, FSIS will conduct extensive outreach to FSIS- and State-regulated small and very small meat establishments throughout the U.S. and its territories in 2011 and early 2012 as well as to foreign countries. The Agency plans to hold workshops and webinars throughout the United States. FSIS will announce exact locations and dates of these events once they are determined. In addition, FSIS will extend its outreach to these establishments by participating at conferences, trade shows, and meetings that cater to meat producers, and developing and disseminating written articles, and audio podcasts on the changes. FSIS welcomes comments on this implementation plan and on whether the Agency should hold a public meeting on the issues addressed in this document during the public comment period.</P>
        <HD SOURCE="HD2">Validation Guidance for Pathogen Detection Test Kits</HD>

        <P>FSIS is announcing the availability of a compliance guide on validating performance of pathogen test kit methods. FSIS will post this compliance guide on its Significant Guidance Documents Web page (<E T="03">http://www.fsis.usda.gov/Significant_Guidance/index.asp</E>). FSIS encourages those organizations that design or conduct validation studies for foodborne pathogen testing methods to avail themselves of this guidance document in meeting the pertinent regulatory requirements. FSIS is also soliciting comments on this compliance guide. The Agency will consider carefully all comments submitted and will revise the guide as warranted.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>The use of “validation” in the guidance document is not intended to have any application to the implementation of 9 CFR 417.4(a)(1) (Validation, Verification, Reassessment) on initial validation of HACCP plans.</P>
        </NOTE>
        <HD SOURCE="HD1">V. Anticipated Costs and Benefits Associated With This Policy</HD>
        <P>FSIS has estimated that implementation of its non-O157 STEC testing policy will result in costs to FSIS laboratories and to the regulated industry. However, the costs are low for a policy that we believe is warranted, given the information presented above, and we believe that the benefits justify the costs.</P>
        <HD SOURCE="HD2">Budgetary Costs to the Agency</HD>
        <P>There will be direct, immediate costs to FSIS laboratories for analyzing trim samples for non-O157 STEC. The Agency has estimated these costs to be approximately $204,050 to $338,270 per year in 2010 dollars, depending on the number of samples analyzed.<SU>22</SU>
          <FTREF/>The costs include equipment, supplies and labor for screening, screen-positive isolations, most-probable-number (MPN) procedures, MPN-positive isolation, pulsed-field gel electrophoresis (PFGE), and PFGE-positive isolation.<SU>23</SU>
          <FTREF/>Some key assumptions behind these cost estimates are as follows:</P>
        <FTNT>
          <P>
            <SU>22</SU>The costs are about $204,100 if 2,578 samples are collected and analyzed, or $338,300 if 4,600 samples are collected and analyzed. Please see assumption in the text.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>Data are from the Laboratory Director, Office of the Assistant Administrator, Office of Public Health Science, FSIS.</P>
        </FTNT>

        <P>• Because the laboratory analysis of samples of beef trim and other components for non-O157 STEC is an extension of the program for<E T="03">E. coli</E>O157:H7, we only have to estimate the marginal or additional cost. There is no additional cost for shipping or sample-collection time.</P>
        <P>• The annual number of samples is the same as the number of<E T="03">E. coli</E>O157:H7 beef trim samples—currently an average of 2,578 samples for beef trim and other components are analyzed per year (2008-2010, sample collection rate about 45 percent).<SU>24</SU>
          <FTREF/>However, the Agency is aiming to increase the sample collection rate to 80 percent. In that case, the annual number of samples to be analyzed will be about 4,600.</P>
        <FTNT>
          <P>
            <SU>24</SU>Data are from the Data Analysis and Integration Group, the Office of Data Integration and Food Protection, FSIS. The numbers of samples include both domestic and imported product samples.</P>
        </FTNT>

        <P>• Screen-positive sample rate is 2 percent, the same as with<E T="03">E. coli</E>O157:H7.</P>
        <P>• Confirmed positive sample rate is 0.5 percent, again the same as with O157:H7.<SU>25</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>25</SU>Data are from the Laboratory Director, Office of the Assistant Administrator, OPHS, FSIS.</P>
        </FTNT>
        <P>FSIS will conduct follow-up testing as it does for<E T="03">E. coli</E>O157:H7. The Agency data show that the average number of domestic follow-up testing in 2008-2010 is about 880.<SU>26</SU>
          <FTREF/>The Agency also estimates that the cost per follow-up testing is about $80. Therefore, the cost for follow-up testing will be about $70,400.</P>
        <FTNT>
          <P>
            <SU>26</SU>Data is from Data Analysis and Integration Group, the Office of Data Integration and Food Protection. The numbers of samples include both domestic and imported product.</P>
        </FTNT>

        <P>In addition, FSIS will conduct a for-cause food safety assessment (FSA) for every positive sample, as it does currently for<E T="03">E. coli</E>O157:H7-positive samples. The Agency estimates the average cost to conduct an FSA (including laboratory work) to be about $14,000. Assuming the foregoing, the cost to FSIS to conduct the for-cause FSA related to non-O157 STECs will be<PRTPAGE P="58163"/>about $180,460 to $322,140 per year (<E T="03">i.e.</E>cost per FSA × annual number of samples × confirmed positive sample rate).<SU>27</SU>
          <FTREF/>Adding the cost to conduct sample testing, follow-up testing and for-cause FSAs, the total cost to the Agency is about $454,910 to $730,810. Note that these cost estimates do not include the costs of expanding testing to raw ground beef products. FSIS intends to provide a full analysis of costs before expanding the testing policy.</P>
        <FTNT>
          <P>
            <SU>27</SU>Data are from the Laboratory Director of Office of the Assistant Administrator, OPHS, FSIS and from the Budget Division, Office of Management, FSIS.</P>
        </FTNT>
        <HD SOURCE="HD2">Costs to the Industry</HD>
        <P>The major costs to the industry will be two-fold: (1) Costs to establishments of starting their own screening for non-O157 STEC and (2) costs of diverting the positive product to cooking or other treatment that would render the product suitable for human food. (Positive-testing product also can be destroyed—sent to a landfill, incinerated, etc.—or rendered into pet food and other products not for human food.) To estimate these costs with precision, we need to know how many establishments will be testing for non-O157 STEC under this document and their HACCP sizes (large, small, or very small). Because the Agency cannot predict with certainty either the number of establishments or the size distribution, our estimate is preliminary.</P>
        <P>FSIS is not aware of data on how many establishments are currently testing for non-O157 STEC, or the size distribution of these establishments. The Agency's best estimate is that about 20 percent of the establishments are testing.<SU>28</SU>

          <FTREF/>According to information collected under FSIS Notice 65-07, 33 percent of the beef slaughter establishments test for<E T="03">E. coli</E>O157:H7.<SU>29</SU>

          <FTREF/>Assuming that the percentage of establishments testing for non-O157 would increase to the same level (<E T="03">i.e.</E>33 percent), we would see 13 percent more establishments starting to test for non-O157 because of this document. The most current Agency beef trim volume survey data, computed from the number of bins of trim produced, show that the total beef trim production is about 2.05 billion pounds per year.<SU>30</SU>
          <FTREF/>Given that in commercial testing a combo bin is 2,000 pounds, an additional 133,000 combo bins will be tested (total beef trim production/weight per combo bin × additional percentage that will test). Further assuming the cost per test is $30 to $40, the preliminary estimate for the cost of the additional 13 percent of establishments testing for non-O157 is about $4.0 million (if $30 per test) to $5.3 million (if $40 per test.)<SU>31</SU>
          <FTREF/>This is a preliminary estimate and we invite the regulated industry and the public to comment.</P>
        <FTNT>
          <P>
            <SU>28</SU>This is based on internal experts' opinion.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>29</SU>U.S. Department of Agriculture. Food Safety and Inspection Service. August, 2008. Results of Checklist and Reassessment of Control for<E T="03">Escherichia coli</E>O157:H7 in Beef Operations. Table 5.4.31, p. 57.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>30</SU>Data are from Applied Analysis Branch, Data Analysis and Integration Group, Office of Data Integration and Food Protection/FSIS/USDA as of October 12, 2010.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>31</SU>Other assumptions behind this estimate include: (1) Positive sample rate being 2 percent—the same with the positive sample rate in FSIS sampling, (2) one test per sample, and (3) using IEH methodology.</P>
        </FTNT>
        <P>To estimate the loss of value from diverting the products to cooking once they test positive, we rely on market data on the wholesale price for beef trim and on internal experts' opinion on the price differential between beef trim and cooked beef products. Market data show that the 3-year average wholesale price for beef trim is about $1.47 per pound.<SU>32</SU>
          <FTREF/>Agency experts estimate that the value for cooked beef products is significantly lower—only about one-half to one-third of the value of beef trim, because the quality of product directed to cooking is generally inferior. On the basis of this assumption, we calculate the loss to the industry from diverting the products to cooking to be about $3.9 to $5.2 million.<SU>33</SU>
          <FTREF/>Again, this is a very preliminary estimate, and we invite comment.</P>
        <FTNT>
          <P>

            <SU>32</SU>Economic Research Service (ERS), USDA, Market and Trade Economics Division provided the data; which are originally from Red Meats Yearbook (<E T="03">http://usda.mannlib.cornell.edu/MannUsda/viewDocumentInfo.do?documentID=1354</E>) and Livestock, Dairy, and Poultry Newsletter tables (<E T="03">http://www.ers.usda.gov/publications/ldp/LDPTables.htm</E>) [both accessed Jan. 20, 2011]. The 3-year range is September 2007 to August 2010.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>33</SU>The equation for calculating the cost for diverting product to cooking is: annual beef trim produced (in pound) × screening positive sample rate × percentage of the value lost × dollar value per pound × percentage of additional establishments testing for STEC.</P>
        </FTNT>
        <P>As for the cost of holding the products while awaiting test results, Agency data show that the great majority of the establishments are already holding their products while awaiting the results of other pathogen testing.<SU>34</SU>
          <FTREF/>The Agency cannot estimate with precision how many more products will be held as a result of FSIS testing for one more pathogen group, but given that the great majority of the products are already being held, the addition is not likely to be significant. Because non-O157 STEC tests will use the samples collected for existing sampling programs, there will be no additional collection of samples. For the establishments that are already holding products for O157 and other pathogen test results, the additional cost will only be holding for one extra day waiting for the confirming non-O157 STEC results, which is minimal. For the few establishments that are not holding products, they would have to do so under the proposed “Test and Hold” Notice, and the additional cost would also only be holding for one more day waiting for the non-O157 STEC results.</P>
        <FTNT>
          <P>

            <SU>34</SU>According to the most recent full-year data (2009) from Data Analysis and Integration Group/Office of Data Integration and Food Protection, the percentages of beef trim and components held by establishments pending FSIS<E T="03">E. coli</E>O157:H7 test results are: 99 percent by large, 97 percent by small and 88 percent by very small establishments. Data are as of December 23, 2010.</P>
        </FTNT>

        <P>As we have stated in this document, many establishments that produce raw non-intact beef products implement controls for<E T="03">E. coli</E>O157:H7. These methods should be as effective in controlling non-O157 STEC as in controlling<E T="03">E. coli</E>O157:H7. In this respect, the industry would incur no additional processing costs in controlling non-O157 STEC as a result of this document.</P>
        <P>Note that these cost estimates do not include the costs associated with expanding FSIS testing to raw ground beef products. FSIS intends to provide a full analysis of costs before expanding the testing policy.</P>
        <HD SOURCE="HD2">Expected Benefits</HD>
        <HD SOURCE="HD3">Reduced Illnesses and Deaths</HD>

        <P>One benefit from sampling and testing for non-O157 STEC is the reduction of illnesses and deaths caused by non-O157 STEC, if testing leads to preventative controls that reduce the risk of illness. As we have stated, controls for<E T="03">E. coli</E>O157:H7 already in place should be as effective in controlling non-O157 STEC as in controlling<E T="03">E. coli</E>O157:H7, and the industry would not need to take additional measures to control non-O157 STEC as a result of the document. However, to the extent that establishments reassess their HACCP plans after receiving positive test results and make appropriate additional changes, overall control of pathogens may improve and illness reductions may result.</P>
        <HD SOURCE="HD3">Avoided Recalls</HD>

        <P>Through early detection of products contaminated with non-O157 STEC, this new program may prevent some food recalls. However, on net, the additional testing may increase the total number of recalls as the new policy would require the recall of all products that test positive and have entered commerce, regardless of whether they are<PRTPAGE P="58164"/>associated with an outbreak or not. Any recall may have a significant impact on the industry, including the loss of sales revenue, the cost to dispose of recalled products, and the loss of consumer confidence and business reputation. Recalls negatively impact consumers by creating anxiety and time-consuming inconveniences (<E T="03">e.g.</E>looking for recall information, checking the products purchased, returning or disposing of products identified by the recalls, etc.). For the Government, the Agency incurs costs for conducting recalls<SU>35</SU>
          <FTREF/>and recovery of adulterated products. The Food and Drug Administration has estimated that a Class I recall<SU>36</SU>
          <FTREF/>may cost as much as $3 to $5 million for the manufacturer, retailers, and State, local, and Federal authorities.<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>35</SU>This includes inspectors' activities at the establishments, FSAs and recall effectiveness checks, and dissemination of information about recalls through press releases.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>36</SU>A Class I recall is defined as a health hazard situation where there is a reasonable possibility that the use of the products will cause serious, adverse health consequences. Non-O157 STEC outbreak fits in this category.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>Preliminary Regulatory Impact Analysis and Initial Regulatory Flexibility Analysis of the Proposed Rules to Ensure the Safety of Juice Products, 63 FR 24258, May 1, 1998.</P>
        </FTNT>
        <P>The first and only FSIS non-O157 STEC recall to date took place in August 2010. It is not clear how many recalls would have occurred if the new testing policy had been implemented or whether, on net, the policy will decrease or increase the number of recalls.</P>
        <HD SOURCE="HD3">Net Benefits</HD>
        <P>As explained in the Expected Costs and Expected Benefits Sections, there are uncertainties in our cost and benefit estimates. For example, we do not know how many illnesses will actually be prevented. It is not clear whether on net there will be a reduction in the number of illnesses. It is also challenging to know what the industry cost will be because it is difficult to predict how many establishments will start to test and what the size distribution will be or to what extent industry will take additional measures that will prevent, reduce, or control those hazards, as they do with regard to O157 STEC.<SU>38</SU>
          <FTREF/>However, the Agency has determined that the potential public health benefits justify the costs.</P>
        <FTNT>
          <P>

            <SU>38</SU>One common measure that establishments use is purchase specifications in a prerequisite program. FSIS Directive 10,010.1 stipulates that FSIS expects the establishment to have: (1) A document from each supplier that provides assurance that the supplier employs CCPs (critical control points) that address<E T="03">E. coli</E>O157:H7, (2) certificates of analysis and the sampling method used by the supplier, and (3) records that verify on an on-going basis that the receiving establishment is executing its program effectively. Other measures establishment can use include (a) treating or washing the product when removed from Cryovac bags and trimming the outer surface before processing non-intact product, and (2) using antimicrobials or other lethality treatments on raw beef product and verifying the effectiveness of those antimicrobials. (FSIS Directive 10,010.1)</P>
        </FTNT>
        <HD SOURCE="HD2">Impact on Small Business<E T="51">39</E>
          <FTREF/>
        </HD>
        <FTNT>
          <P>
            <SU>39</SU>Based on FSIS' HACCP (Hazard Analysis and Critical Control Points) size definition: very small establishments have fewer than 10 employees or generate less than $2.5 million in annual sales; and small establishments have 10 or more but fewer than 500 employees and generate more than $2.5 million in annual sales.</P>
        </FTNT>
        <P>This FSIS document on non-O157 STEC does not impose a testing requirement on official establishments. As mentioned above, establishments are already required to identify hazards reasonably likely to occur and to take measures that will prevent, eliminate, or reduce those hazards under HACCP. The measures could include purchase specifications in a prerequisite program, sanitary activities, and using antimicrobials or other lethality treatments on raw beef product. Establishments that produce non-intact raw beef products, such as ground beef, or the intact raw components of those products, must already operate food safety systems that control STEC O157. Therefore, this document does not impose significant negative impact on a significant number of small and very small businesses. FSIS is requesting comment on the impact of this document on small businesses.</P>
        <HD SOURCE="HD2">Summary of Requests for Comment</HD>
        <P>FSIS is requesting comment on the following specific subjects discussed in this document related to non-O157 STEC serogroups O26, O45, O101, O121, and O145:</P>
        
        <FP SOURCE="FP-1">• FSIS regulatory sampling plan for non-O157 STEC for the above serogroups</FP>
        <FP SOURCE="FP-1">• Suggestions for baseline survey of non-O157 STEC prevalence in certain raw beef products</FP>
        <FP SOURCE="FP-1">• Whether a technical meeting on methods for controlling non-O157 STEC should be held during the comment period</FP>
        <FP SOURCE="FP-1">• Whether to hold an additional public meeting on the plan for implementing the policy on non-O157 STEC</FP>
        <FP SOURCE="FP-1">• Validation guidance for pathogen detection test kits</FP>
        <FP SOURCE="FP-1">• Preliminary estimates of the cost per test for non-O157 STEC</FP>
        <FP SOURCE="FP-1">• Estimates of the loss to industry of diverting positive-testing product to cooking</FP>
        <FP SOURCE="FP-1">• The usefulness of technical workshops for small and very small establishments</FP>
        <FP SOURCE="FP-1">• What obstacles might prevent establishments from adjusting to the FSIS policy on non-O157 STEC by March 5, 2012 and what alternative implementation date would be more practical</FP>
        <FP SOURCE="FP-1">• What education, outreach, or training materials would be of greatest assistance to establishments in preparing for implementation of the Agency's policy</FP>
        <FP SOURCE="FP-1">• For foreign governments, what additional information would be helpful in addressing equivalency or implementation concerns not already addressed in this document and accompanying materials</FP>
        

        <FP>We are also requesting comment on the DRAFT Risk Profile for Pathogenic Non-O157 Shiga Toxin-Producing<E T="03">Escherichia coli</E>that we are making available at<E T="03">http://www.fsis.usda.gov/PDF/Non_O157_STEC_Risk_Profile.pdf.</E>FSIS undertook the preparation of the risk profile to help clarify the extent of the scientific literature available for evaluating the issues raised by the Citizen's Petition.</FP>
        <HD SOURCE="HD2">USDA Nondiscrimination Statement</HD>
        <P>The U.S. Department of Agriculture (USDA) prohibits discrimination in all its programs and activities on the basis of race, color, national origin, gender, religion, age, disability, political beliefs, sexual orientation, and marital or family status. (Not all prohibited bases apply to all programs.) Persons with disabilities who require alternative means for communication of program information (Braille, large print, audiotape, etc.) should contact USDA's Target Center at 202-720-2600 (voice and TTY).</P>
        <P>To file a written complaint of discrimination, write USDA, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue, SW., Washington, DC 20250-9410 or call 202-720-5964 (voice and TTY). USDA is an equal opportunity provider and employer.</P>
        <HD SOURCE="HD2">Additional Public Notification</HD>

        <P>Public awareness of all segments of rulemaking and policy development is important. Consequently, in an effort to ensure that the public and in particular minorities, women, and persons with disabilities, are aware of this document, FSIS will announce it on-line through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations/2010_Notices_Index/.</E>
        </P>
        <P>FSIS also will 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,<PRTPAGE P="58165"/>FSIS public meetings, and other types of information that could affect or would be of interest to our constituents and stakeholders. The Update is communicated via Listserv, a free e-mail subscription service consisting of industry, trade, and farm groups, consumer interest groups, allied health professionals, scientific professionals, and other individuals who have requested to be included. The Update also is available on the FSIS Web page. Through Listserv and the Web page, FSIS is able to provide information to a much broader, more diverse audience. In addition, FSIS offers an e-mail subscription service which provides automatic and customized access to selected food safety news and information. This service is available at<E T="03">http://www.fsis.usda.gov/News_&amp;_Events/Email_Subscription/.</E>Options range from recalls, export information, 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, September 13, 2011.</DATED>
          <NAME>Alfred V. Almanza,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24043 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <CFR>10 CFR Parts 50, 52, and 100</CFR>
        <DEPDOC>[Docket Nos. PRM-50-97, PRM-50-98, PRM-50-99,PRM-50-100, PRM-50-101, PRM-50-102; NRC-2011-0189]</DEPDOC>
        <SUBJECT>Petitions for Rulemaking Submitted by the Natural Resources Defense Council, Inc.</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Petitions for rulemaking; notice of receipt.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) has received six petitions for rulemaking (PRM), dated July 26, 2011, from the Natural Resources Defense Council, Inc. (NRDC or the petitioner). The petitioner requests that the NRC amend its regulations to require emergency preparedness (EP) enhancements for prolonged station blackouts; EP enhancements for multiunit events; licensees to confirm seismic hazards and flooding hazards every 10 years and address any new and significant information; licensees to improve spent nuclear fuel pool safety; each operating and new reactor licensee to establish station blackout mitigation strategies and resources; and more realistic, hands-on training and exercises on Severe Accident Mitigation [sic] Guidelines and Extreme Damage Mitigation Guidelines for specified licensee staff. The NRC is not instituting a public comment period for these PRMs at this time.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You can access publicly available documents related to this action, including the six petitions for rulemaking, using the following methods:</P>
          <P>•<E T="03">NRC's Public Document Room (PDR):</E>The public may examine and have copies made, for a fee, publicly available documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
          <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>Publicly available documents created or received at the NRC are available online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>From this page, the public can gain entry into ADAMS, which provides text and image files of the NRC's public documents. If you do not have access to ADAMS or if there are problems in accessing the documents located in ADAMS, contact the NRC's PDR reference staff at 1-800-397-4209, 301-415-4737, or by e-mail to<E T="03">pdr.resource@nrc.gov.</E>For the ADAMS accession numbers to the six PRMs, see Section I, Procedural Processing, of this document.</P>
          <P>•<E T="03">Federal Rulemaking Web Site:</E>Supporting materials related to the six petitions for rulemaking can be found at<E T="03">http://www.regulations.gov</E>by searching on the related Docket IDs. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; e-mail:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Cindy Bladey, Chief, Rules, Announcements, and Directives Branch, Division of Administrative Services, Office of Administration, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, telephone: 301-492-3667, e-mail:<E T="03">Cindy.Bladey@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Procedural Processing</HD>
        <P>The petitions for rulemaking were docketed by the NRC on July 28, 2011, and have been assigned the following Docket Numbers and can be accessed in ADAMS under the associated ADAMS accession number:</P>
        <GPOTABLE CDEF="s120,r60,xs58" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Title</CHED>
            <CHED H="1">Docket Nos.</CHED>
            <CHED H="1">ADAMS ML No.</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Emergency Preparedness Enhancements for Prolonged Station Blackouts</ENT>
            <ENT>PRM-50-97</ENT>
            <ENT>ML11216A237</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Emergency Preparedness Enhancements for Multiunit Events</ENT>
            <ENT>PRM-50-98</ENT>
            <ENT>ML11216A238</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Seismic Hazards and Flooding Hazards</ENT>
            <ENT>PRM-50-99</ENT>
            <ENT>ML11216A239</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Spent Nuclear Fuel Pool Safety</ENT>
            <ENT>PRM-50-100</ENT>
            <ENT>ML11216A240</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Station Blackout Mitigation</ENT>
            <ENT>PRM-50-101</ENT>
            <ENT>ML11216A241</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Training on Severe Accident Mitigation [sic] Guidelines</ENT>
            <ENT>PRM-50-102</ENT>
            <ENT>ML11216A242</ENT>
          </ROW>
        </GPOTABLE>

        <P>Each submission separately cites the “Recommendations for Enhancing Reactor Safety in the 21st Century: The Near-Term Task Force Review of Insights from the Fukushima Dai-ichi Accident” (Fukushima Task Force Report, ML111861807), dated July 12, 2011, as the rationale for the petition for rulemaking. The Commission has recently directed staff to engage promptly with stakeholders to review and assess the recommendations of the Fukushima Task Force Report for the purpose of providing the Commission with fully-informed options and recommendations.<E T="03">See</E>U.S. Nuclear Regulatory Commission, “Near-Term Report and Recommendations for Agency Actions Following the Events in Japan,” Staff Requirements Memorandum SECY-11-0093, August 19, 2011 (ADAMS Accession No. ML112310021) and U.S. Nuclear Regulatory Commission, “Engagement<PRTPAGE P="58166"/>of Stakeholders Regarding the Events in Japan,” Staff Requirements Memorandum COMWDM-11-0001/COMWCO-11-0001, August 22, 2011 (ADAMS Accession No. ML112340693). The NRC will consider the issues raised by these PRMs through the process the Commission has established for addressing the recommendations from the Fukushima Task Force Report, and is not providing a separate opportunity for public comment on the PRMs at this time.</P>
        <HD SOURCE="HD1">II. Petitioner</HD>
        <P>The NRDC is a national, nonprofit, membership environmental organization incorporated in New York in 1970. The NRDC has offices in Washington, DC, New York City, San Francisco, Chicago, Los Angeles, and Beijing. The staff membership of NRDC consists of lawyers, scientists, and policy experts. The NRDC states that its purpose is to maintain and enhance environmental quality and monitor Federal agency actions to ensure that Federal statutes enacted to protect human health and the environment are fully and properly implemented. With regard to the NRC, the NRDC asserts that, since its inception in 1970, it has sought to improve the environmental, health, and safety conditions at the nuclear facilities licensed by the NRC and its predecessor agency.</P>
        <HD SOURCE="HD1">III. Petitions</HD>
        <P>All six PRMs cite the Recommendations for Enhancing Reactor Safety in the 21st Century: The Near-Term Task Force Review of Insights from the Fukushima Dai-ichi Accident (Fukushima Task Force Report), dated July 12, 2011, currently under review by the Commission, as the rationale and bases for the petitions for rulemaking. The Fukushima Task Force was a group of NRC staff experts specifically selected to review the Fukushima Dai-ichi Accident and made recommendations applicable to power reactors in the United States. A summary of each PRM follows.</P>
        <HD SOURCE="HD2">1. Require EP Enhancements for Prolonged Station Blackouts. [PRM-50-97]</HD>
        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR 50, 52, and other applicable regulations to require emergency preparedness enhancements for prolonged station blackouts in the areas of (1) Communications ability, (2) Emergency Response Data System capability, (3) training and exercises, and (4) equipment and facilities. The petitioner cites Section 4.3.1, pages 50-56—regarding the requiring of facility emergency plans to address prolonged station blackouts—of the Fukushima Task Force Report as the rationale for its PRM.</P>
        <HD SOURCE="HD2">2. Require EP Enhancements for Multiunit Events. [PRM-50-98]</HD>
        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR parts 50, 52, and other applicable regulations to require EP enhancements for multiunit events in the areas of (1) Personnel staffing, (2) dose assessment capability, (3) training and exercises, and (4) equipment and facilities. The petitioner cites Section 4.3.1, pages 50-56—regarding the requiring of facility emergency plans to address multiunit events—of the Fukushima Task Force Report as the rationale for its PRM.</P>
        <HD SOURCE="HD2">3. Require Licensees To Confirm Seismic Hazards and Flooding Hazards Every 10 Years and Address Any New and Significant Information. [PRM-50-99]</HD>
        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR parts 50, 52, 100, and other applicable regulations to require licensees to confirm seismic hazards and flooding hazards every 10 years and address any new and significant information, which would include, if necessary, updating the design basis for structures, systems, and components important to safety to protect against the updated hazards. The petitioner cites Section 4.1.1, pages 25-30—regarding the reevaluation and upgrade of design basis seismic and flooding protection of structures, systems, and components for each operating reactor—of the Fukushima Task Force Report as the rationale for its PRM.</P>
        <HD SOURCE="HD2">4. Require Licensees To Improve Spent Nuclear Fuel Pool Safety. [PRM-50-100]</HD>

        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR parts 50, 52, and other applicable regulations to require licensees to (1) Provide sufficient safety-related instrumentation, able to withstand design-basis natural phenomena, to monitor key spent fuel pool parameters (<E T="03">i.e.,</E>water level, temperature, and area radiation levels) from the control room; (2) provide safety-related AC electrical power for the spent fuel pool makeup system; (3) revise their technical specifications to address requirements to have one train of onsite emergency electrical power operable for spent fuel pool makeup and spent fuel pool instrumentation when there is irradiated fuel in the spent fuel pool, regardless of the operational mode of the reactor; and (4) have an installed seismically qualified means to spray water into the spent fuel pools, including an easily accessible connection to supply the water (<E T="03">e.g.,</E>using a portable pump or pumper truck) at grade outside the building. The petitioner cites Section 4.2.4, pages 43-46—regarding the enhancement of spent fuel pool makeup capability and instrumentation for the spent fuel pool—of the Fukushima Task Force Report as the rationale for its PRM.</P>
        <HD SOURCE="HD2">5. Revise 10 CFR 50.63 [Station Blackout Mitigation]. [PRM-50-101]</HD>
        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR parts 50, 52, and other applicable regulations to revise 10 CFR 50.63 to require each operating and new reactor licensee to (1) Establish a minimum coping time of 8 hours for a loss of all AC power, (2) establish the equipment, procedures, and training necessary to implement an “extended loss of all AC” coping time of 72 hours for core and spent fuel pool cooling and for reactor coolant system and primary containment integrity as needed, and (3) preplan and prestage offsite resources to support uninterrupted core and spent fuel pool cooling and reactor coolant system and containment integrity as needed, including the ability to deliver the equipment to the site in the time period allowed for extending coping, under conditions involving significant degradation of offsite transportation infrastructure associated with significant natural disasters.</P>
        <P>The petitioner cites Section 4.2.1, pages 32-39, of the Fukushima Task Force Report, regarding the enhancement of the ability of nuclear power plants to deal with the effect of prolonged station blackout conditions at single and multiunit sites without damage to the nuclear fuel in the reactor or spent fuel pool and without the loss of reactor coolant system or primary containment integrity.</P>
        <HD SOURCE="HD2">6. Require More Realistic Training on Severe Accident Mitigation Guidelines [PRM-50-102]</HD>

        <P>The petitioner requests that the NRC institute a rulemaking proceeding applicable to nuclear facilities licensed under 10 CFR parts 50, 52, and other applicable regulations to require more realistic, hands-on training and exercises on Severe Accident Mitigation [sic] Guidelines (SAMGs) and Extreme<PRTPAGE P="58167"/>Damage Mitigation Guidelines (EDMGs) for licensee staff expected to implement the strategies and those licensee staff expected to make decisions during emergencies, including emergency coordinators and emergency directors. The petitioner cites Section 4.2.5, pages 46-50—regarding the strengthening and integration of onsite emergency response capabilities such as emergency operating procedures, SAMGs, and EDMGs—of the Fukushima Task Force Report as the rationale for its PRM.</P>
        <HD SOURCE="HD1">IV. Conclusion</HD>
        <P>The Commission is currently reviewing the Fukushima Task Force Report, including each issue presented in the six petitions for rulemaking. The petitioner solely and specifically cites the Fukushima Task Force Report as the rationale and bases for its six PRMs. The NRC will consider the issues raised by these PRMs through the process the Commission has established for addressing the recommendations from the Fukushima Task Force Report and is not providing a separate opportunity for public comment on the PRMs at this time.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 14th day of September 2011.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Annette Vietti-Cook,</NAME>
          <TITLE>Secretary of the Commission.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24079 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">CONSUMER PRODUCT SAFETY COMMISSION</AGENCY>
        <CFR>16 CFR Part 1221</CFR>
        <DEPDOC>[CPSC Docket No. CPSC-2011-0064]</DEPDOC>
        <RIN>RIN 3041-AC92</RIN>
        <SUBJECT>Safety Standard for Play Yards</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Consumer Product Safety Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Section 104(b) of the Consumer Product Safety Improvement Act of 2008 (“CPSIA”) requires the United States Consumer Product Safety Commission (“Commission,” “CPSC,” or “we”) to promulgate consumer product safety standards for durable infant or toddler products. These standards are to be “substantially the same as” applicable voluntary standards or more stringent than the voluntary standard if the Commission concludes that more stringent requirements would further reduce the risk of injury associated with the product. The Commission is proposing a safety standard for play yards in response to the direction under Section 104(b) of the CPSIA.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments by December 5, 2011.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Comments related to the Paperwork Reduction Act aspects of the marking, labeling, and instructional literature of the proposed rule should be directed to the Office of Information and Regulatory Affairs, OMB,<E T="03">Attn:</E>CPSC Desk Officer,<E T="03">Fax:</E>202-395-6974, or e-mailed to<E T="03">oira_submission@omb.eop.gov.</E>
          </P>
          <P>Other comments, identified by Docket No. CPSC-2011-0064, may be submitted electronically or in writing:</P>
          <P>
            <E T="03">Electronic Submissions:</E>Submit electronic comments to the Federal eRulemaking Portal at:<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments. To ensure timely processing of comments, the Commission is no longer directly accepting comments submitted by electronic mail (e-mail), except through<E T="03">http://www.regulations.gov.</E>The Commission encourages you to submit electronic comments by using the Federal eRulemaking Portal, as described above.</P>
          <P>
            <E T="03">Written Submissions:</E>Submit written submissions in the following way: Mail/Hand delivery/Courier (for paper, disk, or CD-ROM submissions), preferably in five copies, to: Office of the Secretary, Consumer Product Safety Commission, Room 502, 4330 East West Highway, Bethesda, MD 20814; telephone (301) 504-7923.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this rulemaking. All comments received may be posted without change, including any personal identifiers, contact information, or other personal information provided, to<E T="03">http://www.regulations.gov.</E>Do not submit confidential business information, trade secret information, or other sensitive or protected information that you do not want to be available to the public. If furnished at all, such information should be submitted in writing.</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>, and insert the docket number, CPSC 2011-0064, into the “Search” box and follow the prompts.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Gregory K. Rea, Project Manager, Directorate for Laboratory Sciences, Consumer Product Safety Commission, 5 Research Place, Rockville, MD 20850; e-mail<E T="03">GRea@cpsc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">A. Background and Statutory Authority</HD>
        <P>The Consumer Product Safety Improvement Act of 2008 (“CPSIA,” Pub. L. 110-314) was enacted on August 14, 2008 Section 104(b) of the CPSIA requires the Commission to promulgate consumer product safety standards for durable infant and toddler products. These standards are to be “substantially the same as” applicable voluntary standards or more stringent than the voluntary standard if the Commission concludes that more stringent requirements would further reduce the risk of injury associated with the product. The term “durable infant or toddler product” is defined in section 104(f)(1) of the CPSIA as a durable product intended for use, or that may be reasonably expected to be used, by children under the age of 5 years. Play yards are one of the products specifically identified in section 104(f)(2)(F) as a durable infant or toddler product.</P>

        <P>In this document, the Commission proposes a safety standard for play yards. The proposed standard is based on the voluntary standard developed by ASTM International (formerly the American Society for Testing and Materials), ASTM F 406-11, “Standard Consumer Safety Specification for Non-Full-Size Baby Cribs/Play Yards” (“ASTM F 406-11”). The ASTM standard is copyrighted but can be viewed as a read-only document, only during the comment period on this proposal, at<E T="03">http://www.astm.org/cpsc.htm</E>, by permission of ASTM.</P>
        <HD SOURCE="HD1">B. The Product</HD>
        <HD SOURCE="HD2">1. Definition</HD>
        <P>ASTM F 406-11 defines a “play yard” as a “framed enclosure that includes a floor and has mesh or fabric sided panels primarily intended to provide a play or sleeping environment for children. It may fold for storage or travel.” Play yards are intended for children who are less than 35 inches tall who cannot climb out of the product. Play yards are convenient because they usually fold for storage or travel. Some play yards include accessory items that attach to the product, including mobiles, toy bars, canopies, bassinets, and changing tables. The accessory item(s) usually attaches to the side rails or corner brackets of the play yard.</P>
        <HD SOURCE="HD2">2. The Market</HD>

        <P>Based on a 2005 survey conducted by American Baby Group titled, “2006 Baby Products Tracking Study,” we estimate that approximately 2.9 million<PRTPAGE P="58168"/>play yards are sold in the United States each year. We estimate that there are 23 manufacturers or importers supplying play yards to the U.S. market. Eleven firms are domestic manufacturers, and 10 firms are domestic importers. Two firms are foreign importers.</P>
        <P>Play yards from 11 of the 23 firms have been certified as compliant with the ASTM voluntary play yard standard by the Juvenile Products Manufacturers Association (“JPMA”), the major U.S. trade association that represents juvenile product manufacturers and importers. In addition, three other firms claim compliance with the ASTM voluntary play yard standard and, in some cases, provide test results publicly.</P>
        <HD SOURCE="HD1">C. Incident Data</HD>
        <P>The CPSC's Directorate for Epidemiology reports that there have been 2,128 incidents reported to the Commission regarding play yards from early November 2007 until early April 2011. Of the 2,128 reported incidents, there were 49 fatalities, 165 nonfatal injuries, and 1,914 noninjury incidents. The data is drawn from the CPSC's “Early Warning System” (“EWS”), a database created in late 2007, which allows the Commission to monitor incoming incident data closely. Once an incident report is entered into EWS, it is carefully reviewed by a subject matter expert. Thus, EWS contains the best data to support the play yard regulatory work.</P>
        <HD SOURCE="HD2">1. Fatalities</HD>
        <P>From early November 2007 through early April 2011, there were 49 fatalities associated with play yards. Twenty-seven deaths are attributable to unsafe sleep environments within the play yard, such as the presence of soft or extra bedding, or unsafe sleep practices, such as putting infants to sleep on their stomach instead of their back.</P>
        <P>Ten suffocation deaths were caused by unsafe environments around the play yard. Examples of hazardous surroundings include: window blind cords or computer cords that fell into the play yard where the cords formed dangerous loops and resulted in strangulation fatalities. Other deaths were caused when items were placed on top of the play yard to prevent the child from climbing out. These items, such as wood, mesh gates, or crib tents, caused suffocation deaths when children tried to crawl out of the product and became stuck between the side rail and the item placed on top of the play yard.</P>
        <P>The remainder of the fatal incidents include:</P>
        <P>• Two children were killed in separate incidents when they were able to climb out of a play yard and gain access to a pool. Both children drowned in the pool.</P>
        <P>• Two toddlers were killed in separate incidents while standing up in a play yard. It is believed that they leaned forward against the side rail (possibly to reach an object that the child had thrown outside the play yard), lost consciousness, and suffocated when the pressure from the side rail compressed the airway.</P>
        <P>• One toddler was killed when the play yard collapsed unexpectedly. The child was trapped and suffocated.</P>
        <P>• One death was caused by a looped strap hanging from a changing table accessory. The changing table was supported by the side rails of the play yard. The looped strap fell into the play yard space occupied by the child and resulted in the child's strangulation.</P>
        <P>• One death was caused by an assembly error that occurred when the mattress pad was not secured completely to the bottom of the play yard. The child suffocated in the pocket created between the unsecured mattress pad and the floor of the play yard.</P>
        <P>• Five other deaths are associated with play yards, but there was insufficient information to determine the cause.</P>
        <HD SOURCE="HD2">2. Nonfatal Injuries</HD>
        <P>From early November 2007 through early April 2011, there were 2,079 nonfatal incident reports. Of those, 165 incidents involved an injury, and four of those required hospitalization. Although the remaining 1,914 nonfatal incident reports did not result in an injury, many of the descriptions indicate the potential for serious injury or death.</P>
        <P>The largest number of nonfatal incident reports were attributable to the unexpected collapse of the side rail of a play yard. Of the 2,079 nonfatal incident reports, 1,902 involved the collapse of one or more sides of a play yard. Of the 165 incidents involving an injury, 124 were the result of a play yard side rail collapse. Of the 124 injuries, there was one hospitalization for a concussion that was caused by the collapse of a side rail.</P>
        <P>The remainder of the nonfatal injury incidents included:</P>
        <P>• Eight injuries caused by broken or detached component parts, such as loose wheels or loose hardware, which resulted in instability or collapse of the product.</P>
        <P>• Eight injuries caused by various product-related problems, including sharp surfaces.</P>
        <P>• Five injuries related to the mesh or fabric sides of the play yard, such as stitching that unraveled, tears in the fabric, mesh holes that were too large, and mesh material that was too abrasive.</P>
        <P>• Five injuries related to the mattress pad or the floor of the play yard. Examples of injuries in this category included: Mattresses or pads that were insufficiently fastened to the play yard floor, resulting in toddlers becoming trapped under the mattress or pad.</P>
        <P>• Five injures related to toddlers climbing out or falling out of the play yard. This category included one toddler who was hospitalized for a serious head injury after climbing or falling out of the play yard.</P>
        <P>• Four injuries resulted when children were standing in the play yard, lost their balance, and fell.</P>
        <P>• Two injuries caused by broken or hazardous accessories, such as dangling straps from changing tables. Other examples of hazardous accessories included: broken or detached components from music boxes, trays, mirrors, and toy holders.</P>
        <P>• Two injuries related to assembly errors, including one child who was hospitalized with a severe finger laceration after getting his or her finger caught in the play yard as it was being assembled.</P>
        <P>• One injury that resulted in a hospitalization was caused by the presence of soft bedding in the play yard. This was a severe injury to a 7-week-old infant who suffered brain damage.</P>
        <P>• One other injury is associated with play yards, but there was insufficient information to determine the cause.</P>
        <HD SOURCE="HD1">D. Play Yard International Standards and the ASTM Voluntary Standard</HD>

        <P>Section 104(b)(1)(A) of the CPSIA requires the Commission to consult representatives of “consumer groups, juvenile product manufacturers, and independent child product engineers and experts” to “examine and assess the effectiveness of any voluntary consumer product safety standards for durable infant or toddler products.” Through the ASTM process, we consulted with manufacturers, retailers, trade organizations, laboratories, consumer advocacy groups, consultants, and members of the public. Most of the consultation involved assessing and reviewing the ASTM standard, which is the primary play yard standard in effect in the United States. Significantly, in 2010, in consultation with ASTM, we identified three hazards that were not addressed in the ASTM play yard standard. Those three hazards are now addressed in ASTM 406-11 and include<PRTPAGE P="58169"/>new requirements to address side rails that collapse into a dangerous V-shape (discussed in section E.5 below); new requirements to address structural failures related to corner brackets (discussed in section E.8 below); and new requirements to address mattress displacement (discussed in section E.10 below).</P>
        <P>In addition to reviewing the ASTM standard, we reviewed several international standards.</P>
        <HD SOURCE="HD2">1. International Standards</HD>
        <P>We reviewed several international standards when working with ASTM to create ASTM 406-11, including:</P>
        <P>• The European Standard, BS EN 12227-1 &amp; 2: 2010, “Playpens for domestic use”;</P>
        <P>• the Australian and New Zealand Standard, AS/NZ S2195: 2010, “Folding cots—Safety Requirements”; and</P>
        <P>• the Canadian standard, C.R.C., c. 932, “Playpen Regulations.”</P>
        <P>We considered the Australian and New Zealand Standard when we, in consultation with ASTM, devised the performance requirement and test method to address V-shape side rail collapses. Ultimately however, CPSC and ASTM chose to use a test method meant to prevent neck entrapment in expansion gates that exists in ASTM F 1004-09, “Standard Consumer Safety Specification for Expansion Gates and Expandable Enclosures.”</P>
        <P>We considered the European Standard when we, in consultation with ASTM, devised the performance requirement and test method to address structural failures in corner brackets. Ultimately, the test method found in the European Standard was rejected because its main purpose is to test latch durability, rather than corner post durability. The requirements currently found in ASTM F 406-11 to address this hazard were developed by CPSC staff and are better suited than the requirements in the European Standard to test corner post durability.</P>
        <P>We also considered the European Standard when we, in consultation with ASTM, created the mattress displacement performance requirement and test method. While the requirements in ASTM F 406-11 are similar to those in the European Standard, we, in consultation with ASTM staff, made changes that will result in more reliable and repeatable results.</P>
        <HD SOURCE="HD2">2. The ASTM Voluntary Standard</HD>
        <P>ASTM F 406 was first approved and published in 1977. ASTM has revised the standard several times since then, with the most current version, ASTM F 406-11, published on May 15, 2011. Historically, one of the most significant changes occurred in ASTM F 406-02, published in June 2002, when the standard for non-full-size cribs merged with the play yard standard to group products with similar uses, and took on its current name, “Standard Consumer Safety Specification for Non-Full-Size Baby Cribs/Play Yards.”</P>
        <P>The proposed rule would only pertain to play yards. In the<E T="04">Federal Register</E>of December 28, 2010 (75 FR 81766), we issued a final rule on safety standards for non-full-size cribs. Thus, the proposed rule would exclude provisions of ASTM F406-11 that apply to non-full-size cribs. The proposed rule would exclude from the play yard standard sections 5.17, 5.19, 5.20, the entirety of section 6, section 8.1 through 8.10.5, and section 10.1.1.1 of ASTM F 406-11. In addition, for section 9.4.2.10 of ASTM F 406-11, we propose to include only the first section, which is a labeling requirement meant to inform consumers that only the mattress or pad provided by the manufacturer should be used. The remainder of section 9.4.2.10 of ASTM F 406-11 is applicable to non-full-size cribs and would be excluded from the play yard standard.</P>
        <P>Many play yards include accessory items, such as bassinets or changing tables that attach to the side of the play yard rails. While ASTM F 406-11 contains requirements to address entrapment of children in accessories, such as requirements designed to prevent changing table straps from forming loops that enter the play yard space and could cause strangulation, the specific requirements for accessories will be addressed in separate rulemakings. For example, ASTM F 406-11 addresses possible entrapment in bassinet attachments, but the performance requirements, test methods, and warning provisions for the bassinet itself will be handled in a separate rulemaking.</P>
        <P>The key provisions of the current ASTM play yard standard include: Definitions; general requirements; performance requirements; specific test methods; and requirements for marking, labeling, and instructional literature.</P>
        <P>
          <E T="03">Definitions.</E>The definition of “play yard (aka playpen)” is a “framed enclosure that includes a floor and has mesh or fabric- sided panels, primarily intended to provide a play or sleeping environment for children. It may fold for storage or travel.”</P>
        <P>
          <E T="03">General Requirements and Specific Test Methods.</E>The play yard standard contains general requirements that the product must meet, as well as mandated test methods that must be used to ensure that the product meets those requirements, including:</P>
        <P>• Requirements for corner posts;</P>
        <P>• Restrictions on sharp points and edges (as well as their protective caps), small parts, lead paint, and flammable solids;</P>
        <P>• Specifications to prevent scissoring, shearing, and pinching;</P>
        <P>• Requirements for toy accessory items;</P>
        <P>• Specifications on latching and locking mechanisms;</P>
        <P>• Specifications on openings (intended to prevent finger and toe entrapment), labeling (intended to prevent labels from being removed and ingested or aspirated on), coil springs and protrusions;</P>
        <P>• Requirements that the play yard be stable;</P>
        <P>• Requirements meant to protect a child from entrapment in accessory items, such as a bassinet or changing table, as well as requirements to protect a child from being strangled in a cord or strap that accompanies the product or an accessory item (such as the restraint straps on a changing table); and</P>
        <P>• Specifications for the mattress in a play yard.</P>
        <P>
          <E T="03">Performance Requirements and Specific Test Methods.</E>The play yard standard provides performance requirements that the product must meet, as well as mandated test methods that must be used to ensure that the product meets the performance requirements, including:</P>
        <P>• A side height requirement (the side of the play yard must be, at least, 20 inches from the top of the noncompressed mattress pad to the top of the side rail);</P>
        <P>• Side deflection and strength requirements (the play yard must be able to withstand testing without collapsing, and the hinge and latch mechanisms must remain operational);</P>
        <P>• Floor strength requirements;</P>
        <P>• Requirements to address the material that covers the top rail, as well as specifications for the mesh or fabric used in play yards;</P>
        <P>• Requirements addressing mattress displacement;</P>
        <P>• Requirements to eliminate the risk that the side rails will form a dangerous V-shape when collapsed; and</P>
        <P>• Requirements addressing corner bracket failures.</P>
        <P>
          <E T="03">Order of Testing.</E>ASTM F 406-11 also addresses the order of testing. ASTM F 406-11 clarifies that the general requirements, such as restrictions on corner posts, must be met both before and after the performance requirement test methods have been completed.</P>

        <P>Additionally, ASTM F 406-11 indicates that the tests to determine<PRTPAGE P="58170"/>compliance with the performance requirements must be conducted in the order specified in the standard because the testing sequence can influence the test results. Therefore, the standard lists tests in a way such that the most potentially destructive tests are performed last.</P>
        <P>
          <E T="03">Marking, Labeling, and Instructional Literature.</E>ASTM F 406-11 has requirements for marking, labeling, and instructions that must accompany a play yard, including warnings regarding proper use of accessory attachment items, and warnings regarding suffocation hazards that may arise if soft bedding is added to the product.</P>
        <HD SOURCE="HD1">E. Assessment of Voluntary Standard ASTM F 406-11</HD>
        <P>We considered the fatalities, injuries, and noninjury incidents associated with play yards, and we evaluated the voluntary standard to determine whether ASTM F 406-11 addresses the incident or whether more stringent standards are required that would further reduce the risk of injury associated with the products. We discuss our assessment in this section, but our assessment does not include deaths and injuries associated with play yards where there was insufficient evidence to determine the cause.</P>
        <HD SOURCE="HD2">1. Unsafe Sleep Environment and Unsafe Sleep Practices</HD>
        <P>Unsafe sleep environments, such as sleep environments that contain additional or soft bedding, and unsafe sleep practices, such as placing infants to sleep on their stomach instead of their back, resulted in 27 fatalities and one very serious injury that required hospitalization and resulted in brain damage to the child. Unsafe sleep environments and unsafe sleep practices are not attributable to the design or construction of play yards. ASTM F 406-11 includes product warnings that address the hazards of soft bedding and the hazards associated with placing a child to sleep on their stomach. We do not believe that there are additional requirements that can be put in place in the standard to address unsafe sleep environments and unsafe sleep practices.</P>
        <HD SOURCE="HD2">2. Hazardous Surroundings</HD>
        <P>Ten suffocation deaths were attributable to unsafe environments around the play yard. Examples of hazardous surroundings include: Window blind cords and computer cords that fall into a play yard, forming a loop, and causing strangulations. Other deaths were caused when caregivers placed an object on top of the play yard to keep the child in the play yard, and fatalities resulted when children tried to climb out of the play yard and became trapped between the cover and the side rail. Risks due to hazardous surroundings are not attributable to the design or construction of play yards. ASTM F 406-11 includes product warnings that address the dangers of placing a product near windows where cords can cause strangulation. ASTM F 406-11 also includes a warning about the dangers of using improvised netting or covers over play yards. We do not believe that there are additional requirements that can be put in place in the standard to address this issue.</P>
        <HD SOURCE="HD2">3. Risks Associated With Children Climbing Out or Falling Out of a Play Yard</HD>
        <P>Two children were killed when they were able to climb out or they fell out of their play yard and accessed a pool. Both children drowned. Additionally, five children were injured after climbing or falling out of their play yard, including one injury that resulted in a serious head injury and required hospitalization.</P>
        <P>We considered alternatives that might make it less likely that a child could climb or fall out of a play yard. For example, play yards could be mandated to have higher sides, or manufacturers could provide a “lid” or cover to the play yard. However, in both cases, we felt that these solutions might create additional hazards. Higher sides might make it more difficult for a caregiver to put the child inside the play yard and might increase the chance that caregivers will find alternative, but less safe, sleep environments (such as allowing infants to sleep in adult beds). Requiring a lid or cover increases the chances that the lid or cover will fail in some way, allowing children to attempt to climb out of the product, only to become stuck between the lid and the side rail, which could cause suffocation.</P>
        <P>Therefore, we determined that warnings are the most appropriate way to address climb-out and fall-out hazards. ASTM F 406-11 includes product warnings indicating that play yards are designed for children who are not able to climb out of the play yard. There are additional warning requirements regarding removing any object that can serve as a step that would enable a child to climb out of the play yard. We do not believe that there are additional requirements that can be put in place in the standard to address this issue.</P>
        <HD SOURCE="HD2">4. Standing/Choking Deaths</HD>
        <P>Two toddlers were killed in a similar, but currently unexplained, manner. In both situations, the toddler stood up in the play yard and placed his or her neck against the side rail. In both situations, it is believed that they leaned forward against the side rail (possibly to reach an object that the child had thrown outside the play yard), lost consciousness, and suffocated when the pressure from the side rail compressed the airway. We have investigated both deaths and believe that further review by CPSC staff is warranted to determine if the design or construction of the play yard contributed to the deaths. If we conclude that the design or construction of the play yard did contribute to these deaths, we will determine whether additional requirements are necessary. Because the causation of these incidents is unclear, we are not proposing additional requirements in the standard to address the possibility of standing/choking deaths at this time.</P>
        <HD SOURCE="HD2">5. Side Rail Collapse</HD>
        <P>One child was killed when a play yard's side rails collapsed, trapping the child and resulting in suffocation. Additionally, 124 of the 165 nonfatal injury reports are attributable to side rail collapse. One injury required hospitalization for a concussion. The largest number of nonfatal incident reports (1,902 out of 2,079 reports) are attributable to play yard side rail collapse. We reviewed these incidents and have determined that the majority are caused by failure of the side rail latch that keeps the side rail locked and in place.</P>
        <P>Side collapse issues were addressed significantly in 1997, in ASTM F 406-97, which required the side rails of play yards to have a locking device in order to prevent the center hinge from collapsing and causing the side rail to fall. In 1999, ASTM added a test method that required the locking mechanism on the side rail hinges to withstand a force of 100 pounds, applied diagonally, without breaking or disengaging.</P>
        <P>In August 2009, after a significant number of recalls involving side collapse issues, ASTM published ASTM F 406-09, which included, for the first time, a false latch test in the ASTM play yard standard. The addition of the false latch test was designed to ensure that the top rail does not give the appearance of being locked, when, in fact, the locking device is not engaged completely.</P>

        <P>The recalls related to side collapse, which prompted the change in the 2009 ASTM standard include:<PRTPAGE P="58171"/>
        </P>

        <P>• A January 2009 recall of 200,000 play yards. The CPSC press release can be found here:<E T="03">http://www.cpsc.gov/cpscpub/prerel/prhtml09/09098.html.</E>
        </P>

        <P>• An April 2009 recall of 25,000 play yards. The CPSC press release can be found here:<E T="03">http://www.cpsc.gov/cpscpub/prerel/prhtml09/09187.html.</E>
        </P>

        <P>• A July 2009 recall of about 1 million play yards. The CPSC press release can be found here:<E T="03">http://www.cpsc.gov/cpscpub/prerel/prhtml09/09265.html.</E>
        </P>

        <P>Additionally, ASTM F 406-11 includes a performance requirement and test method that addresses a side rail collapse issue that was a problem in the past but was never adequately addressed in past editions of the ASTM play yard standard. In brief, when folding play yards were relatively new products in the 1990s, some products did not include features designed to prevent unintentional collapse of the side rails. Some play yards collapsed into a V-shape. If a child's neck is caught in the V-shape, the child could suffocate. Most producers of play yards chose to stop designing products that could form a V-shape when the side rails collapsed. The ASTM standard, however, was not revised to ban this design. According to a CPSC press release, originally issued on August 21, 1998, and last revised on May 10, 2004, 13 children died from suffocation in play yards where the side rail collapsed into a V-shape. (These fatalities are not included in the list of incident data referenced throughout this document because they pre-date the creation of the Early Warning System database [the database used to support the regulatory work here]). The press release also mentioned that more than 1.5 million play yards with this dangerous design flaw have been recalled in past years. The press release can be found at:<E T="03">http://www.cpsc.gov/cpscpub/prerel/prhtml98/98156.html.</E>
        </P>
        <P>Thus, after a review of the incidents, as well as an assessment of the locking and latching provisions, the false latch provision, and the new provisions meant to prevent a side collapse that results in a V-shape, we determined that these performance requirements and test methods are sufficient to address play yard side rail collapse issues. Thus, we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">6. Hazards Related to Accessories</HD>

        <P>Play yards often are sold with accessory items, such as changing tables and bassinets, which are meant to attach to the side rails of the play yard. One child was killed when a dangling strap from a changing table accessory formed a loop inside the occupant area of the play yard, resulting in the child's strangulation. The play yard involved in the fatality prompted a recall of 425,000 play yards. That recall was issued on September 27, 2007. The CPSC press release for the recall can be viewed at:<E T="03">http://www.cpsc.gov/cpscpub/prerel/prhtml07/07315.html.</E>Additionally, there were two injuries caused by broken or hazardous accessories.</P>
        <P>In 2005, ASTM published ASTM F 406-05a, which included a section to address entrapment in accessories. The requirement and the accompanying test method were designed to ensure that accessories cannot create openings that can entrap a child's head. In 2008, ASTM published ASTM F 406-08, which included a provision that prohibits the use on an accessory of cords and straps that are capable of forming a loop that could strangle a child. The 2008 ASTM standard also added requirements for toy attachments intended to address incidents related to broken or detached components from music boxes, mirrors, and toy holders.</P>
        <P>We believe that these requirements are sufficient to address these hazards, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">7. Assembly Errors</HD>
        <P>One fatality and two injuries are attributable to assembly errors. The death occurred when the mattress pad of the play yard was not completely secured to the floor of the play yard. The child suffocated in the pocket created between the unsecured pad and the floor of the product.</P>
        <P>An assembly error was the cause of one very serious injury, which required a hospitalization and occurred when a child got his or her finger caught in the gap between the corner bracket and the side rail of the play yard as it was being assembled. The child suffered a severe laceration that required medical attention.</P>
        <P>ASTM F 406-11 contains provisions requiring clear, easy-to-read assembly instructions. We believe that these requirements are sufficient to address these hazards, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">8. Broken or Detached Component Parts Leading to Structural Failures</HD>
        <P>Eight injuries, including bruises and cuts, were caused by broken or detached component parts, such as loose wheels or loose hardware, which led lead to the product becoming unstable or collapsing. Most incidents involved structural failure at the corner brackets of the play yard, resulting in rivets pulling through the corner brackets, cracking of the plastic under the rivets' heads, and rivets and plastic pieces falling out of the corner bracket. This causes the play yard to collapse.</P>
        <P>We believe corner post failures are caused by repeated loading of the side rails by one of the following methods:</P>
        <P>• Caregivers inadvertently and repeatedly leaning on the side rails to reach the child or to use the bassinet or changing table accessory;</P>
        <P>• Children who use the side rails for support while standing; and/or</P>
        <P>• Accessories that are attached to and removed repeatedly from the side rails and corner posts.</P>
        <P>In 2010, CPSC staff recommended a new performance requirement and test method to address this hazard, which was included for the first time in ASTM F 406-11. We believe that these requirements are sufficient to address these hazards, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">9. Mesh and Fabric Sides</HD>
        <P>Five injuries are related to the mesh or fabric sides of the play yard, such as stitching that unraveled, tears in the fabric, mesh holes that were too large and caught an infant's tooth, and mesh material that was too abrasive.</P>
        <P>ASTM F 406-11 contains several performance requirements and test methods to address hazards caused by mesh or fabric. We believe that these requirements are sufficient to address the associated hazards, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">10. Mattress Pad or Play Yard Floor Hazards</HD>
        <P>Five injuries are attributable to problems with the mattress pad or floor of the play yard. Most of these incidents are related to mattress displacement, which occurs when children are able to pull up the mattress and become trapped between the floor of the play yard and the mattress. The mattress of most play yards is attached to the product by hook and loop straps, commonly referred to as “Velcro” straps. The other commonly used method is a “Velcro” patch.</P>

        <P>ASTM F 406-11 includes a performance requirement and a test method that would require a play yard mattress to be able to withstand a certain amount of force before it can be lifted high enough to allow a child to become trapped between the mattress and the play yard floor. We believe that these requirements are sufficient to address these hazards, and we are not proposing additional requirements at this time.<PRTPAGE P="58172"/>
        </P>
        <HD SOURCE="HD2">11. Impact on Play Yard</HD>
        <P>There were four injuries that occurred in play yards because children were standing up in a play yard, lost their balance, and fell. ASTM F 406-11 does include product warnings that address the need to provide supervision, as necessary, when the child is in the product, particularly when the child is playing in the play yard. We believe that these requirements are sufficient, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD2">12. Other Product-Related Concerns</HD>
        <P>Eight injuries were caused by other product-related problems, such as sharp surfaces. For the incidents where we could determine the problem's cause, we believe that the current requirements are sufficient to address these hazards, and we are not proposing additional requirements at this time.</P>
        <HD SOURCE="HD1">F. Description of Proposed Changes to ASTM Standard</HD>
        <P>The proposed rule would create a new part 1221 titled, “Safety Standard for Play Yards.” The proposal would establish ASTM F 406-11, “Standard Consumer Safety Specification for Non-Full-Size Baby Cribs/Play Yards,” as a consumer product safety standard, but with certain changes. We are proposing three changes to ASTM F 406-11, as it applies to play yards. The provisions of ASTM 406-11 that apply to non-full-size cribs have been excluded because those products are addressed in a separate rulemaking.</P>
        <P>Two of the three proposed changes would clarify the existing provisions. Clarification will reduce potential misinterpretations that could result in improper testing. Thus, these clarifications will strengthen the standard and reduce the risk of injury by ensuring that play yard testing is performed properly.</P>
        <P>The last proposed change would affect the test method for determining the strength of corner brackets. The method in ASTM F406-11 currently requires the tester to use a specific size clamp. The proposed change would allow the tester some flexibility, within a carefully selected range, in choosing the clamp to account for play yards with hinges that vary in size. By allowing the tester to choose the most appropriate clamp, we are strengthening the standard and reducing the risk of injury by ensuring that the appropriate testing equipment is used. Using the most appropriate testing equipment will ensure that the test is performed properly and that only the safest play yards will pass laboratory testing and enter the market.</P>
        <P>We describe these proposed changes immediately below:</P>
        <HD SOURCE="HD3">1. Clarifying the Equipment Needed To Perform the Floor Strength Test (Section 8.12.1)</HD>
        <P>Currently, ASTM F 406-11 contains a performance standard to measure the floor strength of a play yard. Section 8.12.1 of ASTM F 406-11 specifies the use of a “Wood block, 6 by 6 in. (150 by 150 mm).” However, the test method in ASTM F 406-11 requires the use of two wood blocks to test the floor strength of the play yard. The proposed rule, therefore, would clarify that “2 Wood blocks” are needed.</P>
        <HD SOURCE="HD3">2. Clarifying the Floor Strength Test Method (Section 8.12.2.1)</HD>
        <P>The current text of the test method for measuring the floor strength of play yards states that the tester must “(p)lace a 50-lb (23-kg) and a 30-lb (14-kg) weight each onto a 6 by 6-in. (150 by 150-mm) wood block spaced 6 +/−<FR>1/2</FR>in. (150 +\−13 mm) apart and maintain for 60s.” The proposed rule would simplify this sentence by dividing it into three sentences by replacing it with the following: “Place the wood blocks 6 +/−<FR>1/2</FR>inch (150 mm +/−13 mm) apart. Place 50-lb (23-kg) weight on one wood block and a 30 lb (24 kg) weight on the other wood block. Maintain for 60 s.” This revision also clarifies that the wood blocks should be put into position before the weight is applied.</P>
        <HD SOURCE="HD3">3. The Shape and Area of the Clamping Surface for the “Top Rail to Corner Post Attachment Test” (Section 8.30.3.1)</HD>
        <P>Currently, ASTM F 406-11 contains a performance standard to address the structural failure of corner brackets of play yards. The test method directs the tester to use clamps to apply a twisting motion to the rail, which strains the corner brackets. The product will fail the test if, for example, there is cracking of the corner brackets. The current test method specifies the shape and area of the clamping surfaces (2 by 2 in.). The proposed rule would allow the tester to choose the shape and area of the clamping surface, within a specified range (1-square-inch to 4 square inches) to accommodate the variety of hinge latching devices in different models of play yards.</P>
        <HD SOURCE="HD2">4. Exclusion of ASTM F 406-11 Sections That Are Applicable to Non-Rull-Size Cribs</HD>
        <P>The proposed rule would pertain only to play yards. In the<E T="04">Federal Register</E>of December 28, 2010 (75 FR 81766), we issued a final rule on safety standards for non-full-size cribs. Thus, the proposed rule would exclude the provisions of ASTM F406-11 that apply to non-full-size cribs. Specifically, the proposal would exclude sections 5.17, 5.19, 5.20, the entirety of section 6, section 8.1 through 8.10.5, and section 10.1.1.1 of ASTM F 406-11. In addition, for section 9.4.2.10 of ASTM F 406-11, the proposal would include only the first section, which is a labeling requirement meant to inform consumers that only the mattress or pad provided by the manufacturer should be used. The remainder of section 9.4.2.10 of ASTM F 406-11 is applicable to non-full-size cribs, and it would be excluded from the play yard standard.</P>
        <HD SOURCE="HD1">G. Effective Date</HD>

        <P>The Administrative Procedure Act (“APA”) generally requires that the effective date of the rule be at least 30 days after publication of the final rule. 5 U.S.C. 553(d). To allow time for play yards to come into compliance, we intend for the standard to become effective 6 months after the publication of the final rule in the<E T="04">Federal Register</E>. We invite comment on how long it will take play yard manufacturers to come into compliance.</P>
        <HD SOURCE="HD1">H. Regulatory Flexibility Act</HD>
        <HD SOURCE="HD2">1. Introduction</HD>
        <P>The Regulatory Flexibility Act (“RFA”), 5 U.S.C. 601-612, requires agencies to consider the impact of proposed rules on small entities, including small businesses. Section 603 of the RFA requires that we prepare an initial regulatory flexibility analysis and make it available to the public for comment when the notice of proposed rulemaking is published. The initial regulatory flexibility analysis must describe the impact of the proposed rule on small entities and identify any alternatives that may reduce the impact. Specifically, the initial regulatory flexibility analysis must contain:</P>
        <P>• A description of, and where feasible, an estimate of the number of small entities to which the proposed rule will apply;</P>
        <P>• A description of the reasons why action by the agency is being considered;</P>
        <P>• A succinct statement of the objectives of, and legal basis for, the proposed rule;</P>

        <P>• A description of the projected reporting, recordkeeping, and other compliance requirements of the proposed rule, including an estimate of the classes of small entities subject to the requirements and the type of professional skills necessary for the preparation of reports or records; and<PRTPAGE P="58173"/>
        </P>
        <P>• An identification, to the extent possible, of all relevant federal rules that may duplicate, overlap, or conflict with the proposed rule.</P>
        <P>In addition, the initial regulatory flexibility analysis must contain a description of any significant alternatives to the proposed rule that would accomplish the stated objectives of the proposed rule and, at the same time, reduce the economic impact on small businesses.</P>
        <HD SOURCE="HD2">2. The Market</HD>
        <P>Based on a 2005 survey conducted by American Baby Group titled, “2006 Baby Products Tracking Study” and Centers for Disease Control and Prevention birth data, we estimate that approximately 2.9 million play yards are sold in the United States each year. We estimate that there are at least 23 manufacturers or importers supplying play yards to the United States market. Eleven of these firms are domestic manufacturers, and 10 of these firms are domestic importers. Two of the firms are foreign importers.</P>
        <P>Under the U.S. Small Business Administration (“SBA”) guidelines, a manufacturer of play yards is small if it has 500 or fewer employees, and an importer is considered small if it has 100 or fewer employees. Based on these guidelines, 10 domestic manufacturers and all 10 of the domestic importers known to supply play yards to the U.S. market are small businesses. The remaining entities include a large domestic manufacturer and two foreign importers. There may be additional unknown small manufacturers and importers operating in the U.S. market.</P>
        <P>The Juvenile Product Manufacturers Association (“JPMA”) runs a voluntary certification program for juvenile products. Certification under the JPMA program is based on the ASTM voluntary play yard standard. Eleven of the 23 manufacturers or importers have been certified as compliant with the ASTM voluntary play yard standard by the JPMA. Three additional manufacturers or importers claim to comply with the ASTM voluntary play yard standard, but they do not participate in the JPMA certification program. In some cases, these three manufacturers or importers may provide test results on-line. Seven small domestic manufacturers supplying play yards to the U.S. market claim to comply with the ASTM voluntary play yard standard. Of the importers, six claim to comply with the ASTM voluntary play yard standard.</P>
        <HD SOURCE="HD2">3. Impact of the Proposal on Small Business</HD>
        <P>Section 104 of the CPSIA requires the CPSC to promulgate standards for durable infant or toddler products, including play yards. The impact of this rulemaking, if finalized, could have a significant impact on several small manufacturers and importers whose play yards are not ASTM-compliant. The impact of the proposed standard on small manufacturers and importers will differ, based on whether their products are already in compliance with the ASTM voluntary play yard standard.</P>
        <P>Of the 10 small domestic manufacturers, seven produce play yards that are certified as compliant by JPMA or claim to be in compliance with the voluntary standard. There will be little or no impact on these firms. The three noncompliant manufacturers may need to modify their product substantially to meet the ASTM standard. The costs associated with these modifications might include product redesign. The redesign could be minor if, for example, the manufacturer needs to use additional or different fabric or mesh. However, the changes could be more significant if a redesign of the product frame is required. The impact of these costs may be mitigated if they are treated as new product expenses and amortized.</P>
        <P>Of the 10 small domestic importers, six import play yards that are certified as compliant by JPMA or claim to be in compliance with the voluntary standard. The four noncompliant importers may need to find an alternative source if their existing supplier does not modify their play yards to comply with the standard. However, the impact of that decision could be mitigated by replacing the noncompliant product with a compliant product made by a different manufacturer. Deciding to import an alternative product would be a reasonable and realistic way to offset any lost revenue.</P>
        <P>Two of the noncompliant importers import products from a specific foreign country. For these entities, finding an alternative supply source may not be an option. However, they could stop importing noncompliant play yards and replace them with other juvenile products.</P>
        <P>The information in this section assumes that three domestic manufacturers and four domestic importers do not comply with the voluntary standard. This may not be the case. We have identified many cases where products that are not certified by JPMA, or do not otherwise claim compliance with the voluntary standard, actually meet the relevant standard. To the extent that this is true, the impact of the proposed rule will be less significant than described.</P>
        <HD SOURCE="HD2">4. Alternatives</HD>
        <P>For the 13 small domestic entities that already comply with the voluntary standard, there are few or no costs associated with the three minor changes being proposed. For the seven small domestic entities that are not compliant (or where it is unknown if they are compliant) the adoption of the voluntary standard as a mandatory consumer product safety standard could result in substantial costs.</P>
        <P>For these entities, setting an effective date longer than 6 months could reduce the impact. This would allow small manufacturers additional time to make necessary changes to their product, and it would allow small importers to find alternative sources. It would also allow entities to spread costs over a longer period of time.</P>
        <HD SOURCE="HD2">5. Conclusion of Initial Regulatory Flexibility Analysis</HD>
        <P>It is possible that the proposed standard, if finalized, could have a significant impact on some small businesses whose play yards are not ASTM-compliant. The extent of these costs is unknown. For manufacturers of noncompliant play yards, product redesign might be necessary, and it is possible that the costs could be large for some entities. Importers may need to find alternative sources of play yards. Additionally, all manufacturers and importers will eventually be subject to third party testing and certification requirements, as discussed in section L below.</P>
        <P>We invite comments describing the possible impact of this rule on manufacturers and importers, as well as comments containing other information describing how this rule will affect small businesses.</P>
        <HD SOURCE="HD1">I. Environmental Considerations</HD>
        <P>The Commission's regulations address whether we are required to prepare an environmental assessment or an environmental impact statement. If our rule has  “little or no potential for affecting the human environment” it will be categorically exempted from this requirement. 16 CFR 1021.5(c)(1). The proposed rule falls within the categorical exemption.</P>
        <HD SOURCE="HD1">J. Paperwork Reduction Act</HD>

        <P>This proposed rule contains information collection requirements that are subject to public comment and<PRTPAGE P="58174"/>review by the Office of Management and Budget (“OMB”) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3521). In this document, pursuant to 44 U.S.C. 3507(a)(1)(D), we set forth:</P>
        <P>• A title for the collection of information;</P>
        <P>• A summary of the collection of information;</P>
        <P>• A brief description of the need for the information and the proposed use of the information;</P>
        <P>• A description of the likely respondents and proposed frequency of response to the collection of information;</P>
        <P>• An estimate of the burden that shall result from the collection of information; and</P>
        <P>• Notice that comments may be submitted to the OMB.</P>
        <P>
          <E T="03">Title:</E>Safety Standard for Play Yards.</P>
        <P>
          <E T="03">Description:</E>The proposed rule would require each play yard to comply with ASTM F 406-11, Standard Consumer Safety Specification for Non-Full-Size Baby Cribs/Play Yards. Sections 9 and 10 of ASTM F 406-11 contain requirements for marking, labeling, and instructional literature. These requirements fall within the definition of “collection of information,” as defined in 44 U.S.C. 3502(3).</P>
        <P>
          <E T="03">Description of Respondents:</E>Persons who manufacture or import play yards.</P>
        <P>
          <E T="03">Estimated Burden:</E>We estimate the burden of this collection of information as follows:</P>
        <GPOTABLE CDEF="s50,12C,12C,12C,12C,12C" COLS="6" OPTS="L2,i1">
          <TTITLE>Table 1—Estimated Annual Reporting Burden</TTITLE>
          <BOXHD>
            <CHED H="1">16 CFR Section</CHED>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Frequency of<LI>responses</LI>
            </CHED>
            <CHED H="1">Total annual responses</CHED>
            <CHED H="1">Hours per<LI>response</LI>
            </CHED>
            <CHED H="1">Total<LI>burden hours</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">1221.2(a)</ENT>
            <ENT>9</ENT>
            <ENT>3</ENT>
            <ENT>27</ENT>
            <ENT>1</ENT>
            <ENT>27</ENT>
          </ROW>
        </GPOTABLE>
        <P>
          <E T="03">Our estimates are based on the following:</E>
        </P>
        <P>Section 9.1.1.1 of ASTM F 406-11 requires that the name and the place of business (city, state, mailing address, including zip code, or telephone number) of the manufacturer, distributor, or seller be marked clearly and legibly on each product and its retail package. Section 9.1.1.2 of ASTM F 406-11 requires a code mark or other means that identifies the date (month and year, as a minimum) of manufacture.</P>
        <P>There are 23 known entities supplying play yards to the U.S. market. Fourteen entities produce labels that comply with the standard. Thus, there would be no additional burden on these entities. Under the OMB's regulations (5 CFR 1320.3(b)(2)), the time, effort, and financial resources necessary to comply with a collection of information that would be incurred by persons in the “normal course of their activities” are excluded from a burden estimate, where an agency demonstrates that the disclosure activities required to comply are “usual and customary.” Therefore, because these 14 entities already produce labels that comply with the standard, we tentatively estimate that there are no burden hours associated with Sections 9.1.1.1 and 9.1.1.2 of ASTM F 406-11 because any burden associated with supplying these labels would be “usual and customary” and not within the definition of “burden” under the OMB's regulations.</P>
        <P>We assume that the remaining nine entities use labels on their products and their packaging but might need to modify their existing labels. The estimated time required to make these modifications is about 1 hour per model. Each entity supplies an average of three different models of play yards; therefore, the estimated burden hours associated with labels is 1 hour per model × 9 entities × 3 models per entity = 27 hours.</P>

        <P>We estimate that the hourly compensation for the time required to create and update labels is $27.98. This is based on data from March 2011, provided by the U.S. Bureau of Labor Statistics. The information is available at:<E T="03">http://www.bls.gov/news.release/pdf/ecec/pdf</E>in Table 9, under the heading “all workers, goods-producing industries” and the subheading “sales and office.” Therefore, the estimated annual cost to industry associated with the proposed labeling requirements is $755.46 ($27.98 per hour × 27 hours = $755.46).</P>
        <P>Section 10.1 of ASTM F 406-11 requires instructions to be supplied with the product. Play yards are products that generally require assembly, and products sold without such information would not be able to compete successfully with products supplying this information. Under the OMB's regulations (5 CFR 1320.3(b)(2)), the time, effort, and financial resources necessary to comply with a collection of information that would be incurred by persons in the “normal course of their activities” are excluded from a burden estimate, where an agency demonstrates that the disclosure activities required to comply are “usual and customary.” Therefore, because we are unaware of play yards that generally require some installation, but lack any instructions to the user about such installation, we tentatively estimate that there are no burden hours associated with section 10.1 of ASTM F 406-11 because any burden associated with supplying instructions with play yards would be “usual and customary” and not within the definition of “burden” under the OMB's regulations.</P>
        <P>Based on this analysis, the proposed standard for play yards would impose a burden to industry of 27 hours at a cost of $755.46 annually.</P>

        <P>In compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)), we have submitted the information collection requirements of this rule to the OMB for review. Interested persons are requested to submit comments regarding information collection by October 20, 2011, to the Office of Information and Regulatory Affairs, OMB (see the<E T="02">ADDRESSES</E>section at the beginning of this notice).</P>
        <P>Pursuant to 44 U.S.C. 3506(c)(2)(A), we invite comments on:</P>
        <P>• Whether the collection of information is necessary for the proper performance of the CPSC's functions, including whether the information will have practical utility;</P>
        <P>• The accuracy of the CPSC's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>• Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
        <P>• Ways to reduce the burden of the collection of information on respondents, including the use of automated collection techniques, when appropriate, and other forms of information technology; and</P>
        <P>• the estimated burden hours associated with label modification, including any alternative estimates.</P>
        <HD SOURCE="HD1">K. Preemption</HD>

        <P>Section 26(a) of the CPSA, 15 U.S.C. 2075(a), provides that where a consumer product safety standard is in effect and applies to a product, no state or political subdivision of a state may either<PRTPAGE P="58175"/>establish or continue in effect a requirement dealing with the same risk of injury unless the state requirement is identical to the federal standard. Section 26(c) of the CPSA also provides that states or political subdivisions of states may apply to the Commission for an exemption from this preemption under certain circumstances. Section 104(b) of the CPSIA refers to the rules to be issued under that section as “consumer product safety rules,” thus implying that the preemptive effect of section 26(a) of the CPSA would apply. Therefore, a rule issued under section 104 of the CPSIA will invoke the preemptive effect of section 26(a) of the CPSA when it becomes effective.</P>
        <HD SOURCE="HD1">L. Certification</HD>
        <P>Section 14(a) of the CPSA imposes the requirement that products subject to a consumer product safety rule under the CPSA, or to a similar rule, ban, standard, or regulation under any other act enforced by the Commission, must be certified as complying with all applicable CPSC-enforced requirements. 15 U.S.C. 2063(a). Such certification must be based on a test of each product or on a reasonable testing program or, for children's products, on tests on a sufficient number of samples by a third party conformity assessment body accredited by the Commission to test according to the applicable requirements. As discussed in section A of this preamble, section 104(b)(1)(B) of the CPSIA refers to standards issued under this section as “consumer product safety standards.” Similarly, such standards also would be subject to section 14 of the CPSA. Therefore, any such standard would be considered a “consumer product safety rule” to which products subject to the rule must be certified.</P>
        <P>Because play yards are children's products, they must be tested by a third party conformity assessment body whose accreditation is accepted by the Commission. In the future, the Commission will issue a notice of requirements to explain how laboratories can become accredited as third party conformity assessment bodies to test play yards to the new safety standard. (Play yards also must comply with all other applicable CPSC requirements, such as the lead content and phthalate content requirements in section 101 and 108 of CPSIA respectively; the tracking label requirement in section 14(a)(5) of the CPSA; and the consumer registration form requirements in section 104 of the CPSIA.)</P>
        <HD SOURCE="HD1">M. Request for Comments</HD>

        <P>This proposed rule begins a rulemaking proceeding under section 104(b) of the CPSIA to issue a consumer product safety standard for play yards. We invite all interested persons to submit comments on any aspect of the proposed rule. Comments should be submitted in accordance with the instructions in the<E T="02">ADDRESSES</E>section at the beginning of this notice.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 16 CFR Part 1221</HD>
          <P>Consumer protection, Imports, Incorporation by reference, Infants and Children, Labeling, Law enforcement, and Toys.</P>
        </LSTSUB>
        
        <P>Therefore, the Commission proposes to amend Title 16 of the Code of Federal Regulations by adding a new part 1221 to read as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 1221—SAFETY STANDARD FOR PLAY YARDS</HD>
          <CONTENTS>
            <SECHD>Sec.</SECHD>
            <SECTNO>1221.1</SECTNO>
            <SUBJECT>Scope.</SUBJECT>
            <SECTNO>1221.2</SECTNO>
            <SUBJECT>Requirements for play yards.</SUBJECT>
          </CONTENTS>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>The Consumer Product Safety Improvement Act of 2008, Pub. L. 110-314, § 104, 122 Stat. 3016 (August 14, 2008).</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 1221.1</SECTNO>
            <SUBJECT>Scope.</SUBJECT>
            <P>This part establishes a consumer product safety standard for play yards.</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 1221.2</SECTNO>
            <SUBJECT>Requirements for Play Yards.</SUBJECT>

            <P>(a) Except as provided in paragraph (b) of this section, each play yard must comply with all applicable provisions of ASTM F 406-11, Standard Consumer Safety Specification for Non-Full-Size Baby Cribs/Play Yards, approved on May 15, 2011. The Director of the Federal Register approves this incorporation by reference in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. You may obtain a copy from ASTM International, 100 Bar Harbor Drive, P.O. Box 0700, West Conshohocken, PA 19428;<E T="03">http://www.astm.org/cpsc.htm.</E>You may inspect a copy at the Office of the Secretary, U.S. Consumer Product Safety Commission, Room 502, 4330 East West Highway, Bethesda, MD 20814, telephone 301-504-7923, or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal regulations/ibr_locations.html.</E>
            </P>
            <P>(b) Comply with the ASTM F 406-11 standard with the following additions or exclusions:</P>
            <P>(1) Do not comply with section 5.17 of ASTM F 406-11.</P>
            <P>(2) Do not comply with section 5.19 of ASTM F 406-11.</P>
            <P>(3) Do not comply with section 5.20 of ASTM F 406-11.</P>
            <P>(4) Do not comply with section 6, Performance Requirements for Rigid Sided Products, of ASTM F 406-11, in its entirety.</P>
            <P>(5) Do not comply with sections 8.1 through 8.10.5 of ASTM F 406-11.</P>
            <P>(6) Instead of complying with section 8.12.1 of ASTM F 406-11, comply with the following:</P>
            <P>(i) 8.12.1<E T="03">Equipment</E>- 2 Wood blocks, 6 by 6 in. (150 by 150 mm).</P>
            <P>(7) Instead of complying with section 8.12.2.1 of ASTM F 406-11, comply with the following:</P>
            <P>(i) 8.12.2.1 Remove cushions that are not part of the floor or mattress support. Place the wood blocks 6 +/−<FR>1/2</FR>inch (150 mm +/− 13 mm) apart. Place 50-lb (23-kg) weight on one wood block and a 30- lb (24 kg) weight on the other wood block. Maintain for 60 s. Perform the test in those locations deemed to be the weakest or the most likely to fail. Remove the load and check for structural failure.</P>
            <P>(8) Instead of complying with section 8.30.3.1 of ASTM F 406-11, comply with the following:</P>
            <P>(i) 8.30.3.1 Mount a rigid and substantially horizontal moment arm weighing less than 5 lb (2.2 kg) to the hinge/latching device at the longitudinal center of the top rail through two clamping surfaces, each 1 in<SU>2</SU>-4 in<SU>2</SU>(6.5 cm<SU>2</SU>-26 cm<SU>2</SU>) designed to firmly grasp the hinge latching device. The moment arm shall be at least 24 in (603 mm) long and extend towards the outside of the play yard.</P>
            <P>(9) Instead of complying with section 9.4.2.10 of ASTM F 406-11, comply with only the following:</P>
            <P>(i) 9.4.2.10 For products that have a separate mattress that is not permanently fixed in place:</P>
            <P>Use ONLY mattress/pad provided by manufacturer.</P>
            <P>(10) Do not comply with section 10.1.1.1 of ASTM F 406-11.</P>
          </SECTION>
          <SIG>
            <DATED>Dated: September 15, 2011.</DATED>
            <NAME>Todd A. Stevenson,</NAME>
            <TITLE>Secretary, Consumer Product Safety Commission.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24101 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6355-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="58176"/>
        <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
        <CFR>17 CFR Part 23</CFR>
        <RIN>RIN 3038-AC96; 3038-AC97</RIN>
        <SUBJECT>Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements Under Section 4s of the CEA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Commodity Futures Trading Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Further notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Commodity Futures Trading Commission (Commission or CFTC) is proposing regulations that would establish a schedule to phase in compliance with previously proposed requirements, including the swap trading relationship documentation requirement under proposed 17 CFR 23.504, 76 FR 6715 (Feb. 8, 2011) and the margin requirements for uncleared swaps under proposed 17 CFR 23.150 through 23.158, 76 FR 23732 (Apr. 28, 2011). This release is a continuation of those rulemakings. The proposed schedules would provide relief in the form of additional time for compliance with these requirements. This relief is intended to facilitate the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions. The Commission is requesting comment on the proposed compliance schedules, §§ 23.175 and 23.575, described in this release.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before November 4, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>For comments on proposed compliance schedule § 23.175, you may submit comments identified by RIN number 3038-AC97 and Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements under Section 4s of the Commodity Exchange Act (CEA). For comments on proposed compliance schedule § 23.575, you may submit comments identified by RIN number 3038-AC96 and Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements under Section 4s of the CEA. Comments may be submitted by any of the following methods:</P>
          <P>• Agency Web site, via its Comments Online process at<E T="03">http://comments.cftc.gov.</E>Follow the instructions for submitting comments through the Web site.</P>
          <P>•<E T="03">Mail:</E>David A. Stawick, Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street, NW., Washington, DC 20581.</P>
          <P>•<E T="03">Hand Delivery/Courier:</E>Same as mail above.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>Please submit your comments using only one method.</P>

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

          <P>The Commission reserves the right, but shall have no obligation, to review, pre-screen, filter, redact, refuse or remove any or all of your submission from<E T="03">http://www.cftc.gov</E>that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the rulemaking will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other applicable laws, and may be accessible under the Freedom of Information Act.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mark D. Higgins, Counsel, Office of the General Counsel, 202-418-5864,<E T="03">mhiggins@cftc.gov;</E>or Camden Nunery, Office of the Chief Economist,<E T="03">cnunnery@cftc.gov,</E>202-418-5723, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street, NW., Washington, DC 20581.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On July 21, 2010, President Obama signed the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act).<SU>1</SU>
          <FTREF/>Title VII of the Dodd-Frank Act amends the CEA<SU>2</SU>
          <FTREF/>to establish a comprehensive new regulatory framework for swaps. The legislation was enacted to reduce risk, increase transparency, and promote market integrity within the financial system by, among other things: (1) Providing for the registration and comprehensive regulation of swap dealers and major swap participants; (2) imposing clearing and trade execution requirements on standardized derivative products; (3) creating robust recordkeeping and real-time reporting regimes; and (4) enhancing the rulemaking and enforcement authorities of the Commission with respect to, among others, all registered entities and intermediaries subject to the Commission's oversight.</P>
        <FTNT>
          <P>
            <SU>1</SU>
            <E T="03">See</E>Dodd-Frank Wall Street Reform and Consumer Protection Act, Public Law 111-203, 124 Stat. 1376 (2010).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>7 U.S.C. 1<E T="03">et seq.</E>
          </P>
        </FTNT>

        <P>To implement the Dodd-Frank Act, the Commission has to-date issued 55 advance notices of proposed rulemaking or notices of proposed rulemaking, two interim final rules, 12 final rules, and one proposed interpretive order. By the beginning of May 2011, the Commission had published in the<E T="04">Federal Register</E>a significant number of notices of proposed rulemaking, which represented a substantially complete mosaic of the Commission's proposed regulatory framework under Title VII. In recognition of that fact and with the goal of giving market participants additional time to comment on the proposed new regulatory framework for swaps, either in part or as a whole, the Commission reopened or extended the comment period of many of its proposed rulemakings through June 3, 2011.<SU>3</SU>
          <FTREF/>In total, the Commission has received over 20,000 comments in response to its Dodd-Frank Act rulemaking proposals.</P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See</E>Reopening and Extension of Comment Periods for Rulemakings Implementing the Dodd-Frank Wall Street Reform and Consumer Protection Act, 76 FR 25274, May 4, 2011.</P>
        </FTNT>
        <P>To give the public an opportunity to comment further on implementation phasing, on May 2-3, 2011, the Commission, along with the Securities and Exchange Commission (SEC), held a joint, two-day roundtable on issues related to implementation.<SU>4</SU>
          <FTREF/>In connection with this roundtable, Commission staff proposed thirteen concepts to be considered regarding implementation phasing, and staff asked a series of questions based on the concepts outlined.<SU>5</SU>

          <FTREF/>The Commission has received numerous comments in<PRTPAGE P="58177"/>response to both its roundtable and the staff concepts and questions.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>The transcripts from the roundtable are<E T="03">available at http://www.cftc.gov/ucm/groups/public/@newsroom/documents/file/csjac_transcript050311.pdf</E>(“Day 1 Roundtable Tr.”) and<E T="03">http://www.cftc.gov/ucm/groups/public/@newsroom/documents/file/csjac_transcript050211.pdf</E>(“Day 2 Roundtable Tr.”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">See</E>“CFTC Staff Concepts and Questions Regarding Phased Implementation of Effective Dates for Final Dodd-Frank Rules,”<E T="03">available at http://cftc.gov/ucm/groups/public/@newsroom/documents/file/staffconcepts050211.pdf.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>Such comments are<E T="03">available at http://comments.cftc.gov/PublicComments/CommentList.aspx?id=1000.</E>
          </P>
        </FTNT>
        <P>These comments have come from a variety of existing and potential market infrastructures, such as clearinghouses, trading platforms, and swap data repositories. Comments also have come from entities that may potentially be swap dealers (SDs) or major swap participants (MSPs), as well as those financial entities that may not be required to register with the Commission, but whose swap transactions may have to be conducted in compliance with certain requirements under Section 4s of the CEA by virtue of their trading with registered SDs or MSPs. For example, the swap transactions between SDs or MSPs and their counterparties will be subject to certain documentation of trading and margining requirements as proposed by the Commission in “Swap Trading Relationship Documentation Requirements for Swap Dealers and Major Swap Participants,” 76 FR 6715 (Feb. 8, 2011),<SU>7</SU>
          <FTREF/>(hereinafter “Trading Documentation”) and “Margin Requirements for Uncleared Swaps for Swap Dealers and Major Swap Participants,” 76 FR 23732 (Apr. 28, 2011) (hereinafter “Margin Requirements”).<SU>8</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>7</SU>CFTC Docket 3038-AC96.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>CFTC Docket 3038-AC97.</P>
        </FTNT>
        <P>One of the key themes to emerge from the comments received by the Commission is that some market participants may require more time to ensure that their swap transactions comply with certain new regulatory requirements that will apply when they enter into swap transactions with registered SDs and MSPs.<SU>9</SU>
          <FTREF/>For example, one commenter requested a “meaningful” period after finalization of the suite of rulemakings that is applicable to it before actual compliance will be required.<SU>10</SU>
          <FTREF/>Similarly, several trade associations recommended the Commission allow “sufficient” time for infrastructure and business practices to develop before requiring compliance with the new requirements.<SU>11</SU>
          <FTREF/>A group of international banks commented that the Commission should defer compliance until December 31, 2012, at which point the regulatory timetable as per the September 2009 G20 Pittsburgh statement will have reached a conclusion.<SU>12</SU>
          <FTREF/>Another commenter noted that some entities may be able to comply relatively quickly with certain documentation requirements that are largely consistent with current business practices while other requirements may need a longer implementation period.<SU>13</SU>
          <FTREF/>Although commenters varied in their recommendations regarding the time it would take to bring their swaps into compliance with the new regulatory requirements, many commenters agreed on phasing in compliance with these requirements by type of market participant based on a variety of factors, including a market participant's experience, resources, and the size and complexity of its transactions.<SU>14</SU>
          <FTREF/>The Commission has taken these comments into consideration in developing these proposed compliance schedules.</P>
        <FTNT>
          <P>
            <SU>9</SU>E.g., Letter from Electric Trade Association, dated May 4, 2011 at 5; Letter from John R. Gidman, Association of Institutional Investors, dated June 10, 2011 at 3-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>Letter from the Coalition of Physical Energy Companies, dated Mar. 14, 2011 at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>Letter from the Futures Industry Association, the Financial Services Forum, the International Swaps and Derivatives Association and the Securities Industry and Financial Markets Association, dated May 4, 2011 at 5.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>Letter from the Bank of Tokyo-Mitsubishi UFJ, Ltd., et al., dated May 6, 2011 at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>Letter from the Financial Services Roundtable, dated May 12, 2011 at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>14</SU>These comments are more fully discussed later in the preamble.</P>
        </FTNT>
        <P>The swap transaction compliance requirements that are the focus of this proposed rulemaking include compliance with certain provisions of the Trading Documentation and Margin Requirements under Section 4s of the CEA.<SU>15</SU>
          <FTREF/>The Commission's proposed compliance schedules are designed to afford affected market participants a reasonable amount of time to bring their transactions into compliance with such requirements. The proposed schedules also would provide relief in the form of additional time for compliance with these transaction compliance requirements and are further explained below. This relief is intended to facilitate the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions.</P>
        <FTNT>
          <P>
            <SU>15</SU>The Commission also is proposing Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA.</P>
        </FTNT>
        <P>Under this further notice of proposed rulemaking, the Commission is seeking additional public comment on proposed compliance schedules that ultimately would be included in final rules regarding Trading Documentation and Margin Requirements.<SU>16</SU>

          <FTREF/>The proposed schedules would be finalized and become effective at such time as the final Trading Documentation and Margin Requirement rules were published in the<E T="04">Federal Register</E>.</P>
        <FTNT>
          <P>
            <SU>16</SU>This release should be considered to be a continuation of the rulemaking undertaken by CFTC Dockets 3038-AC96 and 3038-AC97. Only comments pertaining to the proposed compliance schedule will be considered as part of this Further Notice.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Proposed Regulation</HD>
        <HD SOURCE="HD2">A. Authority To Implement Proposed Regulations</HD>
        <P>In this further notice of proposed rulemaking, the Commission relies on its general authority to phase in compliance with the rules and regulations enacted pursuant to the Dodd-Frank Act. Section 712(f) of Title VII also authorizes the Commission to promulgate rules to prepare for the effective dates of the provisions of the Dodd-Frank Act.<SU>17</SU>
          <FTREF/>In addition, the Commission relies on Section 8(a)(5) of the CEA, which authorizes the Commission to promulgate such regulations as, in the judgment of the Commission, are reasonably necessary to effectuate any of the provisions or to accomplish any of the purposes of the CEA. In accordance with this authority, the proposed regulations would amend part 23 of the Commission's regulations to phase compliance with previously proposed rules related to Trading Documentation and Margin Requirements under Section 4s of the CEA.</P>
        <FTNT>
          <P>
            <SU>17</SU>Section 712(f) of the Dodd-Frank Act states: “Beginning on the date of enactment of this Act and notwithstanding the effective date of any provision of this Act, the [Commission] * * * may, in order to prepare for the effective dates of the provisions of this Act—(1) promulgate rules, regulations, or orders permitted or required by this Act * * *.”</P>
        </FTNT>
        <HD SOURCE="HD2">B. Implementation Phasing of Trading Documentation Under Section 4s(i) of the CEA</HD>
        <HD SOURCE="HD3">1. Background on the Trading Documentation Requirement</HD>
        <P>Section 731 of the Dodd-Frank Act added a new Section 4s(i)(2) to the CEA that requires the Commission to adopt rules governing documentation standards for SDs and MSPs. As described in Section 4s(i)(1), these documentation standards, as prescribed by the Commission, “relate to the timely and accurate confirmation, processing, netting, documentation, and valuation of all swaps.” On January 13, 2011, the Commission proposed regulations related to the Trading Documentation that SDs and MSPs must enter into with their counterparties in order to establish a swap trading relationship and document the swap transactions that occur pursuant to that relationship.<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">See</E>Swap Trading Relationship Documentation Requirements for Swap Dealers and Major Swap Participants, 76 FR 6715, Feb. 8, 2011.</P>
        </FTNT>
        <PRTPAGE P="58178"/>
        <P>Specifically, previously proposed § 23.504(a) would require SDs and MSPs to establish, maintain, and enforce written policies and procedures designed to ensure that each SD or MSP and its counterparty agree in writing to all terms of their swap trading relationship and have executed all agreements required by the rules.<SU>19</SU>
          <FTREF/>The proposal also would address the essential documentation needed to establish a trading relationship with a registered SD or MSP. Proposed § 23.504(b)(1) would require that the trading documentation include written agreement by the parties on terms relating to payment obligations, netting of payments, events of default or other termination events, netting of obligations upon termination, transfer of rights and obligations, governing law, valuation, and dispute resolution procedures.<SU>20</SU>
          <FTREF/>Proposed § 23.504(b)(2) would establish that all confirmations of swap transactions, as required under proposed § 23.501, would be considered to be part of the required swap trading relationship documents.<SU>21</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>76 FR at 6725.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>76 FR at 6726. In large part, proposed § 23.504(b)(1) reflects existing trading relationship documentation between counterparties, such as the widely-used ISDA Master Agreement, but does propose additional documentation requirements.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>76 FR at 6717 and 6726. In particular, under proposed § 23.504(b)(2) parties must document the confirmation of their swap transactions. The Commission proposed the timing requirements for confirmation under § 23.501 in Confirmation, Portfolio Reconciliation, and Portfolio Compression Requirements for Swap Dealers and Major Swap Participants, 75 FR 81519, Dec. 28, 2010. However, the writing necessary for confirmation is required pursuant to § 23.504(b)(2) and was proposed under the Trading Documentation rules.</P>
        </FTNT>
        <P>Proposed § 23.504(b)(3) would require that the trading documentation include documentation of the credit support arrangements between the counterparties. These arrangements would include the counterparties' agreement on initial and variation margin requirements,<SU>22</SU>
          <FTREF/>the types of assets that may be used as margin, and the investment and rehypothecation terms for those assets. The proposal also would include the custodial arrangements for margin assets, including whether margin assets are to be segregated with an independent third party in accordance with Section 4s(l) of the CEA.<SU>23</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>22</SU>
            <E T="03">See</E>section II.C below for further discussion of Margin Requirements. Proposed § 23.504(b)(3)(i)-(iii) is intended to work together with, and serve as a cross-reference to, rules proposed by the Commission in its Margin Requirements proposal, § 23.151 (76 FR at 23744), as well as rules proposed by the prudential regulators related to initial and variation margin requirements for SDs and MSPs that are banks.<E T="03">See</E>Margin and Capital Requirements for Covered Swap Entities, 76 FR 27564, 27589, May 11, 2011 (proposing § _.5 relating to documentation of margin matters). While proposed § 23.504 would apply to all SDs and MSPs registered with the Commission, the specific initial and variation margin requirements for SDs or MSPs would depend on whether the entity has a prudential regulator as that term is defined under Section 1a(39) of the CEA.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>As explained in the preamble to the Trading Documentation proposal, proposed § 23.504(b)(3)(iii) and (iv) are intended to work together with rules proposed under section 4s(l) of the CEA. 76 FR at 6718 (citing Protection of Collateral of Counterparties to Uncleared Swaps; Treatment of Securities in a Portfolio Margining Account in a Commodity Broker Bankruptcy, 75 FR 75432, Dec. 3, 2010). Accordingly, documentation of the collateral arrangements required under proposed § 23.601-603 would be included in the trading documentation required under § 23.504. Previously proposed § 23.601 requires that the SD and MSP notify each counterparty of the counterparty's right to elect for segregation of the collateral it supplies as initial margin. Previously proposed § 23.602 sets forth requirements for the treatment of segregated margin, including the use of an independent custodian and the requirement for a written agreement that includes the custodian as a party, and also allows for the SD or MSP to agree in writing with its counterparty that variation margin may also be held in a segregated account. Previously proposed § 23.603 relates to the investment and use of collateral.</P>
        </FTNT>
        <P>Proposed § 23.504(b)(4) would require that a SD or MSP and its counterparty agree on how they will value each swap transaction into which they enter from the point of execution until the termination, maturity, or expiration of the swap.<SU>24</SU>
          <FTREF/>Proposed § 23.504(b)(6) would establish certain documentation requirements for bilaterally-executed swaps that are subsequently submitted for clearing to a DCO. Finally, proposed § 23.504(b)(5), the subject of a separate notice of proposed rulemaking,<SU>25</SU>
          <FTREF/>would require that a SD or MSP and its counterparty include in their Trading Documentation “a provision that confirms both parties' understanding of how the new orderly liquidation authority under the Title II of the Dodd-Frank Act and the Federal Deposit Insurance Act may affect their portfolios of uncleared, bilateral swaps.”<SU>26</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>24</SU>76 FR at 6719. The valuation that would be established under § 23.504(b)(4) is relied upon in the Margin Requirements rule § 23.156(b)(1) as the basis for calculating variation margin. Similar valuation provisions also were included by the prudential regulators in their Margin and Capital Requirements proposal.<E T="03">See</E>76 FR 27589.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>25</SU>Orderly Liquidation Termination Provision in Swap Trading Relationship Documentation for Swap Dealers and Major Swap Participants, 76 FR 6708, Feb. 8, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>76 FR at 6709.</P>
        </FTNT>
        <P>The audit, recordkeeping, and reporting provisions of proposed § 23.504(c), (d), and (e) that were proposed by the Commission at the same time as proposed § 23.504(a) and (b) would not be subject to the compliance schedule proposed below because the Commission believes that compliance with those requirements rests solely with registered SDs and MSPs and would not require that SDs or MSPs work with their non-registrant counterparties to comply with these requirements.<SU>27</SU>
          <FTREF/>The Commission solicits comment on whether the compliance schedule should be applied to these provisions as well. The Commission also solicits comment regarding whether the compliance schedule should be applied to proposed § 23.505, which relates to end-user exception documentation.</P>
        <FTNT>
          <P>
            <SU>27</SU>While the compliance schedule proposed in this release would not apply to these provisions, the compliance dates for SDs and MSPs to come into compliance with these provisions will be taken up when the Commission adopts final rules.</P>
        </FTNT>
        <P>The Commission observes that before swap dealers and major swap participants could be required to comply with § 23.504, the Commission must adopt final rules related to confirmation of swap transactions<SU>28</SU>
          <FTREF/>and the protection of collateral for uncleared swaps.<SU>29</SU>
          <FTREF/>This is because the substance of the required documentation under proposed § 23.504 is found in those two rulemakings. For this reason, the Commission anticipates that it will finalize the confirmation and protection of collateral proposals at approximately the same time that it finalizes the Trading Documentation rule. Consequently, the compliance schedules proposed under this release would not become effective until the Commission finalizes those two proposals in addition to the Trading Documentation rule.<SU>30</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>28</SU>Confirmation, Portfolio Reconciliation, and Portfolio Compression Requirements for Swap Dealers and Major Swap Participants, 75 FR 81519, Dec. 28, 2010. The Commission notes that rules related to portfolio reconciliation (§ 23.502) and portfolio compression (§ 23.503) were not cross-referenced in the Trading Documentation rule and would not be required to be included in the counterparties' primary trading relationship documentation. However, if the Commission finalizes those requirements at the same time as the Trading Documentation rule parties may, in their discretion, include documentation establishing compliance with such provisions in their primary documentation, if applicable.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>29</SU>Protection of Collateral of Counterparties to Uncleared Swaps; Treatment of Securities in a Portfolio Margining Account in a Commodity Broker Bankruptcy, 75 FR 75432, Dec. 3, 2010.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>30</SU>In promulgating final rules regarding the timing of confirmation by SDs, MSPs, and their counterparties, the Commission will ensure that compliance with the final confirmation requirements work together with the compliance schedule as proposed under this release.</P>
        </FTNT>

        <P>In addition, the Commission recognizes that the swap transaction compliance schedules that are the subject of this proposal reference terms such as “swap,” “swap dealer,” and “major swap participant” that are the subject of rulemaking under sections 712(d)(1) and 721(c) of the Dodd-Frank<PRTPAGE P="58179"/>Act.<SU>31</SU>
          <FTREF/>The Commission and the SEC have proposed rules that would further define each of these terms.<SU>32</SU>
          <FTREF/>As such, and in a manner consistent with the temporary relief provided in the Commission's Effective Date Order,<SU>33</SU>
          <FTREF/>the Commission must adopt final rules regarding the further definitions in question prior to requiring compliance with the Trading Documentation rule.</P>
        <FTNT>
          <P>
            <SU>31</SU>Section 712(d)(1) provides: “Notwithstanding any other provision of this title and subsections (b) and (c), the Commodity Futures Trading Commission and the Securities and Exchange Commission, in consultation with the Board of Governors [of the Federal Reserve System], shall further define the terms `swap', `security-based swap', `swap dealer', `security-based swap dealer', `major swap participant', `major security-based swap participant', and `security-based swap agreement' in section 1a(47)(A)(v) of the Commodity Exchange Act (7 U.S.C. 1a(47)(A)(v)) and section 3(a)(78) of the Securities Exchange Act of 1934 (15 U.S.C. 78c(a)(78)).” Section 721(c) provides: “To include transactions and entities that have been structured to evade this subtitle (or an amendment made by this subtitle), the Commodity Futures Trading Commission shall adopt a rule to further define the terms `swap', `swap dealer', `major swap participant', and `eligible contract participant'.”</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>Further Definition of “Swap Dealer,” “Security-Based Swap Dealer,” “Major Swap Participant,” “Major Security-Based Swap Participant,” and “Eligible Contract Participant”; Proposed Rule, 75 FR 80174, Dec. 21, 2010 and Further Definition of “Swap,” “Security-Based Swap,” and “Security-Based Swap Agreement”; Mixed Swaps; Security-Based Swap Agreement Recordkeeping, 76 FR 29818, May 23, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>33</SU>
            <E T="03">See</E>Effective Date for Swap Regulation, 76 FR 42508, Jul. 19, 2011.</P>
        </FTNT>
        <P>Lastly, the Commission must adopt final rules relating to the registration, including procedures for the provisional registration, of SDs and MSPs.<SU>34</SU>
          <FTREF/>The finalization of these rules would enable SDs and MSPs to register with the Commission. As explained in the preamble to the proposed registration rule for SDs and MSPs, the Commission would afford SDs and MSPs an overall phased implementation approach with regard to the specific requirements under Section 4s (the “Section 4s Requirements”).<SU>35</SU>
          <FTREF/>In other words, SDs and MSPs would be able to provisionally register with the Commission and come into compliance with the Section 4s Requirements within the compliance deadlines set forth in the respective final implementing rulemakings.<SU>36</SU>
          <FTREF/>The specific compliance schedules proposed in this release comport with the approach discussed in the proposed registration rules.</P>
        <FTNT>
          <P>
            <SU>34</SU>Registration of Swap Dealers and Major Swap Participants, 75 FR 71379, Nov. 23, 2010.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>35</SU>The Section 4s Requirements include capital and margin, reporting and recordkeeping, daily trading records, business conduct standards, documentation standards, risk management and trading duties, designation of a chief compliance officer, and segregation with regard to uncleared swaps. 75 FR at 71380.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>36</SU>In accordance with the preamble to the Registration proposal, the Commission anticipates finalizing other Section 4s Requirements, such as those rules proposed under Section 4s(e) (capital requirements), Section 4s(f) (reporting and recordkeeping), Section 4s(g) (daily trading records), Section 4s(h) (business conduct standards), Section 4s(j) (duties, including trading, risk management, disclosure of information, conflicts of interest, and antitrust considerations), and Section 4s(k) (designation of a chief compliance officer), and providing for specific compliance deadlines in the respective final implementing rulemakings based on the extensive public comment already received.</P>
        </FTNT>

        <P>Another proposed rule under Section 4s of the CEA indicated that certain requirements could be met through the use of swap trading relationship documentation (<E T="03">e.g.,</E>in the ISDA master agreement). The disclosure and documentation requirements proposed under the “Business Conduct Standards for Swap Dealers and Major Swap Participants With Counterparties” rulemaking<SU>37</SU>
          <FTREF/>could be included in Trading Documentation at the discretion of the SD or MSP and its counterparty. However, there is no express requirement under either the proposed Business Conduct Standards with Counterparties rules or proposed § 23.504 that the proposed disclosure and documentation requirements be included in the Trading Documentation. For that reason, issues related to compliance dates for the Business Conduct Standards with Counterparties rules will be taken up when finalizing that proposal.</P>
        <FTNT>
          <P>
            <SU>37</SU>75 FR 80638, Dec. 22, 2010.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Compliance Schedule for Documentation Requirements—§ 23.575</HD>
        <P>As stated above, the Commission is proposing a compliance schedule, § 23.575, that is specific to the documentation requirements of proposed § 23.504. Under the proposed compliance schedule in § 23.575, an SD or MSP would be afforded ninety (90), one hundred eighty (180), or two hundred and seventy (270) days to bring its Trading Documentation with its various counterparties into compliance with the requirements of proposed § 23.504, depending on the identity of each such counterparty. The categorization by type of counterparty is discussed further below.</P>
        <P>As a practical matter, in order for SDs and MSPs to comply with the requirements of proposed § 23.504, they will need to work with each of their counterparties, including non-registrants, to review, negotiate, execute, and deliver the documentation required by proposed § 23.504. Because every bilateral swap transaction has two counterparties, if a non-registrant is trading with a registered SD or MSP, the swap transactions entered into by those two parties would be subject to the new regulatory regime established by Section 4s of CEA.<SU>38</SU>
          <FTREF/>For this reason, the Commission is focusing on phasing swap transaction compliance.</P>
        <FTNT>
          <P>
            <SU>38</SU>Recognizing this reality, the Commission previously proposed rules under which SDs and MSPs would have policies and procedures to bring their transactions with all their counterparties into compliance with the requirements of Section 4s(i) of the CEA.</P>
        </FTNT>
        <P>The Commission recognizes that a number of new regulations under Section 4s will apply to swap transactions where the counterparty to an SD or MSP is not registered with the Commission. In such cases, the Commission is affording more time for those transactions to be brought into compliance with the new regulations. Moreover, registered SDs or MSPs may require additional time to bring their transactions into compliance with respect to non-registrant counterparties that have hundreds or thousands of managed accounts, referred to as third-party subaccounts for the purposes of this proposal.</P>
        <P>In many instances, as noted in the proposing release for § 23.504, counterparties already will have in place industry standard documentation in the form of the widely-used ISDA master agreement, definitions, schedules, confirmations, and credit support annex to document their trades. The Commission anticipates that some of this existing documentation will meet some of the requirements of proposed § 23.504. However, it may be necessary for parties to negotiate certain amendments or additional documentation to comply with the new rules. In these instances, and in instances where counterparties have not previously documented their trading relationship and/or individual transactions, the Commission proposes to afford relief in the form of additional time to comply.</P>
        <HD SOURCE="HD2">C. Implementation Phasing of the Margin Documentation Requirements Under Section 4s(e) of the CEA</HD>
        <HD SOURCE="HD3">1. Background on the Margin for Uncleared Swaps Requirements</HD>
        <P>Section 731 of the Dodd-Frank Act added a new Section 4s(e) to the CEA that explicitly requires the Commission to adopt rules establishing margin requirements for all registered SDs and MSPs that are not banks.<SU>39</SU>
          <FTREF/>Under<PRTPAGE P="58180"/>Section 4s(e)(2)(B), the Commission is required to adopt rules for non-bank SDs and MSPs imposing “both initial and variation margin requirements on all swaps that are not cleared by a registered derivatives clearing organization.”</P>
        <FTNT>
          <P>
            <SU>39</SU>Section 4s(e) applies a bifurcated approach that requires each SD and MSP for which there is a prudential regulator to meet margin requirements established by the applicable prudential regulator,<PRTPAGE/>and each SD and MSP for which there is no prudential regulator to comply with Commission's regulations governing margin.</P>
        </FTNT>
        <P>On April 28, 2011, the Commission issued proposed regulations to implement the margin requirements for uncleared swaps for SDs and MSPs for which there is no prudential regulator (referred to as “covered swap entities” or “CSEs” under the proposal).<SU>40</SU>
          <FTREF/>The proposed Margin Requirements recognized that specific margin requirements would vary by the type of counterparty entering into a swap with a CSE. For instance, the proposed rules would not impose any margin requirements on swaps between CSEs and non-financial end users.<SU>41</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>40</SU>Margin Requirements for Uncleared Swaps for Swap Dealers and Major Swap Participants, 75 FR 23732, Apr. 28, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>41</SU>76 FR at 23734.</P>
        </FTNT>
        <P>The provisions of the proposed Margin Requirements include definitions (§ 23.150), documentation regarding credit support arrangements (§ 23.151), the specific margin requirements between CSEs and their counterparties (§§ 23.152-23.154), provisions for the calculation of initial margin (§ 23.155), provisions for the calculation of variation margin (§ 23.156), requirements for the forms of margin (§ 23.157), and custodial arrangement requirements (§ 23.158). Specific margin requirements vary by the type of counterparty with which a CSE is trading—another SD or MSP<SU>42</SU>
          <FTREF/>(§ 23.152), a financial entity (§ 23.153), or a non-financial entity (§ 23.154).</P>
        <FTNT>
          <P>
            <SU>42</SU>In some instances this SD or MSP counterparty may be subject to regulation by a prudential regulator. The margin rules proposed by the Commission and those proposed by the prudential authorities require any CSE to collect margin, but do require a CSE to post margin. Under this approach, a non-bank SD or MSP will look to the Commission's rules when calculating the margin that should be collected from its counterparty, and a bank SD or MSP will look to the prudential regulators' rules when calculating the margin that should be collected from its counterparty. As a result, in a trade between a bank SD and a non-bank SD, the initial margin amounts collected by each side could differ depending on the applicable rules.</P>
        </FTNT>

        <P>As explained above with regard to the Trading Documentation rules, the Commission observes that no CSE could be required to comply with final Margin Requirements rules until (1) the Commission adopts further definitions of “swap,” “swap dealer,” and “major swap participant”; and (2) the Commission adopts registration rules for SDs and MSPs. As noted above, the proposed Margin Requirements cross-reference certain provisions in the Trading Documentation rule. As a result, the final Trading Documentation rule would have to be published in the<E T="04">Federal Register</E>prior to requiring compliance with the final Margin Requirements.<SU>43</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>43</SU>The Commission's proposed capital rules for SDs and MSPs are related to the proposed Margin Requirements rules, but the margin rules are not dependent on implementation of the capital rule in order to take effect.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Compliance Schedule for Margin Requirements Documentation—§ 23.175</HD>
        <P>In this further notice of proposed rulemaking, the Commission is proposing a compliance schedule, § 23.175, that is specific to the Margin Requirements of proposed § 23.150 through § 23.158. Under the proposed Margin Requirements, an SD or MSP for which there is no prudential regulator, is defined as a “covered swap entity.” For consistency, this term also would be used in the proposed compliance schedule. In order to achieve compliance with the Margin Requirement, a CSE would be required to execute documentation regarding credit support arrangements and custodial arrangements with its counterparties. This documentation, required by proposed § 23.151 and § 23.158, would specify in advance material terms such as how margin would be calculated, what types of assets would be permitted to be posted, what margin thresholds, if any, would apply, and where margin would be held. As stated in the proposal, having comprehensive documentation in place at the time of transaction execution would allow each party to a swap to manage its risks more effectively throughout the life of the swap and to avoid disputes regarding issues such as valuation.<SU>44</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>44</SU>76 FR 23734. As stated in the proposal, margining requirements would also apply to swaps where one side of the trade is not registered with the Commission. 76 FR 23732-36.</P>
        </FTNT>
        <P>Under the proposed compliance schedule, a covered swap entity would be afforded ninety (90), one hundred eighty (180), or two hundred and seventy (270) days (depending on the identity of its counterparty) to come into compliance with all of the Margin Requirements. The categorization by type of counterparty is discussed further below.</P>
        <HD SOURCE="HD2">D. Three-Part Implementation Phasing</HD>
        <P>The Commission believes that it is in the public interest to afford SDs and MSPs over which the Commission has jurisdiction relief in the form of additional time to comply with proposed rules related to Trading Documentation (§ 23.504) and Margin Requirements (§ 23.150-23.158), depending on the type of counterparty with which the SD or MSP is trading.</P>
        <P>These proposed compliance schedules, §§ 23.575 and 23.175, seek to achieve the best balance among several goals. First, the Commission believes that SDs or MSPs may require additional time to work with certain market participants to bring their swaps into compliance with the new requirements of proposed Trading Documentation (§ 23.504) and Margin Requirements (§ 23.150-23.158). This is particularly true for those market participants that have hundreds or thousands of managed accounts, referred to as third-party subaccounts for the purposes of this proposal.</P>
        <P>As one commenter noted, “[i]n the context of asset managers, the account set up process has to be multiplied over hundreds of subaccounts. Processing all of these subaccounts will take time even for the largest and most technologically advanced asset managers.”<SU>45</SU>
          <FTREF/>In light of this, the Commission is proposing to afford SDs and MSPs with additional time to come into compliance with the requirements of Trading Documentation (§ 23.504) and Margin Requirements (§ 23.150-23.158) for swaps involving entities that are defined as “third-party subaccounts” because of the additional burden associated with documenting such accounts.</P>
        <FTNT>
          <P>
            <SU>45</SU>Letter from Karrie McMillan, Investment Company Institute, dated June 10, 2011at 9-10.</P>
        </FTNT>
        <P>Moreover, several commentators emphasized the need to have adequate time to educate their clients regarding the new regulatory requirements.<SU>46</SU>
          <FTREF/>For instance, market participants that may not be registered with the Commission would be less familiar with the new regulatory requirements. In addition, market participants with third-party subaccounts would have to educate additional clients. Accordingly, swaps involving either type of participant should be given additional time to comply with the new requirements.</P>
        <FTNT>
          <P>
            <SU>46</SU>
            <E T="03">See</E>Letter from Financial Services Forum, Futures Industry Association, International Swaps and Derivatives Association, and Securities Industry Association, dated May 4, 2011; Letter from Karrie McMillan, Investment Company Institute, dated June 10, 2011 at 10-11.</P>
        </FTNT>

        <P>Another goal of the proposed compliance schedule is derived from the Commission's belief that it is important to have a cross-section of market participants involved at the outset of implementing the requirements under Trading Documentation (§ 23.504) and Margin<PRTPAGE P="58181"/>Requirements (§§ 23.150-23.158). Accordingly, the Commission proposes that the first phase of implementation include SDs, MSPs and “active funds” (a term that is defined and discussed further below) that are experienced, have the resources, and can come into compliance more readily than entities that trade swaps less frequently. The Commission believes that having a cross-section of market participants involved at the outset will facilitate the development of systems necessary for SDs and MSPs to achieve compliance with the new requirements.</P>
        <P>The Commission proposes a compliance schedule that affords additional time for SDs and MSPs to come into compliance with the requirements of Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) based on the type of counterparty with which they are trading. Market participants that are financial entities, as defined in Section 2(h)(7)(C) of the CEA, are grouped into the following four categories:</P>
        <P>• Category 1 Entities include swap dealers, security-based swap dealers, major swap participants, major security-based swap participants, or active funds.</P>

        <P>• Category 2 Entities include commodity pools; private funds as defined in Section 202(a) of the Investment Advisors Act of 1940 other than active funds; employee benefit plans identified in paragraphs (3) and (32) of section 3 of the Employee Retirement Income and Security Act of 1974; or persons predominantly engaged in activities that are in the business of banking, or in activities that are financial in nature as defined in Section 4(k) of the Bank Holding Company Act of 1956,<E T="03">provided that</E>the entity is not a third-party subaccount.</P>
        <P>• Category 3 Entities include Category 2 Entities whose positions are held as third-party subaccounts.</P>
        <P>• Category 4 Entities includes any person not included in Categories 1, 2, or 3.</P>
        <HD SOURCE="HD3">Phase 1—Category 1 Entities</HD>
        <P>Category 1 Entities include those dealers and major participants in the swap and security-based swap markets that will be required to register with the Commission or the Securities and Exchange Commission (SEC).<SU>47</SU>
          <FTREF/>Under Title VII, these market participants will be required to register with either the CFTC or SEC as a result of their swaps or security-based swaps activities. Based on their level of market experience, and based on their status as registrants, the Commission believes they should be capable of complying with proposed Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) no later than 90 days from the date of adoption of final rules.</P>
        <FTNT>
          <P>
            <SU>47</SU>If a security-based swap dealer or a major security-based swap participant is not yet required to register with the SEC at such time as the Commission issues final rules § 23.504 or §§ 23.150-23.158, then the security-based swap dealer or a major security-based swap participant would be treated as a Category 2 Entity.</P>
        </FTNT>
        <P>The Commission also is proposing to include those entities it defines as “active funds” in the first category of market participants. The proposed definition of “active fund” would mean any private fund as defined in section 202(a) of the Investment Advisors Act of 1940, that is not a third-party subaccount and that executes 20 or more swaps per month based on a monthly average over the 12 months preceding the publication of either § 23.504 or §§ 23.150-23.158, as applicable.<SU>48</SU>
          <FTREF/>By including these entities in Category 1, the Commission seeks to achieve the goal of ensuring a cross-section of market participants are included at the outset of trading and margining documentation implementation.</P>
        <FTNT>
          <P>
            <SU>48</SU>It should be noted that many commodity pools meet the definition of private fund under section 202(a) of the Investment Advisors Act of 1940. Such a commodity pool would only be a Category 1 Entity if it met the other criteria of an active fund.</P>
        </FTNT>
        <P>The Commission is relying on the definition of private fund from Section 2(h)(7)(C) of the CEA, as well as Section 402 of the Dodd-Frank Act. However, the Commission is limiting the definition in two ways. First, the definition excludes third-party subaccounts, as discussed further below. Second, the definition is limited to those private funds that execute 20 or more swaps per month based on the average over the 12 months preceding either (1) the Commission's adoption of § 23.150 through § 23.158 in the case of § 23.175; or (2) the Commission's adoption of § 23.504 in the case of § 23.575. Based on a preliminary assessment, the Commission believes the proposed numerical threshold for active funds is appropriate because a private fund that conducts this volume of swaps would be likely to have: (1) Sufficient resources to enter into arrangements that comply with the Trading Documentation and Margin Requirements earlier than other types of market participants; and (2) sufficient market experience to contribute meaningfully to the “buy-side” perspective as industry standards are being developed.<SU>49</SU>
          <FTREF/>In defining “active fund” accordingly, the Commission believes it has included those market participants that are likely to be among the most experienced participants with expertise and resources needed to come into transaction compliance quickly.</P>
        <FTNT>
          <P>
            <SU>49</SU>The Commission is unaware of any position-level or transaction-level data on private fund swap activity in a publicly available form. In order to determine private fund activity levels the Commission consulted with academics focusing their research in this area, with industry participants, and with groups that represent the industry.</P>
        </FTNT>
        <HD SOURCE="HD3">Phase 2—Category 2 Entities</HD>
        <P>Next, the Commission proposes to phase in compliance for any swap transaction between an SD or MSP and a Category 2 Entity. The Commission is proposing to afford swap transactions between these types of market participants 180 days from the dates of adoption of Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) to come into compliance. This additional time takes into consideration the fact that Category 2 Entities will not be required to be registered with the Commission and they may be less experienced and less frequent users of the swap markets than those in Category 1. Additionally, these financial entities may not have the same level of resources to review, analyze, negotiate, and enter into arrangements that comply with the new Trading Documentation and Margin Requirements as those in Category 1.</P>
        <HD SOURCE="HD3">Phase 3—Category 3 and 4 Entities</HD>
        <P>Finally, the Commission proposes to afford an SD or MSP trading with a Category 3 or 4 Entity 270 days from adoption of final rules relating to Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) to enter into arrangements that comply with the new rules.</P>

        <P>The Commission is proposing to afford SDs and MSPs with additional time to work with entities that are defined as “third-party subaccounts” to bring their documentation into compliance. Under the proposed definition, a third-party subaccount is a managed account that requires specific approval by the beneficial owner of the account to execute documentation necessary for executing, confirming, margining, or clearing swaps. By way of non-exclusive example, if investment management firm X manages the assets of pension fund Y, and does so in a separate account that requires the approval of pension fund Y to execute necessary documentation, then that account would be afforded 270 days to come into compliance. On the other hand, if pension fund Y manages its own assets, it would fall within<PRTPAGE P="58182"/>Category 2 and be afforded 180 days to come into compliance. Likewise, if investment management firm X does not manage the assets of third parties, then it would fall within Category 2. The Commission is proposing to afford Category 3 an additional 90 days beyond the 180 days proposed for Category 2 because such entities may have documentation obligations for hundreds or even thousands of third-party subaccounts, and each such account must meet the requirements of Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158). For example, according to a statement made during the Joint SEC-CFTC Roundtable by Mr. William DeLeon of the firm Pacific Investment Management Company, LLC (PIMCO), PIMCO manages hundreds of third-party subaccounts, as defined above.<SU>50</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>50</SU>Day-2 Roundtable Tr. at 62.</P>
        </FTNT>
        <P>The Commission is proposing to afford an SD or MSP trading with any other person (defined as a Category 4 Entity) 270 days to enter into arrangements that comply with the new rules.</P>
        <P>The Commission stresses that nothing would prohibit any person from complying in advance of the proposed compliance schedule. Indeed, the Commission would encourage market participants that can come into compliance more quickly to do so.</P>
        <HD SOURCE="HD2">E. Comment Requested</HD>
        <P>The Commission requests comment on all aspects of the proposed compliance schedules, §§ 23.175 and 23.575. The Commission may consider alternatives to the proposed compliance schedules and is requesting comment on the following questions:</P>
        <P>• What, if any, other rules should have been taken into consideration when proposing an implementation schedule regarding margin or documentation requirements? If applicable, how should the implementation requirements of those other rules be taken into consideration?</P>
        <P>• What factors, if any, would prevent an entity in any of the proposed categories from adhering to the compliance schedules proposed by the Commission? How much additional time would be needed to address these factors?</P>
        <P>• Are there other considerations that the Commission should have taken into account when designing this tiered implementation schedule? Are the timeframes outlined in this implementation schedule adequate? If not, what alternative schedule should the Commission consider, and why?</P>
        <P>• What other entities, if any, should be included in Category 1, 2, or 3, and why?</P>
        <P>• What adjustments to the compliance schedule and/or other steps could the Commission take to ensure there is adequate representation from all market participants at the outset of implementing the requirements under Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158)?</P>
        <P>• Is an entity's average monthly swap transaction activity a useful proxy for that entity's ability to comply with the Trading Documentation and Margin Requirements? Or whether an entity is required to be registered with the Commission (rather than whether an entity is already registered with the Commission)?</P>
        <P>• Is the Commission's definition of “active fund” overly inclusive or under-inclusive? Should the numerical threshold for number of monthly swap transactions be higher or lower than 20? If so, why? Should the number of monthly swap transactions be linked to swap activity in a particular asset class?</P>
        <P>• Should the Commission exclude from the definition of “active fund” any investment advisor of private funds acting solely as an advisor to private funds with assets under management in the United States of less than $150,000,000, as provided for in the reporting exemption for private funds under Section 408 of the Dodd-Frank Act?</P>
        <P>• Would it be more appropriate for the Commission to measure a market participant's level of swap activity by measuring notional turnover and/or open exposure as suggested by some commenters?<SU>51</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>51</SU>Letter from Adam C. Cooper, Citadel, dated June 3, 2011, Appendix B.</P>
        </FTNT>
        <P>• Are there any anticompetitive implications to the proposed compliance schedules? If so, how could the proposed rules be implemented to achieve the purposes of the CEA in a less anticompetitive manner? If so, please quantify those costs, if possible, and provide underlying data sources, assumptions, and calculations.</P>
        <P>• Are there additional costs or benefits associated with the current proposal that the Commission has not already taken into account? Please discuss any such costs in detail and quantify in dollar terms, if possible.</P>
        <P>• Are there any assumptions, including quantitative assumptions, underlying the Commission's cost benefit analysis that the Commission should consider?</P>
        <P>• Should the Commission consider an alternative implementation schedule? Would such an alternative schedule reduce the costs market participants will bear? Please describe any such alternative implementation schedule in detail, including how it will reduce costs and the benefits it will likely deliver. If possible, please quantify the cost and benefits associated with any alternative. If providing dollar values, please describe any data sources, assumptions, and calculations used to generate them.</P>
        <P>• Should a compliance schedule such as those proposed herein apply to the disclosure and documentation requirements proposed in the Business Conduct Standards for Counterparties proposal? If so, should the compliance schedule be adjusted, and in what manner?</P>
        <HD SOURCE="HD1">III. Related Matters</HD>
        <HD SOURCE="HD2">A. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act requires that agencies consider whether the rules they propose will have a significant economic impact on a substantial number of small entities and, if so, provide a regulatory flexibility analysis respecting the impact.<SU>52</SU>
          <FTREF/>The rules proposed by the CFTC provide compliance schedules for certain new statutory requirements of the Dodd Frank Act and do not by themselves impose significant new regulatory requirements. Accordingly, the Chairman, on behalf of the CFTC, hereby certifies pursuant to 5 U.S.C. 605(b) that the proposed rules will not have a significant economic impact on a substantial number of small entities. The CFTC invites public comment on this determination.</P>
        <FTNT>
          <P>
            <SU>52</SU>5 U.S.C. 601<E T="03">et seq.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD2">B. Paperwork Reduction Act</HD>
        <P>The Paperwork Reduction Act (“PRA”)<SU>53</SU>
          <FTREF/>imposes certain requirements on Federal agencies (including the Commission) in connection with conducting or sponsoring any collection of information as defined by the PRA. This Further Notice of Proposed Rulemaking, if approved, would not require a new collection of information from any persons or entities.</P>
        <FTNT>
          <P>
            <SU>53</SU>44 U.S.C. 3507(d).</P>
        </FTNT>
        <HD SOURCE="HD2">C. Consideration of Costs and Benefits</HD>
        <P>Section 15(a) of the CEA<SU>54</SU>

          <FTREF/>requires the Commission to consider the costs and benefits of its action before promulgating a regulation under the CEA. Section 15(a) of the CEA specifies<PRTPAGE P="58183"/>that the costs and benefits shall be evaluated in light of five broad areas of market and public concern: (1) Protection of market participants and the public; (2) efficiency, competitiveness and financial integrity of futures markets; (3) price discovery; (4) sound risk management practices; and (5) other public interest considerations. The Commission may in its discretion give greater weight to any one of the five enumerated areas and could in its discretion determine that, notwithstanding its costs, a particular regulation is necessary or appropriate to protect the public interest or to effectuate any of the provisions or accomplish any of the purposes of the Act.</P>
        <FTNT>
          <P>
            <SU>54</SU>7 U.S.C. 19(a).</P>
        </FTNT>
        <P>The purpose of this proposed rule is to afford SDs and MSPs additional time to comply with the Trading Documentation and the Margin Requirements beyond that which is provided for in the Dodd-Frank Act. Section 754 of the Dodd-Frank Act provides that required rulemakings can be considered to be effective 60 days after publication of the final rule or regulation. Without the proposed rule, SDs and MSPs could be required to comply with Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) rules without any implementation phasing of the sort provided for by the proposed compliance schedules.</P>
        <P>The Commission recognizes that requiring immediate compliance with the new requirements could indirectly impose costs on market participants that may not be registered with the Commission and those market participants that have hundreds or thousands of third-party subaccounts to bring into compliance. Accordingly, and in an effort to protect the public interest by facilitating an orderly transition to a new regulatory environment, the Commission's proposed compliance schedules would provide a substantial benefit in that they would afford SDs and MSPs adequate time to modify or create the requisite documentation in collaboration with their counterparties.</P>
        <HD SOURCE="HD3">1. Protection of Market Participants and the Public</HD>
        <P>The Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) rules for which the Commission has proposed compliance schedules would encourage transparency in the swap market by requiring that SDs, MSPs, and their counterparties clarify, in writing, many aspects of their trading relationship prior to entering into a swap, and also that they clarify many specific details related to margining their swaps. The proposed compliance schedules would further the objectives of Sections 4s(e) and 4s(i) of the CEA by establishing an orderly process for their implementation. The proposed compliance schedules have several benefits that contribute to protection of the public as well as market participants.</P>
        <P>It is in the public interest that the largest and most active participants in the swap markets come into compliance with Sections 4s(e) and 4s(i) of the CEA as soon as possible, in order to facilitate an orderly transition to the new regulatory environment for swaps. The proposed compliance schedules would prioritize compliance for Category 1 Entities because these entities are likely responsible for a large portion of the swap transactions occurring in this market. But the schedule would do so in a way that still safeguards the interests of the Category 1 Entities by providing the additional time that these entities need in order to document new trading relationship and margining arrangements required by Sections 4s(e) and 4s(i) of the CEA.</P>
        <P>The additional time provided by the proposed compliance schedules would create several benefits for the SDs, MSPs, and their counterparties. First, if market participants were concerned that they might not be able to meet statutory compliance timelines, it is likely that they would incur additional costs associated with the potential lack of regulatory compliance. Providing additional time for compliance through the proposed compliance schedule would reduce the costs that market participants may incur mitigating risks during the transition period, and would re-direct those resources to achieving compliance with the new rules.</P>
        <P>Second, if Category 2, 3, or 4 Entities want to come into compliance ahead of the timeframes proposed for their SD or MSP counterparties through the compliance schedules, they may work with their SD and MSP counterparties to do so. Category 2, 3, or 4 Entities may wish to achieve compliance earlier in order to achieve the benefits associated with greater clarity in their trading relationships and margin arrangements for non-cleared swaps. They also may wish to take advantage of newly developed template agreements as they develop. Such early compliance by market participants would provide additional protection for the public by decreasing the risks associated with failing to document trading relationships and swap transactions properly, as well as decreasing the risks associated with failing to collateralize the credit exposure posed by uncleared swaps. Additionally, early compliance would have the benefit of increasing clarity about how margin will be handled for non-cleared swaps.</P>
        <P>Category 3 Entities have the additional challenge of transitioning hundreds, and in some cases, thousands of subaccounts into compliance with the new documentation requirements for trading relationships and margining non-cleared swaps. The proposed compliance schedules would afford Category 3 Entities additional time to educate their customers about the new requirements, and then negotiate and formalize new trading and margining agreements between their customers and SDs or MSPs. Each of these tasks requires time. By giving Category 3 Entities and their counterparties 270 days to come into compliance, the Commission is attempting to provide adequate time for these entities to come into compliance without the need for significant additional legal assistance. The Commission also is attempting to avoid the risk of inadequate documentation and inappropriate margining arrangements that may result from a more rushed process. Both of these results would tend to reduce costs and risk for both SDs and MSPs and their Category 3 Entities counterparties.</P>
        <P>As far as costs are concerned, by establishing a 3-month, 6-month, and 9-month compliance schedule for SDs and MSPs to achieve compliance with their counterparties that are Category 1, Category 2, and Category 3 and 4 Entities, respectively, the proposed compliance schedule would delay certain benefits that would result from more timely and accurate documentation by SDs and MSPs, as well as timely compliance with Margin Requirements for non-cleared swaps. Those costs primarily include a delay in decreasing the risks associated with the failure to document trading relationships and swap transactions properly, as well as a delay in terms of decreasing the risks associated with not collateralizing the credit exposure posed by uncleared swaps.</P>

        <P>The proposed compliance schedules seek to balance the cost to SDs, MSPs, and the Category 1 Entities that would be associated with bearing a larger proportion of the “start-up” costs associated with most promptly implementing the Trading Documentation and Margin Requirements. SDs, MSPs, and Category 1 Entities are the entities likely to expend the most resources establishing industry standard agreements that can then be used by other market participants. It is appropriate for the<PRTPAGE P="58184"/>entities that are likely to be among the most active participants in these markets to shoulder a larger percentage of the relatively fixed start-up costs.</P>
        <HD SOURCE="HD3">2. Efficiency, Competitiveness, and Financial Integrity of the Markets</HD>
        <P>The SDs, MSPs, and Category 1 Entities that constitute the first phase under the proposed compliance schedules will be likely to work together to establish methods for compliance that other market participants may later consider. The experience with swaps that the first group of market participants brings to this process should help to ensure the integrity and effectiveness of their solutions. These solutions will likely be helpful to other market participants that comply later. This approach is likely to result in benefits for a broad group of market participants.</P>
        <P>Moreover, it is critical that a cross-section of market participants is involved in developing the solutions that become industry conventions in order to ensure that those approaches promote the efficiency, competitiveness, and integrity of participants on both the buy-side and sell-side. Category 1 includes market participants from both sides, which helps ensure that the interests of both will be represented well as the industry identifies and solves the problems that are necessary for compliance.</P>

        <P>With respect to the activities of Category 1 participants, providing them 90 days to come into compliance after the Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) are published in the<E T="04">Federal Register</E>would create some time and opportunity for industry coordination as multiple participants, representing both the sell-side and buy-side of the market, identify shared questions and work to develop sound answers. This is likely to facilitate better compliance systems and processes, which reduces the start-up costs of implementing new regulations for these and other entities, which is expected to lower costs to the public by promoting standardization.</P>
        <P>Lastly, in the absence of the proposed compliance schedules, some entities have expressed concern that they would be unable to comply with the new requirements and would choose to leave the swap market altogether or avoid the market for some period of time. If this occurred, it could reduce liquidity and might increase spreads in the market. By providing additional time for compliance, this rule reduces the chance that these adverse effects will occur in the swap market and facilitates an orderly transition to the new regulatory environment.</P>
        <P>As for costs related to the efficiency, competitiveness, and financial integrity of the markets, the proposed compliance schedules would allow for delayed compliance dates for new Trading Documentation and Margin Requirements. The schedules would delay the benefits of the new requirements that would come from more expeditious implementation.</P>
        <HD SOURCE="HD3">3. Price Discovery</HD>
        <P>As noted above, the Trading Documentation rule contains a requirement that an SD or MSP and its counterparty agree on how they will value each swap transaction into which they enter from the point of execution until the termination, maturity, or expiration of the swap. Prompt implementation of this requirement would facilitate price discovery between the counterparties to a swap. Delay in implementing this provision may inhibit price discovery to the extent that counterparties fail to value their swaps on a timely and accurate basis. In this way, the proposed rule would delay the benefits of increased price transparency that could flow from a more expeditious implementation of the Trading Documentation rule. Additionally, a disorderly implementation may inhibit price discovery to the extent that counterparties fail to value their swaps on a timely and accurate basis; whereas, an orderly implementation process would promote communication between counterparties, which is essential to price discovery.</P>
        <HD SOURCE="HD3">4. Sound Risk Management Practices</HD>
        <P>To the extent that the proposed compliance schedule would delay implementation of the Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) rules, the swap market could suffer costs in terms of poor risk management resulting from a failure to document trading relationships and swap transactions properly, as well as from failure to collateralize the outstanding credit exposure posed by uncleared swaps through appropriate margining.</P>
        <P>However, there are risk management benefits to be gained from the proposed compliance schedule. For instance, if SDs and MSPs were expected to comply with Trading Documentation (§ 23.504) and Margin Requirements (§§ 23.150-23.158) on timelines that they could not meet, it is possible that some firms may avoid the swap market for a period of time, which could expose them to risks they could have otherwise used swaps to mitigate. Therefore, by providing a timetable for orderly implementation, this rule could encourage continued participation in the swap markets and the continued use of swaps for risk mitigation purposes.</P>
        <HD SOURCE="HD3">5. Other Public Interest Considerations</HD>
        <P>There are public interest benefits to phasing in compliance using the implementation structure proposed in this release. The proposed implementation structure generally allows market participants to comply with the requirements of Dodd-Frank as quickly and efficiently as possible and thereby provides a sound basis for achieving the overarching Dodd-Frank goals of risk reduction and increased market transparency.</P>
        <P>In sum, the Commission has considered the costs and benefits as required by Section 15(a) and is proposing the compliance schedules discussed herein. The Commission invites public comment on its cost-benefit considerations. Commenters are also invited to submit any data or other information that they may have quantifying or qualifying the costs and benefits of the proposal with their comment letters.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 17 CFR Part 23</HD>
          <P>Antitrust, Commodity futures, Conduct standards, Conflicts of interest, Major swap participants, Reporting and recordkeeping, Swap dealers, Swaps.</P>
        </LSTSUB>
        
        <P>For the reasons stated in the preamble, 17 CFR part 23 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 23—SWAP DEALERS AND MAJOR SWAP PARTICIPANTS</HD>
          <P>1. The authority citation for part 23 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 1a, 2, 6, 6a, 6b-1, 6c, 6p, 6r, 6s, 6t, 9, 9a, 12, 12a, 13b, 13c, 16a, 18, 19, 21.</P>
          </AUTH>
          
          <P>2. Add § 23.175 to subpart E to read as follows:</P>
          <SECTION>
            <SECTNO>§ 23.175</SECTNO>
            <SUBJECT>Compliance schedule.</SUBJECT>
            <P>(a)<E T="03">Definitions.</E>For the purposes of this rule:</P>
            <P>
              <E T="03">Active Fund</E>means any private fund as defined in section 202(a) of the Investment Advisors Act of 1940, that is not a third-party subaccount and that executes 20 or more swaps per month based on a monthly average over the 12 months preceding the publication of § 23.150 through § 23.158 in the<E T="04">Federal Register.</E>
            </P>
            <P>
              <E T="03">Category 1 Entity</E>means (1) A swap dealer, (2) a security-based swap dealer; (3) a major swap participant; (4) a major security-based swap participant; or (5) an active fund.<PRTPAGE P="58185"/>
            </P>
            <P>
              <E T="03">Category 2 Entity</E>means (1) A commodity pool; (2) a private fund as defined in section 202(a) of the Investment Advisors Act of 1940 other than an active fund; (3) an employee benefit plan as defined in paragraphs (3) and (32) of section 3 of the Employee Retirement Income and Security Act of 1974; or (4) a person predominantly engaged in activities that are in the business of banking, or in activities that are financial in nature as defined in section 4(k) of the Bank Holding Company Act of 1956,<E T="03">provided that,</E>in each case, the entity is not a third-party subaccount.</P>
            <P>
              <E T="03">Category 3 Entity</E>means a Category 2 Entity whose positions are held as a third-party subaccount.</P>
            <P>
              <E T="03">Category 4 Entity</E>means any person not included in Categories 1, 2, or 3.</P>
            <P>
              <E T="03">Covered swap entity</E>means a swap dealer or major swap participant for which there is no prudential regulator.</P>
            <P>
              <E T="03">Third-party Subaccount</E>means a managed account that requires specific approval by the beneficial owner of the account to execute documentation necessary for executing, confirming, margining, or clearing swaps.</P>
            <P>(b)<E T="03">Compliance Schedule.</E>The following schedule for compliance with the requirements of § 23.150 through § 23.158 shall apply:</P>

            <P>(1) For swap transactions with a Category 1 Entity, a covered swap entity shall comply with the requirements of § 23.150 through § 23.158 no later than ninety (90) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>

            <P>(2) For swap transactions with a Category 2 Entity, a covered swap entity shall comply with the requirements of § 23.150 through § 23.158 no later than one hundred and eighty (180) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>

            <P>(3) For swap transactions with a Category 3 Entity or a Category 4 Entity, a covered swap entity shall comply with the requirements of § 23.150 through § 23.158 no later than two hundred and seventy (270) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>
            <P>(c) Nothing in this rule shall prohibit any person from complying voluntarily with the requirements of § 23.150 through § 23.158 sooner than the compliance schedule provided in paragraph (b).</P>
            <P>3. Add new § 23.575 to part 23, subpart I, to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 23.575</SECTNO>
            <SUBJECT>Compliance schedule.</SUBJECT>
            <P>(a)<E T="03">Definitions.</E>For the purposes of this rule:</P>
            <P>
              <E T="03">Active Fund</E>means any private fund as defined in section 202(a) of the Investment Advisors Act of 1940, that is not a third-party subaccount and that executes 20 or more swaps per month based on a monthly average over the 12 months preceding the publication of § 23.504 in the<E T="04">Federal Register.</E>
            </P>
            <P>
              <E T="03">Category 1 Entity</E>means (1) A swap dealer, (2) a security-based swap dealer; (3) a major swap participant; (4) a major security-based swap participant; or (5) an active fund.</P>
            <P>
              <E T="03">Category 2 Entity</E>means (1) A commodity pool; (2) a private fund as defined in section 202(a) of the Investment Advisors Act of 1940 other than an active fund; (3) an employee benefit plan as defined in paragraphs (3) and (32) of section 3 of the Employee Retirement Income and Security Act of 1974; or (4) a person predominantly engaged in activities that are in the business of banking, or in activities that are financial in nature as defined in section 4(k) of the Bank Holding Company Act of 1956,<E T="03">provided that,</E>in each case, the entity is not a third-party subaccount.</P>
            <P>
              <E T="03">Category 3 Entity</E>means a Category 2 Entity whose positions are held as a third-party subaccount.</P>
            <P>
              <E T="03">Category 4 Entity</E>means any person not included in Categories 1, 2, or 3.</P>
            <P>
              <E T="03">Third-party Subaccount</E>means a managed account that requires specific approval by the beneficial owner of the account to execute documentation necessary for executing, confirming, margining, or clearing swaps.</P>
            <P>(b)<E T="03">Compliance schedule.</E>The following schedule for compliance with the requirements of § 23.504 shall apply:</P>

            <P>(1) For swap transactions with a Category 1 Entity, a swap dealer or major swap participant shall comply with the requirements of § 23.504 no later than ninety (90) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>

            <P>(2) For swap transactions with a Category 2 Entity, a swap dealer or major swap participant shall comply with the requirements of § 23.504 no later than one hundred and eighty (180) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>

            <P>(3) For swap transactions with a Category 3 Entity or a Category 4 Entity, a swap dealer or major swap participant shall comply with the requirements of § 23.504 no later than two hundred and seventy (270) days from the date of publication of such requirements in the<E T="04">Federal Register</E>.</P>
            <P>(c) Nothing in this rule shall prohibit any person from complying voluntarily with the requirements of § 23.504 sooner than the compliance schedule provided in paragraph (b).</P>
          </SECTION>
          <SIG>
            <DATED>Issued in Washington, DC, on September 8, 2011, by the Commission.</DATED>
            <NAME>David A. Stawick,</NAME>
            <TITLE>Secretary of the Commission.</TITLE>
          </SIG>
          <HD SOURCE="HD1">Appendices To Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements Under Section 4s of the CEA—Commissioners Voting Summary and Statements of Commissioners</HD>
          <NOTE>
            <HD SOURCE="HED">Note:</HD>
            <P>The following appendices will not appear in the Code of Federal Regulations</P>
          </NOTE>
          <HD SOURCE="HD1">Appendix 1—Commissioners Voting Summary</HD>
          <EXTRACT>
            <P>On this matter, Chairman Gensler and Commissioners Dunn, Sommers, and Chilton voted in the affirmative; Commissioner O'Malia voted in the negative.</P>
          </EXTRACT>
          <HD SOURCE="HD1">Appendix 2—Statement of Chairman Gary Gensler</HD>
          <EXTRACT>
            <P>I support this proposal to establish schedules to phase in compliance with previously proposed requirements, including the swap trading relationship documentation requirement and the margin requirements for uncleared swaps. The proposal would provide greater clarity to swap dealers and major swap participants regarding the timeframe for bringing their swap transactions into compliance with new documentation and margining rules. The proposal also would make the market more open and transparent, while giving market participants an adequate amount of time to comply. The proposal would help facilitate an orderly transition to a new regulatory environment for swaps.</P>
          </EXTRACT>
          <HD SOURCE="HD1">Appendix 3—Statement of Commissioner Scott O'Malia</HD>
          <EXTRACT>

            <P>I respectfully dissent from the Commission's decision today to approve for<E T="04">Federal Register</E>publication two rule proposals related to implementation entitled “Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA” and “Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements under Section 4s of the CEA.” For quite some time, I have been asking that the Commission publish for notice and comment a comprehensive implementation schedule that addresses the entire mosaic of rule proposals under the Dodd-Frank Act. I believe the Commission should have proposed a comprehensive schedule that detailed, at a minimum:</P>
            <P>• For each registered entity (<E T="03">e.g.,</E>swap dealer and major swap participants), compliance dates for each of its entity-specific obligations (<E T="03">e.g.,</E>all obligations under Section 4s of the Commodity Exchange Act) under Dodd-Frank; and</P>
            <P>• For each market-wide obligation (<E T="03">e.g.,</E>the clearing and trading mandates), the<PRTPAGE P="58186"/>entities affected (whether registered or unregistered) along with appropriate compliance dates.</P>
            <P>Such a schedule would have complemented and informed existing proposals and provided structure to future determinations. Additionally, a proposal regarding such a schedule should have adequately analyzed the costs and benefits of alternatives, including appropriate quantification. Unfortunately, the two rule proposals that the Commission approved today fail to either propose a comprehensive schedule or provide an adequate cost benefit analysis.</P>
            <P>The Commission's proposals also fail to request comment on a number of issues that I believe are important considerations in developing an implementation plan. As a result, I am encouraging commenters to submit responses to the questions below as part of their comments on the two rule proposals.</P>
            <HD SOURCE="HD2">Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA</HD>
            <P>• Should the Commission provide guidance on how it will make and communicate a mandatory clearing determination prior to considering the first such determination? If so, what information should be included in guidance?</P>

            <P>• As section II(E) of the proposal states: “When issuing a mandatory clearing determination, the Commission would set an effective date by which all market participants would have to comply. In other words, the proposed compliance schedules would be used only when the Commission believes that phasing is necessary based on the considerations outlined in this release. The Commission will provide the public with notice of its intent to rely upon the compliance schedule pursuant to the process outlined in § 39.5(b)(5).” To afford more certainty to market participants, should the Commission instead create a presumption that it will rely on the compliance schedule for each mandatory clearing determination that it issues, unless it finds that the compliance schedule is not necessary to achieve the benefits set forth in the proposal (<E T="03">e.g.,</E>facilitating the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions)?</P>
            <P>• What, if any, other issues not addressed in current proposed or final rulemakings should the Commission have taken into consideration when proposing the compliance schedule? For example, should the Commission have considered the extent to which its clearing and trade execution requirements apply to entities and transactions located outside the United States? Also, should the Commission have considered the extent to which such requirements apply to transactions between affiliates (whether domestic or cross-border)? If applicable, how should the Commission adjust the proposed compliance schedule to account for such issues?</P>
            <P>• What, if any, adjustments should the Commission make to the proposed compliance schedule for trade execution requirements if the Commission makes a determination that a group, category, type, or class of swaps, rather than a specific swap, is subject to mandatory clearing? Would such adjustments vary depending on the manner in which the Commission defines group, category, type, or class?</P>
            <HD SOURCE="HD2">Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements Under Section 4s of the CEA</HD>
            <P>• What, if any, other issues not addressed in current proposed or final rulemakings should the Commission have taken into consideration when proposing the compliance schedule? For example, should the Commission have considered the extent to which its documentation and margin requirements apply to entities and transactions located outside the United States? Also, should the Commission have considered the extent to which such requirements apply to transactions between affiliates (whether domestic or cross-border)? If applicable, how should the Commission adjust the proposed compliance schedule to account for such issues?</P>
            <P>Finally, I want to be clear that I support completing the final Dodd-Frank rulemakings in a reasonable time frame. I believe that the timely implementation of such rulemakings is important. Knowing when and how the markets are required to do what is vital to the success of implementing the new market structure required under the Dodd-Frank Act. When billions of dollars are at stake, you simply do not rely on guesses and estimates based on vague conditions.</P>
          </EXTRACT>
          
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24128 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6351-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
        <CFR>17 CFR Parts 37, 38, and 39</CFR>
        <RIN>RIN 3038-AD60</RIN>
        <SUBJECT>Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Commodity Futures Trading Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Commodity Futures Trading Commission (Commission or CFTC) is proposing regulations that would establish a schedule to phase in compliance with certain new statutory provisions enacted under Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act). These provisions include the clearing requirement under new section 2(h)(1)(A) of the Commodity Exchange Act (CEA or Act), and the trade execution requirement under new section 2(h)(8)(A) of the CEA. The proposed schedules would provide relief in the form of additional time for compliance with these requirements. This relief is intended to facilitate the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions. The Commission requests comment on the proposed compliance schedules for these clearing and trade execution requirements.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before November 4, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by RIN number 3038-AD60 and Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA, by any of the following methods:</P>
          <P>•<E T="03">Agency Web site,</E>via its Comments Online process at<E T="03">http://comments.cftc.gov.</E>Follow the instructions for submitting comments through the Web site.</P>
          <P>•<E T="03">Mail:</E>David A. Stawick, Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street, NW., Washington, DC 20581.</P>
          <P>•<E T="03">Hand Delivery/Courier:</E>Same as mail above.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>Please submit your comments using only one method.</P>
          

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

          <P>The Commission reserves the right, but shall have no obligation, to review, pre-screen, filter, redact, refuse or remove any or all of your submission from<E T="03">http://www.cftc.gov</E>that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the rulemaking will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other<PRTPAGE P="58187"/>applicable laws, and may be accessible under the Freedom of Information Act.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Dhaval Patel, Counsel, Office of the General Counsel, 202-418-5125,<E T="03">dpatel@cftc.gov,</E>or Camden Nunery, Office of the Chief Economist,<E T="03">cnunnery@cftc.gov,</E>202-418-5723, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street, NW., Washington, DC 20581.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On July 21, 2010, President Obama signed the Dodd-Frank Act.<SU>1</SU>
          <FTREF/>Title VII of the Dodd-Frank Act amends the CEA<SU>2</SU>
          <FTREF/>to establish a comprehensive new regulatory framework for swaps. The legislation was enacted to reduce risk, increase transparency, and promote market integrity within the financial system by, among other things: (1) Providing for the registration and comprehensive regulation of swap dealers and major swap participants; (2) imposing clearing and trade execution requirements on standardized derivative products; (3) creating robust recordkeeping and real-time reporting regimes; and (4) enhancing the rulemaking and enforcement authorities of the Commission with respect to, among others, all registered entities and intermediaries subject to the Commission's oversight.</P>
        <FTNT>
          <P>
            <SU>1</SU>
            <E T="03">See</E>Dodd-Frank Wall Street Reform and Consumer Protection Act, Public Law 111-203, 124 Stat. 1376 (2010).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>7 U.S.C. 1<E T="03">et seq.</E>
          </P>
        </FTNT>

        <P>To implement the Dodd-Frank Act, the Commission has to-date issued 55 advance notices of proposed rulemaking or notices of proposed rulemaking, two interim final rules, 12 final rules, and one proposed interpretive order. By the beginning of May 2011, the Commission had published in the<E T="04">Federal Register</E>a significant number of notices of proposed rulemaking, which represented a substantially complete mosaic of the Commission's proposed regulatory framework under Title VII of the Dodd-Frank Act. In recognition of that fact and with the goal of giving market participants additional time to comment on the proposed new regulatory framework for swaps, either in part or as a whole, the Commission reopened or extended the comment period of many of its proposed rulemakings through June 3, 2011.<SU>3</SU>
          <FTREF/>In total, the Commission has received over 20,000 comments in response to its Dodd-Frank Act rulemaking proposals.</P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See</E>Reopening and Extension of Comment Periods for Rulemakings Implementing the Dodd-Frank Wall Street Reform and Consumer Protection Act, 76 FR 25274, May 4, 2011.</P>
        </FTNT>
        <P>To give the public an opportunity to comment further on implementation phasing, on May 2-3, 2011, the Commission, along with the Securities and Exchange Commission (SEC), held a joint, two-day roundtable on issues related to implementation.<SU>4</SU>
          <FTREF/>In connection with this roundtable, Commission staff proposed thirteen concepts to be considered regarding implementation phasing, and staff asked a series of questions based on the concepts outlined.<SU>5</SU>
          <FTREF/>The Commission received numerous comments in response to both its roundtable and the staff concepts and questions.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>4</SU>The transcripts from the roundtable are available at<E T="03">http://www.cftc.gov/ucm/groups/public/@newsroom/documents/file/csjac_transcript050311.pdf</E>(“Day 1 Roundtable Tr.”) and<E T="03">http://www.cftc.gov/ucm/groups/public/@newsroom/documents/file/csjac_transcript050211.pdf</E>(“Day 2 Roundtable Tr.”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">See</E>“CFTC Staff Concepts and Questions Regarding Phased Implementation of Effective Dates for Final Dodd-Frank Rules,” available at<E T="03">http://www.cftc.gov/ucm/groups/public/@newsroom/documents/file/staffconcepts050211.pdf.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>Such comments are available at<E T="03">http://comments.cftc.gov/PublicComments/CommentList.aspx?id=1000.</E>
          </P>
        </FTNT>
        <P>These comments were submitted by a number of existing and potential market infrastructures, including clearinghouses, trading platforms, and swap data repositories. Comments also were submitted by entities that may potentially be swap dealers (SDs) or major swap participants (MSPs), as well as those financial entities that may not be required to register with the Commission, but whose swap transactions may be required to comply with the clearing requirement under section 2(h)(1)(A) of the CEA, and a trade execution requirement under section 2(h)(8)(A) of the CEA. The Commission also received many comments from non-financial entities.</P>
        <P>One of the key themes to emerge from the comments received by the Commission is that some market participants may require more time to bring their swap transactions into compliance with certain new regulatory requirements.<SU>7</SU>
          <FTREF/>For example, one commenter requested a “meaningful” period after finalization of the suite of rulemakings that is applicable to it before actual compliance will be required.<SU>8</SU>
          <FTREF/>Similarly, several trade associations recommended the Commission allow “sufficient” time for infrastructure and business practices to develop before requiring compliance with the new requirements.<SU>9</SU>
          <FTREF/>A group of international banks commented that the Commission should defer compliance until December 31, 2012, at which point the regulatory timetable as per the September 2009 G20 Pittsburgh statement will have reached a conclusion.<SU>10</SU>
          <FTREF/>Another commenter noted that some entities may be able to comply relatively quickly with certain documentation requirements that are largely consistent with current business practices while other requirements may need a longer implementation period.<SU>11</SU>
          <FTREF/>Although commenters varied in their recommendations regarding the time it would take to bring their swaps into compliance with the new regulatory requirements,<SU>12</SU>
          <FTREF/>many commenters agreed on phasing in compliance with these requirements by type of market participant based on a variety of factors, including a market participant's experience, resources, and the size and complexity of its transactions.<SU>13</SU>
          <FTREF/>The Commission has taken these comments into consideration in developing the proposed compliance schedules.</P>
        <FTNT>
          <P>
            <SU>7</SU>
            <E T="03">E.g.,</E>Letter from Karrie McMillan, Investment Company Institute, dated Jun. 10, 2011 at 8-11; Letter from Financial Services Forum, Futures Industry Association, International Swaps and Derivatives Association, and Securities Industry and Financial Markets Association, dated May 4, 2011 at 7-9; Letter from Jeff Gooch, MarkitSERV, dated Jun. 10, 2011 at 1-2 and 6; Letter from Electric Trade Association, dated May 4, 2011 at 5; Letter from John R. Gidman, Association of Institutional Investors, dated Jun. 10, 2011 at 3.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>Letter from the Coalition of Physical Energy Companies, dated Mar. 14, 2011 at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>Letter from the Futures Industry Association, the Financial Services Forum, the International Swaps and Derivatives Association and the Securities Industry and Financial Markets Association, dated May 4, 2011 at 5.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>10</SU>Letter from the Bank of Tokyo-Mitsubishi UFJ, Ltd.,<E T="03">et al.,</E>dated May 6, 2011 at 6.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>Letter from the Financial Services Roundtable, dated May 12, 2011 at 4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>For example, Javelin stated that it could be open for business and generally be in compliance with the clearing and trade execution requirements within 6 months. Day 1 Roundtable Tr. at 104-105. Citadel suggested moving towards a voluntary clearing launch between day 180 and day 240, and eventually moving towards a mandatory clearing date. Day 1 Roundtable Tr. at 73-74. Moreover, the Swap Financial Group offered a different perspective stating that it generally thought implementation of Dodd-Drank could be accomplished in a year or two. Day 2 Roundtable Tr. at 269.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>These comments are more fully discussed later in the preamble.</P>
        </FTNT>
        <P>The swap transaction compliance requirements that are the subject of this proposed rulemaking include compliance with the clearing requirement and the corresponding trade execution requirement under sections 2(h)(1)(A) and 2(h)(8)(A) of the CEA, respectively.<SU>14</SU>
          <FTREF/>The Commission's<PRTPAGE P="58188"/>proposed compliance schedules are designed to afford affected market participants a reasonable amount of time to bring their transactions into compliance with such requirements. The proposed schedules also would provide relief in the form of additional time for compliance with these transaction compliance requirements and are further explained below.<SU>15</SU>
          <FTREF/>This relief is intended to facilitate the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions.</P>
        <FTNT>
          <P>
            <SU>14</SU>The Commission also is proposing Swap Transaction Compliance and Implementation Schedule: Trade Documentation and Margining Requirements under section 4s of the CEA.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>15</SU>The proposed compliance schedules do not address the effective dates of the clearing and trade execution requirements in the Dodd-Frank Act, including the application of the Commission's Effective Date Order to such requirements.<E T="03">See</E>Effective Date for Swap Regulation, 76 FR 42508, Jul. 19, 2011.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Proposed Regulation</HD>
        <HD SOURCE="HD2">A. Authority to Implement Proposed Regulations</HD>
        <P>In this Notice of Proposed Rulemaking, the Commission relies on its general authority to establish compliance dates with the rules and regulations enacted pursuant to the Dodd-Frank Act. Section 712(f) also authorizes the Commission to promulgate rules to prepare for the effective dates of the provisions of the Dodd-Frank Act.<SU>16</SU>
          <FTREF/>In addition, the Commission relies on section 8(a)(5) of the CEA, which authorizes the Commission to promulgate such regulations as, in the judgment of the Commission, are reasonably necessary to effectuate any of the provisions or to accomplish any of the purposes of the CEA. In accordance with this authority, the proposed regulations would amend parts 37, 38, and 39 of the Commission's regulations to phase in compliance dates for the clearing and trade execution requirements under section 2(h) of the CEA.</P>
        <FTNT>
          <P>
            <SU>16</SU>Section 712(f) of the Dodd-Frank Act states: “Beginning on the date of enactment of this Act and notwithstanding the effective date of any provision of this Act, the [Commission] * * * may, in order to prepare for the effective dates of the provisions of this Act—(1) promulgate rules, regulations, or orders permitted or required by this Act * * *.”</P>
        </FTNT>
        <HD SOURCE="HD2">B. Implementation Phasing of the Clearing Requirement under Section 2(h)(1)</HD>
        <HD SOURCE="HD3">1. Background on Mandatory Clearing Determinations</HD>
        <P>Section 723(a)(3) of the Dodd-Frank Act amended the CEA to provide, under new section 2(h)(1)(A), that “it shall be unlawful for any person to engage in a swap unless that person submits such swap for clearing to a derivatives clearing organization that is registered under this Act or a derivatives clearing organization that is exempt from registration under this Act if the swap is required to be cleared.”<SU>17</SU>
          <FTREF/>Section 2(h)(2) charges the Commission with the responsibility for determining whether a swap is required to be cleared, through one of two avenues: (1) Pursuant to a Commission-initiated review; or (2) pursuant to a submission from a derivatives clearing organization (DCO) of each swap, or any group, category, type, or class of swaps that the DCO “plans to accept for clearing.”<SU>18</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>17</SU>Section 2(h)(7) of the CEA provides an exception to the clearing requirement (“the end-user exception”) when one of the counterparties to a swap (i) Is not a financial entity, (ii) is using the swap to hedge or mitigate commercial risk, and (iii) notifies the Commission how it generally meets its financial obligations associated with entering into a non-cleared swap.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>Under section 2(h)(2)(B)(ii), the Commission must consider swaps listed for clearing by a DCO as of the date of enactment of the Dodd-Frank Act.</P>
        </FTNT>
        <P>On July 26, 2011, the Commission published in the<E T="04">Federal Register</E>a final rule regarding the process for review of swaps for mandatory clearing.<SU>19</SU>
          <FTREF/>Under § 39.5(b)(6), the Commission will review a DCO's submission and determine whether the swap, or group, category, type, or class of swaps, described in the submission is required to be cleared. This determination will be made not later than 90 days after a complete submission has been received from a DCO, unless the submitting DCO agrees to an extension. Under § 39.5(c), Commission-initiated reviews of swaps that have not been accepted for clearing by a DCO will take place on an ongoing basis. However, as explained in the preamble to the final rule, the “Commission anticipates that the initial mandatory clearing determinations would only involve swaps that are already being cleared or that a DCO wants to clear.”<SU>20</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>76 FR 44464, Jul. 26, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>76 FR at 44469.</P>
        </FTNT>
        <P>Because the Commission initially will consider mandatory clearing determinations based on those swaps that DCOs are currently clearing or that a DCO would like to clear, the initial sequence of mandatory clearing determinations will be based on the market's view of which swaps can be cleared and which asset classes are ready for clearing, as reflected by the fact that a DCO is either currently clearing a group, category, type, or class of swaps or is intending to do so. For example, multiple registered DCOs currently clear interest rate, credit, and commodity swaps. For these swaps, the Commission will begin the review process for issuing mandatory clearing determinations in the near term.</P>
        <P>The Commission observes that before market participants could be required to comply with a mandatory clearing determination, the Commission must adopt its final rules related to the end-user exception to mandatory clearing established by section 2(h)(7) of the CEA. In December 2010, the Commission proposed rules governing this elective exception to mandatory clearing.<SU>21</SU>
          <FTREF/>The proposed rule generally provides that a swap otherwise subject to mandatory clearing is subject to an elective exception from clearing if one party to the swap is not a financial entity, is using swaps to hedge or mitigate commercial risk, and notifies the Commission how it generally meets its financial obligations associated with entering into non-cleared swaps (the “end-user clearing exception”).<SU>22</SU>
          <FTREF/>Because this proposed rule would establish the process by which a non-financial entity would elect not to clear a swap subject to a clearing requirement, this rule would need to be finalized prior to requiring compliance with a mandatory clearing determination.</P>
        <FTNT>
          <P>
            <SU>21</SU>End-User Exception to Mandatory Clearing of Swaps, 75 FR 80747, Dec. 23, 2010.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>22</SU>75 FR at 80748.</P>
        </FTNT>
        <P>In addition, the Commission recognizes that the swap transaction compliance schedules that are the subject of this proposal reference terms such as “swap,” “swap dealer,” and “major swap participant” that are the subject of rulemaking under sections 712(d)(1) and 721(c) of the Dodd-Frank Act.<SU>23</SU>
          <FTREF/>The Commission and the SEC have proposed rules that would further define each of these terms.<SU>24</SU>
          <FTREF/>As such,<PRTPAGE P="58189"/>and in a manner consistent with the temporary relief provided in the Commission's Effective Date Order,<SU>25</SU>
          <FTREF/>the Commission must adopt its final rules regarding the further definitions in question prior to requiring compliance with a mandatory clearing determination.<SU>26</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>23</SU>Section 712(d)(1) provides: “Notwithstanding any other provision of this title and subsections (b) and (c), the Commodity Futures Trading Commission and the Securities and Exchange Commission, in consultation with the Board of Governors [of the Federal Reserve System], shall further define the terms `swap', `security-based swap', `swap dealer', `security-based swap dealer', `major swap participant', `major security-based swap participant', and `security-based swap agreement' in section 1a(47)(A)(v) of the Commodity Exchange Act (7 U.S.C. 1a(47)(A)(v)) and section 3(a)(78) of the Securities Exchange Act of 1934 (15 U.S.C. 78c(a)(78)).” Section 721(c) provides: “To include transactions and entities that have been structured to evade this subtitle (or an amendment made by this subtitle), the Commodity Futures Trading Commission shall adopt a rule to further define the terms `swap', `swap dealer', `major swap participant', and `eligible contract participant'.”</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>24</SU>Further Definition of “Swap Dealer,” “Security-Based Swap Dealer,” “Major Swap Participant,” “Major Security-Based Swap Participant,” and “Eligible Contract Participant”; Proposed Rule, 75 FR 80174, Dec. 21, 2010 and Further Definition of “Swap,” “Security-Based Swap,” and “Security-Based Swap Agreement”;<PRTPAGE/>Mixed Swaps; Security-Based Swap Agreement Recordkeeping, 76 FR 29818, May 23, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>25</SU>
            <E T="03">See</E>Effective Date for Swap Regulation, 76 FR 42508, Jul. 19, 2011.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>Notably, under section 712(f) of the Dodd-Frank Act, these definitions would not have to be finalized for the Commission to review swap submissions from DCOs.</P>
        </FTNT>
        <P>Lastly, the Commission notes that it has yet to adopt final rules relating to the protection of cleared swaps customer contracts and collateral. These rules are essential for establishing the customer protection regime associated with client clearing for swaps through Commission-registered futures commission merchants (FCMs) at DCOs.<SU>27</SU>
          <FTREF/>The Commission believes that finalizing the rules regarding the segregation of customer collateral prior to requiring compliance with a mandatory clearing determination is necessary to effectuate the purposes of new section 4d(f) of the CEA.</P>
        <FTNT>
          <P>
            <SU>27</SU>Protection of Cleared Swaps Customer Contracts and Collateral; Conforming Amendments to the Commodity Broker Bankruptcy Provisions, 76 FR 33818, Jun. 9, 2011.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Compliance Schedule for Clearing Requirement—§ 39.5(e)</HD>
        <P>Proposed § 39.5(e) would provide the Commission with the authority to phase in compliance with a clearing requirement upon issuance of a mandatory clearing determination. The proposed compliance schedule is based on the type of market participants entering into the swaps subject to the clearing requirement. The triggering event for the application of this compliance schedule would be the Commission's issuance of a determination that the swap, or group, category, type, or class of swaps, is required to be cleared.<SU>28</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>28</SU>
            <E T="03">See</E>discussion below at p. 21 and above at p. 7. It would be possible for the Commission to issue a mandatory clearing determination but postpone the overall compliance date for all market participants for some period of time. Additionally, market participants may begin clearing their swap transactions as soon as a DCO begins accepting such swaps for clearing, regardless of whether the Commission determines that such swaps are required to be cleared.</P>
        </FTNT>
        <P>In proposing phased implementation schedules for the clearing requirement, the Commission seeks to balance several goals. First, the Commission believes that certain market participants may require additional time to bring their swaps into compliance with the new regulatory requirement for mandatory clearing of a swap or class of swaps. This is particularly true for market participants that may not be registered with the Commission and those market participants that may have hundreds or thousands of managed accounts, referred to as “third-party subaccounts” for the purposes of this proposal. Under this proposal, these parties would be afforded additional time to document new client clearing arrangements, connect to market infrastructure such as DCOs, and prepare themselves and their customers for the new regulatory requirements. As one commenter noted, “[i]n the context of asset managers, the account set up process has to be multiplied over hundreds of subaccounts. Processing all of these subaccounts will take time even for the largest and most technologically advanced asset managers.”<SU>29</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>29</SU>Letter from Karrie McMillan, Investment Company Institute, dated Jun. 10, 2011 at 9-10.</P>
        </FTNT>
        <P>Moreover, several commenters emphasized the need to have adequate time to educate their clients regarding the new regulatory requirements.<SU>30</SU>
          <FTREF/>For instance, market participants not registered with the Commission may not be familiar with the new regulatory requirements. In addition, market participants with third-party subaccounts would have to educate additional clients. Accordingly, both types of participants should be given additional time to prepare for compliance with the new requirements.</P>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">See</E>Letter from Financial Services Forum, Futures Industry Association, International Swaps and Derivatives Association, and Securities Industry Association, dated May 4, 2011 at 9; Letter from Karrie McMillan, Investment Company Institute, dated Jun. 10, 2011 at 10-11.</P>
        </FTNT>
        <P>Another goal of the proposed compliance schedule is to have adequate representation of market participants involved at the outset of implementing a new mandatory clearing regime for swaps. The Commission believes that having a cross-section of market participants involved at the outset of formulating and designing the rules and infrastructure under which mandatory clearing is implemented will best meet the needs of all market participants.</P>
        <P>Several commenters have recommended that the Commission take such an approach. For example, one commenter emphasized the importance of the initiation of so-called “buy-side” clearing access for credit default swaps in 2009 and recommended that “[a]t the time that a class of products is ready for clearing, all market participants (including buy-side participants) should be permitted (but not required) to clear those products * * *.”<SU>31</SU>
          <FTREF/>In another example, one commenter recommended that in phasing mandatory clearing the Commission should aim for open access to establish an “all to all market” with both sides of the trade involved with the initial implementation.<SU>32</SU>
          <FTREF/>In further response to these comments, the Commission notes that market participants can begin (and continue) voluntarily clearing swaps through eligible DCOs at any time.</P>
        <FTNT>
          <P>
            <SU>31</SU>Letter from Richard H. Baker, Managed Funds Association, dated Mar. 24, 2011 at Appendix 1, page 1 and Appendix 2, page 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>Letter from Chris Koppenheffer, Swaps &amp; Derivatives Market Association, dated Jun. 1, 2011 at 2.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Implementation Phasing of the Trade Execution Requirement Under Section 2(h)(8)</HD>
        <HD SOURCE="HD3">1. Background on Trade Execution Requirement</HD>
        <P>Section 723 of the Dodd Frank Act amended the CEA to provide, under new section 2(h)(8)(A), that with respect to a swap that is subject to the clearing requirement of section 2(h)(1)(A), “counterparties shall (i) execute the transaction on a board of trade designated as a contract market under section 5 [a DCM]; or (ii) execute the transaction on a swap execution facility [SEF] registered under section 5h or a swap execution facility exempt from registration under section 5h(f) of this Act.” Under section 2(h)(8)(B), the only exceptions to the trade execution requirement are if no DCM or SEF “makes the swap available to trade” or the swap is subject to the clearing exception under section 2(h)(7) (i.e., the end-user exception).<SU>33</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>33</SU>Section 2(h)(1)(B).</P>
        </FTNT>
        <P>Based on the natural phasing provided for in the statute, a trade execution requirement is triggered for a swap when (1) The Commission has issued a determination that the swap is required to be cleared and (2) any DCM or SEF has made the swap available to trade.<SU>34</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>34</SU>This rulemaking does not address the manner in which it may be determined or established that a DCM or a SEF has made a swap available for trading.</P>
        </FTNT>
        <P>The Commission observes that before market participants could be required to comply with a trade execution requirement the Commission must adopt final rules related to SEFs and DCMs. The Commission has proposed rules related to the new core principles for DCMs and the changes to the 18 original DCM core principles.<SU>35</SU>
          <FTREF/>While<PRTPAGE P="58190"/>none of the new rules proposed for DCMs relate directly to the trade execution requirement under section 2(h)(8), the Commission believes that it is necessary for DCMs to have their new policies, procedures, and rulebooks in place prior to the DCMs making a swap available for trading.</P>
        <FTNT>
          <P>
            <SU>35</SU>Core Principles and Other Requirements for Designated Contract Markets, 75 FR 80572, Dec. 22, 2010.</P>
        </FTNT>
        <P>With regard to SEFs, the Commission also observes that it would have to adopt final rules allowing for SEF registration, including procedures for provisional registration, prior to any SEF making a swap that is required to be cleared available for trading.<SU>36</SU>
          <FTREF/>The finalization of these rules would enable SEFs to register with the Commission and ensure that they have developed their new policies, procedures, and rulebooks.</P>
        <FTNT>
          <P>

            <SU>36</SU>Core Principles and other Requirements for Swap Execution Facilities, 76 FR 1214, Jan. 7, 2011. As part of the SEF rulemaking, the Commission proposed regulation § 37.10, which would require each SEF to conduct an annual review of whether it has made a swap available for trading and to provide a report to the Commission regarding its assessment.<E T="03">Id.</E>at 1222 and 1241.</P>
        </FTNT>
        <HD SOURCE="HD3">2. Compliance Schedule for the Trading Execution Requirement—§§ 37.12 and 38.11</HD>
        <P>Proposed regulations §§ 37.12 and 38.11 provide for the phased implementation of a trade execution requirement by setting forth a compliance schedule tied to the schedule proposed for the clearing requirement.</P>
        <P>The proposed compliance schedules for the trade execution requirement would be triggered upon the later of (1) The applicable deadline established under the compliance schedule for the associated clearing mandate; or (2) 30 days after the swap is made available for trading on either a SEF or a DCM. Consequently, market participants always will have at least thirty days after a DCM or SEF has made a swap available for trading to comply with a trade execution requirement. Prior to a Commission-issued mandatory clearing determination, both DCMs and SEFs would be permitted to offer swaps for trading by market participants on a voluntarily basis. However, those swaps would not be required to be traded on a DCM or SEF, pursuant to section 2(h)(8) of the CEA until the associated clearing requirement took effect.</P>
        <HD SOURCE="HD2">D. Three-Part Implementation Phasing</HD>
        <P>The Commission proposes compliance schedules for phasing implementation that afford relief in the form of additional time for compliance with any clearing requirement or trade execution requirement by category of market participant. The Commission based its proposed categorization of entities on the definition of “financial entity” in section 2(h)(7)(C) of the CEA.<SU>37</SU>
          <FTREF/>Under this statutory provision, Congress identified financial entities that would not be eligible to claim an exception from a clearing requirement under section 2(h)(1) of the CEA.</P>
        <FTNT>
          <P>
            <SU>37</SU>CEA section 2(h)(7)(A)(i) limits availability of the end-user clearing exception to counterparties to the swap that are not a financial entity. The term financial entity is defined in CEA section 2(h)(7)(C)(i), and includes the following eight entities: (i) A swap dealer; (ii) a security-based swap dealer; (iii) a major swap participant; (iv) a major security-based swap participant; (v) a commodity pool as defined in CEA section 1a(10); (vi) a private fund as defined in section 202(a) of the Investment Advisers Act of 1940 (15 U.S.C. 80b-2(a)); (vii) an employee benefit plan as defined in paragraphs (3) and (32) of section 3 of the Employee Retirement Income Security Act of 1974 (29 U.S.C. 1002); or (viii) a person predominantly engaged in activities that are in the business of banking or financial in nature, as defined in section 4(k) of the Bank Holding Company Act of 1956 (12 U.S.C. 1843(k)).</P>
        </FTNT>
        <HD SOURCE="HD3">Phase 1—Category 1 Entities</HD>
        <P>The proposed compliance schedule would define “Category 1 Entities” to include a swap dealer, a security-based swap dealer, a major swap participant, a major security-based swap participant, or an active fund.</P>
        <P>Category 1 Entities include those dealers and major participants in the swap and security-based swap markets that will be registered with the Commission or the Securities and Exchange Commission (SEC).<SU>38</SU>
          <FTREF/>Title VII of the Dodd-Frank Act requires these market participants to register with either the CFTC or SEC as a result of their swaps or security-based swaps activities. Based on their level of market experience and based on their status as registrants with either the CFTC or the SEC, the Commission believes they should be capable of complying with a clearing requirement and a trade execution requirement sooner than other market participants and that 90 days is a reasonable timeframe for these entities to come into compliance with these requirements.</P>
        <FTNT>
          <P>
            <SU>38</SU>If a security-based swap dealer or a major security-based swap participant is not yet required to register with the SEC at such time as the Commission issues mandatory clearing determination, then the security-based swap dealer or a major security-based swap participant would be treated as a Category 2 Entity.</P>
        </FTNT>
        <P>The Commission also is proposing to include those entities it defines as “active funds” in the first category of market participants. The proposed definition of “active fund” would mean “any private fund as defined in section 202(a) of the Investment Advisors Act of 1940, that is not a third-party subaccount and that executes 20 or more swaps per month based on a monthly average over the 12 months preceding the Commission issuing a mandatory clearing determination under section 2(h)(2) of the Act.”<SU>39</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>39</SU>It should be noted that many commodity pools meet the definition of private fund under section 202(a) of the Investment Advisors Act of 1940. Such a commodity pool would only be a Category 1 Entity if it met the other criteria of an active fund.</P>
        </FTNT>
        <P>The Commission is relying on the definition of private fund from section 2(h)(7)(C) of the CEA, as well as section 402 of the Dodd-Frank Act. However, the Commission is limiting the definition in two ways. First, the definition excludes third-party subaccounts, as discussed further below. Second, the definition is limited to those private funds that execute 20 or more swaps per month based on the average over the 12 months preceding the Commission's issuance of a mandatory clearing determination.<SU>40</SU>
          <FTREF/>In choosing this threshold, the Commission's goal was to ensure the involvement of a cross-section of market participants at the outset of both clearing and trading requirement implementation. The Commission also sought to address some commenters' concerns regarding adequate “buy-side” representation early in the mandatory clearing process. Based on a preliminary assessment, the Commission believes the proposed numerical threshold for active funds is appropriate because a private fund that conducts this volume of swaps would be likely to have: (1) Sufficient resources to enter into arrangements that comply with the clearing and trade execution requirement earlier than other types of market participants; and (2) sufficient market experience to contribute meaningfully to the “buy-side” perspective as industry standards are being developed.<SU>41</SU>
          <FTREF/>In defining “active fund” accordingly, the Commission believes it has included those market participants that are likely to be among the most experienced participants with expertise and resources needed to come into transaction compliance quickly.</P>
        <FTNT>
          <P>
            <SU>40</SU>In calculating the numerical threshold, the Commission intends for funds to calculate all swaps it executes not just those that are the subject of a mandatory clearing determination.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>41</SU>The Commission is unaware of any position-level or transaction-level data on private fund swap activity in a publicly available form. In order to determine private fund activity levels, the staff consulted with academics focusing their research in this area, with industry participants, and with groups that represent the industry.</P>
        </FTNT>

        <P>The Commission proposes to phase in compliance with the mandatory clearing requirement for any swap transaction between a Category 1 Entity and another Category 1 Entity, or any other entity<PRTPAGE P="58191"/>that desires to clear the transaction<SU>42</SU>
          <FTREF/>within the first 90 days after the Commission issues any mandatory clearing determination. With respect to the trade execution requirement, the Commission proposes to phase in compliance with this requirement either at the same time as the clearing requirement or thirty days after the swap is made available for trading, whichever is later. The Commission proposes phasing in all Category 1 Entities first because these market participants are likely to be the most active and experienced market participants whose involvement in the early stages of building and rolling out the clearing and trading requirements is critical. The Commission is attempting to include in this category those market participants with the expertise and resources to implement mandatory clearing and trading most quickly. The Commission also believes Category 1 Entities likely will have the most existing connectivity to clearinghouses and trading platforms and would be able to come into compliance sooner than other categories of participants.</P>
        <FTNT>
          <P>
            <SU>42</SU>The intent of this clause is to facilitate clearing by counterparties that desire to comply with a clearing mandate earlier than they would otherwise be required to under the compliance schedule. The Commission solicits comment on whether there would be a better way to accomplish this objective.</P>
        </FTNT>
        <HD SOURCE="HD3">Phase 2—Category 2 Entities</HD>
        <P>The proposed compliance schedule would define “Category 2 Entities” to include a commodity pool; a private fund as defined in section 202(a) of the Investment Advisors Act of 1940 other than an active fund; an employee benefit plan as defined in paragraphs (3) and (32) of section 3 of the Employee Retirement Income and Security Act of 1974; or a person predominantly engaged in activities that are in the business of banking, or in activities that are financial in nature as defined in section 4(k) of the Bank Holding Company Act of 1956, provided that the entity is not a third-party subaccount.</P>
        <P>The Commission proposes to phase in compliance for swap transactions between a Category 2 Entity and Category 1 Entity, another Category 2 Entity, or any other entity that desires to clear the transaction.<SU>43</SU>
          <FTREF/>The Commission is proposing to afford swap transactions between these types of market participants 180 days to come into compliance with a clearing requirement. With respect to the trade execution requirement, the Commission proposes to phase in compliance with this requirement either at the same time as the clearing requirement or thirty days after the swap is made available for trading, whichever is later. In providing these market participants an additional 90 days to come into compliance, the Commission took into consideration the fact that Category 2 Entities may not be required to be registered with the Commission and may be less experienced and less frequent users of the swap markets than those in Category 1.</P>
        <FTNT>
          <P>
            <SU>43</SU>
            <E T="03">See</E>footnote 42.</P>
        </FTNT>
        <P>Additionally, Category 2 Entities may not have the same level of expertise and resources to bring their swaps into compliance with a clearing requirement as quickly as Category 1 Entities. As defined for purposes of these compliance schedules, Category 2 Entities do not include those financial entities that are third-party subaccounts, as described further below.</P>
        <HD SOURCE="HD3">Phase 3—Third-Party Subaccounts and all Other Swap Transactions</HD>
        <P>Finally, the Commission proposes to phase in compliance for all other swap transactions not excepted from the mandatory clearing requirement within 270 days after the Commission issues a clearing requirement. The Commission proposes to phase in compliance with the trade execution requirement either at the same time as the clearing requirement or thirty days after the swap is made available for trading, whichever is later.</P>
        <P>The Commission proposes to include all entities that are third-party subaccounts in this 270-day period. This approach would give these entities the most time to bring their swaps into compliance because they are likely to require the most time for documentation, coordination, and management. A third-party subaccount is afforded 270 days to bring its swaps into compliance because its portfolio is managed by an asset manager that may have to bring numerous accounts into compliance. The Commission also proposes to include any other swap transaction that would be subject to a clearing requirement into compliance within this proposed 270-day period.</P>
        <P>Under the Commission's proposed definition, a third-party subaccount would be a managed account that requires specific approval by the beneficial owner of the account to execute documentation necessary for executing, confirming, margining, or clearing swaps. By way of non-exclusive example, if investment management firm X manages the assets of pension fund Y, and does so in a separate account that requires the approval of pension fund Y to execute necessary documentation, then that account would be afforded 270 days to come into compliance. On the other hand, if pension fund Y manages its own assets, it would fall within Category 2 and be afforded 180 days to come into compliance. Likewise, if investment management firm X does not manage the assets of third parties, then it would fall within Category 2.</P>
        <P>The Commission is proposing to afford third-party subaccounts an additional 90 days beyond the 180 days proposed for Category 2 because such entities may have documentation obligations for hundreds or even thousands of third-party subaccounts, and each such account must meet the mandatory clearing and trading requirements. For example, according to a statement made during the Joint SEC-CFTC Roundtable by Mr. William DeLeon of the firm Pacific Investment Management Company, LLC (PIMCO), PIMCO manages hundreds of third-party subaccounts, as defined above.<SU>44</SU>
          <FTREF/>The proposed compliance schedules would not prohibit any type of market participant from voluntarily complying sooner than the compliance deadline. Indeed, the Commission would encourage market participants that can come into compliance more quickly to move their swaps into clearing and begin trading on trading platforms as soon as possible in order to facilitate development of infrastructure that takes into account the views of many types of market participants. As one commenter noted, “Smaller entities, for example, may have unique issues that need to be accounted for before systems are hardwired. Many swap market participants are small entities; it is important to ensure that these entities and their liquidity are not squeezed out of the swaps market.”<SU>45</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>44</SU>Day 2 Roundtable Tr. at 62.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>45</SU>Investment Company Institute, Jun. 10, 2011 letter, at 12.</P>
        </FTNT>
        <HD SOURCE="HD2">E. Prospective Application of Compliance Schedules</HD>

        <P>The Commission anticipates that it will exercise its authority to trigger the proposed compliance schedules each time it issues a mandatory clearing determination for a new group, category, type, or class of swaps. Under this approach, when a DCO begins offering a new swap for clearing and it is in the same group, category, type, or class of swaps and it meets the requirements imposed under a previously issued mandatory clearing determination, then the proposed compliance schedules would not be triggered. However, if the Commission issues a mandatory clearing determination in any entirely new group, category, type, or class of<PRTPAGE P="58192"/>swaps then the compliance schedules could once again be triggered by the Commission. For example, if the Commission issues a mandatory clearing determination for 5 year credit default swap products and a new 5 year credit default swap product is offered for clearing based on a new 5 year index, then the proposed compliance schedules may not be triggered. If on the other hand, the Commission has not issued a mandatory clearing determination for 10 year credit default swap products and a new 10 year credit default swap product is offered for clearing, then the compliance schedules could be triggered by the Commission.</P>
        <P>When issuing a mandatory clearing determination, the Commission would set an effective date by which all market participants would have to comply. In other words, the proposed compliance schedules would be used only when the Commission believes that phasing is necessary based on the considerations outlined in this release. The Commission will provide the public with notice of its intent to rely upon the compliance schedule pursuant to the process outlined in § 39.5(b)(5).</P>
        <P>The Commission solicits comment on the ongoing usefulness of the proposed compliance schedules once market participants have established documentation and connectivity to DCOs, DCMs, and SEFs.</P>
        <HD SOURCE="HD2">F. Comment Requested</HD>
        <P>The Commission requests comment on all aspects of the proposed compliance schedules, §§ 37.12, 38.11 and 39.5(e). The Commission may consider alternatives to the proposed compliance schedules and is requesting comment on the following questions:</P>
        <P>• What, if any, other rules should have been taken into consideration when proposing an implementation schedule regarding the clearing and trade execution requirements? If applicable, how should the implementation requirements of those other rules be taken into consideration?</P>

        <P>• Should there be a presumption that the Commission will rely on the compliance schedule for each mandatory clearing determination that it issues, unless the Commission finds that the compliance schedule is not necessary to achieve the benefits set forth herein (<E T="03">e.g.,</E>facilitating the transition to the new regulatory requirement established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions)?</P>
        <P>• What factors, if any, would prevent an entity in any of the proposed categories from adhering to the compliance schedules proposed by the Commission? How much additional time would be needed to address these factors?</P>
        <P>• Are there other considerations that the Commission should have taken into account when designing this tiered implementation schedule? Are the timeframes outlined in this implementation schedule adequate? If not, what alternative schedule should the Commission consider, and why?</P>
        <P>• Assuming a situation where a swap first becomes subject to the clearing requirement and then is made available for trading by a DCM or SEF, is an additional thirty days after the swap becomes made available for trading enough time for DCMs, SEFs, and market participants to come into compliance with the trade execution requirement? For example, would thirty days be sufficient for the needed technological linkages to be established between (i) the DCOs, DCMs, and SEFs and (ii) the DCMs, SEFs, and market participants.</P>

        <P>• What other entities, if any, should be included in Category 1 or 2, and why? Should any entities be moved from Category 1 or 2 to a later category? For example, where should the Commission place those entities described in section 2(h)(7)(C)(ii) of the CEA (<E T="03">e.g.,</E>small banks, savings associations, farm credit system institutions, and credit unions)?</P>
        <P>• What adjustments to the compliance schedule and/or other steps could the Commission take to ensure there is adequate representation from all market participants at the outset of clearing and trade execution requirements?</P>
        <P>• In suggesting phasing in transactions between Category 1 or 2 Entities and “any other entity that desires to clear the transaction,” the Commission intended to facilitate clearing by counterparties that desire to comply with a clearing mandate earlier than they would otherwise be required to under the compliance schedule. Is there a better way to achieve this objective?</P>
        <P>• Is an entity's average monthly swap transaction activity a useful proxy for that entity's ability to comply with the clearing and trade execution requirements? Or whether an entity is required to be registered with the Commission (rather than whether an entity is already registered with the Commission)?</P>
        <P>• Is the Commission's definition of “active fund” overly inclusive or under-inclusive? Should the numerical threshold for number of monthly swap transactions be higher or lower than 20? If so, why? Should the number of monthly swap transactions be linked to swap activity in a particular asset class?</P>
        <P>• Should the Commission exclude from the definition of “active fund” any investment advisor of private funds acting solely as an advisor to private funds with assets under management in the United States of less than $150,000,000, as provided for in the reporting exemption for private funds under section 408 of the Dodd-Frank Act?</P>
        <P>• Would it be more appropriate for the Commission to measure a market participant's level of swap activity by measuring notional turnover and/or open exposure, as suggested by some commenters?<SU>46</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>46</SU>Letter from Adam C. Cooper, Citadel, dated June 3, 2011, Appendix B.</P>
        </FTNT>
        <P>• Are there any anticompetitive implications to the proposed compliance schedules? If so, how could the proposed rules be implemented to achieve the purposes of the CEA in a less anticompetitive manner? If so, please quantify those costs, if possible, and provide underlying data sources, assumptions and calculations.</P>
        <P>• Are there additional costs or benefits associated with the current proposal that the Commission has not already taken into account? Please discuss any such costs in detail and quantify in dollar terms, if possible.</P>
        <P>• Are there any assumptions, including quantitative assumptions, underlying the Commission's cost benefit analysis that the Commission should consider?</P>
        <P>• Should the Commission consider an alternative implementation schedule? Would such an alternative schedule reduce the costs market participants bear? Please describe any such alternative implementation schedule in detail, including how it will reduce costs and the benefits it will likely deliver. If possible, please quantify the cost and benefits associated with any alternative. If providing dollar values, please describe any data sources, assumptions, and calculations used to generate them.</P>
        <HD SOURCE="HD1">III. Related Matters</HD>
        <HD SOURCE="HD2">A. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act requires that agencies consider whether the rules they propose will have a significant economic impact on a substantial number of small entities and, if so, provide a regulatory flexibility analysis respecting the impact.<SU>47</SU>

          <FTREF/>The rules proposed by the CFTC provide compliance schedules for<PRTPAGE P="58193"/>certain new statutory requirements of the Dodd Frank Act and do not by themselves impose significant new regulatory requirements. Accordingly, the Chairman, on behalf of the CFTC, hereby certifies pursuant to 5 U.S.C. 605(b) that the proposed rules will not have a significant economic impact on a substantial number of small entities. The CFTC invites public comment on this determination.</P>
        <FTNT>
          <P>
            <SU>47</SU>5 U.S.C. 601<E T="03">et seq.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD2">B. Paperwork Reduction Act</HD>
        <P>The Paperwork Reduction Act (PRA)<SU>48</SU>
          <FTREF/>imposes certain requirements on federal agencies (including the Commission) in connection with conducting or sponsoring any collection of information as defined by the PRA. This notice of proposed rulemaking, if approved, would not require a new collection of information from any persons or entities.</P>
        <FTNT>
          <P>
            <SU>48</SU>44 U.S.C. 3507(d).</P>
        </FTNT>
        <HD SOURCE="HD2">C. Consideration of Costs and Benefits</HD>
        <P>Section 15(a) of the CEA<SU>49</SU>
          <FTREF/>requires the Commission to consider the costs and benefits of its action before promulgating a regulation under the CEA. Section 15(a) of the CEA specifies that the costs and benefits shall be evaluated in light of five broad areas of market and public concern: (1) Protection of market participants and the public; (2) efficiency, competitiveness and financial integrity of futures markets; (3) price discovery; (4) sound risk management practices; and (5) other public interest considerations. The Commission may in its discretion give greater weight to any one of the five enumerated areas and could in its discretion determine that, notwithstanding its costs, a particular regulation is necessary or appropriate to protect the public interest or to effectuate any of the provisions or accomplish any of the purposes of the Act.</P>
        <FTNT>
          <P>
            <SU>49</SU>7 U.S.C. 19(a).</P>
        </FTNT>
        <P>The purpose of the proposed compliance schedules is to afford market participants adequate time to comply with the clearing requirement under section 2(h)(1)(A) of the CEA and the trade execution requirements under section 2(h)(8). Without the proposed compliance schedules, market participants could be required to comply with the clearing requirement immediately upon issuance of a mandatory clearing determination by the Commission, and market participants could be required to comply with the trade execution requirement when (1) The Commission has issued a determination that the swap is required to be cleared and (2) any DCM or SEF has made the swap available to trade.</P>
        <P>The Commission recognizes that requiring such immediate compliance with the clearing and trade execution requirements may impose costs on market participants, particularly for market participants that may not be registered with the Commission and those market participants that have hundreds or thousands of third-party subaccounts to bring into compliance with the new requirements under section 2(h) of the CEA.<SU>50</SU>
          <FTREF/>Accordingly, the Commission's proposal provides substantial benefits in that it affords market participants additional time to document new clearing arrangements, connect to market infrastructures, and prepare themselves and their customers for the new regulatory requirements. The Commission believes that such an approach will help protect the public interest by facilitating an orderly transition to a new regulatory environment.</P>
        <FTNT>
          <P>
            <SU>50</SU>
            <E T="03">E.g.,</E>Letter from Richard H. Baker, Managed Funds Association, dated Mar. 24, 2011 at Appendix 1, page 1.</P>
        </FTNT>
        <HD SOURCE="HD3">1. Protection of Market Participants and the Public</HD>
        <P>In devising the proposed compliance schedules, the Commission sought to balance the goal of protecting the public by bringing market participants into compliance with the clearing and trade execution requirements for swaps as quickly as possible while affording market participants adequate time to come into compliance.</P>
        <P>Market participants in Category 1 (<E T="03">e.g.,</E>SDs, MSPs, and active funds) are likely to be among the most experienced and active participants with the resources needed to come into compliance with the clearing and trading requirements more quickly.<SU>51</SU>
          <FTREF/>The swaps entered into by these market participants are likely to represent a significant portion of the total swap market volume. As a result, moving these transactions into central clearing and onto trading platforms before those of Category 2 and 3 Entities would provide additional protection for the public by ensuring that the most active participants in the swap market come into compliance as soon as possible, thus mitigating risk and promoting transparency in significant portions of the swap market.</P>
        <FTNT>
          <P>
            <SU>51</SU>In a letter from the Financial Services Forum, Futures Industry Association, International Swaps and Derivatives Association, and Securities Industry and Financial Markets Association, dated May 4, 2011, commenters noted that “market participants vary dramatically in their resources, market sophistication and rationale for using Swaps. Swap Entities, in general, have greater resources, access to technology and clearing infrastructure than their end user counterparties.”</P>
        </FTNT>
        <P>By requiring Category 2 Entities to comply within 180 days, the Commission is seeking to balance the needs of those market participants that are not registered with the Commission and may not be as active in the swap market with the public interest of bringing all market participants into compliance as soon as possible.</P>
        <P>The market participants in Category 2 are likely to be less experienced and less active participants than those in Category 1. To the extent these market participants are less active in the swap markets the balance between moving their transactions into central clearing and onto trading platforms and giving them additional time to comply with the new requirements, tips in favor of the latter approach. Additionally, these entities may not have the same level of resources as Category 1 Entities. Therefore, they will benefit from the opportunity to document new clearing arrangements, connect to market infrastructures, and prepare themselves and their customers for the new regulatory requirements by considering examples of how Category 1 Entities have met these requirements.</P>
        <P>It should be noted that Category 2 Entities and other market participants wanting to come into compliance before their respective compliance schedule deadlines in order to take advantage of the risk-mitigating benefits of central clearing and executing swaps on trading platforms are allowed, and encouraged, to do so.</P>
        <P>Entities that are third-party subaccounts have the additional challenge of transitioning hundreds, and in some cases, thousands of subaccounts into compliance with the clearing and trade execution requirements. This process may require that these entities negotiate and formalize new agreements with each of their customers. In order to accomplish this they also will need to educate their customers about how clearing and trade execution requirements will affect the costs and processes associated with their accounts. Each of these tasks requires time. By giving third-party subaccounts 270 days to come into compliance, the Commission seeks to balance the need of these entities and their customers for additional time with the benefits of reducing risks in the swap market and protecting the public as quickly as possible.</P>

        <P>It may be that the Category 1 Entities that constitute the first phase under the proposed compliance schedules will bear a larger proportion of the “start-up”<PRTPAGE P="58194"/>costs associated with implementing the clearing and trade execution requirements. They are the entities likely to expend the most resources documenting new clearing arrangements, connecting to market infrastructures, and preparing themselves and their customers for the new regulatory requirements. The Commission is aware of these costs and believes that it is appropriate for the entities that are likely to be among the most active participants in these markets to shoulder a larger percentage of these start-up costs.</P>
        <HD SOURCE="HD3">2. Efficiency, Competitiveness, and Financial Integrity of the Markets</HD>
        <P>By necessity, the first group of market participants that are required to comply with the clearing and trade execution requirements, along with DCOs, DCMs, and SEFs, are likely to work together to establish methods for compliance that other market participants may later consider. The experience with swaps that the first group of market participants brings to this process should help to ensure the integrity and effectiveness of their solutions. These solutions will likely be helpful to other market participants that comply later. For example, entities that are more experienced in the swap market, such as those in Category 1, are likely to have greater technological expertise and will best be able to develop the necessary technological infrastructure.</P>
        <P>It is critical that a cross-section of market participants is involved in developing the solutions that become industry conventions in order to ensure that those approaches promote the efficiency, competitiveness, and integrity of participants on the buy-side and the sell-side. The Commission's proposed compliance schedules address this need. For example, Category 1 includes active funds and MSPs that are likely to have the experience and expertise to represent “buy-side” interests, whereas SDs generally will represent “sell-side” interests.</P>
        <P>In providing Category 1 Entities with 90 days to comply with the clearing and trade execution requirements, the Commission would afford these market participants additional time to identify issues and work to develop solutions. This is likely to result in more efficient problem-solving processes, which may reduce the system-wide start-up costs of implementing new regulations. Moreover, it is also likely to foster a greater degree of compatibility and interoperability among the varied methods of compliance which, in turn, is likely to reduce the cost and complexity of interconnectedness.<SU>52</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>52</SU>
            <E T="03">See</E>TABB Group, “Technology and Financial Reform: Data, Derivatives and Decision Making”, Aug. 2011 at 12.</P>
        </FTNT>
        <P>Lastly, in the absence of the proposed compliance schedules, some entities have expressed concern that they would be unable to comply with the clearing and trading requirements and would choose to leave the swap market or avoid the market for some period of time. If this occurred, it could reduce liquidity and increase spreads in the market. By providing additional time for compliance, this rule reduces the chance that these adverse effects will occur in the swap market during the transition period.</P>
        <HD SOURCE="HD3">3. Price Discovery</HD>
        <P>The trade execution requirement is expected to facilitate price discovery in the swap market. However, a disorderly implementation may inhibit price discovery by creating confusion about which counterparties are prepared to trade specific swaps and which contracts are fungible. An orderly process, however, promotes good communication between counterparties, which is essential to price discovery during the transition period.</P>
        <P>As for costs, to the extent that market participants could comply sooner than the proposed compliance schedule in an effective and efficient manner, this proposed schedule would delay the benefits that would come from increased price transparency that are expected to accompany a trade execution requirement under section 2(h)(8) of the CEA. The Commission's proposed compliance schedule reflects that the Commission anticipates that market participants will need additional time, however, for an orderly implementation process.</P>
        <HD SOURCE="HD3">4. Sound Risk Management Practices</HD>
        <P>To the extent that the proposed compliance schedule for the clearing requirement would delay implementation of mandatory clearing, the swap market could suffer costs in terms of risk management. For example, there are risk management costs associated with not having counterparty credit risk monitored and managed effectively by a DCO. More prompt implementation of mandatory clearing would have the benefit of preventing losses from accumulating over time through the settlement of variation margin between a DCO's clearing members each day. The settlement of variation margin each day reduces both the chance of default and the size of any default should one occur. Delay in implementing mandatory clearing would also postpone the use of initial margin as a performance bond against potential future losses such that if a party fails to meet its obligation to pay variation margin, resulting in a default, the DCO may use the defaulting party's initial margin to cover most or all of any loss based on the need to replace the open position.</P>
        <P>On the other hand, the proposed compliance schedule for the clearing requirement would provide an orderly process for implementing mandatory clearing of swaps, and to the extent that it does so successfully, it will lead to overall sounder risk management practices for the swap market and the broader financial system, particularly during the implementation period. As noted above, in the absence of this rule, some entities may choose not to engage in swap transactions while they work to come into compliance with the new requirements. This result could expose those entities to risks they would otherwise have used swaps to mitigate. Therefore, by providing a timetable for orderly transition, this rule encourages continued participation in the swap markets and makes possible the continued use of swaps during the transition period for risk mitigation purposes.</P>
        <P>Moreover, if market participants were concerned that they might not be able to meet the proposed compliance schedule timelines, it is likely that they would incur additional costs associated with the potential lack of regulatory compliance. Providing additional time for compliance may reduce the costs that participants may incur mitigating legal risks during the transition period, and focuses those resources on achieving compliance.</P>
        <HD SOURCE="HD3">5. Other Public Interest Considerations</HD>
        <P>There are public interest benefits to phasing in compliance using the implementation structure proposed in this release. The proposed implementation structure generally allows market participants to comply with the requirements of Dodd-Frank as quickly and efficiently as possible and thereby provides a sound basis for achieving the overarching Dodd-Frank goals of risk reduction and increased market transparency.</P>

        <P>In sum, the Commission has considered the costs and benefits as required by section 15(a) and is proposing the compliance schedules discussed herein. The Commission invites public comment on its cost-benefit considerations. Commenters are also invited to submit any data or other<PRTPAGE P="58195"/>information that they may have quantifying or qualifying the costs and benefits of the proposal with their comment letters.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>17 CFR Part 37</CFR>
          <P>Commodity futures, Swaps, Swap execution facilities, Registration application, Registered entities, Reporting and recordkeeping requirements.</P>
          <CFR>17 CFR Part 38</CFR>
          <P>Block transaction, Commodity futures, Designated contract markets, Reporting and Recordkeeping requirements, Transactions off the centralized market.</P>
          <CFR>17 CFR Part 39</CFR>
          <P>Business and industry, Commodity futures, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>For the reasons stated in the preamble, the Commission proposes to amend 17 CFR parts 37, 38 and 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 37—SWAP EXECUTION FACILITIES</HD>
          <P>1. The authority citation for part 37 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 1a, 2, 5, 6, 6c, 7, 7a-2, 7b-3 and 12a, as amended by Titles VII and VIII of the Dodd-Frank Wall Street Reform and Consumer Protection Act, Pub. L. 111-203, 124 Stat. 1376 (2010).</P>
          </AUTH>
          
          <P>2. Add § 37.12 to read as follows:</P>
          <SECTION>
            <SECTNO>§ 37.12</SECTNO>
            <SUBJECT>Trade execution compliance schedule.</SUBJECT>
            <P>(a) A swap transaction shall be subject to the requirements of section 2(h)(8)(A) of the Act upon the later of (1) the applicable deadline established under the compliance schedule provided under § 39.5(e)(2); or (2) 30 days after the swap is first made available for trading on either a swap execution facility registered under section 5h of the Act or a board of trade designated as a contract market under section 5 of the Act.</P>
            <P>(b) Nothing in this rule shall prohibit any counterparty from complying voluntarily with the requirements of section 2(h)(8)(A) of the Act sooner than as provided in paragraph (a) of this section.</P>
          </SECTION>
        </PART>
        <PART>
          <HD SOURCE="HED">PART 38—DESIGNATED CONTRACT MARKETS</HD>
          <P>3. The authority citation for part 38 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 1a, 2, 6, 6a, 6c, 6d, 6e, 6f, 6g, 6i, 6j, 6k, 6l, 6m, 6n, 7, 7a-2, 7b, 7b-1, 7b-3, 8, 9, 15, and 21, as amended by the Dodd-Frank Wall Street Reform and Consumer Protection Act, Pub. L. 111-203, 124 Stat. 1376 (2010).</P>
          </AUTH>
          
          <P>4. Add § 38.11 to read as follows:</P>
          <SECTION>
            <SECTNO>§ 38.11</SECTNO>
            <SUBJECT>Trade execution compliance schedule.</SUBJECT>
            <P>(a) A swap transaction shall be subject to the requirements of section 2(h)(8)(A) of the Act upon the later of (1) the applicable deadline established under the compliance schedule provided under § 39.5(e)(2); or (2) 30 days after the swap is first made available for trading on a swap execution facility registered under section 5h of the Act or a board of trade designated as a contract market under section 5 of the Act.</P>
            <P>(b) Nothing in this rule shall prohibit any counterparty from complying voluntarily with the requirements of section 2(h)(8)(A) of the Act sooner than as provided in paragraph (a) of this section.</P>
          </SECTION>
        </PART>
        <PART>
          <HD SOURCE="HED">PART 39—DERIVATIVES CLEARING ORGANIZATIONS</HD>
          <P>5. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 7a-1 as amended by Pub. L. 111-203, 124 Stat. 1376.</P>
          </AUTH>
          
          <P>6. Amend § 39.5 to add paragraph (e) to read as follows:</P>
          <SECTION>
            <SECTNO>§ 39.5</SECTNO>
            <SUBJECT>Review of swaps for Commission determination on clearing requirement.</SUBJECT>
            <STARS/>
            <P>(e)<E T="03">Mandatory clearing compliance schedule.</E>(1)<E T="03">Definitions.</E>For the purposes of this paragraph:</P>
            <P>
              <E T="03">Category 1 Entity</E>means (1) a swap dealer, (2) a security-based swap dealer; (3) a major swap participant; (4) a major security-based swap participant; or (5) an active fund.</P>
            <P>
              <E T="03">Category 2 Entity</E>means (1) a commodity pool; (2) a private fund as defined in section 202(a) of the Investment Advisors Act of 1940 other than an active fund; (3) an employee benefit plan as defined in paragraphs (3) and (32) of section 3 of the Employee Retirement Income and Security Act of 1974; or (4) a person predominantly engaged in activities that are in the business of banking, or in activities that are financial in nature as defined in section 4(k) of the Bank Holding Company Act of 1956,<E T="03">provided that,</E>in each case, the entity is not a third-party subaccount.</P>
            <P>
              <E T="03">Active Fund</E>means any private fund as defined in section 202(a) of the Investment Advisors Act of 1940, that is not a third-party subaccount and that executes 20 or more swaps per month based on a monthly average over the 12 months preceding the Commission issuing a mandatory clearing determination under section 2(h)(2) of the Act.</P>
            <P>
              <E T="03">Third-party Subaccount</E>means a managed account that requires specific approval by the beneficial owner of the account to execute documentation necessary for executing, confirming, margining, or clearing swaps.</P>
            <P>(2) Upon issuing a mandatory clearing determination under section 2(h)(2) of the Act, the Commission may determine, based on the group, category, type or class of swaps subject to such determination, that the following schedule for compliance with the requirements of section 2(h)(1)(A) of the Act shall apply:</P>
            <P>(i) A swap transaction between a Category 1 Entity and another Category 1 Entity, or any other entity that desires to clear the transaction, must comply with the requirements of section 2(h)(1)(A) of the Act no later than ninety (90) days after the effective date set by the Commission for such mandatory clearing determination.</P>
            <P>(ii) A swap transaction between a Category 2 Entity and a Category 1 Entity, another Category 2 Entity, or any other entity that desires to clear the transaction, must comply with the requirements of section 2(h)(1)(A) of the Act no later than one hundred and eighty (180) days after the effective date set by the Commission for such mandatory clearing determination.</P>
            <P>(iii) All other swap transactions not eligible to claim the exception from mandatory clearing set forth in section 2(h)(7) of the Act and § 39.6, must comply with the requirements of section 2(h)(1)(A) of the Act no later than two hundred and seventy (270) days after the effective date set by the Commission for such mandatory clearing determination.</P>
            <P>(3) Nothing in this rule shall be construed to prohibit any person from voluntarily complying with the requirements of section 2(h)(1)(A) of the Act sooner than the implementation schedule provided under paragraph (2).</P>
          </SECTION>
          <SIG>
            <DATED/>
            <P>Issued in Washington, DC, on September 8, 2011, by the Commission.</P>
            <NAME>David A. Stawick,</NAME>
            <TITLE>Secretary of the Commission.</TITLE>
          </SIG>
          <PRTPAGE P="58196"/>
          <HD SOURCE="HD1">Appendices to Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA—Commissioners Voting Summary and Statements of Commissioners</HD>
          <NOTE>
            <HD SOURCE="HED">NOTE:</HD>
            <P>The following appendices will not appear in the Code of Federal Regulations</P>
          </NOTE>
          <HD SOURCE="HD1">Appendix 1—Commissioners Voting Summary</HD>
          <EXTRACT>
            <P>On this matter, Chairman Gensler and Commissioners Dunn, Sommers, and Chilton voted in the affirmative; Commissioner O'Malia voted in the negative.</P>
          </EXTRACT>
          <HD SOURCE="HD1">Appendix 2—Statement of Chairman Gary Gensler</HD>
          <EXTRACT>
            <P>I support the proposed rule to establish schedules to phase in compliance with the clearing and trade execution requirement provisions in the Dodd-Frank Wall Street Reform and Consumer Protection Act. The proposal would provide greater clarity to market participants regarding the timeframe for bringing their swap transactions into compliance with the clearing and trade execution requirements. The rule also would make the market more open and transparent, while giving market participants an adequate amount of time to comply. The proposed rule would help facilitate an orderly transition to a new regulatory environment for swaps.</P>
          </EXTRACT>
          <HD SOURCE="HD1">Appendix 3—Statement of Commissioner Jill Sommers</HD>
          <EXTRACT>
            <P>I support this proposal to establish a schedule to phase in compliance with certain statutory provisions under Title VII of the Dodd-Frank Act because this will give market participants some degree of certainty about implementation deadlines. However, I believe the Commission should have provided a broader implementation plan encompassing all of the rulemakings under Dodd Frank, rather than the much narrower portion covered by today's proposed rulemaking. In addition, the proposed rule fails to address a critical component of the trade execution requirement in Section 2(h)(8) of the Commodity Exchange Act. That is, what does it mean to “make a swap available to trade?”</P>
            <P>I believe the Commission should clarify who makes the determination that a swap is “made available for trading” and how the decision is to be made, just as the Commission has done with respect to the clearing requirement. This would provide the public with an opportunity to comment on a proposed mechanism for such a determination. In a consultation paper published by the European Commission's Directorate General on Internal Markets and Services on December 8, 2010, the European Commission put forth the idea that the European Securities and Markets Authority, or ESMA, “could assess and decide when a derivative which is eligible for clearing is sufficiently liquid to be traded exclusively” on a trading platform.<SU>53</SU>
              <FTREF/>The European Commission noted that ESMA could base its decision on “the frequency of trades in a given derivative and the average size of transactions,” and solicited comments from the public on which criteria could determine whether a derivative is sufficiently liquid to be required to be traded on a platform.</P>
            <FTNT>
              <P>

                <SU>53</SU>Public Consultation: Review of the Markets in Financial Instruments Directive (MiFID) (December 8, 2010), available at<E T="03">http://ec.europa.eu/internal_market/consultations/docs/2010/mifid/consultation_paper_en.pdf.</E>
              </P>
            </FTNT>
            <P>Both the Dodd-Frank Act and proposed regulations in the European Union require consideration of trading liquidity, in addition to other factors, before a determination is made that a swap is required to be cleared. The Commission should address whether any additional factors will be considered as part of a determination on the trade execution requirement.</P>
            <P>Though I support today's proposal, I believe the Commission should clarify who makes the determination that a swap is “made available for trading” and how that decision will be made.</P>
          </EXTRACT>
          <HD SOURCE="HD1">Appendix 4— Statement of Commissioner Scott O'Malia</HD>
          <EXTRACT>
            <P>I respectfully dissent from the Commission's decision today to approve for Federal Register publication two rule proposals related to implementation entitled “Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA” and “Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements under Section 4s of the CEA.” For quite some time, I have been asking that the Commission publish for notice and comment a comprehensive implementation schedule that addresses the entire mosaic of rule proposals under the Dodd-Frank Act. I believe the Commission should have proposed a comprehensive schedule that detailed, at a minimum:</P>
            <P>• for each registered entity (e.g., swap dealer and major swap participants), compliance dates for each of its entity-specific obligations (e.g., all obligations under Section 4s of the Commodity Exchange Act) under Dodd-Frank; and</P>
            <P>• for each market-wide obligation (e.g., the clearing and trading mandates), the entities affected (whether registered or unregistered) along with appropriate compliance dates.</P>
            <P>Such a schedule would have complemented and informed existing proposals and provided structure to future determinations. Additionally, a proposal regarding such a schedule should have adequately analyzed the costs and benefits of alternatives, including appropriate quantification. Unfortunately, the two rule proposals that the Commission approved today fail to either propose a comprehensive schedule or provide an adequate cost benefit analysis.</P>
            <P>The Commission's proposals also fail to request comment on a number of issues that I believe are important considerations in developing an implementation plan. As a result, I am encouraging commenters to submit responses to the questions below as part of their comments on the two rule proposals.</P>
            <HD SOURCE="HD2">Swap Transaction Compliance and Implementation Schedule: Clearing and Trade Execution Requirements under Section 2(h) of the CEA</HD>
            <P>• Should the Commission provide guidance on how it will make and communicate a mandatory clearing determination prior to considering the first such determination? If so, what information should be included in guidance?</P>
            <P>• As section II(E) of the proposal states: “When issuing a mandatory clearing determination, the Commission would set an effective date by which all market participants would have to comply. In other words, the proposed compliance schedules would be used only when the Commission believes that phasing is necessary based on the considerations outlined in this release. The Commission will provide the public with notice of its intent to rely upon the compliance schedule pursuant to the process outlined in § 39.5(b)(5).” To afford more certainty to market participants, should the Commission instead create a presumption that it will rely on the compliance schedule for each mandatory clearing determination that it issues, unless it finds that the compliance schedule is not necessary to achieve the benefits set forth in the proposal (e.g., facilitating the transition to the new regulatory regime established by the Dodd-Frank Act in an orderly manner that does not unduly disrupt markets and transactions)?</P>
            <P>• What, if any, other issues not addressed in current proposed or final rulemakings should the Commission have taken into consideration when proposing the compliance schedule? For example, should the Commission have considered the extent to which its clearing and trade execution requirements apply to entities and transactions located outside the United States? Also, should the Commission have considered the extent to which such requirements apply to transactions between affiliates (whether domestic or cross-border)? If applicable, how should the Commission adjust the proposed compliance schedule to account for such issues?</P>
            <P>• What, if any, adjustments should the Commission make to the proposed compliance schedule for trade execution requirements if the Commission makes a determination that a group, category, type, or class of swaps, rather than a specific swap, is subject to mandatory clearing? Would such adjustments vary depending on the manner in which the Commission defines group, category, type, or class?</P>
            <HD SOURCE="HD2">Swap Transaction Compliance and Implementation Schedule: Trading Documentation and Margining Requirements under Section 4s of the CEA</HD>

            <P>• What, if any, other issues not addressed in current proposed or final rulemakings should the Commission have taken into consideration when proposing the<PRTPAGE P="58197"/>compliance schedule? For example, should the Commission have considered the extent to which its documentation and margin requirements apply to entities and transactions located outside the United States? Also, should the Commission have considered the extent to which such requirements apply to transactions between affiliates (whether domestic or cross-border)? If applicable, how should the Commission adjust the proposed compliance schedule to account for such issues?</P>
            <P>Finally, I want to be clear that I support completing the final Dodd-Frank rulemakings in a reasonable time frame. I believe that the timely implementation of such rulemakings is important. Knowing when and how the markets are required to do what is vital to the success of implementing the new market structure required under the Dodd-Frank Act. When billions of dollars are at stake, you simply do not rely on guesses and estimates based on vague conditions.</P>
          </EXTRACT>
          
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-24124 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6351-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
        <SUBAGY>Bureau of Prisons</SUBAGY>
        <CFR>28 CFR Part 570</CFR>
        <DEPDOC>[BOP Docket No. 1151]</DEPDOC>
        <RIN>RIN 1120-AB61</RIN>
        <SUBJECT>Pre-Release Community Confinement</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Bureau of Prisons, Justice.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this document, the Bureau of Prisons (Bureau) responds to recent litigation surrounding the pre-release community confinement regulation which it published on October 21, 2008 by publishing a proposed rule on this subject.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments are due by November 21, 2011.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit comments to the Rules Unit, Office of General Counsel, Bureau of Prisons, 320 First Street, NW., Washington, DC 20534. You may view an electronic version of this rule at<E T="03">http://www.regulations.gov.</E>You may also comment via the Internet to the Bureau at<E T="03">BOPRULES@BOP.GOV</E>or by using the<E T="03">http://www.regulations.gov</E>comment form for this regulation. When submitting comments electronically, you must include the BOP Docket No. in the subject box.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Sarah Qureshi, Office of General Counsel, Bureau of Prisons, phone (202) 307-2105.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Posting of Public Comments</HD>

        <P>Please note that all comments received are considered part of the public record and are available for public inspection online at<E T="03">http://www.regulations.gov.</E>Such information includes personal identifying information (such as your name, address, etc.) voluntarily submitted by the commenter.</P>
        <P>If you want to submit personal identifying information (such as your name, address, etc.) as part of your comment, but do not want it to be posted online, you must include the phrase “PERSONAL IDENTIFYING INFORMATION” in the first paragraph of your comment. You must also locate all the personal identifying information you do not want posted online in the first paragraph of your comment and identify what information you want redacted.</P>

        <P>If you want to submit confidential business information as part of your comment but do not want it to be posted online, you must include the phrase “CONFIDENTIAL BUSINESS INFORMATION” in the first paragraph of your comment. You must also prominently identify confidential business information to be redacted within the comment. If a comment contains so much confidential business information that it cannot be effectively redacted, all or part of that comment may not be posted on<E T="03">http://www.regulations.gov.</E>
        </P>

        <P>Personal identifying information identified and located as set forth above will be placed in the agency's public docket file, but not posted online. Confidential business information identified and located as set forth above will not be placed in the public docket file. If you wish to inspect the agency's public docket file in person by appointment, please see the<E T="02">FOR FURTHER INFORMATION CONTACT</E>paragraph.</P>
        <HD SOURCE="HD1">The Proposed Rule</HD>
        <P>In this document, the Bureau of Prisons (Bureau) responds to recent litigation surrounding the pre-release community confinement regulation which it published on October 21, 2008 (73 FR 62443) (2008 regulations) by publishing a proposed rule on this subject.</P>
        <P>The interim rule published in 2008 revised the Bureau's regulations on pre-release community confinement in 28 CFR part 570, subpart B, to conform with the requirements of the Second Chance Act of 2007, approved April 9th, 2008 (Pub. L. 110-199; 122 Stat. 657) (“Second Chance Act”).</P>

        <P>In an opinion filed on June 16, 2010, the District Court for the District of Oregon upheld Bureau policies issued following the Second Chance Act, finding that they are “internal agency guidelines which do not trigger the procedural requirements of 5 U.S.C. § 553,” but invalidated the 2008 interim rule on the grounds that the Bureau did not “establish good cause to forego advance notice and comment” under the Administrative Procedure Act (5 U.S.C. 552,<E T="03">et seq.</E>).<E T="03">Sacora</E>v.<E T="03">Thomas,</E>No. CV 08-578-MA (D. Or. June 16, 2010). The court enjoined the BOP “from considering inmates for pre-release RRC [Residential Re-entry Centers] placement pursuant to 28 CFR 570.20-22 until such time as regulations are promulgated in accordance with 5 U.S.C. 553(b).” We now issue this proposed rule in order to comply with the court's determination. The proposed rule is identical to the 2008 interim rule, and we therefore reprint the rationale for the interim rule below as the rationale for this proposed rule.</P>
        <P>Prior to October 21, 2008, the community confinement regulations implemented the Bureau's categorical exercise of discretion for designating inmates to community confinement. The regulations stated that the Bureau would designate inmates to community confinement only as a condition of pre-release custody and programming, during the last ten percent of the prison sentence being served, for a period not exceeding six months, unless specific Bureau programs allow greater periods of community confinement.</P>
        <P>To conform these regulations to the language of the Second Chance Act, we made the following revisions:</P>
        <HD SOURCE="HD2">Section 570.20Purpose</HD>
        <P>In this regulation, we describe the Bureau's procedures for designating inmates to pre-release community confinement or home detention. We also provide a new definition of the term “community confinement.” Section 231(f) of the Second Chance Act amended 18 U.S.C. 3621 by adding a new subsection (g). New 18 U.S.C. 3621(g)(2) defines the term “community confinement” for purposes of that subsection by adopting the meaning “given that term in the application notes under section 5F1.1 of the Federal Sentencing Guidelines Manual” in effect on the date of enactment of the Act. On April 9, 2008, the application notes to United States Sentencing Guideline (USSG) § 5F1.1 read in pertinent part as follows:</P>
        
        <EXTRACT>

          <P>“Community confinement” means residence in a community treatment center, halfway house, restitution center, mental<PRTPAGE P="58198"/>health facility, alcohol or drug rehabilitation center, or other community facility; and participation in gainful employment, employment search efforts, community service, vocational training, treatment, educational programs, or similar facility-approved programs during non-residential hours.</P>
        </EXTRACT>
        
        <P>Although new subsection 18 U.S.C. 3621(g) relates on its face only to “continued access to medical care,” we adopt the definition of community confinement given in this provision for the purposes of subpart B as amended. The Second Chance Act itself variously uses the terms “community confinement,” “community corrections agencies,” “community corrections facilities,” and “community confinement facilities,” but it does so in contexts that indicate that these terms are meant to refer to the concept of community confinement generally. We therefore adopt the definition in 18 U.S.C. 3621(g) for clarity and consistency, and to maintain uniformity in application of the Second Chance Act provisions, we adopt this definition of “community confinement” as applicable in the context of these regulations. For clarity, we also add a parenthetical that explains that the Bureau includes residential re-entry centers in the definition of “community confinement.”</P>
        <P>In this section, we also add a definition of “home detention.” Section 231(g)(5)(B) of the Second Chance Act provides that “[t]he term `home detention' has the same meaning given the term in the Federal Sentencing Guidelines as of the date of the enactment of this Act * * *.” Once more, although this reference to the Federal Sentencing Guidelines is articulated in a different context, we deem it prudent to model our definition on that given by the Federal Sentencing Guidelines, as suggested by the Second Chance Act, for clarity and consistency in application.</P>
        <P>In this section, therefore, we include a definition of “home detention” which is derived from USSG 5F1.2. Specifically, we define “home detention” as a program of confinement and supervision that restricts the defendant to his or her place of residence continuously, except for authorized absences, enforced by appropriate means of surveillance by the probation office or other monitoring authority. We add the phrase “or other monitoring authority” to the definition given by USSG 5F1.2 to allow for the possibility that the function of monitoring may be accomplished by other federal government agencies, employees, or contractors.</P>
        <HD SOURCE="HD2">Section 570.21Time-frames</HD>
        <P>Section 251(a) of the Second Chance Act amends 18 U.S.C. 3624(c) to require that the Director must, “to the extent practicable, ensure that a prisoner serving a term of imprisonment spends a portion of the final months of that term (not to exceed 12 months), under conditions that will afford that prisoner a reasonable opportunity to adjust to and prepare for the reentry of that prisoner into the community.” Further, section 3624(c) is amended to state that “[t]he authority under this subsection may be used to place a prisoner in home confinement for the shorter of 10 percent of the term of imprisonment of that prisoner or 6 months.”</P>
        <P>In this section, we therefore make the following changes to conform to the specific language in section 251(a) of the Second Chance Act: Paragraph (a) of the revised § 570.21 states that inmates may be designated to community confinement as a condition of pre-release custody and programming during the final months of the inmate's term of imprisonment, not to exceed twelve months; and paragraph (b) of the revised § 570.21 states that inmates may be designated to home detention as a condition of pre-release custody and programming during the final months of the inmate's term of imprisonment, not to exceed the shorter of ten percent of the term of the inmate's imprisonment or six months.</P>
        <HD SOURCE="HD2">Section 570.22Designation</HD>
        <P>In this section, we inform inmates that they will be considered for pre-release community confinement in a manner consistent with 18 U.S.C. 3621(b), determined on an individual basis, and of duration sufficient to optimize the likelihood of successful reintegration into the community. This section reflects the requirements of the Second Chance Act regarding the promulgation of these regulations. Section 251(a)(6) of the Second Chance Act requires the Bureau to implement regulations that ensure that placements in community confinement as a condition of pre-release custody are:</P>
        <P>• Conducted in a manner consistent with 18 U.S.C. 3621(b);</P>
        <P>• Determined on an individual basis; and</P>
        <P>• Long enough “to provide the greatest likelihood of successful reintegration into the community.” Section 570.22 reflects the three factors listed above.</P>
        <P>With regard to the requirement that determinations regarding pre-release community confinement are “conducted in a manner consistent with 18 U.S.C. 3621(b),” the Bureau will ensure that the following factors listed in section 3621(b) will be considered in making such determinations:</P>
        <P>• The resources of the facility contemplated;</P>
        <P>• The nature and circumstances of the offense;</P>
        <P>• The history and characteristics of the prisoner;</P>
        <P>• Any statement by the sentencing court concerning the purpose for which the sentence was imposed or recommending a specific type of institution; and</P>
        <P>• Any pertinent policy statements issued by the United States Sentencing Commission.</P>
        <HD SOURCE="HD1">Executive Order 12866</HD>
        <P>This rule falls within a category of actions that the Office of Management and Budget (OMB) has determined to constitute a “significant regulatory action” under section 3(f) of Executive Order 12866 and, accordingly, it was reviewed by OMB.</P>
        <P>The Bureau has assessed the costs and benefits of this rule as required by Executive Order 12866 Section 1(b)(6) and has made a reasoned determination that the benefits of this rule justify its costs. This rule will have the benefit of eliminating confusion in the courts that has been caused by the changes in the Bureau's statutory interpretation, while allowing us to continue to operate in compliance with the revised statute. There will be no new costs associated with this rulemaking.</P>
        <HD SOURCE="HD1">Executive Order 13132</HD>
        <P>This regulation will not have substantial direct effects on the States, on the relationship between the national government and the States, or on distribution of power and responsibilities among the various levels of government. Therefore, under Executive Order 13132, we determine that this rule does not have sufficient Federalism implications to warrant the preparation of a Federalism Assessment.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>

        <P>The Director of the Bureau of Prisons, under the Regulatory Flexibility Act (5 U.S.C. 605(b)), reviewed this regulation and by approving it certifies that it will not have a significant economic impact upon a substantial number of small entities for the following reasons: This rule pertains to the correctional management of offenders committed to the custody of the Attorney General or the Director of the Bureau of Prisons, and its economic impact is limited to the Bureau's appropriated funds.<PRTPAGE P="58199"/>
        </P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995</HD>
        <P>This rule will not result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more in any one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
        <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act of 1996</HD>
        <P>This rule is not a major rule as defined by § 804 of the Small Business Regulatory Enforcement Fairness Act of 1996. This rule will not result in an annual effect on the economy of $100,000,000 or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 28 CFR Part 570</HD>
          <P>Prisoners.</P>
        </LSTSUB>
        <SIG>
          <NAME>Thomas R. Kane,</NAME>
          <TITLE>Acting Director, Bureau of Prisons.</TITLE>
        </SIG>
        <P>Under rulemaking authority vested in the Attorney General in 5 U.S.C. 301; 28 U.S.C. 509, 510 and delegated to the Director, Bureau of Prisons, we propose to revise 28 CFR part 570 as set forth below.</P>
        <CHAPTER>
          <HD SOURCE="HED">Subchapter D—Community Programs and Release</HD>
          <PART>
            <HD SOURCE="HED">PART 570—COMMUNITY PROGRAMS</HD>
            <P>1. Revise the authority citation for 28 CFR part 570 to read as follows:</P>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>5 U.S.C. 301; 18 U.S.C. 751, 3621, 3622, 3624, 4001, 4042, 4081, 4082 (Repealed in part as to offenses committed on or after November 1, 1987), 4161-4166, 5006-5024 (Repealed October 12, 1984, as to offenses committed after that date), 5039; 28 U.S.C. 509, 510.</P>
            </AUTH>
            
            <P>2. In part 570, subpart B is revised to read as follows:</P>
            <SUBPART>
              <HD SOURCE="HED">Subpart B—Pre-Release Community Confinement</HD>
            </SUBPART>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>570.20</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <SECTNO>570.21</SECTNO>
              <SUBJECT>Time-frames.</SUBJECT>
              <SECTNO>570.22</SECTNO>
              <SUBJECT>Designation.</SUBJECT>
            </CONTENTS>
            <SECTION>
              <SECTNO>§ 570.20</SECTNO>
              <SUBJECT>Purpose.</SUBJECT>
              <P>The purpose of this subpart is to provide the procedures of the Bureau of Prisons (Bureau) for designating inmates to pre-release community confinement or home detention.</P>
              <P>(a)<E T="03">Community confinement</E>is defined as residence in a community treatment center, halfway house, restitution center, mental health facility, alcohol or drug rehabilitation center, or other community correctional facility (including residential re-entry centers); and participation in gainful employment, employment search efforts, community service, vocational training, treatment, educational programs, or similar facility-approved programs during non-residential hours.</P>
              <P>(b)<E T="03">Home detention</E>is defined as a program of confinement and supervision that restricts the defendant to his place of residence continuously, except for authorized absences, enforced by appropriate means of surveillance by the probation office or other monitoring authority.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 570.21</SECTNO>
              <SUBJECT>Time-frames.</SUBJECT>
              <P>(a)<E T="03">Community confinement.</E>Inmates may be designated to community confinement as a condition of pre-release custody and programming during the final months of the inmate's term of imprisonment, not to exceed twelve months.</P>
              <P>(b)<E T="03">Home detention.</E>Inmates may be designated to home detention as a condition of pre-release custody and programming during the final months of the inmate's term of imprisonment, not to exceed the shorter of ten percent of the inmate's term of imprisonment or six months.</P>
              <P>(c)<E T="03">Exceeding time-frames.</E>These time-frames may be exceeded when separate statutory authority allows greater periods of community confinement as a condition of pre-release custody.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 570.22</SECTNO>
              <SUBJECT>Designation.</SUBJECT>
              <P>Inmates will be considered for pre-release community confinement in a manner consistent with 18 U.S.C. Section 3621(b), determined on an individual basis, and of sufficient duration to provide the greatest likelihood of successful reintegration into the community, within the time-frames set forth in this part.</P>
              
            </SECTION>
          </PART>
        </CHAPTER>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23684 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4410-05-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <CFR>32 CFR Part 199</CFR>
        <DEPDOC>[Docket ID: DOD-2011-HA-0038]</DEPDOC>
        <RIN>RIN 0720-AB50</RIN>
        <SUBJECT>TRICARE; Smoking Cessation Program Under TRICARE</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, Department of Defense.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This proposed rule implements Section 713 of the Duncan Hunter National Defense Authorization Act (NDAA) for Fiscal Year 2009 (FY 2009), Public Law 110-417. Section 713 states the Secretary shall establish a smoking cessation program under the TRICARE program. The smoking cessation program under TRICARE shall, at a minimum, include the following: the availability, at no cost to the beneficiary, of pharmaceuticals used for smoking cessation, with the limitation on the availability of such pharmaceuticals to the mail-order pharmacy program under the TRICARE program; smoking cessation counseling; access to a toll-free quit line 24 hours a day, 7 days a week; and access to print and Internet web-based tobacco cessation material. Per the statute, Medicare-eligible beneficiaries are excluded from the TRICARE smoking cessation program.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments received at the address indicated below by November 21, 2011 will be accepted.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number or Regulatory Information Number (RIN) and title, by any of the following methods:</P>
          <P>
            <E T="03">Federal Rulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>
            <E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or RIN for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Barbara (Bobbie) Matthews, Medical<PRTPAGE P="58200"/>Benefits and Reimbursement Branch, TRICARE Management Activity, telephone (303) 676-3558.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>The Duncan Hunter NDAA for FY 2009 (Pub. L. 110-417) provides authority for establishment of a smoking cessation program under the TRICARE program. Prior to enactment of Section 713 of the Duncan Hunter NDAA FY09 (Pub. L. 110-417), all supplies and services related to “stop smoking” programs were excluded from TRICARE coverage per the regulation, 32 Code of Federal Regulations (CFR) 199.4(g)(65).</P>
        <P>Smoking is the number one cause of<E T="03">preventable</E>illness and disease in the United States and yet, the prevalence of smoking among TRICARE beneficiaries exceeds that of the general population. According to the Centers for Disease Control and Prevention (CDC), adverse health effects from smoking account for an estimated 443,000 deaths in the United States each year.</P>
        <P>Smoking causes respiratory diseases such as emphysema, bronchitis, and chronic airway obstruction. It also causes several types of cancers including, but not limited to, esophageal, oral cavity, uterine, and lung cancer. In fact, the CDC estimates that 90 percent of lung cancer deaths in men and 80 percent in women are caused by smoking.</P>
        <P>Smoking also puts individuals at increased risk for several other types of diseases and adverse health outcomes such as coronary artery disease, chronic obstructive lung diseases, peripheral vascular disease, heart attack, and stroke. In addition, it increases the risk of infertility, preterm delivery, stillbirth, low birth weight, and sudden infant death syndrome.</P>

        <P>Smoking and its related adverse effects pose a significant challenge for more than two million TRICARE beneficiaries. Establishment of the TRICARE smoking cessation program attempts to reduce the number of TRICARE beneficiaries who are nicotine dependant, thereby improving the health of the TRICARE beneficiary population and reducing Department of Defense costs, in particular those related to the adverse effects of smoking. For further information on TRICARE and the benefits provided under the TRICARE program, please visit<E T="03">http://www.tricare.mil.</E>
        </P>
        <HD SOURCE="HD1">II. Section 713 of the Duncan Hunter NDAA for FY 2009</HD>
        <P>This proposed rule implements Section 713 of the Duncan Hunter NDAA for FY 2009. Section 713 stipulates the following key features for inclusion in the TRICARE smoking cessation program:</P>
        <P>(1) The availability, at no cost to the beneficiary, of pharmaceuticals used for smoking cessation, with a limitation on the availability of such pharmaceuticals to the national mail-order pharmacy program under the TRICARE program if appropriate.</P>
        <P>(2) Counseling.</P>
        <P>(3) Access to a toll-free quit line that is available 24 hours a day, 7 days a week.</P>
        <P>(4) Access to print and Internet web-based tobacco cessation material.</P>
        <P>(5) Chain of command involvement by officers in the chain of command of participants in the program who are on active duty.</P>
        <P>Additionally, Section 713 of NDAA FY 2009 stated the TRICARE smoking cessation program shall not be made available to Medicare-eligible beneficiaries. The statutory language further stated that refunds of copayments paid by Medicare-eligible beneficiaries are available during fiscal year 2009, subject to the specific availability of appropriations for this purpose. However, this authority was not extended beyond FY 2009; consequently, no action is required by TRICARE regarding this provision.</P>
        <HD SOURCE="HD1">III. Provisions of Proposed Rule</HD>
        <P>This proposed rule establishes a smoking cessation program under the TRICARE program. The TRICARE smoking cessation program will be available to all TRICARE beneficiaries who reside in one of the 50 United States or the District of Columbia who are not eligible for Medicare benefits authorized under Title XVIII of the Social Security Act. In general, the TRICARE smoking cessation program will not be available to TRICARE beneficiaries who reside overseas except that under authority of 32 CFR 199.17 of this part, active duty service members and active duty dependents residing overseas including the U.S. territories of Guam, Puerto Rico, and the Virgin Islands who are enrolled in TRICARE Prime at a military treatment facility may have access to those services that the ASD(HA) has determined may be reasonably provided overseas.</P>
        <P>It is the intent of the Department to provide access to smoking cessation pharmaceuticals and web based smoking cessation materials overseas where feasible. However, beneficiaries residing in certain areas overseas may not have easy access to the mail services, equipment or technology needed to receive these smoking cessation benefits and in those areas there is no requirement to make them available. For example, there is no intent by the Department to make the web based services available in areas where there are no web based carriers to provide such a service. Additionally, the laws and our treaties with various countries restrict the mailing of pharmaceuticals into the country. If such laws or treaties do not allow the delivery of the pharmaceuticals through the TRICARE Mail Order Pharmacy (TMOP), it is not the intent of the Secretary to provide the pharmaceutical benefit in those areas through this mechanism.</P>

        <P>At this time, it is not the intent of the Department to provide access to the toll free quit line overseas due to the technological barriers and cost involved in providing this service. In addition, it is not the intent of the Department at this time to make face-to-face smoking cessation counseling available overseas through the local economy. However, in accordance with 32 CFR 199.17 of this part should the ASD(HA) determine that it is technologically, economically, or otherwise feasible to provide additional benefits or it becomes impractical to continue the benefits and services overseas, the ASD(HA) may use this authority to add or modify any benefit or service. The use of this authority shall be published in the<E T="04">Federal Register</E>.</P>
        <P>There will be no requirement for an eligible beneficiary to be diagnosed with a smoking related illness in order to access benefits under the TRICARE smoking cessation program. Benefits under this program will include, at no cost to the beneficiary, pharmaceuticals used for smoking cessation, with a limitation on the availability of such pharmaceuticals to the national mail-order pharmacy program under the TRICARE program; smoking cessation counseling; access to a toll-free quit line 24 hours a day, 7 days a week; and access to print and internet web-based tobacco cessation materials.</P>
        <HD SOURCE="HD1">IV. Regulatory Procedures</HD>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>

        <P>Section 801 of title 5, United States Code, and Executive Orders 12866 and 13563 require certain regulatory assessments and procedures for any major rule or significant regulatory action, defined as one that would result in an annual effect of $100 million or more on the national economy or which would have other substantial impacts.<PRTPAGE P="58201"/>This proposed rule is not a significant regulatory action.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (RFA) (5 U.S.C. 601)</HD>
        <P>Public Law 96-354, “Regulatory Flexibility Act” (RFA) (5 U.S.C. 601), requires that each Federal agency prepare a regulatory flexibility analysis when the agency issues a regulation which would have a significant impact on a substantial number of small entities. This proposed rule will not have a significant impact on a substantial number of small entities. Therefore, this proposed rule is not subject to the requirements of the RFA.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>This rule does not contain a “collection of information” requirement, and will not impose additional information collection requirements on the public under Pub. L. 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35).</P>
        <HD SOURCE="HD2">Public Law 104-4, Section 202, “Unfunded Mandates Reform Act”</HD>
        <P>Section 202 of Public Law 104-4, “Unfunded Mandates Reform Act,” requires that an analysis be performed to determine whether any federal mandate may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector of $100 million in any one year. This proposed rule does not contain a Federal mandate that may result in the expenditure by State, local and tribal governments, in aggregate, or by the private sector, of $100 million or more in any one year, and thus this proposed rule is not subject to this requirement.</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>Executive Order 13132, “Federalism,” requires that an impact analysis be performed to determine whether the rule has federalism implications that would 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. This proposed rule does not have federalism implications, as set forth in Executive Order 13132.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 199</HD>
          <P>Claims, Dental health, Health care, Health insurance, Individuals with disabilities, Military personnel.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 199 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 199—[AMENDED]</HD>
          <P>1. The authority citation for Part 199 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 301; 10 U.S.C. Chapter 55.</P>
          </AUTH>
          
          <P>2. Section 199.4 is amended by:</P>
          <P>a. Revising paragraph (d)(3)(vi).</P>
          <P>b. Adding new paragraph (d)(3)(vi)(C).</P>
          <P>c. Adding new paragraph (e)(28).</P>
          <P>d. Revising paragraph (g)(39).</P>
          <P>e. Removing and reserving paragraph (g)(65).</P>
          <P>The revisions and additions read as follows:</P>
          <SECTION>
            <SECTNO>§ 199.4</SECTNO>
            <SUBJECT>TRICARE—Basic Program Benefits.</SUBJECT>
            <STARS/>
            <P>(d)<E T="03">Other benefits.</E>
            </P>
            <STARS/>
            <P>(3)<E T="03">Other covered services or supplies.</E>
            </P>
            <STARS/>
            <P>(vi)<E T="03">Drugs and medicines.</E>Drugs and medicines that by United States law require a prescription are also referred to as “legend drugs.” Legend drugs are covered when prescribed by a physician or other authorized individual professional provider acting within the scope of the provider's license and ordered or prescribed in connection with an otherwise covered condition or treatment, and not otherwise excluded by TRICARE. This includes Rh immune globulin.</P>
            <P>(A) * * *</P>
            <P>(B) * * *</P>
            <P>(C) Over-the-counter (OTC) drugs (drugs that by United States law do not require a prescription), in general, are not covered. However, insulin is covered for a known diabetic even in states that do not require a prescription for its purchase. In addition, OTC drugs used for smoking cessation are covered when all requirements under the TRICARE smoking cessation program are met as provided in paragraph (e)(28) of this section.</P>
            <STARS/>
            <P>(e)<E T="03">Special benefit information.</E>
            </P>
            <STARS/>
            <P>(28)<E T="03">Smoking cessation program.</E>The TRICARE smoking cessation program is a behavioral modification program to assist eligible beneficiaries who desire to quit smoking. The program consists of a pharmaceutical benefit; smoking cessation counseling; access to a toll-free quit line for non-medical assistance; and, access to print and Internet Web-based tobacco cessation materials.</P>
            <P>(i)<E T="03">Availability.</E>The TRICARE smoking cessation program is available to all TRICARE beneficiaries who reside in one of the 50 United States or the District of Columbia who are not eligible for Medicare benefits authorized under Title XVIII of the Social Security Act. In addition, pursuant to section 199.17 of this Part, if authorized by the Assistant Secretary of Defense (Health Affairs), the TRICARE smoking cessation program may be implemented in whole or in part in areas outside the 50 states and the District of Columbia for active duty members and their dependents who are enrolled in TRICARE Prime (overseas Prime beneficiaries). In such cases, the Assistant Secretary of Defense (Health Affairs) may also authorize modifications to the TRICARE smoking cessation program rules and procedures as may be appropriate to the overseas area involved. The use of this authority, not otherwise mentioned below, shall be published in the<E T="04">Federal Register.</E>
            </P>
            <P>(ii)<E T="03">Benefits.</E>There is no requirement for an eligible beneficiary to be diagnosed with a smoking related illness to access benefits under this program. The specific benefits available under the TRICARE smoking cessation program are:</P>
            <P>(A)<E T="03">Pharmaceutical agents.</E>Products available under this program are identified through the DoD Pharmacy and Therapeutics Committee, consistent with the DoD Uniform Formulary in section 199.21 of this Part. Smoking cessation pharmaceutical agents, including FDA-approved over-the-counter (OTC) pharmaceutical agents, are available through the TRICARE Mail Order Pharmacy (TMOP) or the MTF at no cost to the beneficiary. Smoking cessation pharmaceuticals will not be available at any retail pharmacies. A prescription from a TRICARE-authorized provider is required to obtain any pharmaceutical agent used for smoking cessation, including OTC agents. For overseas Prime beneficiaries, pharmaceutical agents may be provided either in the MTF or through the TMOP where such facility or service is available.</P>
            <P>(B)<E T="03">Face-to-face smoking cessation counseling.</E>Both individual and group smoking cessation counseling are covered. The number and mix of face-to-face counseling sessions covered under this program shall be determined by the Director, TMA; however, shall not exceed the limits established in paragraph (e)(28)(iii) of this section. A TRICARE-authorized provider listed in section 199.6 of this Part must render all counseling sessions.</P>
            <P>(C)<E T="03">Toll-free quit line.</E>Access to a non-medical toll-free quit line 7 days a week, 24 hours a day will be available. The quit line will be staffed with smoking cessation counselors trained to assess a beneficiary's readiness to quit, identify barriers to quitting, and provide specific<PRTPAGE P="58202"/>suggested actions and motivational counseling to enhance the chances of a successful quit attempt. When appropriate, quit line counselors will refer beneficiaries to a TRICARE-authorized provider for medical intervention. The quit line may, at the discretion of the Director, TMA, include the opportunity for the beneficiary to request individual follow-up contact initiated by quit line personnel; however, the beneficiary is not required to participate in the quit line initiated follow-up. Printed educational materials on the effects of tobacco use will be provided to the beneficiary upon request. This benefit may be made available to overseas Prime beneficiaries should the ASD(HA) exercise his authority to do so and provide appropriate notice in the<E T="04">Federal Register.</E>
            </P>
            <P>(D)<E T="03">Web-based resources.</E>Downloadable educational materials on the effects of tobacco use will be available through the Internet or other electronic media. This service may be made available to overseas Prime beneficiaries in all locations where Web based resources are available. There shall be no requirement to create Web based resources in any geographic area in order to make this service available.</P>
            <P>(iii)<E T="03">Limitations of smoking cessation program.</E>Eligible beneficiaries are entitled to two quit attempts per year (consecutive 12 month period). A third quit attempt may be covered per year with physician justification and pre-authorization. A quit attempt is defined as up to eighteen face-to-face counseling sessions over a 120 consecutive day period and/or 120 days of pharmacologic intervention for the purpose of smoking cessation. Counseling and pharmacological treatment periods that overlap by at least 60-days are considered a single quit attempt.</P>
            <STARS/>
            <P>(g)<E T="03">Exclusions and limitations.</E>
            </P>
            <STARS/>
            <P>(39)<E T="03">Counseling.</E>Educational, vocational, and nutritional counseling and counseling for socioeconomic purposes, stress management, and/or lifestyle modification purposes, except that the following are not excluded:</P>
            <P>(i) Services provided by a certified marriage and family therapist, pastoral or mental health counselor in the treatment of a mental disorder as specifically provided in paragraph (c)(3)(ix) of this section and in section 199.6 of this Part.</P>
            <P>(ii) Diabetes self-management training (DSMT) as specifically provided in paragraph (d)(3)(ix) of this section.</P>
            <P>(iii) Smoking cessation counseling and education as specifically provided in paragraph (e)(28) of this section.</P>
            <P>(iv) Services provided by alcoholism rehabilitation counselors only when rendered in a CHAMPUS-authorized treatment setting and only when the cost of those services is included in the facility's CHAMPUS-determined allowable cost rate.</P>
            <STARS/>
            <P>(65) [Reserved]</P>
            <STARS/>
            <P>3. Section 199.21 is amended by:</P>
            <P>a. Revising paragraph (a)(2);</P>
            <P>b. Revising paragraph (h)(2)(i);</P>
            <P>c. Adding a new paragraph (h)(2)(iii); and</P>
            <P>d. Adding a new (i)(2)(v)(D).</P>
            <P>The additions and revisions read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 199.21</SECTNO>
            <SUBJECT>TRICARE—Pharmacy Benefits Program.</SUBJECT>
            <P>(a)<E T="03">General.</E>
            </P>
            <P>(1) * * *</P>
            <P>(2)<E T="03">Pharmacy benefits program.</E>(i)<E T="03">Applicability.</E>The pharmacy benefits program, which includes the uniform formulary and its associated tiered co-payment structure, is applicable to all of the uniformed services. Geographically, except as specifically provided in paragraph (a)(2)(ii) of this section, this program is applicable to all 50 states and the District of Columbia, Guam, Puerto Rico, and the Virgin Islands. In addition, if authorized by the Assistant Secretary of Defense (Health Affairs) (ASD(HA)), the TRICARE pharmacy benefits program may be implemented in areas outside the 50 states and the District of Columbia, Guam, Puerto Rico, and the Virgin Islands. In such case, the ASD (HA) may also authorize modifications to the pharmacy benefits program rules and procedures as may be appropriate to the area involved.</P>
            <P>(ii)<E T="03">Applicability exception.</E>The pharmaceutical benefit under the TRICARE smoking cessation program under section 199.4(e)(28) of this Part is available to TRICARE beneficiaries who are not entitled to Medicare benefits authorized under Title XVIII of the Social Security Act. Except as noted in section 199.4(e)(28) of this Part, the smoking cessation program, including the pharmaceutical benefit, is not applicable or available to beneficiaries who reside overseas, including the U.S. territories of Guam, Puerto Rico, and the Virgin Islands, except that under the authority of section 199.17 of this part active duty service members and active duty dependents enrolled in TRICARE Prime residing overseas, including the U.S. territories of Guam, Puerto Rico, and the Virgin Islands, shall have access to smoking cessation pharmaceuticals through either an MTF or the TMOP program where available.</P>
            <STARS/>
            <P>(h)<E T="03">Obtaining pharmacy services under the retail network pharmacy benefits program.</E>
            </P>
            <P>(1) * * *</P>
            <P>(2)<E T="03">Availability of formulary pharmaceutical agents.</E>(i)<E T="03">General.</E>Subject to paragraphs (h)(2)(ii) and (h)(2)(iii) of this section, formulary pharmaceutical agents are available under the Pharmacy Benefits Program from all points of service identified in paragraph (h)(1) of this section.</P>
            <P>(ii) * * *</P>
            <P>(iii) Pharmaceutical agents prescribed for smoking cessation are not available for coverage when obtained through a retail pharmacy. This includes network and non-network retail pharmacies.</P>
            <STARS/>
            <P>(i)<E T="03">Cost-sharing requirements under the pharmacy benefits program.</E>
            </P>
            <P>(1) * * *</P>
            <P>(2) * * *</P>
            <P>(v) For pharmaceutical agents obtained under the TMOP program there is a:</P>
            <P>(A) * * *</P>
            <P>(B) * * *</P>
            <P>(C) * * *</P>
            <P>(D) $0.00 co-payment for smoking cessation pharmaceutical agents covered under the smoking cessation program.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Dated: August 24, 2011.</DATED>
            <NAME>Patricia L. Toppings,</NAME>
            <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23764 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <CFR>32 CFR Part 199</CFR>
        <DEPDOC>[Docket ID: DOD-2011-HA-0035]</DEPDOC>
        <RIN>RIN 0720-AB49</RIN>
        <SUBJECT>TRICARE; TRICARE Sanction Authority for Third-Party Billing Agents</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, Department of Defense.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The rule proposes to provide the Director, TRICARE Management Activity (TMA), or designee, with the authority to sanction third-party billing agents by invoking the administrative remedy of exclusion or suspension from the TRICARE program. Such sanctions<PRTPAGE P="58203"/>may be invoked in situations involving fraud or abuse on the part of third-party billing agents that prepare or submit claims presented to TRICARE for payment.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments received at the address indicated below by November 21, 2011 will be accepted.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and or Regulatory Information Number (RIN) number and title, by either 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">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or RIN for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Joy Saly, TRICARE Management Activity, Medical Benefits and Reimbursement Branch, telephone (303) 676-3742.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>TRICARE has regulatory authority under 32 CFR 199.9 to invoke sanctions in situations involving fraud or abuse on the part of providers of TRICARE services. A provider is defined in 32 CFR 199.2 as, “A hospital or other institutional provider, a physician, or other individual professional provider, or other provider of services or supplies as specified in Sec 199.6 of this part.” Third-party billing agents do not meet the definition of a provider as stated in 32 CFR 199.2, nor do TRICARE regulations currently define third-party billing agents.</P>
        <P>Title 42 of the CFR subpart C—Exclusions at 42 CFR 402.200(b)(1) provides for the imposition of an exclusion from the Medicare and Medicaid programs (and, where applicable, other Federal health care programs) against persons that violate the provisions provided in Sec. 402.1(e) (and further described in Sec. 402.1(c)). However, TRICARE has to date established no independent regulatory authority to sanction or exclude third-party billing agents.</P>
        <P>When TRICARE identifies submission of improper claims by a third-party billing agent not identified by the Centers for Medicare and Medicaid Services (CMS), TRICARE must refer the case to another Federal agency (Defense Criminal Investigative Service, Department of Justice, etc.) for action. In addition, CMS' authority extends only to those third-party billing agents in the United States because Medicare only covers care received in the U.S. or its territories.</P>
        <HD SOURCE="HD1">II. Department of Defense Inspector General Report on TRICARE Controls Over Claims Prepared by Third-party Billing Agents</HD>
        <P>The Department of Defense, Office of Inspector General (DoD IG) initiated an audit in February 2008 to review TRICARE controls over claims submitted by third-party billing agents (Department of Defense Inspector General Report No. D-2009-037—“TRICARE Controls Over Claims Prepared by Third-Party Billing Agencies”). The DoD IG published a report on December 31, 2008. The report included a recommendation that the Director, TMA strengthen internal controls by initiating action to obtain statutory or regulatory authority to sanction billing agencies or any entities that prepare or submit improper health care claims to TRICARE contractors.</P>
        <P>Statutory authority already exists that provides the Secretary with the authority to administer the TRICARE program to ensure quality of care for program beneficiaries, including sanctioning entities determined to be involved fraud, abuse, or conflict of interest. TRICARE already has regulatory authority to invoke sanctions on providers under 32 CFR 199.9. Based on the existing statutory authority, TMA is pursuing a regulatory change that will provide the authority to ensure both providers and third-party billing agents are held accountable for the submission of correct and proper billings. The regulatory change proposes to implement the DoD IG recommendation by adding third-party billing agents as another entity under the regulation that can be sanctioned in situations where fraud and abuse are identified on the part of third-party billing agents that prepare or submit claims presented to TRICARE for payment.</P>
        <P>TRICARE program policy acknowledges a participating provider may arrange for a third-party to act on its behalf in the submission and the monitoring of third-party claims, including TRICARE claims. There must be an agency relationship established in which the third-party billing agent is reimbursed for the submission and monitoring of claims, but the claim remains that of the provider and the proceeds of any third-party payments, including TRICARE payments, are paid to the provider. TRICARE contractors may deal with these agents in much the same manner as they deal with the provider's accounts receivable department. This proposed rule does not intend to change the current acknowledgment of a provider's right to use a third-party billing agent as a separate billing resource.</P>
        <P>This rule seeks to establish that such entities, when acting on behalf of a provider, are held to an equal standard in regard to accuracy and honesty when filing claims for services and supplies under the TRICARE program. As such, these entities should be subject to the same administrative controls applied to providers in ensuring that funds are disbursed appropriately. This rule will allow TRICARE to sanction third-party billing agents to prevent the payment of false or improper billings.</P>
        <HD SOURCE="HD1">Regulatory Procedures</HD>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>Section (Sec.) 801 of title 5, United States Code, and Executive Order (E.O.) 12866 require certain regulatory assessments and procedures for any major rule or significant regulatory action, defined as one that would result in an annual effect of $100 million or more on the national economy or which would have other substantial impacts. It has been certified that this rule is not a significant regulatory action.</P>
        <HD SOURCE="HD2">Public Law 104-4, Section 202, “Unfunded Mandates Reform Act”</HD>
        <P>Section 202 of Public Law 104-4, “Unfunded Mandates Reform Act,” requires that an analysis be performed to determine whether any Federal mandate may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector of $100 million in any one year. It has been certified that this proposed rule does not contain a Federal mandate that may result in the expenditure by State, local and tribal governments, in aggregate, or by the private sector, of $100 million or more in any one year, and thus this proposed rule is not subject to this requirement.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (RFA) (5 U.S.C. 601)</HD>

        <P>Public Law 96-354, “Regulatory Flexibility Act” (RFA) (5 U.S.C. 601),<PRTPAGE P="58204"/>requires that each Federal agency prepare a regulatory flexibility analysis when the agency issues a regulation which would have a significant impact on a substantial number of small entities. This proposed rule is not an economically significant regulatory action, and it has been certified that it will not have a significant impact on a substantial number of small entities. Therefore, this proposed rule is not subject to the requirements of the RFA.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>This rule does not contain a “collection of information” requirement, and will not impose additional information collection requirements on the public under Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35).</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>E.O. 13132, “Federalism,” requires that an impact analysis be performed to determine whether the rule has federalism implications that would 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. It has been certified that this proposed rule does not have federalism implications, as set forth in E.O. 13132.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR part 199</HD>
          <P>Claims, Dental health, Health care, Health insurance, Individuals with disabilities, Military personnel.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 199 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 199—[AMENDED]</HD>
          <P>1. The authority citation for Part 199 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 301; 10 U.S.C. chapter 55.</P>
          </AUTH>
          
          <P>2. Section 199.2 is amended by adding to paragraph (b), to appear in alphabetical order, a definition of “Third-party billing agent,” to read as follows:</P>
          <SECTION>
            <SECTNO>§ 199.2</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>Third-party billing agent. Any entity that acts on behalf of a provider to prepare, submit and monitor claims, excluding those entities that act solely as a collection agency.</P>
            <STARS/>
            <P>3. Section 199.9 is amended by adding paragraph (n) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 199.9</SECTNO>
            <SUBJECT>Administrative Remedies for Fraud, Abuse, and Conflict of Interest.</SUBJECT>
            <STARS/>
            <P>(n) * * * Third-party billing agents as defined in § 199.2(b) of this part, while not considered providers, are subject to the provisions of this section to the same extent as such provisions apply to providers.</P>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Dated: August 24, 2011.</DATED>
            <NAME>Patricia L. Toppings,</NAME>
            <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23763 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <CFR>32 CFR Part 199</CFR>
        <DEPDOC>[DOD-2011-HA-0058; RIN 0720-AB51]</DEPDOC>
        <SUBJECT>TRICARE; Changes Included in the National Defense Authorization Act for Fiscal Year 2010; Constructive Eligibility for TRICARE Benefits of Certain Persons Otherwise Ineligible Under Retroactive Determination of Entitlement to Medicare Part A Hospital Insurance Benefits</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, Department of Defense.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department is publishing this proposed rule to implement section 706 of the National Defense Authorization Act (NDAA) for Fiscal Year 2010, Public Law 111-84. Specifically section 706 exempts TRICARE beneficiaries under the age of 65 who become disabled from the requirement to enroll in Medicare Part B for the retroactive months of entitlement to Medicare Part A in order to maintain TRICARE coverage. This statutory amendment and proposed rule only impact eligibility for the period in which the beneficiary's disability determination is pending before the Social Security Administration. Eligible beneficiaries would still be required to enroll in Medicare Part B in order to maintain their TRICARE coverage for future months, but would be considered to have coverage under the TRICARE program for the months retroactive to their entitlement to Medicare Part A. This proposed rule also amends the eligibility section of the TRICARE regulation to more clearly address reinstatement of TRICARE eligibility following a gap in coverage due to lack of enrollment in Medicare Part B.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments received at the address indicated below by November 21, 2011 will be accepted.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number or Regulatory Information Number (RIN) and title, by any of the following methods:</P>
          <P>
            <E T="03">The Web site http://www.regulations.gov</E>. Follow the instructions for submitting comments.</P>
          <P>
            <E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or RIN for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Anne Breslin, TRICARE Management Activity (TMA), TRICARE Operations Branch, telephone (703) 681-0039.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Prior to the enactment of section 706 of the National Defense Authorization Act for Fiscal Year 2010 (Pub. L. 111-84), 10 U.S.C. 1086(d) provided that a person who would otherwise receive benefits under section 1086 who is entitled to Medicare Part A hospital insurance is not eligible for TRICARE unless the individual is enrolled in Medicare Part B. When a TRICARE beneficiary becomes eligible for Medicare, Medicare becomes the primary payer and TRICARE is the secondary payer. Retroactive Medicare eligibility determinations therefore caused DoD and Medicare to reprocess claims. Section 706 of the Fiscal Year 2010 National Defense Authorization Act amended 10 U.S.C. 1086(d) to exempt TRICARE beneficiaries under the age of 65 who became Medicare eligible due to a retroactive disability determination from the requirement to enroll in Medicare Part B for the retroactive months of entitlement to Medicare Part A in order to maintain TRICARE coverage. This statutory amendment became effective upon enactment of the Fiscal Year 2010 National Defense Authorization Act on October 28, 2009. Prior to this amendment, beneficiaries who did not purchase Medicare Part B to cover the retroactive period lost their TRICARE eligibility during that period of time. As a result, beneficiaries and providers were then subject to TRICARE<PRTPAGE P="58205"/>recoupment action for care provided during the period of retroactive disability. Pursuant to this amendment, TRICARE remains first payer for any claims filed during the retroactive months and disabled TRICARE beneficiaries are relieved of the financial burden of making retroactive payments to avoid a gap in coverage. This proposed rule will amend the Code of Federal Regulations to conform to current statury authority regarding TRICARE eligibility.</P>
        <P>Additionally, due to an earlier administrative omission, this proposed rule also amends 32 CFR 199.3 to more clearly address reinstatement of TRICARE eligibility following a gap in coverage due to lack of enrollment in Part B. While most TRICARE beneficiaries who become eligible for Medicare Part A maintain TRICARE coverage through prompt acceptance of Part B coverage, there are a number of beneficiaries that for one reason or another decline Part B and lose their TRICARE eligibility. For those individuals, they can have that eligibility reinstated at a later date if they re-enroll in Part B. This proposed rule amends the section on reinstatement of TRICARE eligibility to include beneficiaries who elect to enroll in Medicare Part B following a gap in TRICARE coverage.</P>
        <P>All comments will be carefully considered. A discussion of the major issues received by public comments will be included with the issuance of the final rule.</P>
        <HD SOURCE="HD1">Regulatory Procedures</HD>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review”; Executive Order 13563. “Improving Regulation and Regulatory Review”; and Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. 601)</HD>
        <P>Executive Orders 12866 and 13563 require that a comprehensive regulatory impact analysis be performed on any economically significant regulatory action, defined as one that would result in an annual effect of $100 million or more on the national economy or which would have other substantial impacts. The Regulatory Flexibility Act (RFA) requires that each Federal agency prepare, and make available for public comment, a regulatory flexibility analysis when the agency issues a regulation which would have a significant impact on a substantial number of small entities. This rule is not an economically significant regulatory action and will not have a significant impact on a substantial number of small entities for purposes of the RFA, thus this rule is not subject to any of these requirements.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3511)</HD>
        <P>This rule will not impose additional information collection requirements on the public. OMB previously cleared the collection requirements under OMB Control Number 0704-0364.</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism,”</HD>
        <P>We have examined the impact(s) of the rule under Executive Order 13132, and it does not have policies that have federalism implications that would 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, therefore, consultation with State and local officials is not required.</P>
        <HD SOURCE="HD2">Sec. 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>This rule does not contain unfunded mandates. It does not contain a Federal mandate that may result in the expenditure by State, local, and tribal governments, in aggregate, or by the private sector, of $100 million or more in any one year.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 199</HD>
          <P>Claims, Dental health, Health care, Health insurance, Individuals with disabilities, Military personnel.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 199 is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 199—[AMENDED]</HD>
          <P>1. The authority citation for part 199 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 301; chapter 55 of 10 U.S.C.</P>
          </AUTH>
          
          <P>2. Section 199.3 is amended by:</P>
          <P>a. Adding paragraph (f)(2)(iii);</P>
          <P>b. Revising paragraph (f)(3)(ix)(C); and</P>
          <P>c. Adding paragraph (g)(3) to read as follows:</P>
          <SECTION>
            <SECTNO>§ 199.3</SECTNO>
            <SUBJECT>Eligibility.</SUBJECT>
            <STARS/>
            <P>(f) * * *</P>
            <P>(2) * * *</P>
            <P>(iii) Attainment of entitlement to hospital insurance benefits (Part A) under Medicare except as provided in paragraphs (b)(3), (f)(3)(vii), (f)(3)(viii) and (f)(3)(ix) of this section.</P>
            <P>(3) * * *</P>
            <P>(ix) * * *</P>
            <P>(C) The individual is enrolled in Part B of Medicare except that in the case of a retroactive determination of entitlement to Medicare Part A hospital insurance benefits for a person under 65 years of age there is no requirement to enroll in Medicare Part B from the Medicare Part A entitlement date until the issuance of such retroactive determination; and</P>
            <STARS/>
            <P>(g) * * *</P>
            <P>(3)<E T="03">Enrollment in Medicare Part B.</E>For individuals whose CHAMPUS eligibility has terminated pursuant to paragraph (f)(2)(iii) or (f)(3)(vi) of this section due to beneficiary action to decline Part B of Medicare, CHAMPUS eligibility resumes, effective on the date Medicare Part B coverage begins, if the person subsequently enrolls in Medicare Part B and the person is otherwise still eligible.</P>
            <P>3. Section 199.8 is amended as follows:</P>
            <P>a. Revise paragraph (d)(1)(i);</P>
            <P>b. Redesignate (d)(1)(vi), (d)(1)(vii) and (d)(1)(viii) as (d)(1)(vii), (d)(1)(viii), and (d)(1)(ix) respectively; and</P>
            <P>c. Add the following new paragraph (d)(1)(vi).</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 199.8</SECTNO>
            <SUBJECT>Double Coverage.</SUBJECT>
            <STARS/>
            <P>(d) * * *</P>
            <P>(1) * * *</P>
            <P>(i)<E T="03">General rule.</E>In any case in which a beneficiary is eligible for both Medicare and CHAMPUS received medical or dental care for which payment may be made under Medicare and CHAMPUS, Medicare is always the primary payer except in the case of retroactive determinations of disability as provided in paragraph (d)(1)(v) of this section. For dependents of active duty members, payment will be determined in accordance to paragraph (c) of this section. For all other beneficiaries eligible for Medicare, the amount payable under CHAMPUS shall be the amount of actual out-of-pocket costs incurred by the beneficiary for that care over the sum of the amount paid for that care under Medicare and the total of all amounts paid or payable by third party payers other than Medicare.</P>
            <STARS/>
            <P>(vi)<E T="03">Retroactive determinations of disability.</E>In circumstances involving determinations of retroactive Medicare Part A entitlement for persons under 65 years of age, Medicare becomes the primary payer effective as of the date of issuance of the retroactive determination by the Social Security Administration. For care and services rendered prior to issuance of the retroactive determination, the CHAMPUS payment will be determined consistent with paragraph (d)(1)(iii)(B) of this section notwithstanding the beneficiary's retroactive entitlement for Medicare Part A during that period.<PRTPAGE P="58206"/>
            </P>
            <P>4. Section 199.11 is amended as follows:</P>
            <P>a. Revising paragraph (f)(3) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 199.11</SECTNO>
            <SUBJECT>Overpayments Recovery.</SUBJECT>
            <STARS/>
            <P>(f) * * *</P>
            <P>(3) Claims arising from erroneous TRICARE payments in situations where the beneficiary has entitlement to an insurance, medical service, health and medical plan, including any plan offered by a third party payer as defined in 10 U.S.C. 1095(h)(1) or other government program, except in the case of a plan administered under Title XIX of the Social Security Act (42 U.S.C. 1396, et seq.) through employment, by law, through membership in an organization, or as a student, or through the purchase of a private insurance or health plan, shall be recouped following the procedures in paragraph (f) of this section. If the other plan has not made payment to the beneficiary or provider, the contractor shall first attempt to recover the overpayment from the other plan through the contractor's coordination of benefits procedures. If the overpayment cannot be recovered from the other plan, or if the other plan has made payment, the overpayment will be recovered from the party that received the erroneous payment from TRICARE. Nothing in this section shall be construed to require recoupment from any sponsor, beneficiary, provider, supplier and/or the Medicare Program under Title XVIII of the Social Security Act in the event of a retroactive determination of entitlement to SSDI and Medicare Part A coverage made by the Social Security Administration as discussed in section 199.8(d) of this part.</P>
          </SECTION>
          <SIG>
            <DATED>Dated: August 24, 2011.</DATED>
            <NAME>Patricia L. Toppings,</NAME>
            <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2011-23765 Filed 9-19-11; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R03-OAR-2010-0986; FRL-9468-3]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; District of Columbia, Maryland, and Virginia; Determinations of Attainment of the 1997 8-Hour Ozone National Ambient Air Quality Standard for the Washington, DC-MD-VA 8-Hour Ozone Moderate Nonattainment Area</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is proposing to make two determinations regarding the Washington, DC-MD-VA moderate 8-hour ozone nonattainment area (the Washington Area). First, EPA is proposing to make a determination that the Washington Area has attained the 1997 8-hour ozone National Ambient Air Quality Standard (NAAQS). This proposed determination is based upon complete, quality assured, and certified ambient air monitoring data that show the area has monitored attainment of the 1997 8-hour ozone NAAQS for the 2007-2009 and 2008-2010 monitoring periods. If this proposal becomes final, the requirement for this area to submit an attainment demonstration, reasonably available control measures (RACM), a reasonable further progress (RFP) plan, and contingency measures related to attainment of the 1997 8-hours ozone NAAQS shall be suspended for so long as the area continues to attain the 1997 8-hour ozone NAAQS. Although these requirements are suspended, EPA is not precluded from acting upon these elements at any time if submitted to EPA for review and approval. Second, EPA is also proposing to determine that the Washington Area has attained the 1997 8-hour ozone NAAQS by its attainment date of June 15, 2010. These actions are being taken under the Clean Air Act (CAA).</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments must be received on or before October 20, 2011.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by Docket ID Number EPA-R03-OAR-2010-0986 by one of the following methods:</P>
          <P>A.<E T="03">http://www.regulations.gov.</E>Follow the on-line instructions for submitting comments.</P>
          <P>B.<E T="03">E-mail: fernandez.cristina@epa.gov.</E>
          </P>
          <P>C.<E T="03">Mail:</E>EPA-R03-OAR-2010-0986, Cristina Fernandez, Associate Director, Office of Air Quality Planning, Mailcode 3AP30, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103.</P>
          <P>D.<E T="03">Hand Delivery:</E>At the previously-listed EPA Region III address. Such deliveries are only accepted during the Docket'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 No. EPA-R03-OAR-2010-0986. EPA's policy is that all comments received will be included in the public 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<E T="03">http://www.regulations.gov</E>or e-mail. The<E T="03">http://www.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 e-mail comment directly to EPA without going through<E T="03">http://www.regulations.gov,</E>your e-mail address will be automatically captured and included as part of the comment that is placed in the public 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 electronic docket are listed in the<E T="03">http://www.regulations.gov</E>index. Although listed in the index, some information is not publicly available,<E T="03">i.e.,</E>CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically in<E T="03">http://www.regulations.gov</E>or in hard copy during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103.</P>
        </ADD>
        <FURINF>
          <PRTPAGE P="58207"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Maria A. Pino, (215) 814-2181, or by e-mail at<E T="03">pino.maria@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>For detailed information regarding this proposal, EPA prepared a Technical Support Document (TSD). The TSD can be viewed at<E T="03">http://www.regulations.gov.</E>The following outline is provided to aid in locating information in this action.</P>
        
        <EXTRACT>
          <FP SOURCE="FP-2">I. What is EPA proposing?</FP>
          <FP SOURCE="FP-2">II. What is the background for these actions?</FP>
          <FP SOURCE="FP-2">III. What are the effects of these actions?</FP>
          <FP SOURCE="FP-2">IV. What is EPA's analysis of the relevant air quality data?</FP>
          <FP SOURCE="FP-2">V. General Information Pertaining to SIP Submittals From the Commonwealth of Virginia</FP>
          <FP SOURCE="FP-2">VI. Proposed Actions</FP>
          <FP SOURCE="FP-2">VII. Statutory and Executive Order Reviews</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. What is EPA proposing?</HD>
        <P>Pursuant to sections 181(b)(2)(A) and 179(c) of the CAA, EPA is proposing to determine that the Washington Area attained the 1997 8-hour ozone NAAQS by its attainment date, June 15, 2010. This proposed determination is based upon complete, quality assured, and certified ambient air monitoring data for the 2007-2009 monitoring period that show the area has monitored attainment of the 1997 8-hour ozone NAAQS during this monitoring period. Complete, quality assured, and certified ambient air monitoring data for the 2008-2010 monitoring period shows continued attainment.</P>
        <P>EPA is also proposing to make a determination that the Washington Area has attained the 1997 8-hour ozone NAAQS. This proposed determination is based upon complete, quality assured, and certified ambient air monitoring data that show the area has monitored attainment of the 1997 8-hour ozone NAAQS for the 2007-2009 and 2008-2010 monitoring periods. Once this proposal is final, the requirement for this area to submit an attainment demonstration, reasonably available control measures, a reasonable further progress plan, and contingency measures related to attainment of the 1997 8-hours ozone NAAQS shall be suspended for so long as the area continues to attain the 1997 8-hour ozone NAAQS. Although these requirements are suspended, EPA is not precluded from acting upon these elements at any time if submitted to EPA for review and approval. The District of Columbia, the State of Maryland, and the Commonwealth of Virginia submitted these SIP elements for the Washington Area to EPA for review and approval in June 2007.</P>
        <P>On March 27, 2008 (73 FR 16436), EPA promulgated a revised 8-hour ozone standard of 0.075 parts per million (ppm). On January 6, 2010, EPA again addressed this 2008 revised standard and proposed to set the primary 8-hour ozone standard within the range of 0.060 to 0.070 ppm, rather than at 0.075 ppm. EPA is working to complete reconsideration of the standard and thereafter will proceed with attainment/nonattainment area designations. This proposed rulemaking relates only to a determination of attainment for the 1997 8-hour ozone standard and is not affected by the ongoing process of reconsidering the 2008 standard. This action addresses only the 1997 8-hour ozone standard of 0.08 ppm, and does not address any subsequently revised 8-hour ozone standard.</P>
        <HD SOURCE="HD1">II. What is the background for these actions?</HD>
        <HD SOURCE="HD2">A. The Washington Area</HD>
        <P>In 1997, EPA revised the health-based NAAQS for ozone, setting it at 0.08 ppm averaged over an 8-hour time frame. EPA set the 8-hour ozone standard based on scientific evidence demonstrating that ozone causes adverse health effects at lower ozone concentrations and over longer periods of time, than was understood when the pre-existing 1-hour ozone standard was set. EPA determined that the 8-hour standard would be more protective of human health, especially children and adults who are active outdoors, and individuals with a pre-existing respiratory disease, such as asthma.</P>

        <P>On April 30, 2004 (69 FR 23951), EPA finalized its attainment/nonattainment designations for areas across the country with respect to the 8-hour ozone standard. These actions became effective on June 15, 2004. Among those nonattainment areas is the Washington Area. The Washington Area includes the District of Columbia; Arlington, Fairfax, Loudoun, and Prince William Counties and the cities of Alexandria, Fairfax, Falls Church, Manassas, and Manassas Park in Virginia; and Calvert, Charles, Frederick, Montgomery, and Prince George's Counties in Maryland. The Washington Area was classified as a moderate nonattainment area.<E T="03">See,</E>40 CFR 81.309, 81.321 and 81.347. Moderate areas are required to attain the 1997 8-hour ozone NAAQS by no later than six years after designation, or June 15, 2010.<E T="03">See,</E>40 CFR 51.903.</P>
        <HD SOURCE="HD2">B. Requirement to Determine Attainment by the Attainment Date</HD>

        <P>Under CAA sections 179(c) and 181(b)(2), EPA is required to make a determination that a nonattainment area has attained by its attainment date, and publish that determination in the<E T="04">Federal Register</E>. Under CAA section 181(b)(2), which is specific to ozone nonattainment areas, if EPA determines that an area failed to attain the ozone NAAQS by its attainment date, EPA is required to reclassify that area to a higher classification.</P>
        <HD SOURCE="HD2">C. Clean Data Determination</HD>
        <P>Under the provisions of EPA's ozone implementation rule (<E T="03">See,</E>40 CFR section 51.918), if EPA issues a determination that an area is attaining the relevant standard (through a rulemaking that includes public notice and comment), it will suspend the area's obligations to submit an attainment demonstration, RACM, RFP, contingency measures and other planning requirements related to attainment for as long as the area continues to attain. The determination of attainment is not equivalent to a redesignation. The state must still meet the statutory requirements for redesignation in order to be redesignated to attainment.</P>
        <HD SOURCE="HD2">D. Ambient Air Quality Monitoring Data</HD>
        <P>Complete, quality assured, certified 8-hour ozone air quality monitoring data for 2007 through 2009 show that the Washington Area has attained the 1997 8-hour ozone NAAQS. The Washington Area continues to attain the 1997 8-hour ozone NAAQS considering complete, quality assured, certified 8-hour ozone air quality monitoring data for 2008 through 2010.</P>
        <HD SOURCE="HD1">III. What are the effects of these actions?</HD>
        <P>If finalized, the proposed actions will not constitute a redesignation to attainment under section 107(d)(3) of the CAA. The designation status of the Washington Area will remain nonattainment for the 1997 8-hour ozone NAAQS until such time as EPA determines that the area meets the CAA requirements for redesignation to attainment, including an approved maintenance plan.</P>
        <HD SOURCE="HD2">A. Proposed Determination of Attainment by the Attainment Date</HD>

        <P>EPA is proposing to determine that the Washington Area has attained the 1997 ozone NAAQS by its applicable attainment date of June 15, 2010. Once this determination of attainment is made final, EPA will have met its<PRTPAGE P="58208"/>requirement pursuant to CAA sections 181(b)(2)(A) and 179(c) to determine, based on the area's air quality as of the attainment date, whether the area attained the standard by that date. The effect of a final determination of attainment by the area's attainment date will be to discharge EPA's obligation under CAA sections 181(b)(2)(A) and 179, and to establish that, in accordance with CAA section 181(b)(2)(A), the area will not be reclassified for failure to attain by its applicable attainment date.</P>
        <HD SOURCE="HD2">B. Clean Data Determination</HD>
        <P>EPA is proposing to determine that the Washington Area is attaining the 1997 8-hour ozone NAAQS. Once EPA finalizes this determination of attainment, the CAA requirement for the Washington Area to submit an attainment demonstration and associated reasonably available control measures, a reasonable further progress plan, contingency measures, and any other planning SIPs related to attainment of the 1997 8-hour ozone NAAQS would be suspended for so long as the area continues to attain the 1997 8-hour ozone NAAQS.</P>
        <P>The determination of attainment will:</P>
        <P>1. Suspend the requirements to submit an attainment demonstration, RACM, RFP plan, contingency measures, and any other planning SIPs related to attainment of the 1997 8-hour ozone NAAQS;</P>
        <P>2. Continue until such time, if any, that EPA (i) redesignates the area to attainment at which time those requirements no longer apply, or (ii) subsequently determines that the area has violated the 1997 8-hour ozone NAAQS;</P>
        <P>3. Be separate from, and not influence or otherwise affect, any future designation determination or requirements for the area based on any new or revised ozone NAAQS; and</P>
        <P>4. Remain in effect regardless of whether EPA designates this area as a nonattainment area for purposes of any new or revised ozone NAAQS.</P>
        <P>Although these requirements are suspended, EPA is not precluded from acting upon these elements, which were submitted to EPA in June 2007.</P>
        <HD SOURCE="HD1">IV. What is EPA's analysis of the relevant air quality data?</HD>
        <P>Consistent with the requirements contained in 40 CFR part 50, EPA has reviewed the complete, quality assured and certified ozone ambient air monitoring data for the monitoring periods 2007-2009 and 2008-2010 for the Washington Area, as recorded in the EPA Air Quality System (AQS) database. On the basis of that review, EPA has concluded that this area attained the 1997 8-hour ozone NAAQS based on data for the 2007-2009 ozone seasons, and continues to attain based on data for the 2008-2010 ozone seasons.</P>
        <HD SOURCE="HD2">A. Data Requirements</HD>

        <P>Under EPA regulations at 40 CFR part 50, the 1997 8-hour ozone standard is attained at a site when the 3-year average of the annual fourth-highest daily maximum 8-hour average ozone concentrations at an ozone monitor is less than or equal to 0.08 parts per million (ppm) (<E T="03">i.e.,</E>0.084 ppm, based on the rounding convention in 40 CFR part 50, appendix I). This 3-year average is referred to as the design value. When the design value is less than or equal to 0.084 ppm at each monitoring site within the area, then the area is meeting the NAAQS.</P>
        <P>Also, the data completeness requirement is met when the average percent of days with valid ambient monitoring data is greater than 90%, and no single year has less than 75% data completeness as determined in appendix I of 40 CFR part 50.</P>
        <HD SOURCE="HD2">B. 2007-2009 Ozone Data</HD>
        <P>Table 1 shows the ozone design values for each monitor in the Washington Area for the years 2007-2009. All 2007-2009 design values are below 0.084 ppm, and all monitors meet the data completeness requirements. Therefore, the Washington Area has attained the 1997 8-hour ozone NAAQS, considering 2007-2009 data.</P>
        <GPOTABLE CDEF="s50,r50,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 1—2007-2009 Washington Area 1997 8-Hour Ozone Design Values</TTITLE>
          <BOXHD>
            <CHED H="1">State</CHED>
            <CHED H="1">County</CHED>
            <CHED H="1">Monitor ID</CHED>
            <CHED H="1">2007-2009 Design value<LI>(ppm)</LI>
            </CHED>
            <CHED H="1">2007-2009 Average %<LI>data</LI>
              <LI>completeness</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Maryland</ENT>
            <ENT>Calvert</ENT>
            <ENT>240090011</ENT>
            <ENT>0.074</ENT>
            <ENT>92</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Charles</ENT>
            <ENT>240170010</ENT>
            <ENT>0.075</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Frederick</ENT>
            <ENT>240210037</ENT>
            <ENT>0.076</ENT>
            <ENT>98</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Montgomery</ENT>
            <ENT>240313001</ENT>
            <ENT>0.078</ENT>
            <ENT>93</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Prince George's</ENT>
            <ENT>240330030</ENT>
            <ENT>0.078</ENT>
            <ENT>95</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>240338003</ENT>
            <ENT>0.078</ENT>
            <ENT>98</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Virginia</ENT>
            <ENT>Arlington</ENT>
            <ENT>510130020</ENT>
            <ENT>0.079</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Fairfax</ENT>
            <ENT>510590005</ENT>
            <ENT>0.073</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>510590018</ENT>
            <ENT>0.080</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>510590030</ENT>
            <ENT>0.080</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>510591005</ENT>
            <ENT>0.078</ENT>
            <ENT>93</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>510595001</ENT>
            <ENT>0.077</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Loudoun</ENT>
            <ENT>511071005</ENT>
            <ENT>0.077</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Prince William</ENT>
            <ENT>511530009</ENT>
            <ENT>0.071</ENT>
            <ENT>98</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Alexandria City</ENT>
            <ENT>515100009</ENT>
            <ENT>0.075</ENT>
            <ENT>97</ENT>
          </ROW>
          <ROW>
            <ENT I="01">District of Columbia</ENT>
            <ENT O="xl"/>
            <ENT>110010025</ENT>
            <ENT>0.077</ENT>
            <ENT>95</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>110010041</ENT>
            <ENT>0.078</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>110010043</ENT>
            <ENT>0.080</ENT>
            <ENT>100</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD2">C. 2008-2010 Ozone Data</HD>

        <P>In 2010, four monitors in Fairfax County, Virginia were shutdown due to lack of funding. Virginia Department of Environmental Quality (VADEQ) worked with EPA prior to the Fairfax County Health Department shutting down these monitors. Because the Washington Area has more ozone monitoring sites than minimally required, and because VADEQ performed an analysis on the sites that were being shutdown showing a strong correlation between the ambient ozone data collected at the Fairfax County<PRTPAGE P="58209"/>ozone sites targeted for discontinuation and existing VADEQ ozone air monitoring sites currently operating in proximity to the Fairfax County area, EPA approved the shutdowns in VADEQ's 2010 Annual Network Plan. Therefore, EPA will not consider these monitors for comparison to the NAAQS with respect to 2010 data.</P>
        <P>Table 2 summarizes the 2008-2010 design values for the Washington Area. All 2008-2010 design values are below 0.084 ppm, and all monitors meet the data completeness requirements. Therefore, 2008-2010 data indicates that the Washington Area continues to attain the 1997 8-hour ozone NAAQS.</P>
        <GPOTABLE CDEF="s50,r50,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 2-2008-2010 Washington Area 8-Hour Ozone Design Values</TTITLE>
          <BOXHD>
            <CHED H="1">State</CHED>
            <CHED H="1">County</CHED>
            <CHED H="1">Monitor ID</CHED>
            <CHED H="1">2008-2010 Design value<LI>(ppm)</LI>
            </CHED>
            <CHED H="1">2008-2010 Average %<LI>data</LI>
              <LI>completeness</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Maryland</ENT>
            <ENT>Calvert</ENT>
            <ENT>240090011</ENT>
            <ENT>0.077</ENT>
            <ENT>93</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Charles</ENT>
            <ENT>240170010</ENT>
            <ENT>0.075</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Frederick</ENT>
            <ENT>240210037</ENT>
            <ENT>0.076</ENT>
            <ENT>98</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Montgomery</ENT>
            <ENT>240313001</ENT>
            <ENT>0.074</ENT>
            <ENT>93</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Prince George's</ENT>
            <ENT>240330030</ENT>
            <ENT>0.079</ENT>
            <ENT>93</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>240338003</ENT>
            <ENT>0.077</ENT>
            <ENT>99</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Virginia</ENT>
            <ENT>Arlington</ENT>
            <ENT>510130020</ENT>
            <ENT>0.079</ENT>
            <ENT>95</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Fairfax</ENT>
            <ENT>510590030</ENT>
            <ENT>0.081</ENT>
            <ENT>94</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Loudoun</ENT>
            <ENT>511071005</ENT>
            <ENT>0.075</ENT>
            <ENT>94</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Prince William</ENT>
            <ENT>511530009</ENT>
            <ENT>0.070</ENT>
            <ENT>94</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>Alexandria City</ENT>
            <ENT>515100009</ENT>
            <ENT>0.074</ENT>
            <ENT>91</ENT>
          </ROW>
          <ROW>
            <ENT I="01">District of Columbia</ENT>
            <ENT/>
            <ENT>110010025</ENT>
            <ENT>0.075</ENT>
            <ENT>90</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>110010041</ENT>
            <ENT>0.077</ENT>
            <ENT>94</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>110010043</ENT>
            <ENT>0.079</ENT>
            <ENT>95</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD2">D. Conclusion</HD>
        <P>EPA's review of the complete, quality assured and certified ozone ambient air monitoring data for the monitoring periods 2007-2009 and 2008-2010 indicates that the Washington Area has met the 19978-hour ozone NAAQS. Additional information on air quality data for the Washington Area can be found in the TSD.</P>
        <HD SOURCE="HD1">V. General Information Pertaining to SIP Submittals From the Commonwealth of Virginia</HD>
        <P>In 1995, Virginia adopted legislation that provides, subject to certain conditions, for an environmental assessment (audit) “privilege” for voluntary compliance evaluations performed by a regulated entity. The legislation further addresses the relative burden of proof for parties either asserting the privilege or seeking disclosure of documents for which the privilege is claimed. Virginia's legislation also provides, subject to certain conditions, for a penalty waiver for violations of environmental laws when a regulated entity discovers such violations pursuant to a voluntary compliance evaluation and voluntarily discloses such violations to the Commonwealth and takes prompt and appropriate measures to remedy the violations. Virginia's Voluntary Environmental Assessment Privilege Law, Va. Code Sec. 10.1-1198, provides a privilege that protects from disclosure documents and information about the content of those documents that are the product of a voluntary environmental assessment. The Privilege Law does not extend to documents or information (1) that are generated or developed before the commencement of a voluntary environmental assessment; (2) that are prepared independently of the assessment process; (3) that demonstrate a clear, imminent and substantial danger to the public health or environment; or (4) that are required by law.</P>
        <P>On January 12, 1998, the Commonwealth of Virginia Office of the Attorney General provided a legal opinion that states that the Privilege law, Va. Code Sec. 10.1-1198, precludes granting a privilege to documents and information “required by law,” including documents and information “required by Federal law to maintain program delegation, authorization or approval,” since Virginia must “enforce Federally authorized environmental programs in a manner that is no less stringent than their Federal counterpartsm * * *.” The opinion concludes that “[r]egarding § 10.1-1198, therefore, documents or other information needed for civil or criminal enforcement under one of these programs could not be privileged because such documents and information are essential to pursuing enforcement in a manner required by Federal law to maintain program delegation, authorization or approval.”</P>
        <P>Virginia's Immunity law, Va. Code Sec. 10.1-1199, provides that “[t]o the extent consistent with requirements imposed by Federal law,” any person making a voluntary disclosure of information to a State agency regarding a violation of an environmental statute, regulation, permit, or administrative order is granted immunity from administrative or civil penalty. The Attorney General's January 12, 1998 opinion states that the quoted language renders this statute inapplicable to enforcement of any Federally authorized programs, since “no immunity could be afforded from administrative, civil, or criminal penalties because granting such immunity would not be consistent with Federal law, which is one of the criteria for immunity.”</P>

        <P>Therefore, EPA has determined that Virginia's Privilege and Immunity statutes will not preclude the Commonwealth from enforcing its program consistent with the Federal requirements. In any event, because EPA has also determined that a state audit privilege and immunity law can affect only state enforcement and cannot have any impact on Federal enforcement authorities, EPA may at any time invoke its authority under the CAA, including, for example, sections 113, 167, 205, 211 or 213, to enforce the requirements or prohibitions of the state plan, independently of any state enforcement effort. In addition, citizen enforcement under section 304 of the CAA is likewise unaffected by this, or any, state audit privilege or immunity law.<PRTPAGE P="58210"/>
        </P>
        <HD SOURCE="HD1">VI. Proposed Action</HD>
        <P>Pursuant to sections 179 and 181(b)(2)(A) of the CAA, EPA is proposing to determine that the Washington Area has attained the 1997 8-hour ozone NAAQS by its moderate area attainment date, June 15, 2010. If EPA finalizes this determination, the requirements to submit an attainment demonstration and associated RACM, RFP plan, contingency measures, and any other planning requirements related to attainment of the 1997 8-hour ozone NAAQS will be suspended, as provi