<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agriculture</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agriculture Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72164-72165</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28552</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Antitrust Division</EAR>
            <HD>Antitrust Division</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Final Judgments and Competitive Impact Statements:</SJ>
                <SJDENT>
                    <SJDOC>United States v. Nexstar Broadcasting Group, Inc., et al., </SJDOC>
                    <PGS>72203-72213</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="10">2014-28585</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Antitrust</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Arts and Humanities, National Foundation</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Foundation on the Arts and the Humanities</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Blind or Severely Disabled, Committee for Purchase From  People Who Are</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Committee for Purchase From People Who Are Blind or Severely Disabled</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Medicare Program:</SJ>
                <SJDENT>
                    <SJDOC>Requirements for the Medicare Incentive Reward Program and Provider Enrollment, </SJDOC>
                      
                    <PGS>72500-72533</PGS>
                    <FRDOCBP T="05DER3.sgm" D="33">2014-28505</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Medicare, Medicaid, and Children's Health Insurance Programs:</SJ>
                <SJDENT>
                    <SJDOC>Provider Enrollment Application Fee Amount for Calendar Year 2015, </SJDOC>
                    <PGS>72183-72185</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28503</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>72165</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28649</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Drawbridge Operations:</SJ>
                <SJDENT>
                    <SJDOC>Gulf Intracoastal Waterway, Belle Chasse, LA, </SJDOC>
                    <PGS>72140</PGS>
                    <FRDOCBP T="05DER1.sgm" D="0">2014-28602</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Drawbridge Operations:</SJ>
                <SJDENT>
                    <SJDOC>Illinois Waterway, Joliet, IL; Public Meeting, </SJDOC>
                    <PGS>72154-72155</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="1">2014-28608</FRDOCBP>
                </SJDENT>
                <SJ>Port Access Route Study:</SJ>
                <SJDENT>
                    <SJDOC>In the Chukchi Sea, Bering Strait and Bering Sea, </SJDOC>
                    <PGS>72157-72159</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="2">2014-28672</FRDOCBP>
                </SJDENT>
                <SJ>Safety Zones:</SJ>
                <SJDENT>
                    <SJDOC>Gallant Channel, Beaufort, NC, </SJDOC>
                    <PGS>72155-72157</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="2">2014-28604</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>
        </AGCY>
        <AGCY>
            <EAR>Committee for Purchase</EAR>
            <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Procurement List; Additions and Deletions, </DOC>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28563</FRDOCBP>
                    <PGS>72171-72172</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28567</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Comptroller</EAR>
            <HD>Comptroller of the Currency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions with Total Consolidated Assets of $50 Billion or More, </SJDOC>
                    <PGS>72245-72247</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28575</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Workforce Investment Act; Native American Employment and Training Council, </SJDOC>
                    <PGS>72214</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28566</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Pesticide Tolerances:</SJ>
                <SJDENT>
                    <SJDOC>2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt; Exemption, </SJDOC>
                    <PGS>72140-72143</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">2014-28603</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>National Emission Standards for Hazardous Air Pollutants:</SJ>
                <SJDENT>
                    <SJDOC>Ferroalloys Production; Extension of Comment Period, </SJDOC>
                    <PGS>72160</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="0">2014-28387</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Environmental Impact Statements; Weekly Receipts, </DOC>
                    <PGS>72172</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28576</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Presidential Documents</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Science and Technology Policy Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Export Import</EAR>
            <HD>Export-Import Bank</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>72172-72173</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28662</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Farm Credit</EAR>
            <HD>Farm Credit Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>72173</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28651</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air Traffic Service Routes:</SJ>
                <SJDENT>
                    <SJDOC>North Central and Northeast United States; Amendment, </SJDOC>
                    <PGS>72135-72139</PGS>
                    <FRDOCBP T="05DER1.sgm" D="4">2014-28618</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus Airplanes, </SJDOC>
                    <PGS>72124-72132</PGS>
                    <FRDOCBP T="05DER1.sgm" D="2">2014-28141</FRDOCBP>
                    <FRDOCBP T="05DER1.sgm" D="5">2014-28477</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Robinson Helicopter Company Helicopters, </SJDOC>
                    <PGS>72132-72135</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">2014-28478</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>The Boeing Company Airplanes, </SJDOC>
                    <PGS>72121-72123</PGS>
                    <FRDOCBP T="05DER1.sgm" D="2">2014-28132</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Airport Property Releases:</SJ>
                <SJDENT>
                    <SJDOC>Eufaula Municipal Airport; Eufaula Municipal Airport, </SJDOC>
                    <PGS>72239-72240</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28611</FRDOCBP>
                </SJDENT>
                <SJ>Waivers of Aeronautical Land-Use Assurance:</SJ>
                <SJDENT>
                    <SJDOC>Office of Commercial Space Transportation; Launch and Mission Risk; Amendment, </SJDOC>
                    <PGS>72240-72241</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28614</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Cellular Service, Including Changes in Licensing of Unserved Area, </DOC>
                    <PGS>72143-72153</PGS>
                    <FRDOCBP T="05DER1.sgm" D="10">2014-28151</FRDOCBP>
                </DOCENT>
                <SJ>Radio Broadcasting Services:</SJ>
                <SJDENT>
                    <SJDOC>Rough Rock, AZ, </SJDOC>
                    <PGS>72153</PGS>
                    <FRDOCBP T="05DER1.sgm" D="0">2014-28589</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <PRTPAGE P="iv"/>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72173-72174</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28581</FRDOCBP>
                </DOCENT>
                <SJ>Radio Broadcasting Services:</SJ>
                <SJDENT>
                    <SJDOC>AM or FM Proposals to Change the Community of License, </SJDOC>
                    <PGS>72175</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28509</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Housing Finance Agency</EAR>
            <HD>Federal Housing Finance Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Reporting by Regulated Entities of Stress Testing Results as of September 30, 2014, </DOC>
                    <PGS>72120-72121</PGS>
                    <FRDOCBP T="05DER1.sgm" D="1">2014-28593</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Maritime</EAR>
            <HD>Federal Maritime Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Complaints:</SJ>
                <SJDENT>
                    <SJDOC>Baltic Auto Shipping, Inc. v. Michael Hitrinov a/k/a Michael Khitrinov, Empire United Lines Co., Inc., </SJDOC>
                    <PGS>72175</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28539</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Ngobros and Co. Nigeria, Ltd. v. Oceane Cargo Link, LLC, and Kingston Ansah, Individually, </SJDOC>
                    <PGS>72175</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28538</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>72175-72176</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28726</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Railroad</EAR>
            <HD>Federal Railroad Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72241-72242</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28506</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Petitions for Waiver of Compliance, </DOC>
                    <PGS>72242-72243</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28518</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Collection of Checks and Other Items by Federal Reserve Banks and Funds Transfers through Fedwire:</SJ>
                <SJDENT>
                    <SJDOC>Time of Settlement by a Paying Bank for an Item Received from a Reserve Bank, </SJDOC>
                    <PGS>72107-72112</PGS>
                    <FRDOCBP T="05DER1.sgm" D="5">2014-28516</FRDOCBP>
                </SJDENT>
                <SJ>Policy Statements:</SJ>
                <SJDENT>
                    <SJDOC>Payment System Risk; Procedures for Measuring Daylight Overdrafts, </SJDOC>
                    <PGS>72112-72120</PGS>
                    <FRDOCBP T="05DER1.sgm" D="8">2014-28664</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Trade</EAR>
            <HD>Federal Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72176-72178</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28597</FRDOCBP>
                </DOCENT>
                <SJ>Proposed Consent Agreements:</SJ>
                <SJDENT>
                    <SJDOC>GlaxoSmithKline, PLC and Novartis AG, </SJDOC>
                    <PGS>72178-72181</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">2014-28605</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Medtronic, Inc. and Covidien plc, </SJDOC>
                    <PGS>72181-72183</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28609</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
                <SJDENT>
                    <SJDOC>Review of Native Species that are Candidates for Listing as Endangered or Threatened; Annual Notice of Findings on Resubmitted Petitions; Annual Description of Progress on Listing Actions, </SJDOC>
                    <PGS>72450-72497</PGS>
                    <FRDOCBP T="05DEP2.sgm" D="47">2014-28536</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Guidance for Industry and Staff:</SJ>
                <SJDENT>
                    <SJDOC>How to Obtain a Letter from the Food and Drug Administration Stating that Bioequivalence Study Protocols Contain Safety Protections Comparable to Applicable Risk Evaluation, etc., </SJDOC>
                    <PGS>72185-72186</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28540</FRDOCBP>
                </SJDENT>
                <SJ>Withdrawal of Approval of New Drug Applications and Abbreviated New Drug Applications:</SJ>
                <SJDENT>
                    <SJDOC>Mallinckrodt Inc. et al., </SJDOC>
                    <PGS>72186-72188</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28541</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Assets</EAR>
            <HD>Foreign Assets Control Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Blocking or Unblocking of Persons and Properties, </DOC>
                    <PGS>72248</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28598</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Claims</EAR>
            <HD>Foreign Claims Settlement Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>72213</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28663</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Authorization of Production Activities:</SJ>
                <SJDENT>
                    <SJDOC>Apple Inc./GTAT Corp., et al., Foreign-Trade Zone 221, Mesa, AZ, </SJDOC>
                    <PGS>72165</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28582</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>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>Indian Health Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
        </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>72188-72190</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28555</FRDOCBP>
                </DOCENT>
            </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>U.S. Immigration and Customs Enforcement</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>Application for Energy Innovation Fund; Multifamily Pilot Program, </SJDOC>
                    <PGS>72194</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28594</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Multifamily Insurance Benefits Claims Package, </SJDOC>
                    <PGS>72194-72195</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28631</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Survey Questions for Small Contractor Marketplace, </SJDOC>
                    <PGS>72192-72193</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28621</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Use Restriction Agreement Monitoring and Compliance, </SJDOC>
                    <PGS>72193-72194</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28629</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Federal Properties Suitable as Facilities to Assist the Homeless, </DOC>
                    <PGS>72195-72199</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="4">2014-28336</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Indian Affairs</EAR>
            <HD>Indian Affairs Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Indian Gaming, </DOC>
                    <PGS>72200</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28600</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Indian Health</EAR>
            <HD>Indian Health Service</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Indian Health Service</P>
            </SEE>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Payment for Physician and Other Health Care Professional Services Purchased:</SJ>
                <SJDENT>
                    <SJDOC>Indian Health Programs and Medical Charges Associated with Non-Hospital-Based Care, </SJDOC>
                    <PGS>72160-72163</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">2014-28508</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Indian Affairs Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Park Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Reclamation Bureau</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Senior Executive Service Performance Review Board Appointments, </DOC>
                    <PGS>72199-72200</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28568</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Certain Activated Carbon from the People's Republic of China, </SJDOC>
                    <PGS>72165-72166</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28577</FRDOCBP>
                </SJDENT>
                <PRTPAGE P="v"/>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Certain Frozen Fish Fillets from the Socialist Republic of Vietnam, </SJDOC>
                    <PGS>72170-72171</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28583</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Circular Welded Non-Alloy Steel Pipe from the Republic of Korea, </SJDOC>
                    <PGS>72168-72170</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28580</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Polyethylene Terephthalate Film, Sheet, and Strip from the People's Republic of China, </SJDOC>
                    <PGS>72166-72168</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28579</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Barium Carbonate from China, </SJDOC>
                    <PGS>72202</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28574</FRDOCBP>
                </SJDENT>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Certain Welded Line Pipe from Korea and Turkey, </SJDOC>
                    <PGS>72202-72203</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28533</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign Claims Settlement Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Contract Compliance Programs Office</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Focus Groups for Evaluating the Effectiveness of Employee Retirement Income Security Act Disclosure Requirements, </SJDOC>
                    <PGS>72213-72214</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28592</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Foundation</EAR>
            <HD>National Foundation on the Arts and the Humanities</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Let's Move Museums, Let's Move Gardens, </SJDOC>
                    <PGS>72214-72215</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28572</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Qualitative Feedback on Agency Service Delivery, </SJDOC>
                    <PGS>72243-72244</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28542</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>72191-72192</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28528</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Clinical Center, </SJDOC>
                    <PGS>72191</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28527</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Cancer Institute, </SJDOC>
                    <PGS>72190</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28530</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Human Genome Research Institute, </SJDOC>
                    <PGS>72190-72191</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28529</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>National Register of Historic Places:</SJ>
                <SJDENT>
                    <SJDOC>Pending Nominations and Related Actions, </SJDOC>
                    <PGS>72200-72201</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28537</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Antarctic Conservation Act Permits, </DOC>
                    <PGS>72215</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28578</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Astronomy and Astrophysics Advisory Committee, </SJDOC>
                    <PGS>72215</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28573</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings:</SJ>
                <SJDENT>
                    <SJDOC>DTE Electric Co., Combined License for Enrico Fermi Unit 3, </SJDOC>
                    <PGS>72215-72217</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28610</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>PROCLAMATIONS</HD>
                <SJ>Special Observances:</SJ>
                <SJDENT>
                    <SJDOC>International Day of Persons With Disabilities (Proc. 9217), </SJDOC>
                    <PGS>72535-72538</PGS>
                    <FRDOCBP T="05DED0.sgm" D="3">2014-28774</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Reclamation</EAR>
            <HD>Reclamation Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Fee Sites:</SJ>
                <SJDENT>
                    <SJDOC>Stony Gorge Reservoir, Elk Creek, CA, </SJDOC>
                    <PGS>72201-72202</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28569</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Science Technology</EAR>
            <HD>Science and Technology Policy Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Science and Technology Council, </SJDOC>
                    <PGS>72217</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28570</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Regulation Systems Compliance and Integrity, </DOC>
                    <PGS>72252-72447</PGS>
                    <FRDOCBP T="05DER2.sgm" D="195">2014-27767</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72218-72219</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28549</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28550</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28551</FRDOCBP>
                </DOCENT>
                <SJ>Options Price Reporting Authority:</SJ>
                <SJDENT>
                    <SJDOC>Reporting of Consolidated Options Last Sale Reports and Quotation Information, </SJDOC>
                    <PGS>72219-72221</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28545</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28546</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Municipal Securities Rulemaking Board, </SJDOC>
                    <PGS>72225-72235</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="8">2014-28543</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28548</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NASDAQ Stock Market, LLC, </SJDOC>
                    <PGS>72221-72223</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28534</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>72223-72225</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28547</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Options Clearing Corp., </SJDOC>
                    <PGS>72225</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28544</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>The NASDAQ Stock Market LLC, </SJDOC>
                    <PGS>72235-72236</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28584</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72236-72237</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28512</FRDOCBP>
                </DOCENT>
                <SJ>Disaster Declarations:</SJ>
                <SJDENT>
                    <SJDOC>Colorado; Amendment 1, </SJDOC>
                    <PGS>72237</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28514</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Social</EAR>
            <HD>Social Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72237-72239</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">2014-28562</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Control Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>Genesee and Wyoming, Inc.; Arkansas Midland Railroad Co., Inc., The Prescott and Northwestern Railroad Co., and Warren and Saline River Railroad Co., </SJDOC>
                    <PGS>72244-72245</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28571</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Railroad Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Surface Transportation Board</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Comptroller of the Currency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign Assets Control Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Immigration</EAR>
            <PRTPAGE P="vi"/>
            <HD>U.S. Immigration and Customs Enforcement</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>72192</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28504</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Application for United States Flag for Burial Purposes, </SJDOC>
                    <PGS>72248</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="0">2014-28558</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>PACT Evaluating Peer Notifications to Improve Statin Medication Adherence among Patients with Coronary Artery Disease, </SJDOC>
                    <PGS>72248-72249</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28556</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Using Peer Mentors to Support Patient Aligned Care Team Efforts to Improve Diabetes, </SJDOC>
                    <PGS>72249-72250</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">2014-28557</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Securities and Exchange Commission, </DOC>
                <PGS>72252-72447</PGS>
                <FRDOCBP T="05DER2.sgm" D="195">2014-27767</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>72450-72497</PGS>
                <FRDOCBP T="05DEP2.sgm" D="47">2014-28536</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>72500-72533</PGS>
                <FRDOCBP T="05DER3.sgm" D="33">2014-28505</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>72535-72538</PGS>
                <FRDOCBP T="05DED0.sgm" D="3">2014-28774</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>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="72107"/>
                <AGENCY TYPE="F">FEDERAL RESERVE SYSTEM</AGENCY>
                <CFR>12 CFR Part 210</CFR>
                <DEPDOC>[Regulation J; Docket No. R-1473]</DEPDOC>
                <RIN>RIN 7100-AE06</RIN>
                <SUBJECT>Collection of Checks and Other Items by Federal Reserve Banks and Funds Transfers Through Fedwire: Time of Settlement by a Paying Bank for an Item Received From a Reserve Bank</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Board of Governors (Board) is adopting amendments to subpart A of its Regulation J, 
                        <E T="03">Collection of Checks and Other Items by Federal Reserve Banks and Funds Transfers through Fedwire,</E>
                         to permit the Federal Reserve Banks (Reserve Banks) to require paying banks that receive presentment of checks from the Reserve Banks to make the proceeds of settlement for those checks available to the Reserve Banks as soon as one half-hour after receipt of the checks. The amendments will also permit the Reserve Banks to obtain settlement from paying banks by as early as 8:30 a.m. eastern time for checks that the Reserve Banks present. These amendments to Regulation J are consistent with the revised method for posting debits and credits to banks' Federal Reserve accounts to measure daylight overdrafts under amendments to the 
                        <E T="03">Federal Reserve Policy on Payment System Risk</E>
                         (PSR policy) that the Board is concurrently adopting. The Board is also adopting a technical amendment to the definition of “Administrative Reserve Bank.”
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         The technical amendment to § 210.2(c) is effective on December 5, 2014. All other amendments are effective on July 23, 2015. 
                        <E T="03">Applicability Date:</E>
                         All items scheduled to settle on July 23, 2015, and after will post according to the new posting rule procedures for these transactions, regardless of date of deposit.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Susan V. Foley, Senior Associate Director (202/452-3596), Samantha J. Pelosi, Manager (202/530-6292), Scott J. Anchin, Senior Financial Services Analyst (202/452-3638), Division of Reserve Bank Operations and Payment Systems; or Evan Winerman, Senior Attorney (202/872-7578), Legal Division; for users of Telecommunication Devices for the Deaf (TDD) only, contact 202/263-4869.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Subpart A of Regulation J, Collection of Checks and Other Items by Federal Reserve Banks, governs the collection of checks and the handling of returned checks by the Reserve Banks. The purpose of the subpart is to provide rules for collecting and returning items and settling balances. Among other things, the subpart specifies the time and manner in which paying banks must settle for items presented to them by the Reserve Banks.</P>
                <P>
                    In accordance with Subpart A, the Reserve Banks have issued Operating Circular 3 (OC 3), 
                    <E T="03">Collection of Cash Items and Returned Checks,</E>
                     which provides specific terms and conditions under which the Reserve Banks will handle checks.
                    <SU>1</SU>
                    <FTREF/>
                     The Board's Regulation CC, 
                    <E T="03">Availability of Funds and Collection of Checks,</E>
                     and provisions of the Uniform Commercial Code (UCC), as adopted in a state, also govern the collection, presentment, and return of checks, to the extent those provisions are not inconsistent with Regulation J.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Operating Circular 3 is available at 
                        <E T="03">www.frbservices.org/regulations/operating_circulars.html.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         12 CFR part 229; UCC Article 4.
                    </P>
                </FTNT>
                <P>
                    On December 10, 2013, the Board requested comment on proposed changes to the PSR policy.
                    <SU>3</SU>
                    <FTREF/>
                     The changes related to the Board's procedures for posting debit and credit entries to depository institutions' Federal Reserve accounts for automated clearinghouse (ACH) debit transactions and commercial check transactions. At the same time, the Board requested comment on proposed changes to Regulation J that would conform to the proposed changes to the PSR policy.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         78 FR 74130 (Dec. 10, 2013). The Federal Reserve's current policy on payment system risk is available at 
                        <E T="03">www.federalreserve.gov/paymentsystems/psr_policy.htm.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         78 FR 74041 (Dec.10, 2013).
                    </P>
                </FTNT>
                <P>
                    Currently, § 210.9(b)(2)(i) of Regulation J provides that the proceeds of a paying bank's settlement must be made available to its Administrative Reserve Bank by the latest of (1) the next clock hour that is at least one hour after the paying bank receives the check; (2) 9:30 a.m. eastern time; or (3) such later time as provided in the Reserve Banks' operating circulars.
                    <SU>5</SU>
                    <FTREF/>
                     Under this section, 9:30 a.m. is the earliest time a paying bank is required to settle for an item, and there has to be at least one hour between the time the item was presented to the paying bank and the time the paying bank settles for the item. The same rules apply to the settlement of returned items under § 210.12(i).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         All times are eastern time unless otherwise specified. Section 210.9(b)(3)(i) sets forth similar times of day if the paying bank closes voluntarily on a Reserve Bank banking day. Section 210.9(b)(4)(i) sets forth analogous times if the paying bank receives an item on a banking day on which the Reserve Bank is closed, 
                        <E T="03">i.e.,</E>
                         a business day that is not a banking day for the Reserve Bank.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Section 210.12(i) of Regulation J provides that recipients of returned items must settle with Reserve Banks in the same manner and by the same time as items presented for payment.
                    </P>
                </FTNT>
                <P>Section 12.2 of the Reserve Banks' Operating Circular 3 currently sets 11:00 a.m. as the earliest settlement time (later than 9:30 a.m. set forth in Regulation J). Under section 12.2, the proceeds of a paying bank's settlement must be available to its Administrative Reserve Bank by the later of 11:00 a.m. or the next clock hour that is at least one hour after the paying bank receives the item, but no later than 3:00 p.m. local time of the paying bank.</P>
                <P>
                    Consistent with the proposed PSR policy changes, the Board proposed that § 210.9(b)(2)(i) of Regulation J be revised to state that the paying bank shall settle for an item by the latest of (1) the next clock hour or clock half-hour that is at least one half-hour after the paying bank receives the item; (2) 8:30 a.m.; or (3) such later time as provided in the Reserve Banks' operating circulars. For example, if a Reserve Bank presents an item by 8:00 a.m., the paying bank would be required to settle for the item at 8:30 a.m., unless a later settlement time were provided for in the Reserve 
                    <PRTPAGE P="72108"/>
                    Banks' operating circulars. The Board proposed similar changes in §§ 210.9(b)(3)(i) and (b)(4)(i).
                </P>
                <P>The Board also proposed to define “clock half-hour,” a new term in § 210.2(p)(2), to mean a time that is on the half-hour (for example, 1:30 or 2:30). Section 210.2(p), which the Board proposed to redesignate as  § 210.2(p)(1), currently defines the term “clock hour” as a time that is on the hour (for example, 1:00 or 2:00).</P>
                <HD SOURCE="HD1">II. Summary of Public Comments and Analysis</HD>
                <P>
                    The Board received six comments submitted by depository institution trade organizations on the proposed amendments to Regulation J.
                    <SU>7</SU>
                    <FTREF/>
                     The Board considered these comments in developing its final rule as discussed below.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The comment letters are available at 
                        <E T="03">http://www.federalreserve.gov/apps/foia/proposedregs.aspx.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. One Half-Hour Window Between Presentment and Settlement</HD>
                <P>The Board requested comment on whether one half-hour between receipt of items by a paying bank and the paying bank's settlement is sufficient for a paying bank to perform a limited verification of cash letters and determine whether to settle for or return the cash letter. The Board also requested comment on whether a shorter period between presentment and settlement would be appropriate (for example, fifteen minutes).</P>
                <P>Two commenters, the American Bankers Association and the Independent Community Bankers of America, supported the Board's proposal to reduce the settlement window to one half-hour, agreeing that advances in check processing allow for a shorter period between check presentment and settlement. One commenter, the American Bankers Association, did not support shortening the period further to 15 minutes but did not provide a specific reason.</P>
                <P>The Board believes that the almost all-electronic nature of check processing that currently exists makes one half-hour between presentment and settlement sufficient because of the reduced time required to verify cash letters in an electronic environment.</P>
                <P>
                    The Board also believes that sufficient tools are available to depository institutions to mitigate any adverse effect that movement to a one half-hour settlement window would have on an institution's Federal Reserve account balance. Past trends indicate that an institution should be able to predict within a reasonable margin of error the approximate dollar value of the checks it expects the Reserve Banks to present and should be able to hold balances sufficient to cover that amount. The Reserve Banks now pay interest on most institutions' Federal Reserve account balances, reducing institutions' opportunity cost (that is, loss of interest) associated with holding higher account balances overnight.
                    <SU>8</SU>
                    <FTREF/>
                     In addition, the PSR policy allows eligible institutions to collateralize their daylight overdrafts to avoid paying a fee. For each two-week reserve maintenance period, depository institutions also receive a $150 fee waiver, reducing the burden on institutions that might incur small amounts of uncollateralized daylight overdrafts.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         12 CFR 204.10.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The Board notes that Federal Home Loan Banks (FHLBs) are not eligible to earn interest on balances in Federal Reserve accounts, but can act as pass-through correspondents. Per § 204.10 of Regulation D, in cases of balances maintained by pass-through correspondents that are not interest-eligible institutions, Reserve Banks shall pay interest only on the balances maintained to satisfy a reserve balance requirement of one or more respondents, and the correspondents shall pass back to its respondents interest paid on balances in the correspondent's account (12 CFR 204.10). The Board notes also that voluntary collateralization of daylight overdrafts and the $150 fee waiver are not available to Edge and agreement corporations, bankers' banks that have not waived their exemption from reserve requirements, limited-purpose trust companies, government-sponsored enterprises (including FHLBs), and international organizations. These types of institutions do not have regular access to the discount window and, therefore, are expected not to incur daylight overdrafts in their Federal Reserve accounts.
                    </P>
                </FTNT>
                <P>For these reasons, the Board is adopting as proposed the amendments shortening the minimum time period between receipt of checks by a paying bank and the paying bank's settlement to one half-hour. The Board did not receive any comments on the proposal to define “clock half-hour” as a new term in § 210.2(p)(2) and is adopting the new term as proposed.</P>
                <HD SOURCE="HD2">B. Earliest Settlement Time at 8:30 a.m.</HD>
                <P>
                    The Board requested comment on whether to permit the Reserve Banks to obtain settlement from a paying bank for a check by as early as 8:30 a.m. The Board also requested comment on the feasibility of settlement earlier than 8:30 a.m., given the current almost all-electronic check processing environment, and whether an earlier settlement time would even better align presentment to settlement.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         In September 1997, the Board revised § 210.9(b) to explicitly refer to 9:30 a.m. (rather than one hour after the opening of Fedwire) as the earliest time a paying bank could be required to settle for an item. This revision to § 210.9(b) was intended to ensure the earliest settlement time for checks remained unchanged when the scheduled opening of Fedwire moved from 8:30 a.m. to an earlier hour. 62 FR 48166, 48169 (Sept. 15, 1997). In December 1997, the scheduled opening of Fedwire was moved from 8:30 a.m.to  12:30 a.m., and in May 2004, it moved to 9:00 p.m. on the preceding calendar day. For example, for the Reserve Banks' banking day of Tuesday, Fedwire opens at 9:00 p.m. on Monday.
                    </P>
                </FTNT>
                <P>Two commenters, the American Bankers Association and the Independent Community Bankers of America, supported the proposal to allow the Reserve Banks to obtain settlement from a paying bank for a check by as early as 8:30 a.m., noting that the rules that allow the Reserve Banks to pay interest on account balances held by institutions reduces the cost that institutions might incur to hold funds overnight to cover any checks presented early the next morning. One commenter, the American Bankers Association, did not support the proposal to move the settlement time earlier than 8:30 a.m. but did not provide a specific reason. Four commenters, the Credit Union National Association, the Georgia Credit Union League, the Missouri Credit Union Association, and the National Association of Federal Credit Unions, expressed concern that some smaller institutions might be negatively affected by the proposed change and might have to increase their Federal Reserve account balances to settle presented checks by holding higher balances overnight, arranging for additional funding before settlement time, or incurring daylight overdrafts.</P>
                <P>
                    The Board recognizes that some depository institutions will need to fund their accounts earlier in order to settle for checks by as early as 8:30 a.m. or incur daylight overdrafts. The Board believes, however, that sufficient tools are available to depository institutions to mitigate any adverse effect that a change to 8:30 a.m. may present. As discussed earlier, the Reserve Banks now pay interest on most institutions' Federal Reserve account balances, eligible institutions can collateralize their daylight overdrafts to avoid paying a fee, and depository institutions receive a  $150 fee waiver for each two-week reserve maintenance period. The changes to the posting rules of the PSR policy and to Regulation J better align the policy and regulation with today's electronic check processing environment, in which over 90 percent of checks are available to be presented by 8:00 a.m. and prompt settlement is possible for the majority of the value of check activity.
                    <SU>11</SU>
                    <FTREF/>
                     Accordingly, the Board 
                    <PRTPAGE P="72109"/>
                    is adopting the amendments to Regulation J, § 210.9(b) as proposed. The Reserve Banks plan to amend OC 3 to conform to the changes in Regulation J.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         In addition, the proposed posting rules would give earlier availability for items deposited with the Reserve Banks and for credit adjustments and corrections.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Effective date</HD>
                <P>
                    The Board proposed that the changes to the PSR policy and these conforming changes to Regulation J would become effective six months after publication in the 
                    <E T="04">Federal Register</E>
                    . The Board requested comment on whether six months provided paying banks with sufficient time to make any necessary operational changes.
                </P>
                <P>Five commenters, the American Bankers Association, the Credit Union National Association, the Georgia Credit Union League, the Independent Community Bankers of America, the Missouri Credit Union Association, believed that a six-month lead time would allow enough time to make any necessary operational changes. One commenter, the National Association of Federal Credit Unions, requested that the Board allow a one-year implementation period, stating that the proposed six-month implementation period would not allow institutions enough time to adjust their policies and procedures to reduce the chances of incurring daylight overdraft fees. The Board is adopting an effective date of July 23, 2015. All items scheduled to settle on this date and after will post according to the new posting rule procedures for these transactions, regardless of date of deposit.</P>
                <HD SOURCE="HD1">III. Technical Amendment</HD>
                <P>
                    The Board is also adopting a technical amendment to the definition of “Administrative Reserve Bank.” 
                    <SU>12</SU>
                    <FTREF/>
                     Section 210.2(c) states that an “Administrative Reserve Bank” is the Reserve Bank in whose District the entity is located, as determined under the procedure described in § 204.3(b)(2) of the chapter (Regulation D). The Board has relocated  § 204.3(b)(2) of Regulation D to § 204.3(g).
                    <SU>13</SU>
                    <FTREF/>
                     Accordingly, the Board is amending the definition of “Administrative Reserve Bank” in § 210.2(c) to cross-reference § 204.3(g) rather than § 204.3(b)(2).
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         12 CFR 210.2(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         74 FR 25629, 25633-34 (May 29, 2009).
                    </P>
                </FTNT>
                <P>
                    The Board did not provide public notice or request comment regarding this technical amendment. Pursuant to section 553(b)(3)(B) of the Administrative Procedure Act,
                    <SU>14</SU>
                    <FTREF/>
                     the Board finds that public notice and comment is unnecessary because the technical amendment does not effect a substantive change; rather, the technical amendment conforms § 210.2(c) to reorganized Regulation D. For the same reasons, the Board finds that there is good cause for the technical amendment to be effective immediately, rather than thirty days after its publication date.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         5 U.S.C. 553(b)(3)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         5 U.S.C. 553(d)(3).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Competitive Impact Analysis</HD>
                <P>
                    The Board conducts a competitive impact analysis when it considers a rule or policy change that may have a substantial effect on payment system participants. Specifically, the Board determines whether there would be a direct and material adverse effect on the ability of other service providers to compete with the Federal Reserve due to legal differences or due to the Federal Reserve's dominant market position deriving from such legal differences.
                    <SU>16</SU>
                    <FTREF/>
                     If such legal differences exist, the Board will assess whether the same objectives could be achieved by a modified proposal with lesser competitive impact or, if not, whether the benefits of the proposal outweigh the effect on competition.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Federal Reserve Regulatory Service, 7-145.2.
                    </P>
                </FTNT>
                <P>The Board believes that the amendments to Regulation J do not have a direct and material adverse effect on the ability of other service providers to compete effectively with the Reserve Banks in providing similar services.</P>
                <P>
                    Under Regulation J, the Reserve Banks have the legal ability to obtain same-day settlement for checks they present before the paying bank's cut-off hour (typically 2:00 p.m. local time) through “auto-charge,” that is, a direct debit to the Federal Reserve account of the paying bank or its correspondent settlement agent.
                    <SU>17</SU>
                    <FTREF/>
                     Under amended Regulation J, the Reserve Banks could present a check at any time before the paying bank's cut-off hour and debit the account of the paying bank or its correspondent settlement agent on the next clock hour or half-hour that is at least one half-hour after presentment.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         12 CFR 210.9(b)(1) and (b)(5).
                    </P>
                </FTNT>
                <P>
                    In contrast, the latest that a private-sector bank may present a paper check for same-day settlement is 8:00 a.m. local time. Section 229.36(f) of Regulation CC requires the paying bank to settle for the check by credit to a Reserve Bank account designated by the presenting bank by the close of Fedwire (currently 6:30 p.m.) or by another agreed-upon method and time.
                    <SU>18</SU>
                    <FTREF/>
                     Thus, the Reserve Banks may present checks later in the day for same-day settlement than private-sector banks. In addition, the Reserve Banks may obtain settlement earlier in the day than private-sector collecting banks and, in turn, may pass credits for deposited checks earlier in the day without incurring significant intraday float.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         12 CFR 229.36(f)(2).
                    </P>
                </FTNT>
                <P>
                    In March 1998, the Board requested comment on whether these legal differences between the rights of the Reserve Banks and private-sector presenting banks provided the Reserve Banks with a competitive advantage and whether the Board should take action to reduce the differences.
                    <SU>19</SU>
                    <FTREF/>
                     Commenters generally concluded that the costs of further changes outweighed any advantage of the Reserve Banks. In particular, commenters noted the efficiency of the Reserve Bank's auto-charge process for paying banks, and stated that moving the private-sector presentment deadline to later in the day or eliminating the direct debit of Federal Reserve accounts for check presentments would result in higher costs to paying banks and their business customers in terms of account management, settlement funds transfer fees, and shortened processing windows, and that those costs would outweigh the benefits gained by presenting banks. Based on an analysis of the comments, the Board took no further action.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         The request for comment and the subsequent notice of the Board's decision can be found, respectively, at 63 FR 12700 (March 16, 1998) and 63 FR 68701 (December 14, 1998).
                    </P>
                </FTNT>
                <P>
                    Currently, institutions may determine, as part of the agreement between a presenting bank and a paying bank, the time at which settlement for electronic checks is required to be funded. A presenting bank and a paying bank could agree, for example, to a minimum time between presentment and settlement. For presenting banks and paying banks that opt to use a check clearinghouse rather than directly exchange checks, private-sector clearinghouses have the option to use the Reserve Banks' National Settlement Service (NSS) to effect settlement of checks or may settle by directing their members to initiate funds transfers over the Reserve Banks' Fedwire Funds Service.
                    <SU>20</SU>
                    <FTREF/>
                     Beginning in January 2015, the NSS file submission window will be 7:30 a.m. to 5:30 p.m. Fedwire Funds operating hours begin at 9:00 p.m. the 
                    <PRTPAGE P="72110"/>
                    previous calendar day and end at 6:30 p.m.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         NSS is a multilateral settlement service owned and operated by the Reserve Banks. The service is offered to depository institutions that settle for participants in clearinghouses, financial exchanges, and other clearing and settlement groups. Settlement agents, acting on behalf of depository institutions in a settlement arrangement, electronically submit settlement files to the Reserve Banks. Files are processed upon receipt, and entries are automatically posted to the depository institutions' Reserve Bank accounts. The NSS file submission window is currently 8:30 a.m. to 5:00 p.m.
                    </P>
                </FTNT>
                <P>Under the final amendments to Regulation J and the recently adopted changes to the PSR policy posting rules, the bulk of the Reserve Banks' postings of credits to senders and debits to paying banks for commercial check transactions will shift to earlier in the day. The value of checks a bank sends to the Reserve Banks could be higher or lower than the value it receives from the Reserve Banks. As a result, the earlier posting of commercial check transactions may be viewed as more or less attractive, depending on whether the value of an institution's check credits is higher or lower than the value of its check debits. Further, private-sector institutions can achieve improvements in earlier settlement similar to those provided by the rule and the PSR policy changes through private agreements among participants, as well as the use of NSS.</P>
                <P>
                    More recently, the Board requested comment on the continued utility of the Regulation CC same-day settlement rule for paper checks and whether the rule should be applied to electronic check presentments by private-sector banks. The Board also noted that if, in the future, it proposes to eliminate the same-day settlement rule, it could also propose to retain the proscription against paying banks' assessment of presentment fees in order to maintain the current balance of bargaining power, as well as reduce the competitive disparities in presentment abilities between the Reserve Banks and private-sector banks.
                    <SU>21</SU>
                    <FTREF/>
                     The Board is in the process of analyzing these comments and will discuss these issues, as appropriate, at a later date in the context of the final amendments to Regulation CC. In the meantime, the Board does not believe that the changes to Regulation J reducing the minimum time between presentment and settlement to 30 from 60 minutes, and moving the earliest settlement time to 8:30 a.m. from 9:30 a.m., changes the Reserve Banks' competitive position versus private-sector presenting banks in a material way.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         79 FR 6674 (Feb. 14, 2014).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Final Regulatory Flexibility Analysis</HD>
                <P>
                    The Board has reviewed the final regulation in accordance with section 3(a) of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). The rule would apply to all depository institutions that receive presentment or return of checks from the Reserve Banks. Based on current information, the Board believes that the final rule would not have a significant economic impact on a substantial number of small entities (5 U.S.C. 605(b)). Nonetheless, a Final Regulatory Flexibility Analysis has been prepared in accordance with 5 U.S.C. 604, after consideration of comments received during the public comment period.
                </P>
                <HD SOURCE="HD3">Statement of the Need for, and Objectives of the Final Rule</HD>
                <P>These final amendments to Regulation J are necessary to conform the required settlement times for checks presented by the Reserve Banks to the method for posting debits and credits to institutions' Federal Reserve accounts to measure daylight overdrafts under recent revisions to the PSR policy. The Board believes that the Regulation J revisions and the PSR policy posting rules better align the settlement for checks with actual deposit and presentment times, reflecting the industry's almost complete shift from paper to electronic check processing.</P>
                <HD SOURCE="HD3">Public Comments</HD>
                <P>
                    The Board requested information and comment on any costs that would arise from the application of the proposed rule. Four institutions expressed concern that some smaller institutions might be negatively affected by the proposed change and might have to increase their Federal Reserve account balances to settle presented checks by holding higher balances overnight, arranging for additional funding before settlement time, or incurring daylight overdrafts. As discussed earlier, the Board believes that sufficient tools are available to depository institutions to mitigate any adverse effect. For example, the Reserve Banks now pay interest on most institutions' Federal Reserve account balances, eligible institutions can collateralize their daylight overdrafts to avoid paying a fee, and depository institutions receive a $150 fee waiver for each two-week reserve maintenance period.
                    <SU>22</SU>
                    <FTREF/>
                     As further discussed earlier, under the PSR policy posting rules, the bulk of the Reserve Banks' postings of debits to paying institutions for commercial check transactions will shift to earlier in the day, allowing the Reserve Banks to provide credits to depositing institutions earlier, thus mitigating adverse effects on depository institutions.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         A small number of institutions could be ineligible to receive intraday credit and would incur overdrafts. To avoid violating the PSR policy and incurring fees, these institutions would need to increase funding either overnight or early in the morning. Some of these institutions could be eligible to receive interest on Federal Reserve account balances.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Small Entities Affected by the Rule</HD>
                <P>The final rule affects all institutions that receive checks or returned checks handled by the Reserve Banks. The Board believes that virtually all depository institutions receive checks or returned checks handled by the Reserve Banks on at least an occasional basis. Pursuant to regulations issued by the Small Business Administration (SBA) (13 CFR 121.201), a “small banking organization” includes a depository institution with $550 million or less in total assets. Based on data reported as of  June 30, 2014, the Board believes that there are approximately 11,750 small depository institutions.</P>
                <HD SOURCE="HD3">Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
                <P>The final rule would permit the Reserve Banks to require a paying bank to settle for an item by as early as 8:30 a.m., instead of 9:30 a.m., and as soon as one half-hour, instead of one hour, after it receives the item from the Reserve Banks. Paying banks may choose to fund their accounts to accommodate the earlier settlement time by holding sufficient balances overnight or arranging for funding before the settlement time. Otherwise, paying banks would incur daylight overdrafts in their Federal Reserve account. The rule contains no other reporting, recordkeeping, or compliance requirements.</P>
                <HD SOURCE="HD3">Steps Taken To Minimize Impact of, and Significant Alternatives to, the Final Rule</HD>
                <P>
                    As noted earlier, four commenters, the Credit Union National Association, the Georgia Credit Union League, the Missouri Credit Union Association, and the National Association of Federal Credit Unions, suggested that some smaller institutions might be negatively affected by the proposed change and might have to increase their Federal Reserve account balances to settle presented checks by holding higher balances overnight or arranging for additional funding before settlement time. Otherwise, paying banks would incur daylight overdrafts. As discussed earlier, the Board believes that sufficient tools are available to depository institutions to mitigate any adverse effect on an institution's Federal Reserve account balance (including interest on Federal Reserve account balances, collateralization of daylight overdrafts to avoid paying a fee, and a $150 fee waiver for each two-week reserve maintenance period). As further 
                    <PRTPAGE P="72111"/>
                    discussed earlier, under the PSR policy posting rules, the bulk of the Reserve Banks' postings of debits to paying institutions for commercial check transactions will shift to earlier in the day, allowing the Reserve Banks to provide credits to depositing institutions earlier, thus mitigating adverse effects on depository institutions.
                </P>
                <P>Alternatively, the Board could have adopted a rule that permits the Reserve Banks to require a paying bank to settle for an item at a time earlier than 8:30 a.m. or leave the earliest possible settlement time at 9:30 a.m. The Board believes the proposed time of 8:30 a.m. better achieves the Board's goal of aligning presentment to settlement, and better aligns with today's electronic check processing environment, than the existing 9:30 a.m. settlement time under Regulation J. In addition, the Board believe that the proposed settlement time of 8:30 a.m. will impose minimal costs on paying banks. The Board sought comment on (1) whether permitting the Reserve Banks to obtain settlement from a paying bank for a check by as early as 8:30 a.m. was appropriate and (2) the feasibility of settlement prior to  8:30 a.m. and whether an earlier posting time would even better align presentment to settlement. (See discussion earlier in section II.B.)</P>
                <P>In addition, in lieu of proposing to permit the Reserve Banks to require a paying bank to settle as soon as one half-hour after it receives the item from the Reserve Banks, the Board could have proposed a shorter or longer period. The Board believes the final time period of one half-hour promotes the Board's objective of minimizing the window between presentment and settlement to reflect technological and operational developments while continuing to provide paying banks with sufficient time to perform a limited verification of cash letters. The Board requested comment on whether one half-hour between presentment and settlement is appropriate or if a shorter window would be sufficient. (See discussion earlier in section II.A.)</P>
                <HD SOURCE="HD1">VI. Paperwork Reduction Act Analysis</HD>
                <P>In accordance with the Paperwork Reduction Act (PRA) of 1995  (44 U.S.C. 3506; 5 CFR part 1320, appendix A.1), the Board reviewed the final rule under the authority delegated to the Board by the Office of Management and Budget (OMB). No collections of information pursuant to the PRA are contained in the final rule.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 210</HD>
                    <P>Banks, Banking, Federal Reserve System.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Authority and Issuance</HD>
                <P>For the reasons set forth in the preamble, the Board amends Regulation J, 12 CFR part 210, as follows:</P>
                <REGTEXT TITLE="12" PART="210">
                    <PART>
                        <HD SOURCE="HED">PART 210—COLLECTION OF CHECKS AND OTHER ITEMS BY FEDERAL RESERVE BANKS AND FUNDS TRANSFERS THROUGH FEDWIRE (REGULATION J)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 210 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>12 U.S.C. 248(i), (j), and 248-1, 342, 360, 464, 4001-4010, and 5001-5018.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="210">
                    <AMDPAR>2. In § 210.2, revise paragraphs (c) and (p) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 210.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Administrative Reserve Bank</E>
                             with respect to an entity means the Reserve Bank in whose District the entity is located, as determined under the procedure described in § 204.3(g) of this chapter (Regulation D), even if the entity is not otherwise subject to that section.
                        </P>
                        <STARS/>
                        <P>
                            (p) 
                            <E T="03">Clock hour and clock half-hour.</E>
                             (1) 
                            <E T="03">Clock hour</E>
                             means a time that is on the hour, such as 1:00, 2:00, etc.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Clock half-hour</E>
                             means a time that is on the half-hour, such as 1:30, 2:30, etc.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="12" PART="210">
                    <AMDPAR>3. In § 210.9, revise paragraphs (b)(2), (3), and (4) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 210.9 </SECTNO>
                        <SUBJECT>Settlement and payment.</SUBJECT>
                        <STARS/>
                        <P>(b)  * * * </P>
                        <P>
                            (2) 
                            <E T="03">Time of settlement.</E>
                             (i) On the day a paying bank receives a cash item from a Reserve Bank, it shall settle for the item so that the proceeds of the settlement are available to its administrative Reserve Bank, or return the item, by the latest of—
                        </P>
                        <P>(A) The next clock hour or clock half-hour that is at least one half-hour after the paying bank receives the item;</P>
                        <P>(B) 8:30 a.m. eastern time; or</P>
                        <P>(C) Such later time as provided in the Reserve Banks' operating circulars.</P>
                        <P>(ii) If the paying bank fails to settle for or return a cash item in accordance with paragraph (b)(2)(i) of this section, it shall be subject to any applicable overdraft charges. Settlement under paragraph (b)(2)(i) of this section satisfies the settlement requirements of paragraph (b)(1) of this section.</P>
                        <P>
                            (3) 
                            <E T="03">Paying bank closes voluntarily.</E>
                             (i) If a paying bank closes voluntarily so that it does not receive a cash item on a day that is a banking day for a Reserve Bank, and the Reserve Bank makes a cash item available to the paying bank on that day, the paying bank shall either—
                        </P>
                        <P>(A) On that day, settle for the item so that the proceeds of the settlement are available to its administrative Reserve Bank, or return the item, by the latest of the next clock hour or clock half-hour that is at least one half-hour after it ordinarily would have received the item, 8:30 a.m. eastern time, or such later time as provided in the Reserve Banks' operating circulars; or</P>
                        <P>(B) On the next day that is a banking day for both the paying bank and the Reserve Bank, settle for the item so that the proceeds of the settlement are available to its administrative Reserve Bank by 8:30 a.m. eastern time on that day or such later time as provided in the Reserve Banks' operating circulars; and compensate the Reserve Bank for the value of the float associated with the item in accordance with procedures provided in the Reserve Bank's operating circular.</P>
                        <P>(ii) If a paying bank closes voluntarily so that it does not receive a cash item on a day that is a banking day for a Reserve Bank, and the Reserve Bank makes a cash item available to the paying bank on that day, the paying bank is not considered to have received the item until its next banking day, but it shall be subject to any applicable overdraft charges if it fails to settle for or return the item in accordance with paragraph (b)(3)(i) of this section. The settlement requirements of paragraphs (b)(1) and (2) of this section do not apply to a paying bank that settles in accordance with paragraph (b)(3)(i) of this section.</P>
                        <P>
                            (4) 
                            <E T="03">Reserve Bank closed.</E>
                             (i) If a paying bank receives a cash item from a Reserve Bank on a banking day that is not a banking day for the Reserve Bank, the paying bank shall—
                        </P>
                        <P>(A) Settle for the item so that the proceeds of the settlement are available to its administrative Reserve Bank by the close of Fedwire on the Reserve Bank's next banking day, or return the item by midnight of the day it receives the item (if the paying bank fails to settle for or return a cash item in accordance with this paragraph (b)(4)(i)(A), it shall become accountable for the amount of the item as of the close of its banking day on the day it receives the item); and</P>
                        <P>
                            (B) Settle for the item so that the proceeds of the settlement are available to its administrative Reserve Bank by 8:30 a.m. eastern time on the Reserve Bank's next banking day or such later 
                            <PRTPAGE P="72112"/>
                            time as provided in the Reserve Bank's operating circular, or return the item by midnight of the day it receives the item. If the paying bank fails to settle for or return a cash item in accordance with this paragraph (b)(4)(i)(B), it shall be subject to any applicable overdraft charges. Settlement under this paragraph (b)(4)(i)(B) satisfies the settlement requirements of paragraph (b)(4)(i)(A) of this section.
                        </P>
                        <P>(ii) [Reserved]</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <P>By order of the Board of Governors of the Federal Reserve System, December 1, 2014.</P>
                    <NAME>Robert deV. Frierson, </NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28516 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <CFR>12 CFR Part 210</CFR>
                <DEPDOC>[Docket No. OP-1472]</DEPDOC>
                <SUBJECT>Federal Reserve Policy on Payment System Risk; Procedures for Measuring Daylight Overdrafts</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Policy statement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Board of Governors of the Federal Reserve System (Board) has adopted revisions to part II of the Federal Reserve Policy on Payment System Risk (PSR policy) related to the procedures for measuring balances intraday in institutions' accounts at the Federal Reserve Banks (Reserve Banks). The changes relate to the Board's procedures for posting debit and credit entries to institutions' Federal Reserve accounts for automated clearinghouse (ACH) debit transactions and commercial check transactions. Elsewhere in the 
                        <E T="04">Federal Register</E>
                         under Docket No. R-1473, the Board has adopted related changes to the Board's Regulation J that affect when paying banks settle for check transactions presented to them by the Reserve Banks. Additionally, in this document, the Board has adopted a set of principles for establishing future posting procedures for the Reserve Banks' same-day ACH service. The Board has also adopted a change in language of the PSR policy intended to clarify the Reserve Banks' administration of the policy for U.S. branches and agencies of foreign banking organizations. Finally, the Board has adopted two technical revisions to the posting procedures to reflect deposit deadlines already in effect for Treasury checks, postal money orders, local Federal Reserve Bank checks, and savings bond redemptions in separately sorted deposits.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Dates:</E>
                         The policy changes related to the set of principles for establishing future posting procedures for the Reserve Banks' same-day ACH service, the Reserve Banks' administration of the policy for U.S. branches and agencies of foreign banking organizations, and the technical revisions to the posting procedures for Treasury checks, postal money orders, local Federal Reserve Bank checks, and savings bond redemptions will take effect on December 5, 2014. The policy changes to the Board's procedures for posting debit and credit entries to institutions' Federal Reserve accounts for ACH debit and commercial check transactions will take effect on July 23, 2015. All items scheduled to settle on this date and after will post according to the new posting rule procedures for these transactions, regardless of date of deposit.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> Susan V. Foley, Senior Associate Director (202/452-3596), Jeffrey D. Walker, Assistant Director (202/721-4559), or Michelle D. Olivier, Senior Financial Services Analyst (202/452-2404), Division of Reserve Bank Operations and Payment Systems, Board of Governors of the Federal Reserve System; for users of Telecommunications Device for the Deaf (TDD) only, contact 202/263-4869.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On December 10, 2013, the Board requested comment on several changes to part II of the PSR policy intended to enhance the efficiency of the payment system.
                    <SU>1</SU>
                    <FTREF/>
                     Technology and processing improvements have enabled payment systems and depository institutions to achieve significant efficiencies since the Board first established the procedures, referred to as posting rules, to measure depository institutions' intraday Federal Reserve account balances. The proposed changes to these posting rules are intended to align them with current operations and processing times and to strategically position the rules for future advancements in the speed of clearing and settlement.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         78 FR 74130 (Dec. 10, 2013). The Board's PSR policy is available at 
                        <E T="03">www.federalreserve.gov/paymentsystems/psr_policy.htm.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Commercial and Government ACH Debit Transactions</HD>
                <P>
                    The Board proposed moving the posting times for commercial and government ACH debit transactions processed overnight to 8:30 a.m. from 11:00 a.m. eastern time (ET) to coincide with the posting time for ACH credit transactions processed overnight.
                    <SU>2</SU>
                    <FTREF/>
                     Under the proposal, other types of ACH transactions, including same-day ACH and certain ACH return items, would not be affected and would continue to post at 5:00 p.m.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         All times are eastern time unless otherwise specified. 
                    </P>
                    <P>In 2008, the Board requested comment on moving the posting time of ACH debit transactions from 11:00 a.m. to 8:30 a.m. to coincide with the posting of ACH credit transactions but decided not to pursue the change because of economic conditions at the time and the additional costs and liquidity pressures that could be placed on some institutions. The request for comment and the subsequent notice of the Board's decision not to pursue the proposed changes can be found, respectively, at 73 FR 12443  (Mar. 7, 2008) and 73 FR 79127 (Dec. 24, 2008).</P>
                </FTNT>
                <P>
                    The Board outlined four potential benefits to shifting earlier the posting for ACH debit transactions. First, posting ACH debit transactions according to the proposed posting rules would simplify account management by allowing institutions to fund the net of all ACH activity at a single posting time, rather than funding debit and credit transactions separately. Second, the change would increase liquidity early in the day both for institutions that originate ACH debit transactions over the FedACH network and for those institutions that originate ACH debit transactions over the Electronic Payments Network (EPN), the other ACH operator, but have transactions delivered to receiving institutions over the FedACH network (interoperator transactions).
                    <SU>3</SU>
                    <FTREF/>
                     Third, moving the posting time for ACH debit transactions to 8:30 a.m. would align the Reserve Banks' FedACH settlement times with those of EPN. The Board believes that this change would remove any potential competitive disparities between the two ACH operators and their participants arising from the different settlement times for ACH debit transactions. Fourth, the earlier posting of ACH debit transactions would increase the efficiency of the ACH network by aligning better the settlement of ACH debit transactions with their processing. Additionally, posting ACH debit transfers at 8:30 a.m. would better conform to the Board's principles for measuring daylight overdrafts, specifically the principle that encourages posting times to be as close as possible to the delivery of payments to the receiving institution.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Liquidity refers to balances in Federal Reserve accounts to make payments. An increase in liquidity involves higher account balances, which could result in fewer daylight overdrafts.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Board's four principles for measuring daylight overdrafts are as follows: (1) The 
                        <PRTPAGE/>
                        measurement procedures should not provide intraday float to participants. (2) The measurement procedures should reflect the times at which payor institutions are obligated to pay for transactions. (3) The users of payment services should be able to control their use of intraday credit. (4) The Reserve Banks should not obtain any competitive advantage from the measurement procedures. The Board developed the principles in the early 1990s; for the latest version, refer to 73 FR 12443 (Mar. 7, 2008).
                    </P>
                </FTNT>
                <PRTPAGE P="72113"/>
                <HD SOURCE="HD2">Commercial Check Transactions</HD>
                <P>
                    The Board proposed several revisions to its posting rules for commercial check transactions to reflect today's nearly 100 percent electronic check-processing environment. Specifically, the Board proposed to post commercial check transactions, both credits and debits, at 8:30 a.m., 1:00 p.m., and 5:30 p.m., with the specific posting time depending on when a check is deposited with the Reserve Banks (for credit) or presented by the Reserve Banks (for debit).
                    <SU>5</SU>
                    <FTREF/>
                     Credits associated with any commercial checks received by the Reserve Banks' deposit deadlines would post on a rolling basis at the next available posting time at least 30 minutes after receipt by the Reserve Banks.
                    <SU>6</SU>
                    <FTREF/>
                     Similarly, debits associated with electronic check transactions would post on a rolling basis at the next available posting time that is at least 30 minutes after presentment to the paying bank. To accommodate the extra time required to make paper presentments, debits for the few remaining paper commercial check transactions, which account for less than one-tenth of 1 percent of checks processed by the Reserve Banks, would post at the final posting time of 5:30 p.m. on the day the paper check is presented to the paying bank.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Under the current posting rules, commercial check credits post according to one of two options: (1) All credits post at a single, float-weighted posting time, or (2) fractional credits post between the hours of 11:00 a.m. and 6:00 p.m., depending on the institution's preference. The second option lets the institution receive portions of its available check credits on the clock hours between 11:00 a.m. and 6:00 p.m. The option selected applies to all check deposits posted to an institution's account. Both crediting options are based on surveys of check presentment times and vary across time zones. Commercial check debits are posted on the next clock hour at least one hour after presentment beginning at 11:00 a.m. for paper checks and 1:00 p.m. local time for electronic checks, and ending at 3:00 p.m. local time.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Immediate credit would not be passed for deferred-availability deposit products. Customer availability for files deposited for these services would be the same as if the file were received at a deposit deadline before 8:00 a.m. the next business day.
                    </P>
                    <P>Currently, the Reserve Banks' electronic check deposit deadlines are 9:00 p.m. on the previous business day, and 1:00 a.m., 5:00 a.m., and 10:00 a.m. on the settlement day. The paper check deposit deadline is 7:00 p.m. on the previous business day. As a result, depositing banks could expect credit for all electronic items deposited for the 9:00 p.m., 1:00 a.m., and 5:00 a.m. deposit deadlines to post at 8:30 a.m., and credit for electronic items deposited for the 10:00 a.m. deadline to post at 1:00 p.m. Paper items deposited by 7:00 p.m. on the previous day would post at 8:30 a.m.</P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The posting of debits associated with electronic presentments earlier than the debits associated with paper check presentments may contribute marginally to a given paying bank's incentive to require that checks be presented to it in paper form. Electronic check presentment is now pervasive, however, and the Board does not believe that a paying bank that receives presentments electronically would be swayed by the later posting time to return to paper presentment.
                    </P>
                    <P>Credits for checks presented in paper form would not be delayed to accommodate the extra time required for presentment and would post at the next available posting time at least 30 minutes after receipt by the Reserve Banks. The Reserve Banks will monitor the value of commercial checks presented in paper form, and should it increase materially, the Board may propose changes to the posting rules to reduce float.</P>
                </FTNT>
                <P>
                    Under the current posting rules and Regulation J, at least one hour must elapse between presentment and posting to allow limited verification of cash letters. The Board proposed reducing this requirement from one hour to 30 minutes. As a result of the widespread use of electronic check-handling methods and the extremely small value of paper presentments, the Board believes 30 minutes is now sufficient for institutions to verify cash letters.
                    <SU>8</SU>
                    <FTREF/>
                     Additionally, as part of the proposed posting rules, the Reserve Banks would present multiple electronic cash letters per day to institutions that receive electronic presentments, with the first presentment by 8:00 a.m. for settlement at 8:30 a.m.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Board issued a companion document requesting comment on proposed changes to Regulation J, under which a paying bank would be required to settle for an item by as early as 8:30 a.m. and as soon as one half-hour after it receives the item from the Reserve Banks. The request for comment can be found at 78 FR 74041 (Dec. 10, 2013). Elsewhere in the 
                        <E T="04">Federal Register</E>
                         under Docket No. R-1473, the Board adopted these changes to Regulation J.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The timing and frequency of presentments is subject to change by the Reserve Banks to align better with processing advancements and product type.
                    </P>
                </FTNT>
                <P>
                    The Board also proposed to revise the posting rules for large-value check corrections and adjustments amounting to $1 million or more.
                    <SU>10</SU>
                    <FTREF/>
                     In alignment with the proposed posting times for commercial check transactions, the Board proposed to move the settlement of large-value credit corrections and adjustments to begin at 8:30 a.m. and hourly thereafter on the half-hour depending on when the discrepancy is detected.
                    <SU>11</SU>
                    <FTREF/>
                     Additionally, the Board proposed to post large-value debit corrections after the close of the Fedwire Funds Service, the same time as large-value debit adjustments are posted.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Corrections are account entries made to correct discrepancies detected by a Reserve Bank during the initial processing of checks. Adjustments are account entries made to correct discrepancies detected by an institution after entries have posted to Federal Reserve accounts.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Currently, credit corrections and adjustments amounting to $1 million or more post at 11:00 a.m. and hourly thereafter, coinciding with the current posting rules for commercial checks.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Currently, debit corrections amounting to $1 million or more post at 11:00 a.m. and hourly thereafter.
                    </P>
                </FTNT>
                <P>
                    The Board outlined four potential benefits from the proposed changes to its commercial check posting rules. First, the proposed posting rules would give earlier availability for items deposited with the Reserve Banks based on an institution's deposit behavior and would provide earlier availability for credit adjustments and corrections. Second, these changes would simplify the posting rule structure and, as a result, reduce the administrative burden on institutions and Reserve Banks. Third, the proposed rules would reduce the amount of intraday float currently provided by the Reserve Banks as a result of posting rules that do not adequately reflect current operations.
                    <SU>13</SU>
                    <FTREF/>
                     Fourth, the proposals would align the posting rules with the significant shift over the past decade from paper to electronic check clearing. The proposed commercial check posting rules would conform better to the Board's principles for measuring daylight overdrafts, specifically the principles that discourage providing intraday float and encourage posting times to be as close as possible to the delivery of payments to the receiving institution.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Under the current posting rules, check credits and paper check debits begin posting at 11:00 a.m., whereas electronic check debits begin posting at 1:00 p.m. local time. As a result, the current measurement procedures provide intraday float, which has increased over time as electronic deposits and presentments have expanded.
                    </P>
                </FTNT>
                <P>
                    As part of its posting rule proposals, the Board assessed the effect of the ACH debit and commercial check transaction posting rule changes on institutions' account balances and daylight overdraft fees both separately and combined. The Board recognized that the combined effect of the changes would, on average, reduce institutions' Federal Reserve account balances at 8:30 a.m. for the majority of master accounts that settle ACH and commercial check activity (94 percent of approximately 3,500 master accounts) based on second-quarter 2013 payment data.
                    <SU>14</SU>
                    <FTREF/>
                     Less than 1 percent of 
                    <PRTPAGE P="72114"/>
                    these institutions, only 33 institutions, would incur overdraft fees in any of the six two-week reserve maintenance periods within the quarter analyzed. The low incidence of fees can be attributed to the current levels of pledged collateral and collateralized daylight overdrafts receiving a zero fee, the $150 fee waiver covering modest amounts of uncollateralized overdrafts, and the high balances held in Federal Reserve accounts. Twenty-eight of the 33 institutions are eligible to incur daylight overdrafts and could avoid paying higher fees by pledging (additional) collateral, holding higher balances and receiving interest on their Federal Reserve balances, or arranging early-morning funding. The remaining 5 institutions are ineligible to receive intraday credit and would need to increase funding in their accounts either by holding higher balances (and in some cases potentially receiving interest on their Federal Reserve balances) or by arranging early-morning funding.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Although most institutions that maintain master accounts are involved in both ACH and commercial check activity, approximately half of these institutions settle their activity through a correspondent rather than their own master account.
                    </P>
                    <P>
                        In connection with the 2013 proposal, analysis reflects activity at the master account level from the 
                        <PRTPAGE/>
                        second quarter 2013 and is intended to be illustrative only. All institutions should consider their own historical payment activity when evaluating the effect of the posting rule changes.
                    </P>
                    <P>The average balance calculation only includes days in the second quarter of 2013 for which institutions had ACH debit or commercial check payment activity. The simulation of balances focused only on balances held at 8:30 a.m., while the analysis of fees and collateral took into account balances held and collateral pledged over the entire 21.5-hour Fedwire operating day.</P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         These institutions include bankers' banks and Federal Home Loan Banks, and not all would be eligible to earn interest on their Federal Reserve balances.
                    </P>
                </FTNT>
                <P>For both the ACH debit and commercial check posting rule proposals, the Board proposed an effective date of no less than six months from the publication of the revised PSR policy to give institutions sufficient time to make any necessary changes.</P>
                <HD SOURCE="HD2">Principles for Future Posting Rules for the Reserve Banks' Same-Day ACH Service</HD>
                <P>
                    Given the Board's expectations that the Reserve Banks' same-day ACH service will evolve, with the potential establishment of additional processing cycles that require new posting times for settlement, the Board proposed establishing a set of principles that would be applied to any new same-day ACH posting rules.
                    <SU>16</SU>
                    <FTREF/>
                     Under the proposal, the Board would generally request public comment on changes to the posting rules only when the changes deviate from the principles. Such principles would apply to the Reserve Banks' voluntary (opt-in) same-day ACH service and to any future same-day ACH service, such as a universal same-day ACH service covering all participants in the ACH network.
                    <SU>17</SU>
                    <FTREF/>
                     These principles, which would apply in addition to the current four posting-rules principles, were proposed as follows:
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         The current processing schedule has a 2:00 p.m. deadline for submitting same-day, forward ACH transactions for settlement at 5:00 p.m. Return same-day ACH transactions post at 5:30 p.m.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         In 2011, NACHA, a not-for-profit association that manages the development, administration, and governance of the ACH network for participating depository institutions, proposed amendments to its operating rules to enable ACH debit and credit transfers to be cleared and settled on the same day that they are originated. The expedited service would require the participation of all receiving institutions in the ACH network, going beyond the Reserve Banks' voluntary service. Although the majority of NACHA's voting members were in favor of the proposal, NACHA did not receive the 75 percent positive votes required for passage. NACHA is currently evaluating modifications to its earlier proposal to address concerns expressed regarding it.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         These four posting-rule principles are outlined in a footnote earlier in this document.
                    </P>
                </FTNT>
                <P>(1) For each same-day ACH transmission deadline, the Reserve Banks will establish expected distribution times for the same-day ACH files.</P>
                <P>a. The Reserve Banks will post settlement for same-day ACH debit transactions no earlier than 15 minutes after the Reserve Banks' expected distribution times for the associated same-day ACH file.</P>
                <P>b. The Reserve Banks will post settlement for ACH credit and debit transactions associated with a particular same-day ACH file distribution time at the same time.</P>
                <P>(2) The Reserve Banks will not post settlement for same-day ACH transactions between 6:30 p.m. and 8:30 a.m. on the next processing day.</P>
                <P>
                    (3) The Reserve Banks will post settlement for same-day ACH transactions exchanged with another operator to support universal same-day ACH during the operating hours for the Reserve Banks' National Settlement Service (NSS).
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         NSS is a multilateral settlement service owned and operated by the Reserve Banks. The service is offered to institutions that settle for participants in clearinghouses, financial exchanges, and other clearing and settlement groups. Settlement agents, acting on behalf of those institutions in a settlement arrangement, electronically submit settlement files to the Reserve Banks. Files are processed upon receipt, and entries are automatically posted to the institutions' Federal Reserve accounts. The NSS file submission window is currently 8:30 a.m. to 5:00 p.m.
                    </P>
                </FTNT>
                <P>The Board proposed that the principles for future posting rules for the Reserve Banks' same-day ACH service would be effective on final approval.</P>
                <HD SOURCE="HD2">Language Clarification in Section II.G.3</HD>
                <P>
                    The Board proposed a language clarification to part II of the PSR policy to explain more clearly the Reserve Banks' administration of the PSR policy as it relates to U.S. branches and agencies of foreign banking organizations (FBOs). The proposed language would clarify that U.S. branches and agencies of the same foreign bank (also referred to as an FBO family) are expected to manage their accounts so that the daylight overdraft position in each account does not exceed the capacity allocated to that account from the FBO family's net debit cap.
                    <SU>20</SU>
                    <FTREF/>
                     In the past, the Reserve Banks monitored the master accounts of FBO families on a consolidated basis rather than requiring an FBO family to allocate its net debit cap if it wanted to incur daylight overdrafts in more than one account across the Federal Reserve.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         The previous language in the PSR policy that related to the administration of multiple master accounts was somewhat ambiguous and could have been interpreted to allow the Federal Reserve to administer these accounts as is the current practice (separate administration for the multiple master accounts) or the previous practice (consolidated administration).
                    </P>
                </FTNT>
                <P>The Board proposed that the language change clarifying the Reserve Banks' administration of the policy for U.S. branches and agencies of FBOs would be effective on final approval.</P>
                <HD SOURCE="HD1">III. Summary of Public Comments and Analysis</HD>
                <P>
                    The Board received thirteen comment letters in response to its PSR policy proposals.
                    <SU>21</SU>
                    <FTREF/>
                     Comments were submitted by seven depository institution trade organizations, one private-sector clearing and settlement system, one commercial banking organization, one bankers' bank, one government-sponsored enterprise, and two individuals. Most commenters expressed support for the posting-rule proposals' intent to improve the speed and efficiency of the payment system but also raised specific concerns. The Board considered these comments in finalizing its changes to the PSR policy, as discussed in more detail below.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         The comment letters are available at 
                        <E T="03">http://www.federalreserve.gov/apps/foia/proposedregs.aspx.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Effect on Credit Unions and Small Institutions</HD>
                <P>
                    Five commenters, including four depository institution trade organizations and a bankers' bank, expressed concerns regarding the effect of the ACH debit and commercial check posting rule proposals on credit unions and small institutions.
                    <SU>22</SU>
                    <FTREF/>
                     The 
                    <PRTPAGE P="72115"/>
                    commenters were supportive of the proposals' intent but believed that credit unions and smaller institutions might be disproportionately affected and the proposals could lead to more-frequent and larger daylight overdrafts and associated fees. Given the concerns raised by commenters related to these types of institutions, the Board performed additional analysis on the effect of the combined ACH debit and commercial check proposals on these institutions based on second-quarter 2013 payment data, consistent with the 2013 proposal. Of the approximately 3,500 master accounts maintained by institutions that settle ACH and commercial check activity, almost 800 (22 percent) are maintained by natural person credit unions. The combined posting rule proposals would, on average, reduce account balances held in Federal Reserve accounts at 8:30 a.m. for 94 percent of these institutions. Out of those credit unions that would experience lower balances, only 1 credit union would incur higher daylight overdraft fees as a result of the proposals, and this credit union was already incurring fees under the current posting rules. The average increase in fees over the quarter under the proposed posting rules would be $132 per reserve maintenance period.
                    <SU>23</SU>
                    <FTREF/>
                     To avoid fee increases, this credit union could pledge on average $7 million of additional collateral.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Commenters were the Credit Union National Association, Georgia Credit Union League, Missouri Credit Union Association, National Association of Federal Credit Unions, and Midwest Independent Bank.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         The average calculation includes all reserve maintenance periods in the quarter.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         The average calculation only includes reserve maintenance periods for which the credit union required (additional) collateral.
                    </P>
                </FTNT>
                <P>Excluding natural person credit unions, an additional 2,500 master accounts of the approximately 3,500 master accounts maintained by institutions that settle ACH and commercial check activity are maintained by institutions with assets of less than $10 billion. The combined posting rule proposals would reduce, on average, account balances held in Federal Reserve accounts at 8:30 a.m. for 95 percent of these institutions. Out of those small institutions that would experience lower balances, approximately 1 percent, only 25 institutions, would incur higher fees as a result of the proposals. More than one-third of the 25 institutions were already incurring fees under the current posting rules, and the average increase in fees over the quarter under the proposed posting rules would be $66 per reserve maintenance period. To avoid fee increases, these 25 institutions could pledge on average $10 million of (additional) collateral.</P>
                <P>The Board recognizes that many institutions are holding higher balances in their Federal Reserve accounts today, and although second-quarter 2013 payment data indicate that only a very limited number of credit unions and institutions with assets less than $10 billion would incur higher fees under the proposal, over time, more of these institutions may need to alter their account management in response to the posting rule changes. Nevertheless, the Board believes that institutions have the tools to mitigate any adverse impact. For each two-week reserve maintenance period, institutions receive a $150 fee waiver, which is intended to reduce the burden on institutions that incur a small amount of uncollateralized daylight overdrafts. Many institutions have considerable room for additional daylight overdrafts under the waiver. In addition, institutions could post (additional) collateral, hold higher balances overnight, or arrange early morning funding. Interest on balances in Federal Reserve accounts would help compensate those institutions that hold higher balances overnight in their Federal Reserve accounts.</P>
                <HD SOURCE="HD2">Effect on Institutions Ineligible for Access to Intraday Credit</HD>
                <P>
                    One commenter, representing the interests of five Federal Home Loan Banks without regular access to the discount window and thus without access to intraday credit under the PSR policy because of their classification as government-sponsored enterprises, expressed concern that the proposed posting rule for ACH debit transactions would be excessively burdensome for institutions ineligible for access to intraday credit.
                    <SU>25</SU>
                    <FTREF/>
                     The commenter believed that, in addition to account management changes necessary to avoid incurring daylight overdrafts, such as holding higher balances overnight or finding alternative liquidity sources, the proposal might require these institutions to reduce their income-generating investments of overnight funds. The commenter also believed that, if adopted, the new posting rule for ACH debit transactions might cause institutions ineligible for access to intraday credit to re-evaluate the provision of ACH services to their customers and the fees associated with ACH services. The Board acknowledges that institutions ineligible for access to intraday credit may face additional challenges as a result of the proposed posting rule for ACH debit transactions. Of the 26 institutions ineligible to incur daylight overdrafts that participate in FedACH, 22 on average would experience lower balances at 8:30 a.m. under the proposed posting rule for ACH debit transactions. Only 4 of these 22 institutions, however, would incur daylight overdrafts according to the Board's analysis of second-quarter 2013 payment data. The average maximum overdrafts incurred by these 4 institutions over the quarter analyzed ranged from just under $100,000 to slightly below $100 million, with an average of $33 million across the 4 institutions. These institutions would need to arrange early-morning funding or hold higher balances overnight based on expected settlement of ACH activity.
                    <SU>26</SU>
                    <FTREF/>
                     The Board understands that there may be costs associated with these actions, and institutions would need to weigh the costs and benefits of their account-management options. In addition, the Board acknowledges that some institutions that would experience lower balances might also need to manage their Federal Reserve accounts more closely to avoid daylight overdrafts under the proposed posting rule for ACH debit transactions.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Edge and agreement corporations, bankers' banks that have not waived their exemption from reserve requirements, limited-purpose trust companies, government-sponsored enterprises including Federal Home Loan Banks (FHLBs), and international organizations do not have regular access to the discount window and are not permitted to incur daylight overdrafts in their Federal Reserve accounts. Voluntary collateralization of daylight overdrafts and the $150 fee waiver are not available to these institutions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Only one of the four institutions is eligible to earn interest on its Federal Reserve account balance.
                    </P>
                </FTNT>
                <P>A limited number of institutions that are ineligible for access to intraday credit may need to manage their Federal Reserve accounts to avoid daylight overdrafts as a result of the earlier posting time for ACH debit transfers. The Board believes that these institutions can reasonably manage their Federal Reserve accounts for activity settling at 8:30 a.m. given the availability of Fedwire Funds beginning at 9:00 p.m. the previous calendar day. The Board believes that the associated burden of closer account management by a small number of institutions is outweighed by the benefits of the earlier posting time discussed earlier, including the long-run efficiency of the payment system.</P>
                <HD SOURCE="HD2">Competitive Disparity Between Reserve Bank and Private-Sector Services</HD>
                <P>
                    In response to the Board's ACH debit and commercial check posting rule proposals, The Clearing House (TCH), which owns EPN, was supportive of the Board's intent to align and modernize the posting rules but expressed several 
                    <PRTPAGE P="72116"/>
                    short-term and long-term competitive disparity concerns. Specifically, TCH was concerned that the posting rules might give the Reserve Banks an unfair advantage over private-sector clearing and settlement systems as a result of underlying legal differences and the limited settlement hours of NSS. TCH also stated that in the long run, the Board should ensure that all processes related to the posting and settlement of Reserve Bank priced services do not provide an advantage to Reserve Bank priced services over those of other clearing and settlement systems. TCH stated that, in the short-term, the posting rules should avoid disrupting the settlement of clearing and settlement systems, specifically EPN's 8:30 a.m. settlement of ACH transactions over NSS. Two additional commenters, U.S. Bank and NACHA, endorsed and emphasized the importance of addressing TCH's concerns related to the proposed posting rules for ACH debit and commercial check transactions.
                </P>
                <P>
                    Reserve Bank priced services settle transactions in participants' Federal Reserve accounts through direct entries to the Federal Reserve's accounting system whereas private-sector clearing and settlement systems typically use Fedwire Funds, ACH, or NSS to settle transactions in participants' Federal Reserve accounts. The Board has traditionally encouraged the use of NSS for multilateral settlement arrangements to mitigate counterparty credit risk. The establishment of posting rules outside of the NSS operating day could potentially create competitive disparities between Reserve Bank and private-sector clearing and settlement systems. The posting rules proposed for ACH debit and commercial check transactions occur within the NSS file submission window, with the exception of the final posting time for commercial check transactions at  5:30 p.m. and the posting of a limited number of check debit and small-dollar credit corrections and adjustments after the close of Fedwire. The Reserve Banks will extend the NSS file submission window until 5:30 p.m. beginning in January 2015. In regard to the posting of debit corrections and adjustments after the close of Fedwire Funds, such late posting ensures that an institution could not receive a debit correction or adjustment before the associated transaction posted. Given the minimal occurrence of large-value check corrections and adjustments and the low value of other check corrections and adjustments, the Board does not believe posting these transactions after the close of Fedwire creates a significant competitive disparity between Reserve Bank and private-sector service providers.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         In addition to debit corrections and adjustments, small-dollar credit corrections and adjustments also post after the close of the Fedwire Funds Service.
                    </P>
                </FTNT>
                <P>
                    Additionally, TCH was concerned that the Reserve Banks' priced services personnel could view participants' Federal Reserve account balances, daylight overdraft capacity, and placement on the real-time monitor and use that information to restrict transactions or payment services as a means of managing potential settlement failures.
                    <SU>28</SU>
                    <FTREF/>
                     Although the Reserve Banks' priced services personnel may have the ability to view account balances in the normal course of business operations, they do not have access to daylight overdraft capacity or risk control information. The Reserve Banks, like other clearing and settlement systems, use a range of risk-management tools that may include requiring minimum balances and collateral to manage the inherent risk of providing services, but Reserve Bank priced services personnel do not influence the application of these controls to be able to affect the outcome of settlement and do not have the ability to apply such controls.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         For the limited number of institutions that may expose the Federal Reserve and other payment system participants to risk of loss, the Reserve Banks have implemented tools, including the Account Balance Monitoring System (ABMS), which can monitor institutions' payment activity in real time. ABMS verifies that institutions have sufficient balances to fund their Fedwire Funds, NSS, and certain ACH credit transactions as these payment files are submitted and processed. ABMS may reject these transactions if there are insufficient funds to cover the associated payments, regardless of whether the payment files are processed by the Reserve Banks or submitted by private-sector clearing and settlement systems through NSS.
                    </P>
                    <P>
                        Institutions that are monitored in real time must fund the total amount of their commercial ACH credit originations in order for the transactions to be processed. If the Federal Reserve receives commercial ACH credit transactions from institutions monitored in real time after the scheduled close of the Fedwire Funds Service, these transactions are currently processed at 12:30 a.m. the next business day, or by the ACH deposit deadline, whichever is earlier. ABMS provides intraday account information to the Reserve Banks and institutions and is used primarily to give authorized Reserve Bank personnel a mechanism to control and monitor account activity for selected institutions. For more information on ACH transaction processing, refer to the “ACH Settlement Day Finality Guide” available through the Federal Reserve Financial Services Web site at 
                        <E T="03">http://www.frbservices.org.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         The Federal Reserve's “Standards Related to Priced-Service Activities of the Federal Reserve Banks” states that “No Reserve Bank personnel with responsibility for priced services, unless acting in the capacity of president or first vice president, will also be responsible for monetary policy, bank supervision, or lending areas. Priced-service personnel will not make policy decisions affecting monetary policy, bank supervision, or lending matters.” 
                        <E T="03">http://www.federalreserve.gov/paymentsystems/pfs_standards.htm</E>
                        .
                    </P>
                </FTNT>
                <P>
                    TCH encouraged the Board to ensure that, in the long run, all processes related to the posting and settlement for Reserve Bank priced services more broadly do not provide an advantage to the Reserve Banks over the private-sector clearing and settlement systems as a result of legal or settlement differences between providers. In the normal course, the Board will continue to assess Reserve Bank priced service proposals for new products, pricing, or posting rules to determine if any competitive advantage is derived from legal differences. In the case of settlement, the Board believes that potential competitive disparities can be addressed by expanding NSS operating hours to encompass more of the Fedwire Funds day. Private-sector clearing and settlement systems would then generally have the ability if needed to settle transactions in participants' Federal Reserve accounts over similar hours as Reserve Bank priced services.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         Commercial check debit and small-dollar credit corrections and adjustments post after the close of Fedwire. Given the minimal occurrence of large-value check corrections and adjustments and the low value of other check corrections and adjustments, the Board does not believe posting these transactions after the close of Fedwire provides a competitive advantage to the Reserve Bank priced services.
                    </P>
                </FTNT>
                <P>
                    In the short run, TCH also requested that the Board delay the posting of ACH debit transactions until after 8:30 a.m. to avoid potentially disrupting EPN's 8:30 a.m. settlement over NSS.
                    <SU>31</SU>
                    <FTREF/>
                     TCH believed that posting FedACH debit transactions at 8:30 a.m. could lower EPN participants' Federal Reserve account balances and increase the likelihood that a participant would have insufficient funds to settle its activity over EPN. The Board believes there are several factors that minimize the likelihood of such an outcome. The posting of ACH debit and credit transactions simultaneously at 8:30 a.m. may result in an increase in balances held by institutions that are large originators of ACH debit transactions; many of the largest ACH debit originators are EPN customers. The posting-rule change benefits not only FedACH participants that originate debit transactions but also EPN 
                    <PRTPAGE P="72117"/>
                    customers that originate debit transactions destined to FedACH customers, which settle according to the Board's posting rules. Institutions currently hold high balances, and most have access to daylight overdrafts, with total daylight overdraft capacity calculated as multiples of capital for healthy institutions, to ensure the smooth functioning of the payment system. Although high balances may not remain, balances are not likely to drop precipitously in the near term, giving institutions time to adjust account-management activity, if needed, to ensure sufficient balances for all payment activity settling at 8:30 a.m. In addition, the Reserve Banks debit funds to cover ACH credit transactions for any institution on the highest level of control under the real-time monitor at the time of file submission, not when the payments settle under the posting rules. The Reserve Banks also will extend the NSS file submission window from 7:30 a.m. to 5:30 p.m., beginning in January 2015, and are evaluating potential further expansion of NSS hours in the future. Given these factors, the Board continues to believe that posting ACH debit transactions at 8:30 a.m. is the best option for the long-run safety and efficiency of the payment system.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         TCH also requested a clarification on how FedACH debit and credit transactions would post simultaneously at 8:30 a.m. Under the proposed posting rules, both ACH debit and credit transactions would be assigned the same posting time, 8:30 a.m., and post exactly at the same time for purposes of measuring an institution's daylight overdraft balance. Debit and credit transactions would not be netted before posting; however, because all transactions would post exactly at the same minute, the institution's account balance would only change by the net of its activity.
                    </P>
                </FTNT>
                <P>The Board acknowledges some of the competitive concerns expressed by TCH and agrees with the need to have settlement options available at the same time to avoid introducing potential competitive disparities. In the near term, the Board believes that extending the NSS file submission window from 7:30 a.m. to 5:30 p.m. mitigates any adverse competitive effect of the ACH debit and commercial check posting rule changes. In the long run, the Board believes that any competitive disparity concerns resulting more broadly from Reserve Banks' ability to settle transactions outside of NSS hours can be addressed by further expanding NSS operating hours, and potentially functionality.</P>
                <P>The Board has adopted the posting rules for ACH debit and commercial check transactions as proposed.</P>
                <HD SOURCE="HD2">Effective Dates for Posting Rule Proposals</HD>
                <P>
                    As part of its posting rules proposals for ACH debit and commercial check transactions, the Board proposed a six-month implementation period before the new posting rules would become effective. Five commenters, including four depository institution trade associations and one government-sponsored enterprise, indicated that an effective date six months after the publication of the final rule in the 
                    <E T="04">Federal Register</E>
                     would allow enough time to make necessary operational changes.
                    <SU>32</SU>
                    <FTREF/>
                     One commenter, the National Association of Federal Credit Unions, requested a one-year implementation period to allow institutions additional time to determine if they were affected by the proposed posting rules and, if so, to raise capital. Given commenters' feedback, the Board is adopting an implementation period of no less than six months as proposed, and the posting rule changes for ACH debit and commercial check transactions will take effect on July 23, 2015. All items scheduled to settle on this date and after will post according to the new posting rule procedures, regardless of the date of deposit.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         Commenters were the American Bankers Association, Credit Union National Association, Georgia Credit Union league, Missouri Credit Union Association, and a joint letter from five Federal Home Loan Banks.
                    </P>
                </FTNT>
                <P>
                    Elsewhere in the 
                    <E T="04">Federal Register</E>
                     under Docket No. R-1473, the Board also adopted necessary related changes to the Board's Regulation J (12 CFR part 210) regarding the timing of when paying banks settle for check transactions presented to them by the Reserve Banks effective on July 23, 2015.
                </P>
                <HD SOURCE="HD2">Principles for Future Posting Rules for the Reserve Banks' Same-Day ACH Service</HD>
                <P>Two commenters, TCH and U.S. Bank, raised account-management and competitive disparity concerns regarding the second principle proposed by the Board for future posting rules for the Reserve Banks' same-day ACH service. The principle stated that the Reserve Banks would not post settlement for same-day ACH transactions between 6:30 p.m. and 8:30 a.m. the next processing day. Commenters' concerns related to the Reserve Banks' ability to settle same-day ACH transactions until 6:30 p.m. Specifically, the commenters were concerned that posting these transactions up to the close of the Fedwire Funds Service would not allow sufficient time between the settlement of same-day ACH transactions and the close of Fedwire Funds for institutions to settle other positions amongst themselves, and that the period between 5:00 p.m. and 6:30 p.m. was outside of current NSS operating hours, putting any future private-sector same-day ACH service providers at a potential disadvantage relative to the Reserve Banks' service. To address this concern, the Board has modified the second principle to read, “The Reserve Banks will not post settlement for same-day ACH transactions between the close of the Reserve Banks' National Settlement Service and 8:30 a.m. the next processing day.” The modified principle requires that settlement post within the NSS operating day before the close of Fedwire Funds. As a result of the modification, the third proposed posting rule principle, which stated that the Reserve Banks will post settlement for same-day ACH transactions exchanged with another operator to support universal same-day ACH during the operating hours for the Reserve Banks' NSS, is no longer needed. The Board has removed the third principle from the final principles for establishing future posting rules for the Reserve Banks' same-day ACH service. The revised principles are as follows:</P>
                <P>(1) For each same-day ACH transmission deadline, the Reserve Banks will establish expected distribution times for the same-day ACH files.</P>
                <P>a. The Reserve Banks will post settlement for same-day ACH debit transactions no earlier than 15 minutes after the Reserve Banks' expected distribution times for the associated same-day ACH file.</P>
                <P>b. The Reserve Banks will post settlement for ACH credit and debit transactions associated with a particular same-day ACH file distribution time at the same time.</P>
                <P>(2) Settlement will not post between the close of the Reserve Banks' National Settlement Service and 8:30 a.m. on the next processing day.</P>
                <P>
                    In addition, five commenters, including one commercial banking organization, one private-sector clearing and settlement system, and three depository institution trade organizations indicated their preference that the Board always request comment on new same-day ACH posting rule proposals, regardless of whether these rules conformed to the posting rule principles.
                    <SU>33</SU>
                    <FTREF/>
                     Commenters believed it was important to request comment, given that future material considerations may emerge that may not be addressed by the principles and any alterations to the current same-day ACH service may require institutions to make significant changes. The Board continues to believe that the principles provide a reasonable gating mechanism to enable flexibility in the evolution of same-day ACH while still constraining settlement to the NSS operating day during core business hours. The Board expects that 
                    <PRTPAGE P="72118"/>
                    institutions can reasonably manage their Federal Reserve accounts during the core business day. The Board will assess each future posting rule for same-day ACH to determine if public comment may be warranted based on the specific circumstances and the environment at that time and in conformance with the Board's “Principles for Pricing of Federal Reserve Bank Services.” 
                    <SU>34</SU>
                    <FTREF/>
                     Those principles provide that that the Board will request comment on proposed fee or service changes that would have significant longer-run effects on the nation's payment system.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Commenters were U.S. Bank, TCH, Credit Union National Association, Georgia Credit Union League, and Missouri Credit Union Association.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         The Board's “Principles for Pricing of Federal Reserve Bank Services” are available at 
                        <E T="03">http://www.federalreserve.gov/paymentsystems/pfs_principles.htm.</E>
                    </P>
                </FTNT>
                <P>The Board has adopted the same-day ACH principles as revised earlier, effective on December 5, 2014.</P>
                <HD SOURCE="HD2">Language Clarification to Section II.G.3</HD>
                <P>The Board received no comments on its proposed language clarification to part II of the PSR policy regarding operational changes in the administration of the policy as it relates to U.S. branches and agencies of FBOs. The Board has adopted the proposed language changes to section II.G.3 of the PSR policy as proposed effective on December 5, 2014.</P>
                <HD SOURCE="HD1">IV. Additional Technical Revisions to the Posting Rules</HD>
                <P>
                    The Board has revised the PSR policy's posting rules to conform to the current deposit deadline for Treasury checks, postal money orders, local Federal Reserve Bank checks, and savings bond redemptions in separately sorted deposits, which post at 8:30 a.m. The posting rule currently reflects a previous deposit deadline for these items at 12:01 a.m. local time or the local deposit deadline, whichever is later.
                    <SU>35</SU>
                    <FTREF/>
                     Additionally, the Board has revised the posting rules to conform to the current deposit deadline for Treasury checks, postal money orders, and savings bond redemptions in separately sorted deposits which post at 5:00 p.m. The posting rule currently reflects a previous deposit deadline for these items at 4:00 p.m.
                    <SU>36</SU>
                    <FTREF/>
                     The Board is removing these obsolete deposit deadline references and, in both cases, indicating that the posting time will apply to items deposited by the latest applicable deposit deadline preceding the posting time.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         At this time, for posting at 8:30 a.m., the electronic deposit deadline is 5:00 a.m. the same day and the paper check deposit deadline is 7:00 p.m. on the previous business day.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         At this time, the deposit deadline is 10:00 a.m. for items posting at 5:00 p.m.
                    </P>
                </FTNT>
                <P>As the updated deposit deadlines are already in effect for the transactions described earlier, institutions' Federal Reserve account balances are not affected by these updates to the incorrectly stated deposit deadlines in the posting rules. These revisions are effective on December 5, 2014.</P>
                <HD SOURCE="HD1">V. Competitive Impact Analysis</HD>
                <P>
                    The Board conducts a competitive impact analysis when it considers a rule or policy change that may have a substantial effect on payment system participants, such as that being proposed for the posting of ACH debit and commercial check transactions. Specifically, the Board determines whether there would be a direct and material adverse effect on the ability of other service providers to compete with the Federal Reserve due to differing legal powers or due to the Federal Reserve's dominant market position deriving from such legal differences.
                    <SU>37</SU>
                    <FTREF/>
                     The Board believes that there are no adverse effects resulting from the changes due to legal differences.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Federal Reserve Regulatory Service, 7-145.2.
                    </P>
                </FTNT>
                <P>Shifting the posting of ACH debit transactions to 8:30 a.m. brings the settlement of ACH debit transactions processed by the Reserve Banks' FedACH service in line with the private-sector ACH operator, EPN. The posting-rule change benefits not only FedACH participants that originate debit transactions but also EPN customers that originate debit transactions destined to FedACH customers, which settle according to the Board's posting rules. The Board also believes that the implementation window will provide ample time for institutions to make account-management changes, if any.</P>
                <P>
                    Under Regulation J, the Reserve Banks have the legal ability to obtain same-day settlement for checks they present before the paying bank's banking day cutoff hour through “auto-charge,” that is, a direct debit to the Federal Reserve account of the paying bank or its correspondent settlement agent.
                    <SU>38</SU>
                    <FTREF/>
                     Under the amendments to Regulation J explained elsewhere in this 
                    <E T="04">Federal Register</E>
                    , the Reserve Banks will have the right to debit the account of the paying bank or its correspondent settlement agent on the next clock hour or half-hour that is at least one half-hour after presentment. In contrast, when a private-sector bank presents a paper check by 8:00 a.m. for same-day settlement, Regulation CC requires the paying bank to settle for the check by sending a Fedwire Funds transfer to the presenting bank by the close of Fedwire (or by another agreed upon method).
                    <SU>39</SU>
                    <FTREF/>
                     Thus, Reserve Banks may present checks later in the day for same-day settlement than private-sector banks. In addition, Reserve Banks may obtain settlement earlier in the day than private-sector collecting banks and, in turn, may pass credits for deposited checks earlier in the day without incurring significant intraday float.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         12 CFR 210.9(b)(1) and (b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         12 CFR 229.36(f)(2).
                    </P>
                </FTNT>
                <P>
                    In March 1998, the Board requested comment on whether the legal differences between rights of the Reserve Banks and the private-sector presenting banks provided the Reserve Banks with a competitive advantage and whether the Board should take action to reduce the differences. Commenters generally concluded that the costs of further changes outweighed any advantage of the Reserve Banks.
                    <SU>40</SU>
                    <FTREF/>
                     In particular, commenters noted the efficiency of the Reserve Bank's auto-charge process for paying banks, and stated that moving the private-sector presentment deadline to later in the day or eliminating the direct debit of Federal Reserve accounts for check presentments would result in higher costs to paying banks and their business customers in terms of account management, settlement funds transfer fees, and shortened processing windows, and that those costs would outweigh the benefits gained by presenting banks. Based on an analysis of the comments, the Board took no further action.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         The request for comment and the subsequent notice of the Board's decision can be found, respectively, at 63 FR 12700 (March 16, 1998) and 63 FR 68701 (December 14, 1998).
                    </P>
                </FTNT>
                <P>
                    For the vast majority of checks presented by private-sector banks today, which are presented in electronic form, settlement occurs as agreed between the presenting bank and paying bank. Banks may determine, as part of the agreement between the presenting bank and paying bank, the time at which settlement for checks is required to be funded. Furthermore, for collecting banks and paying banks that opt to use a check clearinghouse, the clearinghouses have the option to use NSS to effect settlement of checks or may settle by directing their members to initiate funds transfers over the Reserve Banks' Fedwire Funds Service. Beginning in January 2015, the NSS file submission window will be 7:30 a.m. to 5:30 p.m. Fedwire Funds operating hours begin at 9:00 p.m. the previous calendar day and end at 6:30 p.m. As adopted in this 
                    <E T="04">Federal Register</E>
                     document, effective on July 23, 2015, the Reserve Banks will settle commercial check transactions at 
                    <PRTPAGE P="72119"/>
                    8:30 a.m., 1:00 p.m., and 5:30 p.m. and debits from corrections and adjustments amounting to $1 million or more will settle after the close of Fedwire Funds Service. A limited number of commercial check debit and small-dollar credit corrections and adjustments post after the close of Fedwire. Such late posting ensures that institutions only benefit intraday from detected processing errors and that an institution could not receive a debit correction or adjustment before the associated check transaction posted. Given the minimal occurrence of large-value check corrections and adjustments and the low value of other check corrections and adjustments, the Board does not believe posting these transactions after the close of Fedwire creates a direct and material competitive disparity between Reserve Bank and private-sector service providers.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         In addition to debit corrections and adjustments, small-dollar credit corrections and adjustments also post after the close of Fedwire Funds.
                    </P>
                </FTNT>
                <P>Under the adopted posting rules, the bulk of the Reserve Banks' postings of credits to depositing banks and debits to paying banks for commercial check transactions will shift to earlier in the day. The value of checks a bank sends to the Reserve Banks could be higher or lower than the value it receives from the Reserve Banks. As a result, the earlier posting of commercial check transactions may be viewed as more or less attractive, depending on whether the value of an institution's check credits is higher or lower than the value of its check debits. Further, private-sector banks can achieve improvements similar to those provided by the proposed changes through private agreements among participants, as well as the use of the NSS.</P>
                <P>Given the factors discussed earlier, the Board does not believe that the changes to the posting rules would have a direct and material adverse effect on other service providers to compete effectively with Reserve Banks in providing similar services.</P>
                <HD SOURCE="HD1">VI. Paperwork Reduction Act</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3506; 5 CFR part 1320 appendix A.1), the Board reviewed the PSR policy changes it is considering under the authority delegated to the Board by the Office of Management and Budget. No collection of information pursuant to the Paperwork Reduction Act are contained in the policy statement.</P>
                <HD SOURCE="HD1">VII. Federal Reserve Policy on Payment System Risk</HD>
                <HD SOURCE="HD2">Technical Revisions to the Posting Rules</HD>
                <P>Effective on December 5, 2014, the “Federal Reserve Policy on Payment System Risk” section II.A. under the heading “Procedures for Measuring Daylight Overdrafts” and the subheadings “Post at 8:30 a.m. eastern time” and “Post at 5:00 p.m. eastern time” is amended as follows.</P>
                <P>Post at 8:30 a.m. eastern time:</P>
                <FP SOURCE="FP-2">+/− Term deposit maturities and accrued interest</FP>
                <FP SOURCE="FP-2">
                    +/− Government and commercial ACH credit transactions 
                    <SU>42</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         Institutions that are monitored in real time must fund the total amount of their commercial ACH credit originations before the transactions are processed by the Reserve Banks. If the Federal Reserve receives commercial ACH credit transactions from institutions monitored in real time after the scheduled close of the Fedwire Funds Service, these transactions are currently processed at 12:30 a.m. the next business day, or by the ACH deposit deadline, whichever is earlier. The Account Balance Monitoring System provides intraday account information to the Reserve Banks and institutions and is used primarily to give authorized Reserve Bank personnel a mechanism to control and monitor account activity for selected institutions. For more information on ACH transaction processing, refer to the ACH Settlement Day Finality Guide available through the Federal Reserve Financial Services Web site at 
                        <E T="03">http://www.frbservices.org.</E>
                    </P>
                </FTNT>
                <FP SOURCE="FP-2">+ Treasury checks, postal money orders, local Federal Reserve Bank checks, and savings bond redemptions in separately sorted deposits; these items must be deposited by the latest applicable deposit deadline preceding the posting time.</FP>
                <FP SOURCE="FP-2">+ Advance-notice Treasury investments</FP>
                <FP SOURCE="FP-2">
                    − Penalty assessments for tax payments from the Treasury Investment Program (TIP).
                    <SU>43</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         The Reserve Banks will identify and notify institutions with Treasury-authorized penalties on Thursdays. In the event that Thursday is a holiday, the Reserve Banks will identify and notify institutions with Treasury-authorized penalties on the following business day. Penalties will then be posted on the business day following notification.
                    </P>
                </FTNT>
                <P>Post at 5:00 p.m. eastern time:</P>
                <FP SOURCE="FP-2">+/− FedACH SameDay Service transactions</FP>
                <FP SOURCE="FP-2">+/− Immediate settlement ACH transactions; these transactions include ACH return items and check-truncation items.</FP>
                <FP SOURCE="FP-2">+ Treasury checks, postal money orders, and savings bond redemptions in separately sorted deposits; these items must be deposited by the latest applicable deposit deadline preceding the posting time.</FP>
                <FP SOURCE="FP-2">+ Local Federal Reserve Bank checks; these items must be presented before 3:00 p.m. eastern time</FP>
                <HD SOURCE="HD2">Revisions to Section II.G.3 of the PSR Policy</HD>
                <P>Effective December 5, 2014, section II.G.3 of the “Federal Reserve Policy on Payment System Risk” is amended to clarify the Reserve Banks' administration of the policy for U.S. branches and agencies of foreign banking organizations as follows.</P>
                <HD SOURCE="HD3">3. Multi-District Institutions</HD>
                <P>An institution maintaining merger-transition accounts or an Edge or agreement corporation that accesses Fedwire through master accounts in more than one Federal Reserve District is expected to manage its accounts so that the total daylight overdraft position across all accounts does not exceed the institution's net debit cap. One Reserve Bank will act as the administrative Reserve Bank and will have overall risk-management responsibilities for an institution maintaining master accounts in more than one Federal Reserve District. For domestic institutions that have branches in multiple Federal Reserve Districts, the administrative Reserve Bank generally will be the Reserve Bank where the head office of the bank is located.</P>
                <P>
                    U.S. branches and agencies of the same foreign bank (also referred to as an FBO family) are assigned one net debit cap per FBO family. FBO families that access Fedwire through master accounts in more than one Federal Reserve District are expected to manage their accounts so that the daylight overdraft position in each account does not exceed the capacity allocated to that account from the FBO family's net debit cap. The administrative Reserve Bank generally is the Reserve Bank that exercises the Federal Reserve's oversight responsibilities under the International Banking Act.
                    <SU>44</SU>
                    <FTREF/>
                     The administrative Reserve Bank, in consultation with the management of the foreign bank's U.S. operations and with Reserve Banks in whose territory other U.S. agencies or branches of the same foreign bank are located, may recommend that these agencies and branches not be permitted to incur overdrafts in Federal Reserve accounts. Alternatively, the administrative Reserve Bank, after similar consultation, may recommend that all or part of the foreign family's net debit cap be allocated to the Federal Reserve accounts of agencies or branches that are located outside of the administrative Reserve Bank's District; in this case, the Reserve Bank in whose Districts those agencies or branches are 
                    <PRTPAGE P="72120"/>
                    located will be responsible for administering all or part of this policy.
                    <SU>45</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         12 U.S.C. 3101-3108.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         As in the case of Edge and agreement corporations and their branches, with the approval of the designated administrative Reserve Bank, a second Reserve Bank may assume the responsibility for administering this policy regarding particular foreign branch and agency families. This would often be the case when the payments activity and national administrative office of the foreign branch and agency family is located in one District, while the oversight responsibility under the International Banking Act is in another District. If a second Reserve Bank assumes management responsibility, monitoring data will be forwarded to the designated administrator for use in the supervisory process.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Changes to the Posting Rules for ACH Debit and Commercial Check Transactions</HD>
                <P>Effective on July 23, 2015, the “Federal Reserve Policy on Payment System Risk” section II.A. under the heading “Procedures for Measuring Daylight Overdrafts” is amended as follows.</P>
                <HD SOURCE="HD2">
                    Procedures for Measuring Daylight Overdrafts 
                    <E T="01">
                        <SU>46</SU>
                        <FTREF/>
                    </E>
                </HD>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         This schedule of posting rules does not affect the overdraft restrictions and overdraft-measurement provisions for nonbank banks established by the Competitive Equality Banking Act of 1987 and the Board's Regulation Y (12 CFR 225.52).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Opening Balance (Previous Day's Closing Balance)</HD>
                <P>Post at 8:30 a.m. eastern time:</P>
                <FP SOURCE="FP-2">+/− Term deposit maturities and accrued interest</FP>
                <FP SOURCE="FP-2">
                    +/− Government and commercial ACH transactions 
                    <SU>47</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         Institutions that are monitored in real time must fund the total amount of their commercial ACH credit originations in order for the transactions to be processed. If the Federal Reserve receives commercial ACH credit transactions from institutions monitored in real time after the scheduled close of the Fedwire Funds Service, these transactions are currently processed at 12:30 a.m. the next business day, or by the ACH deposit deadline, whichever is earlier. The Account Balance Monitoring System provides intraday account information to the Reserve Banks and institutions and is used primarily to give authorized Reserve Bank personnel a mechanism to control and monitor account activity for selected institutions. For more information on ACH transaction processing, refer to the ACH Settlement Day Finality Guide available through the Federal Reserve Financial Services Web site at 
                        <E T="03">http://www.frbservices.org.</E>
                    </P>
                </FTNT>
                <FP SOURCE="FP-2">
                    +/− Commercial check transactions, including returned checks 
                    <SU>48</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         For the three commercial check transaction posting times, the Reserve Banks will post credits and debits to institutions' accounts for checks deposited and presented, respectively, at least 30 minutes before the posting time.
                    </P>
                </FTNT>
                <FP SOURCE="FP-2">+ Treasury checks, postal money orders, local Federal Reserve Bank checks, and savings bond redemptions in separately sorted deposits; these items must be deposited by the latest applicable deposit deadline preceding the posting time.</FP>
                <FP SOURCE="FP-2">+ Advance-notice Treasury investments</FP>
                <FP SOURCE="FP-2">
                    − Penalty assessments for tax payments from the Treasury Investment Program (TIP).
                    <SU>49</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         The Reserve Banks will identify and notify institutions with Treasury-authorized penalties on Thursdays. In the event that Thursday is a holiday, the Reserve Banks will identify and notify institutions with Treasury-authorized penalties on the following business day. Penalties will then be posted on the business day following notification.
                    </P>
                </FTNT>
                <P>Post at 8:30 a.m. eastern time and hourly, on the half-hour, thereafter:</P>
                <FP SOURCE="FP-2">+/− Main account administrative investment or withdrawal from TIP</FP>
                <FP SOURCE="FP-2">+/− Special Direct Investment (SDI) administrative investment or withdrawal from TIP</FP>
                <FP SOURCE="FP-2">+ 31 CFR part 202 account deposits from TIP</FP>
                <FP SOURCE="FP-2">
                    + Credit corrections amounting to $1 million or more 
                    <SU>50</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         Corrections are account entries made to correct discrepancies detected by a Reserve Bank during the initial processing of checks.
                    </P>
                </FTNT>
                <FP SOURCE="FP-2">
                    + Credit adjustments amounting to $1 million or more 
                    <SU>51</SU>
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         Adjustments are account entries made to correct discrepancies detected by an institution after entries have posted to Federal Reserve accounts.
                    </P>
                </FTNT>
                <FP SOURCE="FP-2">− Uninvested paper tax (PATAX) deposits from TIP</FP>
                <FP SOURCE="FP-2">− Main account balance limit withdrawals from TIP</FP>
                <FP SOURCE="FP-2">− Collateral deficiency withdrawals from TIP</FP>
                <FP SOURCE="FP-2">− 31 CFR part 202 deficiency withdrawals from TIP</FP>
                <P>Post at 11:00 a.m. eastern time and hourly thereafter:</P>
                <FP SOURCE="FP-2">+ Currency and coin deposits</FP>
                <P>Post at 1:00 p.m. eastern time:</P>
                <FP SOURCE="FP-2">
                    <E T="03">+/−</E>
                     Commercial check transactions, including returned checks
                </FP>
                <P>Post at 5:30 p.m. eastern time:</P>
                <FP SOURCE="FP-2">+/− FedACH SameDay Service return transactions.</FP>
                <FP SOURCE="FP-2">+/− Commercial check transactions, including returned checks</FP>
                <P>Post after the close of Fedwire Funds Service:</P>
                <FP SOURCE="FP-2">+/− All other transactions. These transactions include the following: currency and coin shipments; noncash collection; term-deposit settlements; Federal Reserve Bank checks presented after 3:00 p.m. eastern time but before 3:00 p.m. local time; foreign check transactions; small-dollar credit corrections and adjustments; and all debit corrections and adjustments. Discount-window loans and repayments are normally posted after the close of Fedwire as well; however, in unusual circumstances a discount window loan may be posted earlier in the day with repayment 24 hours later, or a loan may be repaid before it would otherwise become due.</FP>
                <P>Equals:</P>
                <P>Closing Balance.</P>
                <STARS/>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <P>By order of the Board of Governors of the Federal Reserve System,</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28664 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL HOUSING FINANCE AGENCY</AGENCY>
                <CFR>12 CFR Part 1238</CFR>
                <DEPDOC>[No. 2014-N-15]</DEPDOC>
                <SUBJECT>Orders: Reporting by Regulated Entities of Stress Testing Results as of September 30, 2014</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Housing Finance Agency.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Orders.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Federal Housing Finance Agency (FHFA) provides notice that it issued Orders dated December 1, 2014, with respect to reporting under section 165(i)(2) of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective December 5, 2014. Each Order is applicable on December 1, 2014.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Naa Awaa Tagoe, Senior Associate Director, Office of Financial Analysis, Modeling and Simulations, (202) 649-3140, 
                        <E T="03">naaawaa.tagoe@fhfa.gov;</E>
                         Stefan Szilagyi, Examination Manager, FHLBank Modeling, FHLBank Risk Modeling Branch, (202) 649-3515, 
                        <E T="03">Stefan.szilagy@fhfa.gov;</E>
                         or Mark D. Laponsky, Deputy General Counsel, Office of General Counsel, (202) 649-3054 (these are not toll-free numbers), 
                        <E T="03">mark.laponsky@fhfa.gov.</E>
                         The telephone number for the Telecommunications Device for the Hearing Impaired is (800) 877-8339.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FHFA is responsible for ensuring that the regulated entities operate in a safe and sound manner, including the maintenance of adequate capital and internal controls, that their operations and activities foster liquid, efficient, competitive, and resilient national housing finance markets, and that they carry out their public policy missions 
                    <PRTPAGE P="72121"/>
                    through authorized activities. 
                    <E T="03">See</E>
                     12 U.S.C. 4513. These Orders are being issued under 12 U.S.C. 4514(a), which authorizes the Director of FHFA to require by Order that the regulated entities submit regular or special reports to FHFA and establishes remedies and procedures for failing to make reports required by Order. The Orders are accompanied by Summary Instructions and Guidance to which is appended reporting templates and scenarios for stress testing.
                </P>
                <HD SOURCE="HD1">II. Orders</HD>
                <P>
                    For the convenience of the affected parties, the text of the Orders, without the accompanying Summary Instructions and Guidance and appendices, follows below in its entirety. You may access these Orders with all of the accompanying material from FHFA's Web site at: 
                    <E T="03">http://www.fhfa.gov/Media/PublicAffairs/Pages/FHFA-Issues-Scenarios-and-Guidance-to-FannieMae,-Freddie-Mac-and-the-Federal-Home-Loan-Banks-Regarding-Annual-Dodd-Frank-St.aspx.</E>
                     The Orders and Summary Instructions and Guidance will be available for public inspection and copying at the Federal Housing Finance Agency, Eighth Floor, 400 Seventh St. SW., Washington, DC 20024. To make an appointment, call (202) 649-3804.
                </P>
                <P>The text of the Orders is as follows: </P>
                <HD SOURCE="HD1">Federal Housing Finance Agency</HD>
                <HD SOURCE="HD2">Order Nos. 2014-OR-B-3, 2014-OR-FNMA-2, and 2014-OR-FHLMC-2</HD>
                <HD SOURCE="HD3">ORDER ON REPORTING BY REGULATED ENTITIES OF STRESS TESTING RESULTS AS OF SEPTEMBER 30, 2014</HD>
                <P>
                    <E T="03">Whereas,</E>
                     section 165(i)(2) of the Dodd-Frank Wall Street Reform and Consumer Protection Act (“Dodd-Frank Act”) requires certain financial companies with total consolidated assets of more than $10 billion, and which are regulated by a primary Federal financial regulatory agency, to conduct annual stress tests to determine whether the companies have the capital necessary to absorb losses as a result of adverse economic conditions;
                </P>
                <P>
                    <E T="03">Whereas,</E>
                     FHFA's rule implementing section 165(i)(2) of the Dodd-Frank Act is codified as 12 CFR part 1238 and requires that “[e]ach regulated entity must file a report in the manner and form established by FHFA.” 12 CFR 1238.5(b);
                </P>
                <FP>WHEREAS, 12 CFR 1238.3(b) requires that FHFA issue to each regulated entity scenarios to be used in conducting annual stress testing;</FP>
                <P>
                    <E T="03">Whereas,</E>
                     the Director of FHFA considers it appropriate to Order each regulated entity to report to FHFA results of stress testing under 12 CFR part 1238 using scenarios supplied by FHFA;
                </P>
                <P>
                    <E T="03">Whereas,</E>
                     FHFA issued to each regulated entity the required scenarios and reporting templates on November 14, 2014, fifteen calendar days following the Federal Reserve Board's release of global shock scenario elements for use in its Dodd-Frank stress testing exercises; and
                </P>
                <P>
                    <E T="03">Whereas,</E>
                     section 1314 of the Safety and Soundness Act, 12 U.S.C. 4514(a) authorizes the Director of FHFA to require regulated entities, by general or specific order, to submit such reports on their management, activities, and operations as the Director considers appropriate.
                </P>
                <P>
                    <E T="03">Now therefore,</E>
                     it is hereby Ordered as follows:
                </P>
                <P>Each regulated entity shall conduct annual stress testing and report to FHFA and to the Board of Governors of the Federal Reserve System the results of such stress testing as required by 12 CFR part 1238, in the form and with the content described therein and in the Summary Instructions and Guidance accompanying this Order, using the scenarios and assumptions issued on November 14, 2014, and provided in Appendices 4 through 11 to the Summary Instructions and Guidance that accompanies this Order.</P>
                <P>
                    <E T="03">It is so ordered,</E>
                     this 1st day of December 2014.
                </P>
                <P>This Order is effective immediately.</P>
                <EXTRACT>
                    <FP SOURCE="FP-1">Signed at Washington, DC, this 1st day of December, 2014.</FP>
                    <FP>Melvin L. Watt,</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Director, Federal Housing Finance Agency.</E>
                    </FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Melvin L. Watt,</NAME>
                    <TITLE>Director, Federal Housing Finance Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28593 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD> </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-2014-0168; Directorate Identifier 2013-NM-208-AD; Amendment 39-18039; AD 2014-24-06]</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 certain The Boeing Company Model 787-8 airplanes. This AD was prompted by failure during testing of the anchor attachment on the occupant restraint system on the standard attendant seat due to an understrength attachment fitting. This AD requires replacing the existing restraint attachment fitting on the standard attendant seat with a new, improved attachment fitting. We are issuing this AD to prevent failure of the restraint attachment fitting of the attendant seat during an emergency landing, which could cause injury to the cabin crew and passengers and could impede a rapid evacuation.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of January 9, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, WA 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; Internet 
                        <E T="03">https://www.myboeingfleet.com.</E>
                         You may view this referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. 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>
                     by searching for and locating Docket No. FAA-2014-0168; 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 Docket 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>
                        Eric M. Brown, Aerospace Engineer, Cabin Safety and Environmental Systems Branch, ANM-150S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton, WA 98057-3356; phone: 425-917-6746; fax: 425-917-6590; email: 
                        <E T="03">eric.m.brown@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <PRTPAGE P="72122"/>
                <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 by adding an AD that would apply to certain The Boeing Company Model 787-8 airplanes. The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on March 28, 2014 (79 FR 17455). The NPRM was prompted by failure during testing of the anchor attachment on the occupant restraint system on the standard attendant seat due to an understrength attachment fitting. The NPRM proposed to require replacing the existing restraint attachment fitting on the standard attendant seat with a new, improved attachment fitting. We are issuing this AD to prevent failure of the restraint attachment fitting of the attendant seat during an emergency landing, which could cause injury to the cabin crew and passengers and could impede a rapid evacuation.
                </P>
                <HD SOURCE="HD1">Comments</HD>
                <P>We gave the public the opportunity to participate in developing this AD. The following presents the comments received on the NPRM (79 FR 17455, March 28, 2014) and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Request To Change the Reason for the Unsafe Condition</HD>
                <P>
                    Boeing asked that we change the reason for the unsafe condition in the 
                    <E T="02">SUMMARY</E>
                     and Discussion sections of the NPRM (79 FR 17455, March 28, 2014). The reason specifies that the AD was prompted by failure of the anchor attachment on the occupant restraint system on the standard attendant seat due to an undersized attachment fitting. Boeing stated that the reason stated in the NPRM is ambiguous and may give an incorrect impression of the nature of the failure. Boeing asked that the reason be changed to specify that the triggering failure occurred during testing, and not in service.
                </P>
                <P>We agree with the commenter that the failure of the anchor attachment occurred during testing. We have changed this final rule accordingly.</P>
                <HD SOURCE="HD1">Requests for Changes to the Unsafe Condition</HD>
                <P>
                    Boeing asked that we clarify the unsafe condition specified in the 
                    <E T="02">SUMMARY</E>
                     and Discussion sections of the NPRM (79 FR 17455, March 28, 2014). The unsafe condition in the NPRM specified that the AD is being issued to “prevent failure” of the restraint attachment fitting and consequent “detachment of the attendant seat. . . .” Boeing stated that the language should be clarified to specify that only the restraint system, not the attendant seat, will detach. Boeing added that the undersized fitting is not the correct reason for the failure because the geometry of the existing fitting increased the local internal loads beyond the attachment capability, and the new fitting is actually smaller than the existing fitting, yet reduces the internal loads that lead to failure.
                </P>
                <P>
                    We agree with the commenter that only the restraint system, not the attendant seat, will detach. We have clarified this language in the 
                    <E T="02">SUMMARY</E>
                     and Discussion sections, as well as paragraph (e) of this final rule.
                </P>
                <P>
                    We agree that the failure is due to the excessive internal loads generated by the attachment fitting geometry; however, we note that the term “undersized” refers to the loading capability of the attachment fitting, not the actual physical size. We have clarified the 
                    <E T="02">SUMMARY</E>
                     and Discussion sections, as well as paragraph (e) of this final rule, by changing the term “undersized” to “understrength.”
                </P>
                <P>Boeing also asked that the end level effect, which specifies in part, “. . . could cause injury to passengers and crew . . .” be changed to “. . . could cause injury to cabin crew and passengers. . .” Boeing stated that the language in the NPRM (79 FR 17455, March 28, 2014) could suggest that the equivalent or primary threat is to passengers because they are identified first; however, the primary threat would be to the cabin crew. Boeing noted that unrestrained cabin crew may be injured by impact to the aircraft interior or other cabin crew or passengers.</P>
                <P>
                    We agree with the commenter that the primary threat would be to the cabin crew. Our evaluation shows that an injury to a flight attendant would increase the risk of injury to a passenger during an emergency evacuation. We have clarified the 
                    <E T="02">SUMMARY</E>
                     and Discussion sections, as well as paragraph (e) of this final rule, to include the phrase “injury to the cabin crew and passengers.”
                </P>
                <HD SOURCE="HD1">Request To Clarify the Applicability Section</HD>
                <P>
                    Boeing asked that we clarify the scope of the affected airplanes specified in the 
                    <E T="02">SUMMARY</E>
                     section of the NPRM (79 FR 17455, March 28, 2014), by referring to the service information as follows: “. . . certain The Boeing Company Model 787-8 airplanes, certificated in any category, as identified in Boeing Service Bulletin B787-81205-SB250027-00, Issue 001, dated January 14, 2014.” Boeing stated that the current language identifies the target airplanes only as “certain The Boeing Company 787-8 airplanes,” which is not specific.
                </P>
                <P>
                    We disagree with the request to add details for the affected airplanes specified in the 
                    <E T="02">SUMMARY</E>
                     section. The 
                    <E T="02">SUMMARY</E>
                     section of this final rule provides an overview and does not include detailed information. Paragraph (c) of this AD lists the full details for the airplanes affected by this final rule. We have, however, changed the applicability section specified in paragraph (c) of this AD to also refer to the effectivity of Boeing Service Bulletin B787-81205-SB250027-00, Issue 001, dated January 14, 2014.
                </P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>We reviewed the relevant data, considered the comments received, and determined that air safety and the public interest require adopting this AD with the changes described previously. We also determined that these changes will not increase the economic burden on any operator or increase the scope of this AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this AD affects 1 airplane of U.S. registry.</P>
                <P>We estimate the following costs to comply with this AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r100,12C,12C,12C">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">
                            Cost per 
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">
                            Cost on U.S. 
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Replacement</ENT>
                        <ENT>1 work-hour × $85 per hour = $85</ENT>
                        <ENT>$0</ENT>
                        <ENT>$85</ENT>
                        <ENT>$85</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="72123"/>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify that this AD:</E>
                </P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
                <P>(3) Will not affect intrastate aviation in Alaska, and</P>
                <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <REGTEXT TITLE="14" PART="39">
                    <PART>
                        <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2014-24-06 The Boeing Company:</E>
                             Amendment 39-18039; Docket No. FAA-2014-0168; Directorate Identifier 2013-NM-208-AD.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This AD is effective January 9, 2015.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to The Boeing Company Model 787-8 airplanes, certificated in any category, with Goodrich Model 2787 seat assemblies installed; as identified in Boeing Service Bulletin B787-81205-SB250027-00, Issue 001, dated January 14, 2014.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 25, Equipment/furnishings.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by failure during testing of the anchor attachment on the occupant restraint system on the standard attendant seat due to an understrength attachment fitting. We are issuing this AD to prevent failure of the restraint attachment fitting of the attendant seat during an emergency landing, which could cause injury to the cabin crew and passengers and could impede a rapid evacuation.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Replacement</HD>
                        <P>Within 24 months after the effective date of this AD: Replace the existing restraint attachment fitting on the standard attendant seat with a new, improved attachment fitting, in accordance with the Accomplishment Instructions of Boeing Service Bulletin B787-81205-SB250027-00, Issue 001, dated January 14, 2014; and UTC Aerospace Systems Service Bulletin 2787-25-006, Revision B, dated July 10, 2013.</P>
                        <HD SOURCE="HD1">(h) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, Seattle 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 paragraph (i) of this AD. Information may be emailed to: 
                            <E T="03">9-ANM-Seattle-ACO-AMOC-Requests@faa.gov.</E>
                        </P>
                        <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                        <P>(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Seattle ACO, to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane.</P>
                        <HD SOURCE="HD1">(i) Related Information</HD>
                        <P>
                            For more information about this AD, contact Eric M. Brown, Aerospace Engineer, Cabin Safety and Environmental Systems Branch, ANM-150S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton, WA 98057-3356; phone: 425-917-6476; fax: 425-917-6590; email: 
                            <E T="03">eric.m.brown@faa.gov.</E>
                        </P>
                        <HD SOURCE="HD1">(j) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(i) Boeing Service Bulletin B787-81205-SB250027-00, Issue 001, dated January 14, 2014.</P>
                        <P>(ii) UTC Aerospace Systems Service Bulletin 2787-25-006, Revision B, dated July 10, 2013.</P>
                        <P>
                            (3) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, WA 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; Internet 
                            <E T="03">https://www.myboeingfleet.com.</E>
                        </P>
                        <P>(4) You may view this service information at FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.</P>
                        <P>
                            (5) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Renton, Washington, on November 19, 2014.</DATED>
                    <NAME>Suzanne Masterson,</NAME>
                    <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28132 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="72124"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2014-0193; Directorate Identifier 2013-NM-234-AD; Amendment 39-18040; AD 2014-24-07]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus 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 adopting a new airworthiness directive (AD) for certain Airbus Model A318, A319, A320, and A321 series airplanes. This AD was prompted by a report of a crack found in the fuselage during a fatigue test campaign. This AD requires repetitive rototest inspections for cracking; corrective actions if necessary; and modification of the torsion box, which would terminate the repetitive inspections. We are issuing this AD to prevent cracking in the side box beam flange of the fuselage, which could affect the structural integrity of the airplane.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD becomes effective January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of January 9, 2015.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the Internet at 
                        <E T="03">http://www.regulations.gov/#!docketDetail;D=FAA-2014-0193;</E>
                         or in person at the Docket 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.
                    </P>
                    <P>
                        For service information identified in this AD, contact Airbus, Airworthiness Office—EIAS, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 44 51; email 
                        <E T="03">account.airworth-eas@airbus.com;</E>
                         Internet 
                        <E T="03">http://www.airbus.com.</E>
                         You may view this referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sanjay Ralhan, Aerospace Engineer, International Branch, ANM 116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, WA 98057-3356; telephone 425-227-1405; fax 425-227-1149.</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 by adding an AD that would apply to certain Airbus Model A318, A319, A320, and A321 series airplanes. The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on April 10, 2014 (79 FR 19846).
                </P>
                <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued EASA Airworthiness Directive 2013-0261, dated October 28, 2013 (referred to after this as the Mandatory Continuing Airworthiness Information, or “the MCAI”), to correct an unsafe condition for certain Airbus Model A318, A319, A320, and A321 series airplanes. The MCAI states:</P>
                <EXTRACT>
                    <P>During the full scale fatigue test campaign of the A320 family type design, a crack was reported in the fuselage side box beam flange at frame (FR) 43 level, both sides.</P>
                    <P>This condition, if not detected and corrected, could affect the structural integrity of the aeroplane.</P>
                    <P>For the reason describe above, this [EASA] AD requires repetitive inspections of the fuselage side box beam flange at FR43, and, depending on findings, corrective action(s) [repair]. This [EASA] AD also requires a modification, which constitutes terminating action for the repetitive inspections.</P>
                </EXTRACT>
                <FP>
                    The modification includes related investigative and corrective actions. The related investigative actions include a rotoprobe inspection of the holes for cracks, and a high frequency eddy current (HFEC) inspection for cracks. The corrective action includes repair. You may examine the MCAI in the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov/#!documentDetail;D=FAA-2014-0193-0002.</E>
                </FP>
                <HD SOURCE="HD1">Comments</HD>
                <P>We gave the public the opportunity to participate in developing this AD. The following presents the comments received on the NPRM (79 FR 19846, April 10, 2014) and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Request To Remove Requirement To Refer to This AD in Repair Approvals</HD>
                <P>Airlines for America, Inc. (A4A), on behalf of several affected member airlines, requested that we revise paragraphs (h), (i), and (l)(2) of the NPRM (79 FR 19846, April 10, 2014) to remove the requirement to include the AD reference in repair approvals. The commenters have made this request because this proposed requirement is overly broad and would add significant cost and complexity to their operations. The commenters were concerned that this proposed requirement would set a precedent for how repairs are approved, and could negatively affect all U.S. operators of foreign-manufactured airplanes.</P>
                <P>We concur with the commenters' request to remove from this AD the requirement that repair approvals specifically refer to this AD.</P>
                <P>Since late 2006, we have included a standard paragraph titled “Airworthy Product” in all MCAI ADs in which the FAA develops an AD based on a foreign authority's AD. The MCAI or referenced service information in an FAA AD often directs the owner/operator to contact the manufacturer for corrective actions, such as a repair. Briefly, the Airworthy Product paragraph allowed owners/operators to use corrective actions provided by the manufacturer if those actions were FAA-approved. In addition, the paragraph stated that any actions approved by the State of Design Authority (or its delegated agent) are considered to be FAA-approved.</P>
                <P>In the NPRM (79 FR 19846, April 10, 2014), we proposed to prevent the use of repairs that were not specifically developed to correct the unsafe condition, by requiring that the repair approval provided by the State of Design Authority or its delegated agent specifically refer to this FAA AD. This change was intended to clarify the method of compliance and to provide operators with better visibility of repairs that are specifically developed and approved to correct the unsafe condition. In addition, we proposed to change the phrase “its delegated agent” to include “the Design Approval Holder (DAH) with a State of Design Authority's design organization approval (DOA)” to refer to a DAH authorized to approve required repairs for the proposed AD.</P>
                <P>Comments were provided to the NPRM (79 FR 19846, April 10, 2014) about these proposed changes. One commenter, UPS, stated the following: “The proposed wording, being specific to repairs, eliminates the interpretation that Airbus messages are acceptable for approving minor deviations (corrective actions) needed during accomplishment of an AD mandated Airbus service bulletin.”</P>
                <P>
                    This comment has made the FAA aware that some operators have misunderstood or misinterpreted the Airworthy Product paragraph to allow the owner/operator to use messages 
                    <PRTPAGE P="72125"/>
                    provided by the manufacturer as approval of deviations during the accomplishment of an AD-mandated action. The Airworthy Product paragraph does not approve messages or other information provided by the manufacturer for deviations to the requirements of the AD-mandated actions. The Airworthy Product paragraph only addresses the requirement to contact the manufacturer for corrective actions for the identified unsafe condition and does not cover deviations from other AD requirements. However, deviations to AD-required actions are addressed in 14 CFR 39.17, and anyone may request the approval for an alternative method of compliance to the AD-required actions using the procedures found in 14 CFR 39.19.
                </P>
                <P>To address this misunderstanding and misinterpretation of the Airworthy Product paragraph, we have changed that paragraph and retitled it “Contacting the Manufacturer.” This paragraph now clarifies that for any requirement in this AD to obtain corrective actions from a manufacturer, the actions must be accomplished using a method approved by the FAA, EASA, or Airbus's EASA DOA.</P>
                <P>The Contacting the Manufacturer paragraph also clarifies that, if approved by the DOA, the approval must include the DOA-authorized signature. The DOA signature indicates that the data and information contained in the document are EASA-approved, which is also FAA-approved. Messages and other information provided by the manufacturer that do not contain the DOA-authorized signature approval are not EASA-approved, unless EASA directly approves the manufacturer's message or other information.</P>
                <P>This clarification does not remove flexibility afforded previously by the Airworthy Product paragraph. Consistent with long-standing FAA policy, such flexibility was never intended for required actions. This is also consistent with the recommendation of the AD Implementation Aviation Rulemaking Committee to increase flexibility in complying with ADs by identifying those actions in manufacturers' service instructions that are “Required for Compliance” with ADs. We continue to work with manufacturers to implement this recommendation. But once we determine that an action is required, any deviation from the requirement must be approved as an alternative method of compliance.</P>
                <P>Other commenters pointed out that in many cases the foreign manufacturer's service bulletin and the foreign authority's MCAI may have been issued some time before the FAA AD. Therefore, the DOA may have provided U.S. operators with an approved repair, developed with full awareness of the unsafe condition, before the FAA AD is issued. Under these circumstances, to comply with the FAA AD, the operator would be required to go back to the manufacturer's DOA and obtain a new approval document, adding time and expense to the compliance process with no safety benefit.</P>
                <P>Based on these comments, we removed the requirement from this AD that the DAH-provided repair specifically refer to this AD. Before adopting such a requirement in the future, the FAA will coordinate with affected DAHs and verify they are prepared to implement means to ensure that their repair approvals consider the unsafe condition addressed in an AD. Any such requirements will be adopted through the normal AD rulemaking process, including notice-and-comment procedures, when appropriate.</P>
                <P>We have also decided not to include a generic reference to either the “delegated agent” or the “DAH with State of Design Authority design organization approval,” but instead we will provide the specific delegation approval granted by the State of Design Authority for the DAH.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>We reviewed the relevant data, considered the comments received, and determined that air safety and the public interest require adopting this AD with the changes described previously and minor editorial changes. We have determined that these minor changes:</P>
                <P>• Are consistent with the intent that was proposed in the NPRM (79 FR 19846, April 10, 2014) for correcting the unsafe condition; and</P>
                <P>• Do not add any additional burden upon the public than was already proposed in the NPRM (79 FR 19846, April 10, 2014).</P>
                <P>We also determined that these changes will not increase the economic burden on any operator or increase the scope of this AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this AD affects 851 airplanes of U.S. registry.</P>
                <P>We also estimate that it would take about 178 work-hours per product to comply with the basic requirements of this AD. The average labor rate is $85 per work hour. Required parts would cost about $31,334 per product. Based on these figures, we estimate the cost of this AD on U.S. operators to be $39,540,864, or $46,464 per product.</P>
                <P>We have received no definitive data that would enable us to provide cost estimates for the on-condition actions specified in this AD.</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 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 the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
                <P>3. Will not affect intrastate aviation in Alaska; and</P>
                <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <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/#!docketDetail;D=FAA-2014-0193;</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 street address for the Docket Operations office (telephone 
                    <PRTPAGE P="72126"/>
                    800-647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </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 TITLE="14" PART="39">
                    <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 TITLE="14" PART="39">
                    <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">2014-24-07 Airbus:</E>
                             Amendment 39-18040. Docket No. FAA-2014-0193; Directorate Identifier 2013-NM-234-AD.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This AD becomes effective January 9, 2015.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to Airbus Model A318-111, -112, -121, and -122 airplanes; Model A319-111, -112, -113, -114, -115, -131, -132, and -133 airplanes; Model A320-111, -211, -212, -214, -231, -232, and -233 airplanes; and Model A321-111, -112, -131, -211, -212, -213, -231, and -232 airplanes; certificated in any category; all manufacturer serial numbers on which Airbus Modification 21202 has been embodied in production, except those on which Modification 152569 has been embodied in production.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 53, Fuselage.</P>
                        <HD SOURCE="HD1">(e) Reason</HD>
                        <P>This AD was prompted by a report of a crack found in the side box beam flange of the fuselage at the frame (FR) 43 level during a fatigue test campaign. We are issuing this AD to prevent cracking in the side box beam flange of the fuselage, which could affect the structural integrity of the airplane.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Inspection</HD>
                        <P>At the time specified in paragraph (g)(1) or (g)(2) of this AD, whichever occurs later: Do a rototest inspection for cracking of the beam flange of the stiffener 15 side box on the left- and right-hand sides in the FR43 area, in accordance with the Accomplishment Instructions of Airbus Service Bulletin A320-53-1258, dated October 18, 2012. Repeat the inspection thereafter at intervals not to exceed 7,500 flight cycles or 15,000 flight hours, whichever occurs first.</P>
                        <P>(1) Before exceeding 24,000 flight cycles or 48,000 flight hours, whichever occurs first since the airplane's first flight.</P>
                        <P>(2) Within 3,000 flight cycles or 6,000 flight hours, whichever occurs first after the effective date of this AD.</P>
                        <HD SOURCE="HD1">(h) Corrective Action</HD>
                        <P>If any crack is found during any inspection required by paragraph (g) of this AD: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the European Aviation Safety Agency (EASA); or Airbus's EASA Design Organization Approval (DOA).</P>
                        <HD SOURCE="HD1">(i) Modification</HD>
                        <P>Before exceeding 48,000 flight cycles or 96,000 flight hours, whichever occurs first since the airplane's first flight: Modify the fittings on the left- and right-hand sides of the torsion box, including doing all applicable related investigative and corrective actions, in accordance with the Accomplishment Instructions of Airbus Service Bulletin A320-53-1251, Revision 01, dated October 18, 2013; except where Airbus Service Bulletin A320-53-1251, Revision 01, dated October 18, 2013, specifies to contact Airbus for repair, before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or EASA; or Airbus's EASA DOA.</P>
                        <HD SOURCE="HD1">(j) Terminating Action</HD>
                        <P>Modification of the airplane as required by paragraph (i) of this AD constitutes terminating action for the repetitive inspections required by paragraph (g) of this AD.</P>
                        <HD SOURCE="HD1">(k) Credit for Previous Actions</HD>
                        <P>This paragraph provides credit for actions required by paragraph (i) of this AD, if those actions were performed before the effective date of this AD using Airbus Service Bulletin A320-53-1251, dated November 16, 2012, which is not incorporated by reference in this AD.</P>
                        <HD SOURCE="HD1">(l) Other FAA AD Provisions</HD>
                        <P>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, Transport Airplane Directorate, 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: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, WA 98057-3356; telephone 425-227-1405; fax 425-227-1149. Information may be emailed 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">Contacting the Manufacturer:</E>
                             For any requirement in this AD to obtain corrective actions from a manufacturer, the action must be accomplished using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or EASA; or Airbus's EASA DOA. If approved by the DOA, the approval must include the DOA-authorized signature.
                        </P>
                        <HD SOURCE="HD1">(m) Related Information</HD>
                        <P>
                            (1) Refer to Mandatory Continuing Airworthiness Information (MCAI) EASA Airworthiness Directive 2013-0261, dated October 28, 2013, for related information. This MCAI may be found in the AD docket on the Internet at 
                            <E T="03">http://www.regulations.gov/#!documentDetail;D=FAA-2014-0193-0002.</E>
                        </P>
                        <P>(2) Service information identified in this AD that is not incorporated by reference is available at the addresses specified in paragraphs (n)(3) and (n)(4) of this AD.</P>
                        <HD SOURCE="HD1">(n) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                        <P>(i) Airbus Service Bulletin A320-53-1251, Revision 01, dated October 18, 2013.</P>
                        <P>(ii) Airbus Service Bulletin A320-53-1258, dated October 18, 2012.</P>
                        <P>
                            (3) For service information identified in this AD, contact Airbus, Airworthiness Office—EIAS, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 44 51; email 
                            <E T="03">account.airwortheas@airbus.com;</E>
                             Internet 
                            <E T="03">http://www.airbus.com.</E>
                        </P>
                        <P>(4) You may view this service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.</P>
                        <P>
                            (5) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Renton, Washington, on November 19, 2014.</DATED>
                    <NAME>Suzanne Masterson,</NAME>
                    <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28141 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="72127"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2013-1066; Directorate Identifier 2013-NM-021-AD; Amendment 39-18029; AD 2014-23-13]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus 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 Airworthiness Directive (AD) 2000-12-12, for certain Airbus Model A300, A300-600, and A310 series airplanes. AD 2000-12-12 required inspecting to detect cracks in the lower spar axis of the nacelle pylon between ribs 9 and 10, and repair if necessary. AD 2000-12-12 also provided for optional modification of the pylon, which terminated the inspections for Model A300 series airplanes. This new AD reduces the initial and repetitive inspection compliance times. This AD was prompted by reports of cracking of the lower pylon spar after accomplishing the existing modification. We are issuing this AD to detect and correct fatigue cracking, which could result in reduced structural integrity of the lower spar of the nacelle pylon.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD becomes effective January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain other publication listed in this AD as of July 28, 2000 (65 FR 39072, June 23, 2000).</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain other publications listed in this AD as of June 12, 1995 (60 FR 25604, May 12, 1995).</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the Internet at 
                        <E T="03">http://www.regulations.gov/#!docketDetail;D=FAA-2013-1066;</E>
                         or in person at the Docket 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.
                    </P>
                    <P>
                        For service information identified in this AD, contact Airbus SAS, Airworthiness Office—EAW, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 44 51; email 
                        <E T="03">account.airworth-eas@airbus.com;</E>
                         Internet 
                        <E T="03">http://www.airbus.com</E>
                        . You may view this referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dan Rodina, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, WA 98057-3356; telephone 425-227-2125; fax 425-227-1149.</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 supersede AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000). AD 2000-12-12 applied to certain Airbus Model A300, A300-600, and A310 series airplanes. The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on December 30, 2013 (78 FR 79333).
                </P>
                <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued EASA Airworthiness Directive 2013-0016, dated September 17, 2013 (referred to after this as the Mandatory Continuing Airworthiness Information, or “the MCAI”), to correct an unsafe condition for certain Airbus Model A300, A300-600, and A310 series airplanes. The MCAI states:</P>
                <EXTRACT>
                    <P>Cracks were found between ribs 9 and 10 in the lower pylon spar of A310 aeroplanes equipped with Pratt &amp; Whitney (PW) engines.</P>
                    <P>For A310, A300 and A300-600 aeroplanes and, in order to prevent crack initiation, the implementation of a first inspection programme of this area was required by DGAC [Direction Générale de l'Aviation Civile] France AD 1992-049-130(B) [which corresponds to certain actions in FAA AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000)], currently at Revision 4.</P>
                    <P>General Electric (GE) and PW pylons on A300 aeroplanes are also affected, due to similar design.</P>
                    <P>
                        After that [DGAC] AD was issued, prompted by new findings, a specific inspection programme for A310 aeroplanes was introduced and required by DGAC France AD 1999-237-285(B) [which corresponds to certain actions in FAA AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000)], which was subsequently superseded by EASA AD 2008-0008 [
                        <E T="03">http://ad.easa.europa.eu/blob/easa_ad_2008_0008_superseded.pdf/AD_2008-0008_1</E>
                        ], which introduced new thresholds and intervals in the frame of the A310 extended service goal exercise.
                    </P>
                    <P>Some cracks, which were discovered after the implementation of the preventive modification, prompted Airbus to perform a new Fatigue and Damage Tolerance analysis with a refined model of the area with and without repair or preventive reinforcement before crack appearance. Based on the results of this analysis, Airbus revised the related Service Bulletins to introduce more restrictive thresholds and intervals for curative and preventive repair configuration.</P>
                    <P>
                        EASA issued AD 2013-0014 [
                        <E T="03">http://ad.easa.europa.eu/blob/easa_ad_2013_0214.pdf/AD_2013-0014_1</E>
                        ], which superseded DGAC France AD 1992-049-130(B) and EASA AD 2008-0008, to mandate a new inspection programme [including related investigative and corrective actions].
                    </P>
                    <P>After EASA AD 2013-0014 was issued, further analysis allowed to identify one A300 aeroplane model and one retrofitted A300 MSN [manufacturer serial number] missing in the applicability chapter.</P>
                    <P>For the reason described above, this [EASA] AD retains the requirements of EASA AD 2013-0014, which is superseded, and clarifies the Applicability section and adds one A300 model and one A300 MSN.</P>
                </EXTRACT>
                <P>
                    The unsafe condition is fatigue cracking, which could result in reduced structural integrity of the lower spar of the nacelle pylon. Related investigative actions include additional eddy current and liquid penetrant inspections for cracking. Corrective actions include repairing cracking. For certain cracking lengths, repairs are described as reinforcing the lower spar with a doubler. You may examine the MCAI in the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov/#!documentDetail;D=FAA-2013-1066-0002</E>
                    .
                </P>
                <HD SOURCE="HD1">Comments</HD>
                <P>We gave the public the opportunity to participate in developing this AD. The following presents the comments received on the NPRM (78 FR 79333, December 30, 2013) and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">“Contacting the Manufacturer” Paragraph in This AD</HD>
                <P>
                    United Parcel Service (UPS) requested that we revise the NPRM (78 FR 79333, December 30, 2013) to remove the requirement to include the AD reference in repair approvals. UPS noted its concerns that the proposal would require development of a unique Airbus process for U.S. operators; that it could have significant financial and administrative impacts to existing customer support agreements and different AD records requirements within an operator's fleet; that it will increase requests for approval of alternative methods of compliance 
                    <PRTPAGE P="72128"/>
                    (AMOC) and result in delayed return to service; and that it creates a new requirement that did not exist when the superseded AD was written.
                </P>
                <P>We concur with the commenter's request to remove from this AD the requirement that repair approvals must specifically refer to this AD.</P>
                <P>Since late 2006, we have included a standard paragraph titled “Airworthy Product” in all MCAI ADs in which the FAA develops an AD based on a foreign authority's AD. The MCAI or referenced service information in an FAA AD often directs the owner/operator to contact the manufacturer for corrective actions, such as a repair. Briefly, the Airworthy Product paragraph allowed owners/operators to use corrective actions provided by the manufacturer if those actions were FAA-approved. In addition, the paragraph stated that any actions approved by the State of Design Authority (or its delegated agent) are considered to be FAA-approved.</P>
                <P>In the NPRM (78 FR 79333, December 30, 2013), we proposed to prevent the use of repairs that were not specifically developed to correct the unsafe condition, by requiring that the repair approval provided by the State of Design Authority or its delegated agent specifically refer to this FAA AD. This change was intended to clarify the method of compliance and to provide operators with better visibility of repairs that are specifically developed and approved to correct the unsafe condition. In addition, we proposed to change the phrase “its delegated agent” to include a design approval holder (DAH) with State of Design Authority design organization approval (DOA), as applicable, to refer to a DAH authorized to approve required repairs for the proposed AD.</P>
                <P>UPS specifically stated the following in its comments to the NPRM (78 FR 79333, December 30, 2013): “The proposed wording, being specific to repairs, eliminates the interpretation that Airbus messages are acceptable for approving minor deviations (corrective actions) needed during accomplishment of an AD mandated Airbus service bulletin.”</P>
                <P>This comment has made the FAA aware that some operators have misunderstood or misinterpreted the Airworthy Product paragraph to allow the owner/operator to use messages provided by the manufacturer as approval of deviations during the accomplishment of an AD-mandated action. The Airworthy Product paragraph does not approve messages or other information provided by the manufacturer for deviations to the requirements of the AD-mandated actions. The Airworthy Product paragraph only addresses the requirement to contact the manufacturer for corrective actions for the identified unsafe condition and does not cover deviations from other AD requirements. However, deviations to AD-required actions are addressed in 14 CFR 39.17, and anyone may request the approval for an alternative method of compliance to the AD-required actions using the procedures found in 14 CFR 39.19.</P>
                <P>To address this misunderstanding and misinterpretation of the Airworthy Product paragraph, we have changed that paragraph and retitled it “Contacting the Manufacturer.” This paragraph now clarifies that for any requirement in this AD to obtain corrective actions from a manufacturer, the actions must be accomplished using a method approved by the FAA, EASA, or Airbus's EASA DOA.</P>
                <P>The Contacting the Manufacturer paragraph also clarifies that, if approved by the DOA, the approval must include the DOA-authorized signature. The DOA signature indicates that the data and information contained in the document are EASA-approved, which is also FAA-approved. Messages and other information provided by the manufacturer that do not contain the DOA-authorized signature approval are not EASA-approved, unless EASA directly approves the manufacturer's message or other information.</P>
                <P>This clarification does not remove flexibility afforded previously by the Airworthy Product paragraph. Consistent with long-standing FAA policy, such flexibility was never intended for required actions. This is also consistent with the recommendation of the Airworthiness Directive Implementation Aviation Rulemaking Committee to increase flexibility in complying with ADs by identifying those actions in manufacturers' service instructions that are “Required for Compliance” with ADs. We continue to work with manufacturers to implement this recommendation. But once we determine that an action is required, any deviation from the requirement must be approved as an alternative method of compliance.</P>
                <P>Commenters to an NPRM having Directorate Identifier 2012-NM-101-AD (78 FR 78285, December 26, 2013) pointed out that in many cases the foreign manufacturer's service bulletin and the foreign authority's MCAI may have been issued some time before the FAA AD. Therefore, the DOA may have provided U.S. operators with an approved repair, developed with full awareness of the unsafe condition, before the FAA AD is issued. Under these circumstances, to comply with the FAA AD, the operator would be required to go back to the manufacturer's DOA and obtain a new approval document, adding time and expense to the compliance process with no safety benefit.</P>
                <P>Based on these comments, we removed from this AD the requirement that the DAH-provided repair specifically refer to this AD. Before adopting such a requirement, the FAA will coordinate with affected DAHs and verify they are prepared to implement means to ensure that their repair approvals consider the unsafe condition addressed in the AD. Any such requirements will be adopted through the normal AD rulemaking process, including notice-and-comment procedures, when appropriate.</P>
                <P>We also have decided to revise the language in paragraphs (g)(3), (g)(4), (h)(3), (h)(4), (i)(3), and (i)(4) of this AD to retain references to repair approvals done by the DGAC (or its delegated agent) from AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), as well as including references to EASA and the specific delegation approval granted by EASA for the DAH. Further, we revised paragraphs (n)(2) and (n)(3) of this AD to remove references to the “delegated agent” and the “DAH with State of Design Authority design organization approval” and instead provided the specific delegation approval granted by the State of Design Authority for the DAH.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>We reviewed the relevant data, including the comments received, and determined that air safety and the public interest require adopting this AD with the changes described previously and minor editorial changes. We have determined that these minor changes:</P>
                <P>• Are consistent with the intent that was proposed in the NPRM (78 FR 79333, December 30, 2013) for correcting the unsafe condition; and</P>
                <P>• Do not add any additional burden upon the public than was already proposed in the NPRM (78 FR 79333, December 30, 2013).</P>
                <P>We also determined that these changes will not increase the economic burden on any operator or increase the scope of this AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this AD affects 91 airplanes of U.S. registry.</P>
                <P>
                    The actions required by AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), and retained in 
                    <PRTPAGE P="72129"/>
                    this AD take about 4 work-hours per product, at an average labor rate of $85 per work-hour. Based on these figures, the estimated cost of the actions required by AD 2000-12-12 is $340 per product.
                </P>
                <P>We also estimate that it would take about 12 work-hours per product to comply with the basic requirements of this AD. The average labor rate is $85 per work-hour. Based on these figures, we estimate the cost of this AD on U.S. operators to be $92,820, or $1,020 per product.</P>
                <P>In addition, we estimate that any necessary follow-on actions would take about 60 work-hours and require parts costing $1,680, for a cost of $6,780 per product. We have no way of determining the number of aircraft that might need these actions.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify that this AD:</E>
                </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
                <P>3. Will not affect intrastate aviation in Alaska; and</P>
                <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <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/#!docketDetail;D=FAA-2013-1066;</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 street address for the Docket Operations office (telephone 800-647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </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 TITLE="14" PART="39">
                    <PART>
                        <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The FAA amends § 39.13 by removing Airworthiness Directive (AD) 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), and adding the following new AD:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2014-23-13 Airbus:</E>
                             Amendment 39-18029. Docket No. FAA-2013-1066; Directorate Identifier 2013-NM-021-AD.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This AD becomes effective January 9, 2015.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>This AD replaces AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000).</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>This AD applies to the Airbus airplanes identified in paragraphs (c)(1) through (c)(4) of this AD, certificated in any category.</P>
                        <P>(1) Airbus Model A300 B2-203, B2K-3C, B4-103, B4-203, and B4-2C airplanes on which Airbus Modification 2434 has been embodied in production.</P>
                        <P>(2) Airbus Model A300 airplane having manufacturer serial number 125, on the left hand side pylon only.</P>
                        <P>(3) Airbus Model A300 B4-620, B4-622R, and B4-622 airplanes, except for airplanes on which Airbus Modification 10149 has been embodied in production.</P>
                        <P>(4) Airbus Model A310-221, -222, -322, -324, and -325 airplanes, except for airplanes on which Airbus Modification 10149 has been embodied in production.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 54, Nacelles/pylons.</P>
                        <HD SOURCE="HD1">(e) Reason</HD>
                        <P>This AD was prompted by reports of cracking of the lower pylon spar after accomplishing an existing modification. We are issuing this AD to detect and correct fatigue cracking, which could result in reduced structural integrity of the lower spar of the nacelle pylon.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Retained Inspection and Corrective Action for Certain Model A300 Series Airplanes</HD>
                        <P>This paragraph restates the requirements of paragraph (a) of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), with additional sources for repair approvals. For Model A300 B4-2C, B2K-3C, B2-203, B4-103, and B4-203 series airplanes: Prior to the accumulation of 9,000 total landings, or within 500 landings after June 12, 1995 (the effective date of AD 95-10-03, Amendment 39-9220 (60 FR 25604, May 12, 1995)), whichever occurs later, perform an internal eddy current inspection to detect cracks in the lower spar axis of the pylon between ribs 9 and 10, in accordance with Airbus Service Bulletin A300-54-071, dated November 12, 1991; or Revision 1, dated October 15, 1993. Accomplishment of an inspection required by paragraph (k), (l), or (m) of this AD terminates the inspection requirements of this paragraph.</P>
                        <P>(1) If no crack is found, repeat the inspection thereafter at intervals not to exceed 2,500 landings.</P>
                        <P>(2) If any crack is found that is less than or equal to 30 millimeters (mm): Perform subsequent inspections and repair in accordance with the methods and times specified in Airbus Service Bulletin A300-54-071, dated November 12, 1991; or Revision 1, dated October 15, 1993.</P>
                        <P>(3) If any crack is found that is greater than 30 mm, but less than 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the Direction Générale de l'Aviation Civile (DGAC) (or its delegated agent); or the European Aviation Safety Agency (EASA); or Airbus's EASA Design Organization Approval (DOA).</P>
                        <P>(4) If any crack is found that is greater than or equal to 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the DGAC (or its delegated agent); or the EASA; or Airbus's EASA DOA.</P>
                        <P>
                            (5) Accomplishment of the modification specified in Airbus Service Bulletin A300-54-0079, dated October 15, 1993, constitutes terminating action for the inspections required by paragraph (g) of this AD.
                            <PRTPAGE P="72130"/>
                        </P>
                        <HD SOURCE="HD1">(h) Retained Inspection and Corrective Action for Model A300-600 Series Airplanes</HD>
                        <P>This paragraph restates the requirements of paragraph (b) of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), with additional sources for repair approvals. For Model A300-600, B4-620, C4-620, B4-622R, and B4-622 series airplanes: Except as provided by paragraph (h)(5) of this AD, prior to the accumulation of 4,000 total landings, or within 500 landings after June 12, 1995 (the effective date of AD 95-10-03, Amendment 39-9220 (60 FR 25604, May 12, 1995)), whichever occurs later, perform an internal eddy current inspection to detect cracks in the lower spar axis of the pylon between ribs 9 and 10, in accordance with Airbus Service Bulletin A300-54-6011, dated November 12, 1991, as amended by Airbus Service Bulletin Change Notice O.A., dated July 10, 1992; or Revision 1, dated October 15, 1993. Accomplishment of an inspection required by paragraph (k), (l), or (m) of this AD terminates the inspection requirements of this paragraph.</P>
                        <P>(1) If no crack is found, repeat the inspection thereafter at intervals not to exceed 2,500 landings.</P>
                        <P>(2) If any crack is found that is less than or equal to 30 mm: Perform subsequent inspections and repair in accordance with the methods and times specified in Airbus Service Bulletin A300-54-6011, dated November 12, 1991, as amended by Airbus Service Bulletin Change Notice O.A., dated July 10, 1992; or Revision 1, dated October 15, 1993.</P>
                        <P>(3) If any crack is found that is greater than 30 mm, but less than 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the DGAC (or its delegated agent); or the EASA; or Airbus's EASA DOA.</P>
                        <P>(4) If any crack is found that is greater than or equal to 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the DGAC (or its delegated agent); or the EASA; or Airbus's EASA DOA.</P>
                        <P>(5) Accomplishment of the modification specified in Airbus Service Bulletin A300-54-6019, dated October 15, 1993, increases the threshold and repetitive interval of the inspections required by paragraph (h) of this AD to the threshold and interval specified in paragraph 2.D. of the Accomplishment Instructions of Airbus Service Bulletin A300-54-6011, Revision 1, dated October 15, 1993.</P>
                        <HD SOURCE="HD1">(i) Retained Inspection and Corrective Action for Model A310 Series Airplanes</HD>
                        <P>This paragraph restates the requirements of paragraph (c) of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), with additional sources for repair approvals. For Model A310-221, -222, -322, -324, and -325 series airplanes: Perform an internal eddy current inspection to detect cracks in the lower spar axis of the pylon between ribs 9 and 10, in accordance with Airbus Service Bulletin A310-54-2016, dated November 12, 1991; or Revision 1, dated October 15, 1993; or Revision 02, dated June 11, 1999; at the time specified in paragraph (j) of this AD. Accomplishment of an inspection required by paragraph (k), (l), or (m) of this AD terminates the inspection requirements of this paragraph.</P>
                        <P>(1) If no crack is found, repeat the inspection thereafter at intervals not to exceed 2,500 landings.</P>
                        <P>(2) If any crack is found that is less than or equal to 30 mm: Perform subsequent inspections and repair in accordance with the methods and times specified in Airbus Service Bulletin A310-54-2016, dated November 12, 1991; or Revision 1, dated October 15, 1993; or Revision 02, dated June 11, 1999.</P>
                        <P>(3) If any crack is found that is greater than 30 mm, but less than 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the DGAC (or its delegated agent); or the EASA; or Airbus's EASA DOA.</P>
                        <P>(4) If any crack is found that is greater than or equal to 100 mm: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the DGAC (or its delegated agent); or the EASA; or Airbus's EASA DOA.</P>
                        <P>(5) Accomplishment of the modification specified in Airbus Service Bulletin A310-54-2022, dated October 15, 1993; or Revision 01, dated March 16, 1999; increases the threshold and repetitive interval of the inspections required by paragraph (i) of this AD to the threshold and interval specified in paragraph 2.D. of the Accomplishment Instructions of Airbus Service Bulletin A310-54-2016, Revision 02, dated June 11, 1999.</P>
                        <HD SOURCE="HD1">(j) Retained Compliance Time for Paragraph (i) of This AD</HD>
                        <P>This paragraph restates the requirements of paragraph (d) of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), with no changes. Perform the initial inspection required by paragraph (i) of this AD at the earlier of the times specified by paragraphs (j)(1) and (j)(2) of this AD.</P>
                        <P>(1) Prior to the accumulation of 25,000 total landings, or within 500 landings after June 12, 1995 (the effective date of AD 95-10-03, Amendment 39-9220 (60 FR 25604, May 12, 1995), whichever occurs later.</P>
                        <P>(2) At the applicable time specified by paragraph (j)(2)(i), (j)(2)(ii), or (j)(2)(iii) of this AD.</P>
                        <P>(i) For airplanes that have accumulated fewer than 10,000 landings as of July 28, 2000 (the effective date of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000)): Perform the inspection prior to the accumulation of 3,800 total landings, or within 1,500 landings after July 28, 2000, whichever occurs later.</P>
                        <P>(ii) For airplanes that have accumulated 10,000 total landings or more, but fewer than 20,000 total landings, as of July 28, 2000 (the effective date of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000)): Perform the inspection within 1,000 landings after July 28, 2000.</P>
                        <P>(iii) For airplanes that have accumulated 20,000 total landings or more as of July 28, 2000 (the effective date of AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000)): Perform the inspection within 500 landings after July 28, 2000.</P>
                        <HD SOURCE="HD1">(k) New Repetitive Inspections for Cracking</HD>
                        <P>(1) For airplanes identified in paragraph (k)(2) of this AD: Except as provided by paragraphs (n)(1) and (n)(4) of this AD, at the applicable compliance time specified in paragraph 1.E.(2), “Compliance,” of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, or within 100 flight cycles after the effective date of this AD, whichever occurs later, do an eddy current inspection or liquid penetrant inspection for cracking of the lower spar of the pylon between ribs 9 and 10; and do all applicable related investigative and corrective actions; in accordance with the Accomplishment Instructions of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, except as required by paragraphs (n)(2) and (n)(3) of this AD. Do all applicable related investigative and corrective actions before further flight. Repeat the inspection of the lower spar of the pylon between ribs 9 and 10 thereafter at intervals not to exceed the applicable interval specified in paragraph 1.E.(2), “Compliance,” of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD. Accomplishment of corrective actions required by this paragraph terminates the repetitive inspections required by this paragraph. Accomplishment of an inspection required by this paragraph terminates the inspection requirements of paragraphs (g), (h), and (i) of this AD. Accomplishment of the optional modification specified in the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD terminates the repetitive inspections required by this paragraph.</P>
                        <P>(i) Airbus Service Bulletin A300-54-0071, Revision 04, dated April 11, 2013 (for Model A300 B2-203, B2K-3C, B4-103, B4-203, and B4-2C airplanes).</P>
                        <P>(ii) Airbus Service Bulletin A310-54-2016, Revision 06, dated January 16, 2013 (for Model A310-221, -222, -322, -324, and -325 airplanes).</P>
                        <P>(iii) Airbus Service Bulletin A300-54-6011, Revision 03, dated June 23, 2011 (for Model A300 B4-620, B4-622R, and B4-622 airplanes).</P>
                        <P>(2) For airplanes that have not been modified or repaired with a doubler as specified in the applicable service bulletin specified in paragraph (k)(2)(i), (k)(2)(ii), or (k)(2)(iii) of this AD, do the inspections required by paragraph (k)(1) of this AD.</P>
                        <P>(i) Airbus Service Bulletin A300-54-0079 (for Model A300 B2-203, B2K-3C, B4-103, B4-203, and B4-2C airplanes).</P>
                        <P>(ii) Airbus Service Bulletin A310-54-2022 (for Model A310-221, -222, -322, -324, and -325 airplanes).</P>
                        <P>(iii) Airbus Service Bulletin A300-54-6019 (for Model A300 B4-620, B4-622R, and B4-622 airplanes).</P>
                        <HD SOURCE="HD1">(l) New Repetitive Inspections for Post-Repair Airplanes</HD>
                        <P>
                            For airplanes that have been repaired with a doubler as specified in the applicable Airbus service bulletin specified in 
                            <PRTPAGE P="72131"/>
                            paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD: At the applicable time specified in paragraph 1.E.(2), “Compliance,” in the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, except as specified in paragraphs (n)(1) and (n)(4) of this AD, do an eddy current inspection or liquid penetrant inspection for cracking of the lower spar of the pylon between ribs 9 and 10, and do all applicable corrective actions, in accordance with the Accomplishment Instructions of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, except as required by paragraph (n)(2) of this AD. Do all applicable corrective actions before further flight. Repeat the inspection of the lower spar of the pylon between ribs 9 and 10 thereafter at intervals not to exceed the applicable interval specified in paragraph 1.E.(2), “Compliance,” of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD. Accomplishment of an inspection required by this paragraph terminates the inspection requirements of paragraphs (g), (h), and (i) of this AD.
                        </P>
                        <HD SOURCE="HD1">(m) New Repetitive Inspections for Post-Modification Airplanes</HD>
                        <P>For airplanes that have been modified as specified in the applicable Airbus service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD: At the applicable time specified in paragraph 1.E.(2), “Compliance,” in the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, except as specified in paragraph (n)(1) and (n)(4) of this AD: Do an eddy current inspection or liquid penetrant inspection for cracking of the lower spar of the pylon between ribs 9 and 10; and do all applicable corrective actions; in accordance with the Accomplishment Instructions of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD, except as required by paragraph (n)(2) of this AD. Do all applicable corrective actions before further flight. Repeat the inspection of the lower spar of the pylon between ribs 9 and 10 thereafter at intervals not to exceed the applicable interval specified in paragraph 1.E.(2), “Compliance,” of the applicable service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD. Accomplishment of an inspection required by this paragraph terminates the inspection requirements of paragraphs (g), (h), and (i) of this AD.</P>
                        <HD SOURCE="HD1">(n) New Service Bulletin Exceptions</HD>
                        <P>(1) Where the service bulletins specified in paragraphs (k)(1)(i), (k)(1)(ii), and (k)(1)(iii) of this AD specify a compliance time “from the publication date,” this AD requires compliance within the specified compliance time after the effective date of this AD.</P>
                        <P>(2) If any crack is detected during any inspection required by paragraph (k), (l), or (m) of this AD, and the service bulletin specified in paragraph (k)(1)(i), (k)(1)(ii), or (k)(1)(iii) of this AD specifies to contact the manufacturer: Before further flight, repair using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the EASA; or Airbus's EASA DOA. If approved by the DOA, the approval must include the DOA-authorized signature.</P>
                        <P>(3) Where the service bulletins specified in paragraphs (k)(1)(i), (k)(1)(ii), and (k)(1)(iii) of this AD specify to contact the manufacturer for inspection requirements: Inspect using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the EASA; or Airbus's EASA DOA. If approved by the DOA, the approval must include the DOA-authorized signature.</P>
                        <P>(4) Where the “Threshold” column in the tables in paragraph 1.E., “Compliance,” of the service bulletins specified in paragraphs (k)(1)(i), (k)(1)(ii), and (k)(1)(iii) of this AD specifies a compliance time in flight cycles/flight hours, this AD requires compliance within the corresponding time in total flight cycles/total flight hours; except that for tables for post-repair and post-modification airplanes, this AD requires compliance within the corresponding time after accomplishing the repair or modification.</P>
                        <HD SOURCE="HD1">(o) Credit for Previous Actions</HD>
                        <P>This paragraph provides credit for actions required by paragraph (k) of this AD, if those actions were performed before the effective date of this AD using the applicable service bulletin specified in paragraphs (o)(1) through (o)(4) of this AD.</P>
                        <P>(1) Airbus Service Bulletin A300-54-071, Revision 02, dated August 25, 2000 (for Model A300 B2-203, B2K-3C, B4-103, B4-203, and B4-2C airplanes), which is not incorporated by reference in this AD.</P>
                        <P>(2) Airbus Service Bulletin A300-54-0071, Revision 03, dated October 5, 2012 (for Model A300 B2-203, B2K-3C, B4-103, B4-203, and B4-2C airplanes), which is not incorporated by reference in this AD.</P>
                        <P>(3) Airbus Service Bulletin A310-54-2016, Revision 04, dated November 16, 2007; or Airbus Service Bulletin A310-54-2016, Revision 05, dated October 5, 2012 (for Model A310-221, -222, -322, -324, and -325 airplanes); which are not incorporated by reference in this AD.</P>
                        <P>(4) Airbus Service Bulletin A300-54-6011, Revision 02, dated August 25, 2000 (for Model A300 B4-620, B4-622R, and B4-622 airplanes), which is not incorporated by reference in this AD.</P>
                        <HD SOURCE="HD1">(p) Other FAA AD Provisions</HD>
                        <P>The following provisions also apply to this AD:</P>
                        <P>
                            (1) 
                            <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                             The Manager, International Branch, 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: Dan Rodina, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, WA 98057-3356; telephone 425-227-2125; fax 425-227-1149. Information may be emailed to: 
                            <E T="03">9-ANM-116-AMOC-REQUESTS@faa.gov.</E>
                        </P>
                        <P>(i) 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>(ii) AMOCs approved previously for AD 2000-12-12, Amendment 39-11790 (65 FR 39072, June 23, 2000), are approved as AMOCs for the corresponding provisions of this AD.</P>
                        <P>
                            (2) 
                            <E T="03">Contacting the Manufacturer:</E>
                             As of the effective date of this AD, for any requirement in this AD to obtain corrective actions from a manufacturer, the action must be accomplished using a method approved by the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA; or the EASA; or Airbus's EASA DOA. If approved by the DOA, the approval must include the DOA-authorized signature.
                        </P>
                        <HD SOURCE="HD1">(q) Related Information</HD>
                        <P>
                            (1) Refer to Mandatory Continuing Airworthiness Information (MCAI) European Aviation Safety Agency Airworthiness Directive 2013-0216, dated September 17, 2013, for related information. You may examine the MCAI in the AD docket on the Internet at 
                            <E T="03">http://www.regulations.gov/#!documentDetail;D=FAA-2013-1066-0002.</E>
                        </P>
                        <P>(2) Service information identified in this AD that is not incorporated by reference in this AD is available at the addresses specified in paragraphs (r)(6) and (r)(7) of this AD.</P>
                        <HD SOURCE="HD1">(r) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                        <P>(3) The following service information was approved for IBR on January 9, 2015.</P>
                        <P>(i) Airbus Service Bulletin A300-54-0071, Revision 04, dated April 11, 2013.</P>
                        <P>(ii) Airbus Service Bulletin A310-54-2016, Revision 06, dated January 16, 2013.</P>
                        <P>(iii) Airbus Service Bulletin A300-54-6011, Revision 03, dated June 23, 2011.</P>
                        <P>(4) The following service information was approved for IBR on July 28, 2000 (65 FR 39072, June 23, 2000).</P>
                        <P>(i) Airbus Service Bulletin A310-54-2016, Revision 02, dated June 11, 1999.</P>
                        <P>(ii) Reserved.</P>
                        <P>(5) The following service information was approved for IBR on June 12, 1995 (60 FR 25604, May 12, 1995).</P>
                        <P>(i) Airbus Service Bulletin A300-54-071, dated November 12, 1991.</P>
                        <P>(ii) Airbus Service Bulletin A300-54-071, Revision 1, dated October 15, 1993.</P>
                        <P>(iii) Airbus Service Bulletin A300-54-6011, dated November 12, 1991.</P>
                        <P>(iv) Airbus Service Bulletin Change Notice O.A., A300-54-6011, dated July 10, 1992.</P>
                        <P>
                            (v) Airbus Service Bulletin A300-54-6011, Revision 1, dated October 15, 1993. (Pages 1 through 10 and 12 through 19 of this document are identified as Revision 1, dated October 15, 1993; page 11 is dated November 12, 1991.)
                            <PRTPAGE P="72132"/>
                        </P>
                        <P>(vi) Airbus Service Bulletin A300-54-6019, dated October 15, 1993.</P>
                        <P>
                            (6) For service information identified in this AD, contact Airbus SAS, Airworthiness Office—EAW, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 44 51; email 
                            <E T="03">account.airworth-eas@airbus.com;</E>
                             Internet 
                            <E T="03">http://www.airbus.com.</E>
                        </P>
                        <P>(7) You may view this service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, WA. For information on the availability of this material at the FAA, call 425-227-1221.</P>
                        <P>
                            (8) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Renton, Washington, on November 6, 2014.</DATED>
                    <NAME>Jeffrey E. Duven,</NAME>
                    <TITLE>Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28477 Filed 12-4-14; 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-2013-0159; Directorate Identifier 2012-SW-010-AD; Amendment 39-18032; AD 2014-23-16]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Robinson Helicopter Company Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are superseding Airworthiness Directive (AD) 2011-12-10 for Robinson Helicopter Company (Robinson) Model R22, R22 Alpha, R22 Beta, R22 Mariner, R44, and R44 II helicopters with certain main rotor blades (blade) installed. AD 2011-12-10 required inspecting each blade at the skin-to-spar line for debonding, corrosion, a separation, a gap, or a dent and replacing any damaged blade with an airworthy blade. This new AD also requires a terminating action for those inspection requirements. These actions are intended to detect debonding of the blade skin, which could result in blade failure and subsequent loss of control of the helicopter, and to correct the unsafe condition by replacing the main rotor blades with new blades that do not require the AD inspection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of January 9, 2015.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain other publications listed in this AD as of July 5, 2011 (76 FR 35330, June 17, 2011); corrected March 5, 2012 (77 FR 12991).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        For service information identified in this AD, contact Robinson Helicopter Company, 2901 Airport Drive, Torrance, CA 90505; telephone (310) 539-0508; fax (310) 539-5198; or at 
                        <E T="03">http://www.robinsonheli.com/servelib.htm.</E>
                         You may review a copy of the referenced service information at the FAA, Office of the Regional Counsel, Southwest Region, 2601 Meacham Blvd., Room 663, Fort Worth Texas, 76137.
                    </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 Operations Office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this AD, any incorporated-by-reference service information, the economic evaluation, any comments received, and other information. The street address for the Docket Operations Office (phone: 800-647-5527) is U.S. Department of Transportation, Docket Operations Office, 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>
                        Fred Guerin, Aviation Safety Engineer, Los Angeles Aircraft Certification Office, Transport Airplane Directorate, FAA, 3960 Paramount Blvd., Lakewood, CA 90712; telephone (562) 627-5232; email 
                        <E T="03">fred.guerin@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    On February 25, 2013, at 78 FR 12648, the 
                    <E T="04">Federal Register</E>
                     published our notice of proposed rulemaking (NPRM), which proposed to amend 14 CFR part 39 to supersede AD 2011-12-10, Amendment 39-16717 (76 FR 35330, June 17, 2011), corrected March 5, 2012 (77 FR 12991), that applied to Robinson Model R22, R22 Alpha, R22 Beta, and R22 Mariner helicopters with blade, part number (P/N) A016-4; and Model R44 and R44 II helicopters with blade, P/N C016-2 or C-016-5, installed. AD 2011-12-10 required a pilot check of the blade skin-to-spar joint area for any bare metal before the first flight of each day. AD 2011-12-10 also required repetitively inspecting each blade for corrosion, separation, a gap, or a dent, refinishing any bare metal before further flight, and replacing any damaged blade with an airworthy blade. AD 2011-12-10 was prompted by a fatal accident due to blade delamination.
                </P>
                <P>At the time we issued AD 2011-12-10, Robinson had developed replacement blades on the R22 and R44 model helicopters. AD 2011-12-10 was issued as a Final rule; request for comment; however, the amount of time permitted to replace the blades required allowing the public an opportunity to comment. Thus, the NPRM proposed to retain the pilot check, recurring inspection, and blade refinishing requirements of AD 2011-12-10. An owner/operator (pilot) may perform the visual check required by paragraph (f)(1) of this AD and must enter compliance with that paragraph into the helicopter maintenance records in accordance with 14 CFR 43.9(a)(1) through (4) and 91.417(a)(2)(v). A pilot may perform this check because it involves only looking at a visible area of the blades and can be performed equally well by a pilot or a mechanic. This check is an exception to our standard maintenance regulations. The NPRM also proposed to add a part-numbered blade to its applicability for R22 model helicopters. Lastly, the NPRM proposed to require, within five years of the effective date, replacing both main rotor blades with the new part-numbered aluminum blades, which would constitute terminating action of the recurring inspection requirements. These actions are intended to detect and prevent debonding of the blade skin, which could result in blade failure and subsequent loss of control of the helicopter.</P>
                <HD SOURCE="HD1">Comments</HD>
                <P>After our NPRM (78 FR 12648, February 25, 2013) was published, we received comments from 15 commenters and have given due consideration to each one. We have identified five unique issues and addressed those issues as follows.</P>
                <HD SOURCE="HD1">Requests</HD>
                <P>
                    Ten operators requested that we withdraw the NPRM and allow continued repetitive inspections of the blades for all affected models, as there is insufficient data justifying the termination of the requirement for repetitive inspections and for replacing the main rotor blades with new blades that do not require the AD inspection. One commenter noted that there have been no blade failures since the procedures of AD 2011-12-10 have 
                    <PRTPAGE P="72133"/>
                    been implemented, and therefore the NPRM increases the financial burden to an operator without increasing safety. Another commenter requested that more data be obtained regarding the effect of the operating environment and the inspection accordingly modified. Two commenters stated that a salt air environment caused the debonding due to corrosion. Some commenters state that inspections and routine maintenance, if done correctly, will ensure continued operational safety.
                </P>
                <P>We do not agree. Blade debonding continues to occur in service. The cause of the debonding was determined to be erosion on unpainted blade tip bond lines which allows the bond to weaken and the skin to pull up. The erosion is mechanical and occurs in any environment regardless of salt or moisture in the air. This unsafe condition is sufficient to mandate inspections due to the catastrophic consequences if the blade becomes delaminated. However, airworthiness cannot be assured long-term by reliance on continued repetitive inspections. Although there have been no fatalities since we issued AD 2011-12-10, Robinson continues to report instances of blade delamination found during maintenance checks. Because blades continue to have debond issues, and as using a safety-by-inspection approach for a critical component has been shown to have an inherent amount of risk, it is in the interest of safety to reduce the retirement of the blades from 12 years from the blade manufacturing date to an earlier date.</P>
                <P>Five operators requested that we remove the requirement for replacing the blades for the R44 Astro models, because these models are not equipped with hydraulic assisted controls and the new blades cannot be installed on these models unless the helicopter is converted to hydraulic assisted controls, a costly conversion which is not necessary for safe flight. These commenters further stated that the conversion is not only an additional expense but also can only be performed at the Robinson factory. One commenter believed the new blades are compatible with the non-hydraulic airframe and requested we require that Robinson test the new blades on the non-hydraulic R44 Astro airframe, so that the new blades can be installed on the R44 Astro without also having to convert the helicopter. The commenters also stated that Robinson then reserves the right to upgrade any component on the helicopter to their latest revision even though there is no AD or SB stating the Robinson required change, and this Robinson requirement results in additional cost increase. One commenter requested that we justify this requirement for the R44 Astro helicopters by identifying the number of reports of blade delamination on R44 Astros and explain the safety improvement resulting from converting a helicopter to hydraulic assisted controls. Finally, the commenters also stated that requiring replacement of the blades (and thus, conversion) for R44 Astro helicopters significantly reduces the resale value of these helicopters.</P>
                <P>We do not agree. The R44 Astro is subject to the same unsafe condition as the other R22 and R44 helicopter models. The purpose of this AD is not to require converting a helicopter to hydraulic assisted controls; the purpose is to correct this unsafe condition on the blades. Robinson's decision whether to test the new blades with the non-hydraulic R44 Astro helicopter is a business decision, and the FAA does not have the authority to mandate a different decision. Similarly, Robinson's decision to discontinue blades designed for the non-hydraulic equipped helicopters is a business decision that the FAA does not have the authority to change. Because the blades for the non-hydraulic equipped R44 Astro helicopters are calendar life limited to 12 years and will no longer be produced, and as the manufacturer has not pursued FAA approval for installation of the new blades on the non-hydraulic R44 Astro, the owners of the Astro helicopter will need to install hydraulic assisted flight controls after 12 years regardless of the AD requirements. The FAA acknowledges that the expense and downtime to accomplish the blade replacement is greater for the R44 helicopters that are not equipped with hydraulic assisted controls. However, this greater cost due to an absence of hydraulic controls, while unfortunate, does not change the blade safety issue or the need to require replacement of the blades prior to their retirement life.</P>
                <P>Four operators stated that the FAA has not considered the cost of this AD on operators and requested that Robinson be responsible for the cost of the new blades. One commenter also requested that Robinson be responsible for the cost of converting the R44 Astro to hydraulic assisted flight controls, as this will be required for that model when the new blades are installed.</P>
                <P>We do not agree. While we acknowledge that the costs associated with the actions of this AD are not minimal, we have determined that these costs are reasonable given the unsafe condition. As far as request for Robinson to bear these costs, the FAA does not have the authority to require a manufacturer to bear the cost of a repair.</P>
                <P>One commenter requested that we require blade replacement at the 2,200 hour overhaul or 12 years instead of the 5-year compliance time. The commenter stated that as Robinson started the production of new blades about 3 years ago, the 5-year replacement period would require some owners to replace the blades long before reaching the 12-year inspection, and this financial cost was not taken into account with the proposed rule.</P>
                <P>We do not agree. We determined a replacement period of five years from the date of the AD by using a quantitative and qualitative risk assessment methodology. The risk of blade skin debonding results in a loss of control of the helicopter and is beyond acceptable risk guidelines when allowing the blades to continue in service indefinitely. Although the risk assessment indicates that immediate action is required to correct the unsafe condition, this risk is partially mitigated by the improved inspection techniques, making it acceptable to allow a five year period of time for blades to be replaced. The added cost to retire the blades has been anticipated in the financial burden justification of this AD. The FAA acknowledges that in some situations the cost to the operator may be in excess of the cost of the replacement blades, but we have determined that the costs associated with the actions of this AD are reasonable given the safety issue.</P>
                <P>Lastly, one commenter did not make a request but stated that bare metal can be seen on areas of the helicopter and that the helicopter manufacturer provides poor corrosion protection on the helicopter. The commenter explained that metal-to-metal contact causes the corrosion that occurs on the blades.</P>
                <P>We disagree. Metal-to-metal contact may be a mechanism that is causing the corrosion in the rotor blade tip cap to skin interface, but it has not been shown to be a mechanism for skin debonding in the area of the blade that has been found in the fleet. Skin debonding is the unsafe condition the actions in this AD are correcting.</P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>
                    We have reviewed the relevant information, considered the comments received, and determined that an unsafe condition exists and is likely to exist or develop on other products of these same type designs and that air safety and the public interest require adopting the AD requirements as proposed, except we are allowing compliance with the revised service information as an optional 
                    <PRTPAGE P="72134"/>
                    action. We have also made clarifications in the economic analysis to reflect the correct cost of required parts and labor for R-44 helicopters without hydraulically boosted flight controls installed. The total estimated cost for these model helicopters has not changed. These changes are consistent with the intent of the proposals in the NPRM (78 FR 12648, February 25, 2013) and will not increase the economic burden on any operator nor increase the scope of the AD.
                </P>
                <HD SOURCE="HD1">Related Service Information</HD>
                <P>We have reviewed the following Robinson service information:</P>
                <P>• Letter titled “Additional Information Regarding Main Rotor Blade Skin Debonding,” dated May 25, 2007, discussing blade skin debonding;</P>
                <P>• Rotorcraft Flight Manual (RFM) changes to the Normal Procedures Section 4 and Systems Description Section 7, revised April 20, 2007, for each applicable model helicopter containing a “caution” about skin-to-spar bond line erosion;</P>
                <P>• One Service Letter with two different Nos.: R22 SL-56B and R44 SL-32B, both revised April 30, 2010, specifying proper inspection and protection (refinishing) of bonded areas; and</P>
                <P>• Service Bulletins SB-103 for the Model R22 and SB-72 for the Model R44, both dated April 30, 2010, and SB-103A and SB-72A, both dated July 19, 2012, specifying proper inspection and protection (refinishing) of bonded areas for certain affected blades.</P>
                <P>• R44 Service Letter SL-37, dated June 18, 2010, specifying the required modifications for a carbureted R-44 to install P/N C016-7 blades.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this AD affects 1,290 Model R22 helicopters and 1,353 Model R44 helicopters, for a total of 2,643 helicopters of U.S. Registry. At an average labor rate of $85 per hour, we estimate that operators will incur the following costs in order to comply with this AD:</P>
                <P>• Time to perform the before flight check each day is negligible.</P>
                <P>• Inspecting both blades will require about three work hours, for a total cost per helicopter of $255 and a total cost to the U.S. operator fleet of $673,965.</P>
                <P>• Replacing both blades on a Model R22 helicopter will require about 20 work hours, and required parts will cost $29,808, for a total cost per helicopter of $31,508 and a total cost to the U.S. R22 operator fleet of $40,645,320 over a 5-year period.</P>
                <P>• Replacing both blades on a Model R44 helicopter with hydraulically boosted flight controls installed (approximately 1,053 helicopters) will require about 20 work hours, and required parts will cost $43,783, for a total cost per helicopter of $45,483 and a total cost to the U.S. R44 operator fleet of $47,893,599 over a 5-year period.</P>
                <P>• Replacing both blades on a Model R44 helicopter without hydraulically boosted flight controls installed (approximately 300 helicopters) will require modifying the aircraft with hydraulic flight controls, and adding the P/N C016-7 blades and the required airframe provisions at a cost of 100 work-hours for a total labor cost of $8,500. Parts will cost $103,747 for a total cost per helicopters of $112,247, and a cost to U.S. operators of $33,674,100 over 5 years.</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 to the extent that it justifies making a regulatory distinction; 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>
                <P>We prepared an economic evaluation of the estimated costs to comply with this AD and placed it in the AD docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, 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 TITLE="14" PART="39">
                    <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 TITLE="14" PART="39">
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The FAA amends § 39.13 by removing Airworthiness Directive (AD) 2011-12-10, Amendment 39-16717 (76 FR 35330, June 17, 2011); corrected March 5, 2012 (77 FR 12991), and adding the following new AD:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2014-23-16 Robinson Helicopter Company:</E>
                             Amendment 39-18032; Docket No. FAA-2013-0159; Directorate Identifier 2012-SW-010-AD.
                        </FP>
                        <HD SOURCE="HD1">(a) Applicability</HD>
                        <P>This AD applies to Model R22, R22 Alpha, R22 Beta, and R22 Mariner helicopters with main rotor blade (blade), part number (P/N) A016-2 or A016-4; and Model R44 and R44 II helicopters with blade, P/N C016-2 or C-016-5, certificated in any category.</P>
                        <HD SOURCE="HD1">(b) Unsafe Condition</HD>
                        <P>This AD defines the unsafe condition as blade skin debonding, which could result in blade failure and subsequent loss of control of the helicopter.</P>
                        <HD SOURCE="HD1">(c) Affected ADs</HD>
                        <P>This AD supersedes AD 2011-12-10, Amendment 39-16717 (76 FR 35330, June 17, 2011); corrected March 5, 2012 (77 FR 12991).</P>
                        <HD SOURCE="HD1">(d) Effective Date</HD>
                        <P>This AD becomes effective January 9, 2015.</P>
                        <HD SOURCE="HD1">(e) Compliance</HD>
                        <P>You are responsible for performing each action required by this AD within the specified compliance time unless it has already been accomplished prior to that time.</P>
                        <HD SOURCE="HD1">(f) Required Actions</HD>
                        <P>
                            (1) Before the first flight of each day, visually check for any exposed (bare metal) skin-to-spar joint area on the lower surface of each blade. The actions required by this 
                            <PRTPAGE P="72135"/>
                            paragraph may be performed by the owner/operator (pilot) holding at least a private pilot certificate and must be entered into the aircraft records showing compliance with this AD in accordance with 14 CFR 43.9(a)(1) through (4) and 14 CFR 91.417(a)(2)(v). The record must be maintained as required by 14 CFR 91.417, 121.380, or 135.439.
                        </P>
                        <P>(2) If there is any bare metal in the area of the skin-to-spar bond line, before further flight, inspect the blade by following the requirements of paragraph (f)(3) of this AD.</P>
                        <P>(3) Within 10 hours time-in-service (TIS), and at intervals not to exceed 100 hours TIS or at each annual inspection, whichever occurs first, inspect each blade for corrosion, separation, a gap, or a dent by following the Compliance Procedure, paragraphs 1 through 6 and 8, of Robinson R22 Service Bulletin SB-103, dated April 30, 2010 (SB103), or Robinson Service Bulletin SB-72, dated April 30, 2010 (SB72), as appropriate for your model helicopter. Although the Robinson service information limits the magnification to 10X, a higher magnification is acceptable for this inspection. Also, an appropriate tap test tool which provides similar performance, weight, and consistency of tone may be substituted for the “1965 or later United States Quarter-dollar coin,” which is specified in the Compliance Procedure, paragraph 2, of SB72 and SB103.</P>
                        <P>(4) Before further flight, refinish any exposed area of a blade by following the Compliance Procedure, paragraphs 2 through 6, of Robinson R22 Service Letter SL-56B or R44 Service Letter SL-32B, both dated April 30, 2010, as appropriate for your model helicopter.</P>
                        <P>(5) Before further flight, replace any unairworthy blade with an airworthy blade.</P>
                        <P>(6) Within 5 years of the effective date of this AD:</P>
                        <P>(i) For Model R22 series helicopters, replace blade P/N A016-2 or A016-4 with a blade, P/N A016-6.</P>
                        <P>(ii) For Model R44 series helicopters fitted with hydraulically boosted main rotor flight controls, replace blade P/N C016-2 or C016-5 with a blade, P/N C016-7.</P>
                        <P>(iii) For Model R44 series helicopters without hydraulically boosted main rotor flight controls, replace blade P/N C016-2 or C016-5 with a blade, P/N C016-7. Prior to installing a blade P/N C016-7, verify the helicopter has been modified as required by Robinson R44 Service Letter SL-37, dated June 18, 2010, Compliance Procedures, paragraphs 1. through 10.</P>
                        <P>(iv) Installing blades, P/N A016-6 or P/N C016-7, is terminating action for the inspection requirements of paragraphs (f)(1) through (f)(4) of this AD.</P>
                        <P>(7) As an option for complying with paragraph (f)(3) of this AD, you may perform a blade inspection by following the corresponding provisions of SB-103A or SB-72A, both dated July 19, 2012, as appropriate for your model helicopter.</P>
                        <HD SOURCE="HD1">(g) Special Flight Permits</HD>
                        <P>Special flight permits will not be issued.</P>
                        <HD SOURCE="HD1">(h) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, Los Angeles Aircraft Certification Office, FAA, may approve AMOCs for this AD. Send your proposal to: Fred Guerin, Aviation Safety Engineer, Los Angeles Aircraft Certification Office, Transport Airplane Directorate, FAA, 3960 Paramount Blvd., Lakewood, CA 90712; telephone (562) 627-5232; email 
                            <E T="03">fred.guerin@faa.gov.</E>
                        </P>
                        <P>(2) For operations conducted under a 14 CFR part 119 operating certificate or under 14 CFR part 91, subpart K, we suggest that you notify your principal inspector, or lacking a principal inspector, the manager of the local flight standards district office or certificate holding district office before operating any aircraft complying with this AD through an AMOC.</P>
                        <P>(3) AMOCs approved for AD 2011-12-10 (76 FR 35330, June 17, 2011); corrected March 5, 2012 (77 FR 12991), are approved as AMOCs for the corresponding requirements in paragraph (f) of this AD.</P>
                        <HD SOURCE="HD1">(i) Additional Information</HD>
                        <P>
                            The Robinson letter titled “Additional Information Regarding Main Rotor Blade Skin Debonding,” dated May 25, 2007, which is not incorporated by reference, contains additional information about the subject of this AD. For service information identified in this AD, contact Robinson Helicopter Company, 2901 Airport Drive, Torrance, CA 90505; telephone (310) 539-0508; fax (310) 539-5198; or at 
                            <E T="03">http://www.robinsonheli.com/servelib.htm.</E>
                             You may review a copy of this information at the FAA, Office of the Regional Counsel, Southwest Region, 2601 Meacham Blvd., Room 663, Fort Worth, Texas 76137.
                        </P>
                        <HD SOURCE="HD1">(j) Subject</HD>
                        <P>Joint Aircraft Service Component (JASC) Code: 6210: Main Rotor Blades.</P>
                        <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                        <P>(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                        <P>(3) The following service information was approved for IBR on January 9, 2015.</P>
                        <P>(i) Robinson R44 Service Letter SL-37, dated June 18, 2010.</P>
                        <P>(ii) Reserved.</P>
                        <P>(4) The following service information was previously approved for IBR on July 5, 2011 (76 FR 35330, June 17, 2011); corrected March 5, 2012 (77 FR 12991).</P>
                        <P>(i) Robinson R22 Service Bulletin SB-103, dated April 30, 2010.</P>
                        <P>(ii) Robinson R44 Service Bulletin SB-72, dated April 30, 2010.</P>
                        <P>(iii) Robinson R22 Service Letter SL-56B, dated April 30, 2010.</P>
                        <P>(iv) Robinson R44 Service Letter SL-32B, dated April 30, 2010.</P>
                        <P>
                            (5) For Robinson service information identified in this AD, contact Robinson Helicopter Company, 2901 Airport Drive, Torrance, CA 90505; telephone (310) 539-0508; fax (310) 539-5198; or at 
                            <E T="03">http://www.robinsonheli.com/servelib.htm.</E>
                        </P>
                        <P>(6) You may view this service information at FAA, Office of the Regional Counsel, Southwest Region, 2601 Meacham Blvd., Room 663, Fort Worth, Texas 76137. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                        <P>
                            (7) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call (202) 741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on November 4, 2014.</DATED>
                    <NAME>Lance T. Gant,</NAME>
                    <TITLE>Acting Directorate Manager, Rotorcraft Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28478 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2014-0986; Airspace Docket No. 14-AGL-14]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Multiple Air Traffic Service (ATS) Routes; North Central and Northeast United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule, technical amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action amends multiple high altitude Area Navigation (RNAV) routes (Q-routes) in the north central and northeast United States (U.S.) to change 13 fixes identified in the Q-routes to match waypoint (WP) characterizations contained in the FAA and Canadian aeronautical database information establishing the WPs. This action also amends the route termination point and geographic latitude/longitude position in RNAV route Q-822 to reflect changes made by Canada as part of its Windsor-Toronto-Montreal (WTM) airspace redesign effort.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date 0901 UTC, January 8, 2015. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order 7400.9Y, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">http://www.faa.gov/air_traffic/publications/.</E>
                         The Order is also available for inspection at the National Archives and Records 
                        <PRTPAGE P="72136"/>
                        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>FAA Order 7400.9, Airspace Designations and Reporting Points, is published yearly and effective on September 15. For further information, you can contact the Airspace Policy and Regulations Group, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: 202-267-8783.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colby Abbott, Airspace Policy and Regulations Group, Office of Airspace Services, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: (202) 267-8783.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>
                    On September 26, 2014, the FAA published in the 
                    <E T="04">Federal Register</E>
                     a final rule (79 FR 57758) that amended, removed, and established multiple ATS routes in the north central and northeast United States to reflect and accommodate route changes being made in Canadian airspace as part of Canada's WTM airspace redesign project, and corrected a notice of proposed rulemaking (NPRM) publishing error. The rule also made a number of changes or corrections deemed necessary following the NPRM public comment period.
                </P>
                <P>The FAA now has identified in the rule that the following 13 fixes in several route descriptions were established in the FAA and Canadian aeronautical databases as WPs: DUTSH, OH; RICCS, WV; WAYLA, NY; PUPPY, NY; ARKKK, NY; FABEN, NY; STOMP, NY; POSTS, MI; JOSSY, NY; KRAZZ, NY; AGNOB, Canada; LORKA, Canada; and ADVIK, Canada.</P>
                <P>Additionally, the final route segment providing cross border connectivity between the U.S. and Canada for the RNAV route Q-822 description was changed within Canadian airspace by NAV CANADA due to route realignment requirements. Also in RNAV route Q-822, the TANGU, Canada, WP was changed to the SINVI, Canada, WP located in a new geographic latitude/longitude position.</P>
                <P>This rule makes the corrections to be in concert with FAA and Canadian aeronautical databases.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>The FAA is amending Title 14, Code of Federal Regulations (14 CFR) part 71 by modifying RNAV routes Q-29, Q-69, Q-82, Q-84, Q-103, Q-140, Q-812, Q-818, Q-822, Q-907, Q-935, and Q-937. The RNAV route modifications correct fix characterizations to match FAA and Canadian aeronautical database information and support Canadian airspace redesign changes for routes into and out of the Winsor, Toronto, and Montreal areas within Canada to ensure safe and efficient across border connectivity.</P>
                <P>The RNAV route modifications accomplished by this action are outlined below.</P>
                <FP SOURCE="FP-1">Q-29: Change the “DUTSH, OH FIX” to read “DUTSH, OH WP.”</FP>
                <FP SOURCE="FP-1">Q-69: Change the “RICCS, WV FIX” to read “RICCS, WV WP.”</FP>
                <FP SOURCE="FP-1">Q-82: Change the “WAYLA, NY FIX” to read “WAYLA, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-84: Change the “PUPPY, NY FIX” to read “PUPPY, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-103: Change the “RICCS, WV FIX” to read “RICCS, WV WP.”</FP>
                <FP SOURCE="FP-1">Q-140: Change the “ARKKK, NY FIX” to read “ARKKK, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-812: Change the “FABEN, NY FIX” to read “FABEN, NY WP;” the “ARKKK, NY FIX” to read “ARKKK, NY WP;” and the “STOMP, NY FIX” to read “STOMP, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-818: Change the “STOMP, NY FIX” to read “STOMP, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-822: Change the route title to read “Q-822 “Flint, MI (FNT) to SINVI, Canada;” the “PUPPY, NY FIX” to read “PUPPY, NY WP;” and the “TANGU, Canada WP (lat. 44°50′58.00″ N., long. 063°58′43.00″ W.)” to read “SINVI, Canada WP (lat. 44°48′15.00″ N., long. 064°19′27.00″ W.).”</FP>
                <FP SOURCE="FP-1">Q-907: Change the “POSTS, MI FIX” to read “POSTS, MI WP;” the “AGNOB, Canada FIX” to read “AGNOB, Canada WP;” the “LORKA, Canada FIX” to read “LORKA, Canada WP;” and the “ADVIK, Canada FIX” to read “ADVIK, Canada WP.”</FP>
                <FP SOURCE="FP-1">Q-935: Change the “JOSSY, NY FIX” to read “JOSSY, NY WP;” and the “FABEN, NY FIX” to read “FABEN, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-937: Change the “TULEG, Canada WP” to read “TULEG, Canada FIX;” and the “KRAZZ, NY FIX” to read “KRAZZ, NY WP.”</FP>
                <FP SOURCE="FP-1">Q-951: Change the “POSTS, MI FIX” to read “POSTS, MI WP.”</FP>
                <P>High altitude United States RNAV routes (Q-routes) are published in paragraph 2006 and high altitude Canadian RNAV routes (Q-routes) are published in paragraph 2007 of FAA Order 7400.9Y dated August 6, 2014, and effective September 15, 2014, which is incorporated by reference in 14 CFR 71.1. The high altitude United States and Canadian RNAV routes (Q-routes) listed in this rule will be subsequently published in the Order.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this regulation: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under Department of Transportation (DOT) Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that only affects air traffic procedures and air navigation, it is certified that this rule, when promulgated, does not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority.</P>
                <P>This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of the airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it modifies the route structure as necessary to preserve the safe and efficient flow of air traffic within the National Airspace System. In addition, as this rule is correcting errors in certain Q routes and updating RNAV route Q-822 to accommodate changes by Canada that affect these routes, I find that notice and public procedure under 5 U.S.C. 553(b) are impractical, unnecessary and not in the public interest.</P>
                <HD SOURCE="HD1">Environmental Review</HD>
                <P>The FAA has determined that this action qualifies for categorical exclusion under the National Environmental Policy Act in accordance with FAA Order 1050.1E, “Environmental Impacts: Policies and Procedures,” paragraph 311a. This airspace action is not expected to cause any potentially significant environmental impacts, and no extraordinary circumstances exist that warrant preparation of an environmental assessment.</P>
                <LSTSUB>
                    <PRTPAGE P="72137"/>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <REGTEXT TITLE="14" PART="71">
                    <PART>
                        <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <SECTION>
                        <SECTNO>§ 71.1</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order 7400.9Y, Airspace Designations and Reporting Points, dated August 6, 2014, and effective September 15, 2014, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 2006 United States Area Navigation Routes</HD>
                        <STARS/>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,8/9,g1,t1,i1" CDEF="xls100,xls50,xls190">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-29 HARES, LA to DUVOK, Canada (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">HARES, LA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 33°00′00.00″ N., long. 091°44′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">BAKRE, MS</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 33°53′45.85″ N., long. 090°58′04.75″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Memphis, TN (MEM)</ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 35°00′54.42″ N., long. 089°58′59.55″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">OMDUE, TN</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 36°07′47.32″ N., long. 088°58′11.49″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SIDAE, KY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 37°20′00.00″ N., long. 087°50′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CREEP, OH </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 39°55′15.28″ N., long. 084°18′31.41″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KLYNE, OH</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 40°41′54.46″ N., long. 083°18′44.19″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DUTSH, OH</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°08′26.35″ N., long. 082°33′12.68″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WWSHR, OH</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°20′34.09″ N., long. 082°03′05.76″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DORET, OH </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 41°48′05.90″ N., long. 080°35′04.64″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Jamestown, NY (JHW) </ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°11′18.99″ N., long. 079°07′16.70″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HANKK, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°53′41.82″ N., long. 077°09′15.21″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GONZZ, NY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°05′22.00″ N., long. 076°41′12.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KRAZZ, NY</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°25′00.00″ N., long. 074°18′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">NIPPY, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 43°41′23.08″ N., long. 073°58′06.74″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CABCI, VT</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°49′19.94″ N., long. 071°42′55.14″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EBONY, ME </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 44°54′08.68″ N., long. 067°09′23.65″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DUNOM, ME</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°54′06.95″ N., long. 067°00′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DUVOK, Canada</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 44°55′37.33″ N., long. 065°17′11.66″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the portion within Canada.</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-69 BLANN, SC to RICCS, WV (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">BLAAN, SC</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 33°51′09.38″ N., long. 080°53′32.78″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RYCKI, NC</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 36°24′43.05″ N., long. 080°25′07.50″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LUNDD, VA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 36°44′22.38″ N., long. 080°21′07.11″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ILLSA, VA</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 37°38′55.85″ N., long. 080°13′18.44″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EWESS, WV</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 38°21′50.31″ N., long. 080°06′52.03″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RICCS, WV</ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 38°55′14.65″ N., long. 080°05′01.68″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-82 WWSHR, OH to PONCT, NY (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">WWSHR, OH </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°20′34.09″ N., long. 082°03′05.76″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DORET, OH </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 41°48′05.90″ N., long. 080°35′04.64″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Jamestown, NY (JHW) </ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°11′18.99″ N., long. 079°07′16.70″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WAYLA, NY </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°20′58.54″ N., long. 077°48′57.18″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VIEEW, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°26′22.07″ N., long. 077°01′33.30″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MEMMS, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°30′59.71″ N., long. 076°18′15.43″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LOXXE, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°34′29.55″ N., long. 075°43′33.49″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PONCT, NY </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 42°44′48.83″ N., long. 073°48′48.07″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-84 Jamestown, NY (JHW) to Cambridge, NY (CAM) (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">Jamestown, NY (JHW) </ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°11′18.99″ N., long. 079°07′16.70″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AUDIL, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 42°52′18.74″ N., long. 076°26′35.07″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PUPPY, NY </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 43°03′26.46″ N., long. 075°17′39.29″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PAYGE, NY </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 43°00′50.48″ N., long. 074°15′12.76″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Cambridge, NY (CAM) </ENT>
                                <ENT>VOR/DME</ENT>
                                <ENT>(Lat. 42°59′39.40″ N., long. 073°20′38.50″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-103 Pulaski, VA (PSK) to AIRRA, PA (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">Pulaski, VA (PSK) </ENT>
                                <ENT>VORTAC</ENT>
                                <ENT>(Lat. 37°05′15.74″ N., long. 080°42′46.44″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ASBUR, WV </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 37°49′24.41″ N., long. 080°27′51.44″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">OAKLE, WV </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 38°07′13.80″ N., long. 080°21′44.84″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PERRI, WV </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 38°17′50.49″ N., long. 080°18′05.11″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PERKS, WV </ENT>
                                <ENT>FIX</ENT>
                                <ENT>(Lat. 38°39′40.84″ N., long. 080°10′29.36″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RICCS, WV </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 38°55′14.65″ N., long. 080°05′01.68″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EMNEM, WV </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 39°31′27.12″ N., long. 080°04′28.21″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AIRRA, PA </ENT>
                                <ENT>WP</ENT>
                                <ENT>(Lat. 41°06′16.48″ N., long. 080°03′48.73″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-140 WOBED, WA to YODAA, NY (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">WOBED, WA </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 48°36′01.07″ N., long. 122°49′46.52″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GETNG, WA </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 48°25′30.57″ N., long. 119°31′38.98″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="72138"/>
                                <ENT I="01">CORDU, ID </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 48°10′46.41″ N., long. 116°40′21.84″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PETIY, MT </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 47°58′46.55″ N., long. 114°36′20.31″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CHOTE, MT </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 47°39′56.68″ N., long. 112°09′38.13″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LEWIT, MT </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 47°23′00.21″ N., long. 110°08′44.78″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SAYOR, MT </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 47°13′58.34″ N., long. 104°58′39.28″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WILTN, ND </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 47°04′58.09″ N., long. 100°47′43.84″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">TTAIL, MN </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 46°41′28.00″ N., long. 096°41′09.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CESNA, WI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°52′14.00″ N., long. 092°10′59.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WISCN, WI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°18′19.45″ N., long. 089°27′53.91″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EEGEE, WI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°08′53.00″ N., long. 088°45′58.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DAYYY, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°10′10.00″ N., long. 084°22′23.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RUBKI, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°14′56.00″ N., long. 082°15′25.99″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PEPLA, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°47′51.00″ N., long. 080°01′02.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SIKBO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°39′13.00″ N., long. 079°20′57.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MEDAV, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°29′19.00″ N., long. 078°45′46.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AHPAH, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°18′19.00″ N., long. 078°07′35.11″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HANKK, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°53′41.82″ N., long. 077°09′15.21″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">BEEPS, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°49′13.26″ N., long. 076°59′04.84″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">EXTOL, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°39′27.69″ N., long. 076°37′06.10″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MEMMS, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°30′59.71″ N., long. 076°18′15.43″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KODEY, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°16′47.53″ N., long. 075°47′04.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ARKKK, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°03′48.52″ N., long. 075°19′00.41″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RODYY, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 41°52′25.85″ N., long. 074°35′49.39″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">YODAA, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°43′21.19″ N., long. 074°01′52.76″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                        <HD SOURCE="HD2">Paragraph 2007 Canadian Area Navigation Routes (Amended)</HD>
                        <GPOTABLE COLS="3" OPTS="L0,tp0,p0,8/9,g1,t1,i1" CDEF="xls100,xls50,xls190">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-812 TIMMR, ND to GAYEL, NY (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">TIMMR, ND </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 46°22′49.49″ N., long. 100°54′29.80″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WELOK, MN </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°41′26.32″ N., long. 094°15′28.74″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">CEWDA, WI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°48′32.00″ N., long. 088°33′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ZOHAN, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°55′57.00″ N., long. 084°23′09.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">NOSIK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°59′00.00″ N., long. 082°11′52.30″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AGDOX, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°17′01.71″ N., long. 079°05′29.29″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KELTI, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°16′57.00″ N., long. 078°56′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AHPAH, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°18′19.00″ N., long. 078°07′35.11″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GOATR, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°17′26.08″ N., long. 076°39′07.75″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Syracuse, NY (SYR) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 43°09′37.87″ N., long. 076°12′16.41″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">FABEN, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°51′12.04″ N., long. 075°57′07.91″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LOXXE, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°34′29.55″ N., long. 075°43′33.49″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ARKKK, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°03′48.52″ N., long. 075°19′00.41″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">STOMP, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 41°35′46.78″ N., long. 074°47′47.79″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MSLIN, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°29′30.82″ N., long. 074°33′14.28″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GAYEL, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°24′24.09″ N., long. 074°21′25.75″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-818 Flint, MI (FNT) to GAYEL, NY (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">Flint, MI (FNT) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 42°58′00.38″ N., long. 083°44′49.08″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">TANKO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°01′32.00″ N., long. 082°22′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KITOK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°02′30.00″ N., long. 081°55′34.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DERLO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′59.00″ N., long. 081°05′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">IKNAV, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°57′43.00″ N., long. 078°59′04.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WOZEE, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°56′01.65″ N., long. 078°44′19.64″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KELIE, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°39′37.32″ N., long. 077°44′41.05″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VIEEW, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°26′22.07″ N., long. 077°01′33.30″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Binghampton, NY (CFB) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 42°09′26.96″ N., long. 076°08′11.30″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">BUFFY, PA </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°56′27.98″ N., long. 075°36′45.35″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">STOMP, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 41°35′46.78″ N., long. 074°47′47.79″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MSLIN, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°29′30.82″ N., long. 074°33′14.28″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GAYEL, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 41°24′24.09″ N., long. 074°21′25.75″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">
                                    <E T="04">Q-822 Flint, MI (FNT) to SINVI, Canada (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">Flint, MI (FNT) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 42°58′00.38″ N., long. 083°44′49.08″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">TANKO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°01′32.00″ N., long. 082°22′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KITOK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°02′30.00″ N., long. 081°55′34.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DERLO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′59.00″ N., long. 081°05′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HOZIR, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°06′03.59″ N., long. 079°02′05.27″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">GONZZ, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°05′22.00″ N., long. 076°41′12.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PUPPY, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′26.46″ N., long. 075°17′39.29″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PAYGE, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 43°00′50.48″ N., long. 074°15′12.76″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Cambridge, NY (CAM) </ENT>
                                <ENT>VOR/DME </ENT>
                                <ENT>(Lat. 42°59′39.44″ N., long. 073°20′38.47″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="72139"/>
                                <ENT I="01">Kennebunk, ME (ENE) </ENT>
                                <ENT>VOR/DME </ENT>
                                <ENT>(Lat. 43°25′32.42″ N., long. 070°36′48.69″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AJJAY, ME </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°43′40.55″ N., long. 069°36′08.22″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ALLEX, ME </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°25′00.00″ N., long. 067°00′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SINVI, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°48′15.00″ N., long. 064°19′27.00″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-907 POSTS, MI to MIILS, Canada (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">POSTS, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°18′00.00″ N., long. 085°02′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PADDE, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°17′09.00″ N., long. 084°28′28.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Salem, MI (SVM) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 42°24′31.09″ N., long. 083°35′38.05″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DERLO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′59.00″ N., long. 081°05′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SIKBO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°39′13.00″ N., long. 079°20′57.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AGNOB, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°12′03.30″ N., long. 077°30′07.20″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">LORKA, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°46′08.70″ N., long. 076°12′59.90″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ADVIK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°08′04.00″ N., long. 074°46′33.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ATENE, Canada </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 46°14′04.20″ N., long. 070°16′21.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">MIILS, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 46°52′42.00″ N., long. 067°02′09.00″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-935 MONEE, MI to Boston, MA (BOS) (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">MONEE, MI</ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 43°14′25.80″ N., long. 084°27′50.95″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HOCKE, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°15′43.38″ N., long. 082°42′38.27″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">OMRAK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°16′06.00″ N., long. 082°16′25.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DERLO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′59.00″ N., long. 081°05′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">IKNAV, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°57′43.00″ N., long. 078°59′04.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WOZEE, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°56′01.65″ N., long. 078°44′19.64″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">HANKK, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°53′41.82″ N., long. 077°09′15.21″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">JOSSY, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°53′29.93″ N., long. 077°02′36.80″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">AUDIL, NY </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 42°52′18.74″ N., long. 076°26′35.07″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">FABEN, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°51′12.04″ N., long. 075°57′07.91″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PONCT, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°44′48.83″ N., long. 073°48′48.07″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Gardner, MA (GDM) </ENT>
                                <ENT>VOR/DME </ENT>
                                <ENT>(Lat. 42°32′45.32″ N., long. 072°03′29.48″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Boston, MA (BOS) </ENT>
                                <ENT>VOR/DME </ENT>
                                <ENT>(Lat. 42°21′26.82″ N., long. 070°59′22.37″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">
                                    <E T="04">Q-937 TULEG, Canada to KRAZZ, NY (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">TULEG, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°43′54.84″ N., long. 076°43′09.82″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">WAYGO, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°25′00.00″ N., long. 075°55′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">KRAZZ, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°25′00.00″ N., long. 074°18′00.00″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *    *    *</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">
                                    <E T="04">Q-951 POSTS, MI to PUXOP, Canada (Amended)</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">POSTS, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°18′00.00″ N., long. 085°02′00.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PADDE, MI </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 42°17′09.00″ N., long. 084°28′28.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Salem, MI (SVM) </ENT>
                                <ENT>VORTAC </ENT>
                                <ENT>(Lat. 42°24′31.09″ N., long. 083°35′38.05″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DERLO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°03′59.00″ N., long. 081°05′43.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SIKBO, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 43°39′13.00″ N., long. 079°20′57.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SANIN, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°04′41.00″ N., long. 077°25′55.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">OLABA, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°28′35.00″ N., long. 076°12′12.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ALONI, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°38′54.00″ N., long. 075°39′10.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DAVDA, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°43′27.00″ N., long. 075°22′28.20″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">SAVAL, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 44°54′15.00″ N., long. 074°42′01.20″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">TALNO, NY </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°00′02.00″ N., long. 074°19′52.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">RABIK, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°17′56.00″ N., long. 072°36′37.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">ANTOV, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°22′35.00″ N., long. 071°02′15.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DANOL, ME </ENT>
                                <ENT>FIX </ENT>
                                <ENT>(Lat. 45°41′54.22″ N., long. 067°47′16.00″ W.)</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">PUXOP, Canada </ENT>
                                <ENT>WP </ENT>
                                <ENT>(Lat. 45°56′41.00″ N., long. 066°26′24.00″ W.)</ENT>
                            </ROW>
                            <ROW EXPSTB="02">
                                <ENT I="22">Excluding the airspace within Canada.</ENT>
                            </ROW>
                        </GPOTABLE>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on December 1, 2014.</DATED>
                    <NAME>Gary A. Norek,</NAME>
                    <TITLE>Manager, Airspace Policy &amp; Regulations Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28618 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>
                BILLING CODE 4910-13-P
                <PRTPAGE P="72140"/>
            </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 117</CFR>
                <DEPDOC>[Docket No. USCG-2014-1012]</DEPDOC>
                <SUBJECT>Drawbridge Operation Regulation; Gulf Intracoastal Waterway, Belle Chasse, LA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of deviation from drawbridge regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard has issued a temporary deviation from the operating schedule that governs the Louisiana State Route 23 (LA 23) vertical lift span bridge, also known as the Judge Perez Bridge, across the Gulf Intracoastal Waterway (Algiers Alternate Route), mile 3.8, at Belle Chasse, Plaquemines Parish, Louisiana. This deviation is necessary to provide for the safe movement of vehicular traffic during major plant reconstruction on one side of the waterway and the resulting change in work schedule and increase in workforce transiting the bridge. This deviation allows the bridge to remain temporarily closed to navigation for an additional one hour in the evening during weekdays for five weeks.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This deviation is effective without actual notice from December 5, 2014 through 6:30 p.m. on December 25, 2014. For the purposes of enforcement, actual notice will be used from 5:30 p.m. on November 24, 2014, until December 5, 2014.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The docket for this deviation, [USCG-2014-1012] is available at 
                        <E T="03">http://www.regulations.gov.</E>
                         Type the docket number in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this deviation. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 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 deviation, call or email David Frank, Bridge Administration Branch, Coast Guard; telephone 504-671-2128, email 
                        <E T="03">David.M.Frank@uscg.mil.</E>
                         If you have questions on viewing the docket, call Cheryl F. Collins, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On November 10, 2014, a Notice of Temporary Deviation entitled, “Drawbridge Operation Regulation; Gulf Intracoastal Waterway, Belle Chasse, LA” was published in the 
                    <E T="04">Federal Register</E>
                    . 79 FR 66621.
                </P>
                <P>That temporary deviation allowed for the Louisiana State Route 23 (LA 23) vertical lift span bridge, also known as the Judge Perez Bridge, across the Gulf Intracoastal Waterway (Algiers Alternate Route), mile 3.8, at Belle Chasse, Plaquemines Parish, Louisiana, to remain closed to navigation for an additional one hour in the evenings from 5:30 p.m. to 6:30 p.m. from December 26, 2014, through February 20, 2015.</P>
                <P>Subsequent to publication, the Sheriff of Plaquemines Parish requested by letter dated November 18, 2014, that the additional one hour deviation commence immediately because of major safety concerns with regard to parish residents and the ability of emergency vehicles to transit the area. The Sheriff of Plaquemines Parish indicated that the area has experienced increased traffic during a construction pre-shut down phase at the Phillips 66 plant.</P>
                <P>The deviation requested allows the bridge to remain closed to navigation for an additional one hour in the evening, Monday through Friday, effecting a total deviation period from Friday, November 24, 2014, through Friday, February 20, 2015. Coordination with local Coast Guard and waterway users was conducted, and immediate commencement of the deviation will not have a significant impact on mariners.</P>
                <P>Presently, in accordance with 33 CFR 117.451(b), the draw shall open on signal; except that, from 6 a.m. to 8:30 a.m. and from 3:30 p.m. to 5:30 p.m. Monday through Friday, except Federal holidays, the draw need not open for the passage of vessels.</P>
                <P>This temporary deviation allows the vertical lift bridge to remain closed to navigation for one additional hour in the afternoon. This additional hour extends the afternoon curfew hours to 6:30 p.m. Monday through Friday beginning November 24, 2014 through December 25, 2014. In case of an emergency, the bridge will be able to open for the passage of vessels.</P>
                <P>The State Route 23 vertical lift span drawbridge across the Gulf Intracoastal Waterway (Algiers Alternate Route), mile 3.8, at Belle Chasse, Louisiana has a vertical clearance of 40 feet above mean high water in the closed-to-navigation position and 100 feet above mean high water in the open-to-navigation position. Navigation on the waterway consists primarily of tugs with tows, commercial fishing vessels, and occasional recreational craft. Mariners may use the Gulf Intracoastal Waterway (Harvey Canal) to avoid unnecessary delays. The Coast Guard has coordinated this closure with the Gulf Intracoastal Canal Association (GICA). The GICA representative indicated that the vessel operators will be able to schedule transits through the bridge to avoid delays and significant impacts on operations. Due to prior experience, as well as coordination with waterway users, it has been determined that this closure will not have a significant effect on these vessels.</P>
                <P>In accordance with 33 CFR 117.35, the drawbridge must return to its regular operating schedule immediately at the end of the effective period of this temporary deviation.</P>
                <P>This deviation from the operating regulations is authorized under 33 CFR 117.35.</P>
                <SIG>
                    <DATED>Dated: November 24, 2014.</DATED>
                    <NAME>David M. Frank,</NAME>
                    <TITLE>Bridge Administrator, Eighth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28602 Filed 12-4-14; 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 180 </CFR>
                <DEPDOC>[EPA-HQ-OPP-2014-0668; FRL-9918-42]</DEPDOC>
                <SUBJECT>2,5-Furandione, Polymer With Methoxyethene, Butyl Ethyl Ester, Sodium Salt; Tolerance Exemption</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>
                        This regulation establishes an exemption from the requirement of a tolerance for residues of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt; when used as an inert ingredient in a pesticide chemical formulation. The firm Lewis &amp; Harrison, on behalf of International Specialty Products submitted a petition to EPA under the Federal Food, Drug, and Cosmetic Act (FFDCA), requesting an exemption from the requirement of a 
                        <PRTPAGE P="72141"/>
                        tolerance. This regulation eliminates the need to establish a maximum permissible level for residues of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt on food or feed commodities.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This regulation is effective December 5, 2014. Objections and requests for hearings must be received on or before February 3, 2015, and must be filed in accordance with the instructions provided in 40 CFR part 178 (see also Unit I.C. of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        ).
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The docket for this action, identified by docket identification (ID) number EPA-HQ-OPP-2014-0668, is available at 
                        <E T="03">http://www.regulations.gov</E>
                         or at the Office of Pesticide Programs Regulatory Public Docket (OPP Docket) in the Environmental Protection Agency Docket Center (EPA/DC), West William Jefferson Clinton Bldg., Rm. 3334, 1301 Constitution Ave. NW., Washington, DC 20460-0001. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the OPP Docket is (703) 305-5805. Please review the visitor instructions and additional information about the docket available at 
                        <E T="03">http://www.epa.gov/dockets</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Susan Lewis, Registration Division (7505P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; main telephone number: (703) 305-7090; email address: 
                        <E T="03">RDFRNotices@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>You may be potentially affected by this action if you are an agricultural producer, food manufacturer, or pesticide manufacturer. The following list of North American Industrial Classification System (NAICS) codes is not intended to be exhaustive, but rather provides a guide to help readers determine whether this document applies to them. Potentially affected entities may include:</P>
                <P>• Crop production (NAICS code 111).</P>
                <P>• Animal production (NAICS code 112).</P>
                <P>• Food manufacturing (NAICS code 311).</P>
                <P>• Pesticide manufacturing (NAICS code 32532).</P>
                <HD SOURCE="HD2">B. How can I get electronic access to other related information?</HD>
                <P>
                    You may access a frequently updated electronic version of 40 CFR part 180 through the Government Printing Office's e-CFR site at 
                    <E T="03">http://www.ecfr.gov/cgi-bin/text-idx?&amp;c=ecfr&amp;tpl=/ecfrbrowse/Title40/40tab_02.tpl</E>
                    .
                </P>
                <HD SOURCE="HD2">C. Can I file an objection or hearing request?</HD>
                <P>Under FFDCA section 408(g), 21 U.S.C. 346a, any person may file an objection to any aspect of this regulation and may also request a hearing on those objections. You must file your objection or request a hearing on this regulation in accordance with the instructions provided in 40 CFR part 178. To ensure proper receipt by EPA, you must identify docket ID number EPA-HQ-OPP-2014-0668 in the subject line on the first page of your submission. All objections and requests for a hearing must be in writing, and must be received by the Hearing Clerk on or before February 3, 2015. Addresses for mail and hand delivery of objections and hearing requests are provided in 40 CFR 178.25(b).</P>
                <P>In addition to filing an objection or hearing request with the Hearing Clerk as described in 40 CFR part 178, please submit a copy of the filing (excluding any Confidential Business Information (CBI)) for inclusion in the public docket. Information not marked confidential pursuant to 40 CFR part 2 may be disclosed publicly by EPA without prior notice. Submit the non-CBI copy of your objection or hearing request, identified by docket ID number EPA-HQ-OPP-2014-0668, by one of the following methods.</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                    . Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be CBI or other information whose disclosure is restricted by statute.
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     OPP Docket, Environmental Protection Agency Docket Center (EPA/DC), (28221T), 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001.
                </P>
                <P>
                    • 
                    <E T="03">Hand Delivery:</E>
                     To make special arrangements for hand delivery or delivery of boxed information, please follow the instructions at 
                    <E T="03">http://www.epa.gov/dockets/contacts.html</E>
                    .
                </P>
                <P>
                    Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at 
                    <E T="03">http://www.epa.gov/dockets</E>
                    .
                </P>
                <HD SOURCE="HD1">II. Background and Statutory Findings</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of October 15, 2014 (79 FR 61844) (FRL-9917-24), EPA issued a document pursuant to FFDCA section 408, 21 U.S.C. 346a, announcing the receipt of a pesticide petition (PP IN-10755) filed by the firm Lewis &amp; Harrison, 122 C Street NW., Suite 505, Washington, DC 20001, on behalf of International Specialty Products. The petition requested that 40 CFR 180.960 be amended by establishing an exemption from the requirement of a tolerance for residues of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt (CAS Reg. No. 1471342-08-1). That document included a summary of the petition prepared by the petitioner and solicited comments on the petitioner's request. A comment was received on the notice of filing. EPA's response to the comment is discussed in Unit VIII.B.
                </P>
                <P>Section 408(c)(2)(A)(i) of FFDCA allows EPA to establish an exemption from the requirement for a tolerance (the legal limit for a pesticide chemical residue in or on a food) only if EPA determines that the exemption is “safe.” Section 408(c)(2)(A)(ii) of FFDCA defines “safe” to mean that “there is a reasonable certainty that no harm will result from aggregate exposure to the pesticide chemical residue, including all anticipated dietary exposures and all other exposures for which there is reliable information.” This includes exposure through drinking water and use in residential settings, but does not include occupational exposure. Section 408(b)(2)(C) of FFDCA requires EPA to give special consideration to exposure of infants and children to the pesticide chemical residue in establishing an exemption from the requirement of a tolerance and to “ensure that there is a reasonable certainty that no harm will result to infants and children from aggregate exposure to the pesticide chemical residue . . .” and specifies factors EPA is to consider in establishing an exemption.</P>
                <HD SOURCE="HD1">III. Risk Assessment and Statutory Findings</HD>
                <P>
                    EPA establishes exemptions from the requirement of a tolerance only in those cases where it can be shown that the risks from aggregate exposure to pesticide chemical residues under reasonably foreseeable circumstances will pose no appreciable risks to human health. In order to determine the risks from aggregate exposure to pesticide inert ingredients, the Agency considers the toxicity of the inert in conjunction with possible exposure to residues of 
                    <PRTPAGE P="72142"/>
                    the inert ingredient through food, drinking water, and through other exposures that occur as a result of pesticide use in residential settings. If EPA is able to determine that a finite tolerance is not necessary to ensure that there is a reasonable certainty that no harm will result from aggregate exposure to the inert ingredient, an exemption from the requirement of a tolerance may be established.
                </P>
                <P>Consistent with FFDCA section 408(b)(2)(D), EPA has reviewed the available scientific data and other relevant information in support of this action and considered its validity, completeness and reliability and the relationship of this information to human risk. EPA has also considered available information concerning the variability of the sensitivities of major identifiable subgroups of consumers, including infants and children. In the case of certain chemical substances that are defined as polymers, the Agency has established a set of criteria to identify categories of polymers expected to present minimal or no risk. The definition of a polymer is given in 40 CFR 723.250(b) and the exclusion criteria for identifying these low-risk polymers are described in 40 CFR 723.250(d). 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt conforms to the definition of a polymer given in 40 CFR 723.250(b) and meets the following criteria that are used to identify low-risk polymers.</P>
                <P>1. The polymer is not a cationic polymer nor is it reasonably anticipated to become a cationic polymer in a natural aquatic environment.</P>
                <P>2. The polymer does contain as an integral part of its composition the atomic elements carbon, hydrogen, and oxygen.</P>
                <P>3. The polymer does not contain as an integral part of its composition, except as impurities, any element other than those listed in 40 CFR 723.250(d)(2)(ii).</P>
                <P>4. The polymer is neither designed nor can it be reasonably anticipated to substantially degrade, decompose, or depolymerize.</P>
                <P>5. The polymer is manufactured or imported from monomers and/or reactants that are already included on the TSCA Chemical Substance Inventory or manufactured under an applicable TSCA section 5 exemption.</P>
                <P>6. The polymer is not a water absorbing polymer with a number average molecular weight (MW) greater than or equal to 10,000 daltons.</P>
                <P>7. The polymer does not contain certain perfluoroalkyl moieties consisting of a CF3- or longer chain length as specified in 40 CFR 723.250(d)(6) and less than 5% oligomeric material below MW 1,000.</P>
                <P>Thus, 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt meets the criteria for a polymer to be considered low risk under 40 CFR 723.250. Based on its conformance to the criteria in this unit, no mammalian toxicity is anticipated from dietary, inhalation, or dermal exposure to 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt.</P>
                <HD SOURCE="HD1">IV. Aggregate Exposures</HD>
                <P>For the purposes of assessing potential exposure under this exemption, EPA considered that 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt could be present in all raw and processed agricultural commodities and drinking water, and that non-occupational non-dietary exposure was possible. The number average MW of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt is 18,200 daltons. Generally, a polymer of this size would be poorly absorbed through the intact gastrointestinal tract or through intact human skin. Since 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt conform to the criteria that identify a low-risk polymer, there are no concerns for risks associated with any potential exposure scenarios that are reasonably foreseeable. The Agency has determined that a tolerance is not necessary to protect the public health.</P>
                <HD SOURCE="HD1">V. Cumulative Effects From Substances With a Common Mechanism of Toxicity</HD>
                <P>Section 408(b)(2)(D)(v) of FFDCA requires that, when considering whether to establish, modify, or revoke a tolerance, the Agency consider “available information” concerning the cumulative effects of a particular pesticide's residues and “other substances that have a common mechanism of toxicity.”</P>
                <P>
                    EPA has not found 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt to share a common mechanism of toxicity with any other substances, and 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt does not appear to produce a toxic metabolite produced by other substances. For the purposes of this tolerance action, therefore, EPA has assumed that 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt does not have a common mechanism of toxicity with other substances. For information regarding EPA's efforts to determine which chemicals have a common mechanism of toxicity and to evaluate the cumulative effects of such chemicals, see EPA's Web site at 
                    <E T="03">http://www.epa.gov/pesticides/cumulative</E>
                    .
                </P>
                <HD SOURCE="HD1">VI. Additional Safety Factor for the Protection of Infants and Children</HD>
                <P>Section 408(b)(2)(C) of FFDCA provides that EPA shall apply an additional tenfold margin of safety for infants and children in the case of threshold effects to account for prenatal and postnatal toxicity and the completeness of the data base unless EPA concludes that a different margin of safety will be safe for infants and children. Due to the expected low toxicity of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt, EPA has not used a safety factor analysis to assess the risk. For the same reasons the additional tenfold safety factor is unnecessary.</P>
                <HD SOURCE="HD1">VII. Determination of Safety</HD>
                <P>Based on the conformance to the criteria used to identify a low-risk polymer, EPA concludes that there is a reasonable certainty of no harm to the U.S. population, including infants and children, from aggregate exposure to residues of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt.</P>
                <HD SOURCE="HD1">VIII. Other Considerations</HD>
                <HD SOURCE="HD2">A. Analytical Enforcement Methodology</HD>
                <P>An analytical method is not required for enforcement purposes since the Agency is establishing an exemption from the requirement of a tolerance without any numerical limitation.</P>
                <HD SOURCE="HD2">B. Response to Comments</HD>
                <P>One comment was received for a notice of filing from a private citizen who opposed any pesticide product that leaves a residue above 0.00. The Agency understands the commenter's concerns and recognizes that some individuals believe that no residue of pesticides should be allowed. However, under the existing legal framework provided by FFDCA section 408, EPA is authorized to establish pesticide tolerances or exemptions where persons seeking such tolerances or exemptions have demonstrated that the pesticide meets the safety standard imposed by the statute.</P>
                <HD SOURCE="HD2">C. International Residue Limits</HD>
                <P>
                    In making its tolerance decisions, EPA seeks to harmonize U.S. tolerances with international standards whenever possible, consistent with U.S. food safety standards and agricultural 
                    <PRTPAGE P="72143"/>
                    practices. EPA considers the international maximum residue limits (MRLs) established by the Codex Alimentarius Commission (Codex), as required by FFDCA section 408(b)(4). The Codex Alimentarius is a joint United Nations Food and Agriculture Organization/World Health Organization food standards program, and it is recognized as an international food safety standards-setting organization in trade agreements to which the United States is a party. EPA may establish a tolerance that is different from a Codex MRL; however, FFDCA section 408(b)(4) requires that EPA explain the reasons for departing from the Codex level.
                </P>
                <P>The Codex has not established a MRL for 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt.</P>
                <HD SOURCE="HD1">IX. Conclusion</HD>
                <P>Accordingly, EPA finds that exempting residues of 2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt from the requirement of a tolerance will be safe.</P>
                <HD SOURCE="HD1">X. Statutory and Executive Order Reviews</HD>
                <P>
                    This final rule establishes a tolerance under FFDCA section 408(d) in response to a petition submitted to the Agency. The Office of Management and Budget (OMB) has exempted these rules from review under Executive Order 12866, entitled “Regulatory Planning and Review” (58 FR 51735, October 4, 1993). Because this final rule has been exempted from review under Executive Order 12866, this final rule is not subject to Executive Order 13211, entitled “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001) or Executive Order 13045, entitled “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997). This final rule does not contain any information collections subject to OMB approval under the Paperwork Reduction Act (PRA) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), nor does it involve any technical standards that would require Agency consideration of voluntary consensus standards pursuant to section 12(d) of the National Technology Transfer and Advancement Act of 1995 (NTTAA) (15 U.S.C. 272 note).
                </P>
                <P>
                    Since tolerances and exemptions that are established on the basis of a petition under FFDCA section 408(d), such as the tolerance in this final rule, do not require the issuance of a proposed rule, the requirements of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), do not apply.
                </P>
                <P>
                    This final rule directly regulates growers, food processors, food handlers, and food retailers, not States or tribes, nor does this action alter the relationships or distribution of power and responsibilities established by Congress in the preemption provisions of FFDCA section 408(n)(4). As such, the Agency has determined that this action will not have a substantial direct effect on States or tribal governments, on the relationship between the national government and the States or tribal governments, or on the distribution of power and responsibilities among the various levels of government or between the Federal Government and Indian Tribes, or otherwise have any unique impacts on local governments. Thus, the Agency has determined that Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999) and Executive Order 13175, entitled “Consultation and Coordination with Indian Tribal Governments” (65 FR 67249, November 9, 2000) do not apply to this final rule. In addition, this final rule does not impose any enforceable duty or contain any unfunded mandate as described under Title II of the Unfunded Mandates Reform Act of 1995 (UMRA) (2 U.S.C. 1501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>Although this action does not require any special considerations under Executive Order 12898, entitled “Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations” (59 FR 7629, February 16, 1994), EPA seeks to achieve environmental justice, the fair treatment and meaningful involvement of any group, including minority and/or low-income populations, in the development, implementation, and enforcement of environmental laws, regulations, and policies. As such, to the extent that information is publicly available or was submitted in comments to EPA, the Agency considered whether groups or segments of the population, as a result of their location, cultural practices, or other factors, may have atypical or disproportionately high and adverse human health impacts or environmental effects from exposure to the pesticide discussed in this document, compared to the general population.</P>
                <HD SOURCE="HD1">XI. Congressional Review Act</HD>
                <P>
                    Pursuant to the Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . This action is not a “major rule” as defined by 5 U.S.C. 804(2).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 180</HD>
                    <P>Environmental protection, Administrative practice and procedure, Agricultural commodities, Pesticides and pests, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 24, 2014.</DATED>
                    <NAME>Susan Lewis,</NAME>
                    <TITLE>Director, Registration Division, Office of Pesticide Programs.</TITLE>
                </SIG>
                <P>Therefore, 40 CFR chapter I is amended as follows:</P>
                <REGTEXT TITLE="40" PART="180">
                    <PART>
                        <HD SOURCE="HED">PART 180—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 180 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>21 U.S.C. 321(q), 346a and 371.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="180">
                    <AMDPAR>2. In § 180.960, the table is amended by alphabetically adding an entry for “2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt, minimum number average molecular weight (in amu), 18,200” after the entry for “2,5-Furandione, polymer with ethenylbenzene, reaction, products with polyethylene-polypropylene glycol 2-aminopropyl Me ether; minimum number average molecular weight (in amu), 14,000” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 180.960 </SECTNO>
                        <SUBJECT>Polymers; exemptions from the requirement of a tolerance.</SUBJECT>
                        <STARS/>
                        <GPOTABLE COLS="02" OPTS="L1,tp0,i1" CDEF="s100,12">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Polymer</CHED>
                                <CHED H="1">CAS No.</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2,5-Furandione, polymer with methoxyethene, butyl ethyl ester, sodium salt, minimum number average molecular weight (in amu), 18,200</ENT>
                                <ENT>1471342-08-1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*    *    *    *    *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28603 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Parts 1 and 22</CFR>
                <DEPDOC>[WT Docket No. 12-40; RM-11510; FCC 14-181]</DEPDOC>
                <SUBJECT>Cellular Service, Including Changes in Licensing of Unserved Area</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="72144"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In this 
                        <E T="03">Report and Order</E>
                         (“
                        <E T="03">R&amp;O</E>
                        ”), the Federal Communications Commission (“Commission”) adopts new and revised rules governing the 800 MHz Cellular (“Cellular”) Service, changing the licensing model from site-based to geographic-based and eliminating numerous filing requirements while preserving direct access to area not yet licensed (“Unserved Area”). The Commission also deletes obsolete and unnecessary provisions in the rules and streamlines requirements remaining in place. The resulting modernized scheme gives greater flexibility to Cellular licensees to make improvements to their systems in response to changing market demands.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Effective January 5, 2015, except for the amendments to 47 CFR 22.165(e), 47 CFR 22.948, and 47 CFR 22.953, which contain information collection requirements that have not yet been approved by the Office of Management and Budget (OMB). The Commission will publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing the effective date of those three amendments.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nina Shafran, Mobility Division, Wireless Telecommunications Bureau, (202) 418-2781, TTY (202) 418-7233.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Federal Communications Commission's 
                    <E T="03">Report and Order</E>
                     (“
                    <E T="03">R&amp;O</E>
                    ”), WT Docket No. 12-40, RM No. 11510, FCC 14-181, adopted November 7, 2014 and released November 10, 2014. The full text of the 
                    <E T="03">R&amp;O,</E>
                     including all Appendices, is available for inspection and copying during normal business hours in the FCC Reference Center, 445 12th Street SW., Room CY-A157, Washington, DC 20554, or by downloading the text from the Commission's Web site at 
                    <E T="03">http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db1110/FCC-14-181A1.pdf.</E>
                     The complete text also may be purchased from the Commission's duplicating contractor, Best Copy and Printing, Inc. Portals II, 445 12th Street SW., Suite CY-B402, Washington, DC 20554. Alternative formats are available for people with disabilities (Braille, large print, electronic files, audio format), by sending an email to 
                    <E T="03">FCC504@fcc.gov</E>
                     or calling the Consumer and Government Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (TTY).
                </P>
                <HD SOURCE="HD1">Synopsis of the Report and Order</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>1. Under the current site-based licensing rules, a Cellular applicant requests authorization to construct at a specific transmitter location (or multiple locations) in Unserved Area and may construct only authorized transmitters. Cellular Unserved Area applications specify the area to be licensed as CGSA and, because they are classified as “major” applications no matter how small the expansion area, they are subject to a 30-day public comment period during which petitions to deny and competing applications may be filed. In the event that mutually exclusive applications are accepted for a particular Unserved Area, they are resolved through competitive bidding in closed auctions. Unserved Area licenses granted are subject to a one-year construction deadline for the authorized site; failure to build out results in automatic termination of the authorization for that site, and the Unserved Area again is subject to re-licensing.</P>
                <P>
                    2. In a 
                    <E T="03">Notice of Proposed Rulemaking</E>
                     released on February 15, 2012 (“
                    <E T="03">2012 NPRM</E>
                    ”), the Commission proposed to transition the Cellular Service to geographic-based licensing by issuing geographic-area overlay licenses through competitive bidding in two stages. The Commission also proposed new and revised rules. The Commission sought comment on all aspects of its proposals as well as on other ideas, proposals, and comments discussed in the 
                    <E T="03">2012 NPRM,</E>
                     and also invited the submission of alternative ideas. In response to the 
                    <E T="03">2012 NPRM,</E>
                     interested parties submitted comments, reply comments, and 
                    <E T="03">ex parte</E>
                     letters. The specific reforms adopted by the Commission in the 
                    <E T="03">R&amp;O</E>
                     are described below.
                </P>
                <HD SOURCE="HD1">II. Report and Order</HD>
                <HD SOURCE="HD2">A. Geographic License Boundaries</HD>
                <P>3. While the traditional geographic licensing model, such as the model for the Broadband Personal Communications Service (“PCS”) and other commercial wireless services, entails awarding licenses (via competitive bidding if mutually exclusive applications are accepted) for areas whose boundaries are co-terminus with well-known political boundaries or other market areas established by the Commission, such as Metropolitan Statistical Areas, the Commission concludes that geographic areas should be defined for the Cellular Service at this time by CGSA boundaries. This is consistent with the Commission's goals and recognizes the history and current status of the Cellular Service.</P>
                <P>
                    4. As explained in more detail in the 
                    <E T="03">2012 NPRM,</E>
                     the Commission digitized all CGSAs using the most recent maps on file for licensed CGSAs, creating map files in geographic information system (“GIS”) format. Since then, the staff has regularly updated the files, and in October 2013, made them publicly available online. They draw directly from official Universal Licensing System (“ULS”) station records for the Cellular Service, using the most recent CGSA maps of record, including those accompanying Cellular applications submitted pursuant to Commission rules. The staff uses them to determine the official boundary of an authorized CGSA (and a proposed CGSA when reviewing a Cellular Service application). They will continue to be updated regularly, and licensees as well as new-system applicants should consult them to verify CGSA boundaries.
                </P>
                <HD SOURCE="HD2">B. Field Strength Limit</HD>
                <P>
                    5. Based on the record in this proceeding, the Commission finds that its proposed 40 dBµV/m field strength limit is appropriate for the Cellular Service and, accordingly, the Commission adopts a new rule establishing this limit. The Commission also finds it appropriate, consistent with other geographic-based wireless services, to permit neighboring co-channel Cellular licensees to negotiate different field strength limits—higher or lower than 40 dBµV/m. The Commission emphasizes that Cellular licensees must comply at all times with the applicable radiated power limits as well as applicable provisions of international agreements and treaties. However, given that the Commission is preserving the ability to expand service coverage into any Unserved Area nationwide, both through CGSA expansions and SAB extensions (as discussed further below), the Commission finds it appropriate to depart from the 
                    <E T="03">2012 NPRM</E>
                     proposal to subject all Cellular licensees to a 40 dBµV/m (or negotiated) signal field strength limit at their respective license boundaries. Under the approach the Commission has adopted in the 
                    <E T="03">R&amp;O,</E>
                     a Cellular licensee's CGSA will not always be adjacent to a neighboring co-channel licensee's CGSA; it may in some cases be bordered by Unserved Area. Therefore, increased flexibility for Cellular licensees is warranted when applying the field strength limit rule.
                </P>
                <P>
                    6. Accordingly, the Commission adopts a rule that will apply at every 
                    <PRTPAGE P="72145"/>
                    point along the neighboring co-channel licensee's CGSA boundary. The following two examples illustrate this new rule: (1) If a licensee's CGSA borders Unserved Area (whether currently or through a service coverage expansion in compliance with the new rules), that licensee can exceed the 40 dBµV/m limit at its own CGSA boundary, so long as it complies with that limit (or a negotiated limit) at every point along the neighboring co-channel licensee's CGSA boundary; (2) if two co-channel licensees' CGSAs are adjacent, both licensees will be subject to the field strength limit rule at every point along their shared CGSA boundary to protect one another. The Commission concludes that this more flexible approach serves the public interest.
                </P>
                <P>
                    7. The Commission declines at this time to provide a methodology regarding how the field strength should be determined. Cellular licensees are best positioned to choose a methodology that takes into account factors unique to their systems and the area involved, including, for example, technologies, traffic loading, topography, and location of major roads. The Commission recognizes that the existing regime in the Gulf of Mexico (“Gulf”) Cellular market was carefully crafted following lengthy Commission and judicial proceedings. Accordingly, as set forth in the new field strength limit rule (47 CFR 22.983) and the revised version of 47 CFR 22.912 that the Commission also adopts in this 
                    <E T="03">R&amp;O</E>
                     (discussed further below), the Commission finds that it serves the public interest to continue to maintain the status quo Gulf regime in most respects and not apply the new field strength limit rule. Specifically, the Commission will continue to require service area extension agreements and associated filings with the Commission as follows: land-based carriers adjoining the Gulf will be required to negotiate any desired SAB extensions into the Gulf of Mexico Exclusive Zone and submit minor modification applications to the Commission, certifying that such consent has been obtained; and licensees in the Gulf of Mexico Exclusive Zone will likewise be required to negotiate any desired SAB extensions into the licensed area of neighboring land-based carriers and submit minor modification applications to the Commission, certifying that such consent has been obtained. The Commission clarifies that all land-based carriers will, however, be subject to the new field strength limit rule to protect the licensed CGSA boundaries of all neighboring co-channel land-based licensees.
                </P>
                <P>
                    8. No commenters objected to the proposal to retain the requirements for mandatory coordination currently set forth in 47 CFR 22.907, and the Commission finds that it serves the public interest to adopt that proposal. As the Commission emphasizes, Cellular licensees will be permitted to expand their CGSAs and extend their SABs (in compliance with the new rules adopted in the 
                    <E T="03">R&amp;O</E>
                    ), which are calculated based on contours. The formulas in 47 CFR 22.911 provide a proven method for the requisite calculation of such contours and the service area within them, and the Commission finds that they do not warrant change at this time. The Commission does, however, revise 47 CFR 22.911 to delete provisions rendered obsolete by its decision to adopt a field strength limit rule and the related decision to eliminate certain requirements governing SAB extensions into another licensee's CGSA, discussed below, in connection with transitioning the Cellular Service to a geographic-based model. These revisions to 47 CFR 22.911 do not affect the formulas for calculating CGSAs and SABs.
                </P>
                <HD SOURCE="HD2">C. SAB Extensions Negotiated With Another Licensee</HD>
                <P>
                    9. 
                    <E T="03">Background.</E>
                     Under the current Cellular site-based licensing regime, a licensee seeking to extend service coverage on a secondary basis into the licensed area of a neighboring co-channel licensee is required to negotiate an SAB extension agreement and is then required to file a minor modification application for the extension and certify that the neighboring licensee's consent has been obtained. In response to the 
                    <E T="03">2012 NPRM,</E>
                     some commenters cautioned that previously negotiated SAB extension agreements should not be disrupted by the Commission.
                </P>
                <P>10. Consistent with the approach taken in other commercial wireless services and the Commission's goals in this proceeding, the Commission revises 47 CFR 22.912 to reflect that the Commission will no longer require applications for SAB extensions into neighboring CGSAs, and it adopts a conforming change to 47 CFR 22.911(d). The Commission clarifies that, so long as a licensee either meets the 40 dBµV/m field strength limit or negotiates a different limit (higher or lower) with the neighboring co-channel licensee, resulting SAB extensions into a neighboring licensee's CGSA will be permitted without a minor modification application or a certification that consents have been obtained. The exception is with respect to the Gulf, as discussed above. The Commission emphasizes that it does not seek to disrupt previously negotiated SAB extension agreements between Cellular licensees, nor does it seek to prohibit new ones. The Commission fully expects that parties will continue to comply with the terms of their existing SAB extension agreements or negotiate new terms if they deem warranted.</P>
                <HD SOURCE="HD2">D. SABs Remaining Within CGSA Boundaries</HD>
                <P>11. Under the existing site-based licensing regime, Cellular licensees are required to file minor modification applications notifying the Commission of the addition or modification of transmitter sites that form the CGSA boundary—so-called border sites. While system changes to purely internal (non-border) sites generally do not require a Commission filing, changes to border sites require the notifications (but not prior approval) even when the resulting new or modified SAB remains entirely within the CGSA boundary.</P>
                <P>12. The Commission finds that it serves the public interest to no longer require that Cellular licensees notify the Commission of changes to cell sites, or the addition of new cell sites, where the SAB remains confined within the existing CGSA boundary. This approach is consistent with the Commission's goals of reducing licensee administrative burdens, enhancing flexibility to adapt quickly to technological and market place changes, and increasing harmonization of the Cellular Service rules with those of other geographically licensed services.</P>
                <P>
                    13. 
                    <E T="03">Section 22.165(e).</E>
                     The introductory clause of 47 CFR 22.165 limits the scope of the entire rule to transmitters that may be added without prior Commission approval, and subsection 22.165(e) governs Cellular licensees solely in that context; it does not address whether adding a Cellular transmitter triggers the requirement to file a notification with the Commission. Consistent with the licensing approach the Commission adopts in this 
                    <E T="03">R&amp;O,</E>
                     the Commission also adopts a simplified 47 CFR 22.165(e) that eliminates references to the legacy Cellular licensing model (
                    <E T="03">e.g.,</E>
                     the five-year construction period of an initial primary license) and clarifies when a Cellular transmitter may be added without prior Commission approval.
                </P>
                <HD SOURCE="HD2">E. 50-Square-Mile Minimum for CGSA Expansions</HD>
                <P>
                    14. There is currently no required minimum for expansion of an existing system's CGSA into Unserved Area, and any expansion no matter how small requires a major modification 
                    <PRTPAGE P="72146"/>
                    application seeking prior Commission approval. All CGSA-expansion applications are placed on public notice for 30 days. This reform proceeding has evaluated whether there is a continued need for modification applications and subsequent buildout notifications for very small system changes. Also, a high number of amendments are subsequently filed, either to cure applicant errors or change the coverage or certain technical parameters initially proposed. The result is a process that consumes significant licensee and FCC resources. Commission data indicate that, by limiting CGSA-expansion major modification applications to those that propose expansion of 50 contiguous square miles or more, together with adopting a streamlined procedure for service coverage expansions of less than 50 contiguous square miles, the volume of major modification applications and associated amendments for CGSA expansions will be dramatically reduced. Likewise, the volume of build-out notification filings would also be significantly reduced.
                </P>
                <P>
                    15. The Commission is persuaded, as noted above, to continue to permit CGSA expansions in all CMA Blocks at this time. The Commission also agrees with the commenters that it serves the public interest to establish by rule a minimum requirement of 50 contiguous square miles (as determined pursuant to the applicable formula in 47 CFR 22.911) for all CGSA expansions (
                    <E T="03">i.e.,</E>
                     to expand service coverage on a primary, protected basis). The Commission concludes that this approach balances the concerns of large and smaller carriers alike, particularly because the Commission will not only continue to permit secondary operation to serve smaller parcels (less than 50 contiguous square miles), but will enhance flexibility by eliminating previously required Commission filings for such parcels, as discussed in detail in the next section of this 
                    <E T="03">R&amp;O.</E>
                     The Commission incorporates this minimum requirement for CGSA expansions into the revised version of 47 CFR 22.949 that the Commission adopts in this 
                    <E T="03">R&amp;O</E>
                     and, consistent with the Commission's regulatory reform agenda to streamline rules where possible, the Commission consolidates the existing new-system coverage requirements currently set forth in 47 CFR 22.951 into 47 CFR 22.949. The Commission declines at this time to adopt a commenter's proposal to establish a two-year build-out requirement solely for licensees in Alaska; it finds that the one-year build-out requirement applicable to all Cellular licensees has generally worked well and does warrant change at this time.
                </P>
                <P>
                    16. The Commission anticipates that licensees will not make unnecessary filings under the new rules it adopts in this 
                    <E T="03">R&amp;O.</E>
                     The Commission clarifies that, to the extent that applications are filed claiming Unserved Area as CGSA without meeting the new minimum square mileage requirement, Commission staff will not process them; rather, they will return or dismiss such filings unless first withdrawn by the applicant.
                </P>
                <HD SOURCE="HD2">F. SAB Extensions Into Unserved Area; Shared Service on a Secondary Basis</HD>
                <P>
                    17. Since 2004, the Commission has permitted Cellular licensees to extend their SABs into adjacent Unserved Area and provide service on a secondary basis without first filing a major modification application seeking prior Commission approval, so long as the extension is less than 50 square miles. In such instances, the licensee has been required to file only a notification upon commencing service on a secondary (
                    <E T="03">i.e.,</E>
                     an unlicensed, unprotected) basis. A licensee seeking to claim the area as part of its CGSA (
                    <E T="03">i.e.,</E>
                     for primary, protected service) is required to submit a major modification application subject to a 30-day public comment period, no matter how small the area. The 2004 relaxation of the prior approval requirement in such circumstances was designed to provide licensees with additional flexibility to respond to operational demands immediately in a manner that remained consistent with site-based licensing rules.
                </P>
                <P>18. As explained in the preceding section, to balance the concerns of smaller, more rural carriers and large carriers alike, the Commission adopts revised Cellular rules based on a geographic licensing model while also preserving certain elements of the existing site-based model, including the continued ability to expand CGSAs into Unserved Area so long as the proposed expansion area is at least 50 contiguous square miles. A high volume of applications under current Cellular rules are to make improvements in response to technological changes, demographic changes, and consumer demand that change the CGSA boundary by an extremely small amount. The Commission finds that it serves the public interest to permit continued access to these small parcels of Unserved Area, but the Commission recognizes that filings associated with minor system changes that expand service into these small parcels often constitute hindrances to system improvements.</P>
                <P>
                    19. The Commission declines to adopt commenters' unsupported proposals to permit Cellular incumbents simply to absorb small parcels of Unserved Area into their existing CGSAs, even when bordered on all sides by only one incumbent. The Commission finds these proposals to be inconsistent with Commission precedent. Consistent, however, with the approach the Commission adopts in this 
                    <E T="03">R&amp;O</E>
                     to increase flexibility to make changes to an existing system without Commission filings, the Commission finds it serves the public interest to permit incumbents to extend their SABs (as calculated under 47 CFR 22.911) into adjacent Unserved Area parcels that are less than 50 contiguous square miles and provide service coverage on a secondary basis indefinitely and without any filings with the Commission. The Commission clarifies that this is applicable whether the SAB extension is the result of an added transmitter, modification of a cell site, or both. A licensee extending its SAB into an Unserved Area parcel of less than 50 contiguous square miles must: (1) Pursuant to 47 CFR 22.983 that the Commission adopts in this 
                    <E T="03">R&amp;O,</E>
                     comply with the 40 dBµV/m field strength limit at the boundary of the neighboring co-channel licensee's CGSA or negotiate a different field strength limit; (2) accept interference from other Cellular systems; and (3) avoid causing harmful interference to any neighboring co-channel licensee's CGSA. To the extent that more than one incumbent borders and wishes to serve the same Unserved Area parcel less than 50 contiguous square miles, such incumbents will be required to provide service in that parcel on a shared secondary (unprotected) basis only. The Commission finds that these revisions serve the public interest and further the Commission's goals in this proceeding.
                </P>
                <HD SOURCE="HD2">G. Submission of Maps</HD>
                <P>
                    20. In the 
                    <E T="03">2012 NPRM,</E>
                     the Commission noted that, pursuant to delegated authority and rules adopted in the ULS proceeding to eliminate paper filings, the Bureau had announced optional electronic filing of CGSA map files in lieu of the large-scale (1:500,000 scale) paper CGSA maps required to be submitted with certain Cellular applications. The Commission also reaffirmed the Bureau's delegated authority to determine and announce the effective date of mandatory electronic filing of such maps, with instructions for the public regarding access to such submissions. The Bureau continued its voluntary policy to allow all Cellular licensees, including the smaller carriers, time to explore and 
                    <PRTPAGE P="72147"/>
                    choose appropriate software for their electronic map filings. The 
                    <E T="03">2012 NPRM</E>
                     anticipated mandatory electronic filing and sought comment on proposed rules incorporating this requirement.
                </P>
                <P>
                    21. Nearly all large-scale CGSA maps are now submitted by applicants electronically in ULS. The Commission finds that, in conjunction with the numerous other changes adopted in the 
                    <E T="03">R&amp;O</E>
                     to modernize the Cellular rules, it is appropriate to adopt final rules that require mandatory electronic filing of map files (rather than the large-scale paper CGSA maps) in GIS format with any Cellular applications that require maps. The Commission will continue to accept and preserve large-scale paper maps filed prior to the effective date of the electronic filing requirement that the Commission adopts in this 
                    <E T="03">R&amp;O.</E>
                     Thereafter, the Commission will not accept paper maps with Cellular applications unless it finds that a large-scale paper map is necessary to review and act on a particular application and requests such a submission. Applications that do not comply with the new requirement will either be returned to the applicant or dismissed.
                </P>
                <HD SOURCE="HD2">H. Elimination of Certain Application Content Requirements</HD>
                <P>
                    22. In an effort to streamline and modernize the Cellular Service-specific rules in Subpart H as well as certain Part 1 and other Part 22 rules applicable to Cellular licensing, the Commission proposed in the 
                    <E T="03">2012 NPRM</E>
                     numerous rule deletions and changes to current requirements. The Commission specifically indicated that, in the future, certain information and exhibits currently required pursuant to 47 CFR 22.929 and 22.953(a) would not be routinely required by the Commission's engineering staff in their review of Cellular new-system and modification applications, and therefore proposed streamlining the information requirements in those rules.
                </P>
                <P>23. Based on the record and consistent with the Commission's regulatory reform agenda, the Commission finds that it serves the public interest to adopt revised provisions to minimize the content requirements for Cellular applications. Specifically, the Commission adopts the proposal to delete 47 CFR 22.929 and consolidate application requirements into a single revised and streamlined rule, 47 CFR 22.953, such that applicants for new systems or system modifications will no longer be required routinely to submit the following information in their exhibits: Height of the center of radiation of the antenna above average terrain; antenna gain in the maximum lobe; antenna model; antenna manufacturer name; antenna type; antenna height to tip above ground level; maximum effective radiated power; beam-width of the maximum lobe of the antenna; polar plot of the horizontal gain pattern of the antenna; electrical field polarization of the wave emitted by the antenna when installed as proposed; channel plan; service proposal; Cellular design; blocking level; start-up expenses; and interconnection.</P>
                <P>24. In light of technological advances and maturity of the Cellular Service, the Commission finds that the information and technical exhibits identified above are either no longer routinely necessary for Commission staff in reviewing Cellular applications or can be accessed elsewhere. By eliminating all 16 of these requirements for routine review, the Commission is alleviating to a significant degree the resources that licensees will need to expend on Cellular applications. The Commission concludes that such streamlining and modernization of the current rules serves the public interest.</P>
                <HD SOURCE="HD2">I. Mutually Exclusive Applications in the Cellular Service</HD>
                <HD SOURCE="HD3">1. Initial License for Chambers, Texas Market (CMA672-A)</HD>
                <P>25. Block A of the Chambers, Texas CMA (CMA672-A) (“Chambers”) is the only CMA in the country for which a Cellular initial primary license has never been issued, and AT&amp;T Mobility of Galveston LLC (“AT&amp;T Galveston”) holds an interim operating authorization—not a permanent license—and provides Cellular service to nearly all of the area under Call Sign KNKP971. The Commission proposed that the entire CMA672-A be licensed on a geographic area basis by auction, with specified build-out benchmarks.</P>
                <P>
                    26. In light of the Commission's decision in this 
                    <E T="03">R&amp;O</E>
                     to adopt a geographic-based licensing model for the Cellular Service, the Commission finds it appropriate to adopt the Commission's proposal regarding the Chambers license, with a few clarifications. The current rules provide for the acceptance of mutually exclusive applications for the initial license for Chambers, which would be resolved by competitive bidding pursuant to section 309(j) of the Communications Act of 1934, as amended. Accordingly, the Wireless Telecommunications Bureau (“Bureau”) will accept applications for a CMA-based initial primary license for Chambers, consistent with initial licensing of other CMA Blocks that have been subject to competitive bidding where mutually exclusive applications have been accepted. The Commission finds that it serves the public interest to adopt the proposed geographic coverage build-out requirements, rather than subjecting the new Chambers licensee to the legacy five-year and Unserved Area licensing build-out/application processes. The Chambers licensee will therefore be required to provide signal coverage and offer service over at least 35% of the geographic area of CMA672-A within four years of initial license grant, and to at least 70% of that same area by the end of the license term, as set forth in new 47 CFR 22.960 that the Commission adopts in this 
                    <E T="03">R&amp;O.</E>
                     As proposed, for purposes of this geographic benchmark, the licensee is to count total land, and failure to meet these coverage benchmarks will result in automatic termination of the license and its return to the Commission for re-licensing by auction. Any licensee that so fails to meet these benchmarks will not be eligible to regain the Chambers license. The Commission emphasizes that the holder of the interim operating authorization (currently AT&amp;T Galveston) does not have primary authority to operate and would not be afforded incumbent status entitled to protection from the Chambers licensee.
                </P>
                <P>27. The performance obligations for the Chambers license are consistent with those for geographic area licenses in certain other services similarly issued through competitive bidding. Accordingly, consistent with its regulatory reform agenda and as proposed, the Commission finds that it serves the public interest to eliminate—or, where appropriate, update—the numerous existing provisions pertaining to or referencing the legacy build-out periods for the Cellular Service throughout Parts 1 and 22 of the Commission's rules. The Commission discusses these specific rule changes further below.</P>
                <P>
                    28. Moreover, the Commission concludes that it is appropriate to deem the boundary of CMA672-A as the CGSA boundary of the Chambers licensee. Neighboring co-channel licensees will not be permitted to claim as CGSA any area within CMA672-A, even if not built out by the Chambers licensee by the end of the initial license term. The Chambers licensee will be permitted to claim, as a CGSA expansion, Unserved Area in a neighboring CMA, provided that it has first met all of its build-out requirements in CMA672-A by the end of the initial license term. Any such CGSA expansion area will not, however, remain part of the Chambers license in the event the Chambers license is 
                    <PRTPAGE P="72148"/>
                    automatically terminated by Commission rule or revoked for any reason, in which case the area within CMA672-A will revert to the Commission for re-licensing by auction, while the CGSA expansion area will revert to the Commission for re-licensing pursuant to the Unserved Area licensing rules.
                </P>
                <P>
                    29. With respect to licensee protection requirements, pursuant to the field strength limit rule the Commission adopts in this 
                    <E T="03">R&amp;O,</E>
                     the Commission clarifies that the Chambers licensee will have the flexibility to construct anywhere within CMA672-A subject to Cellular Service technical requirements, but must comply with the 40 dBµV/m field strength limit at the CGSA boundaries of neighboring co-channel licensees, unless a different limit is negotiated. Further, consistent with the new Cellular field strength limit rule and with protection requirements in other geographic-based wireless services, a neighboring co-channel Cellular licensee must comply with the 40 dBµV/m field strength limit at the Chambers licensed area boundary (
                    <E T="03">i.e.,</E>
                     the boundary of CMA672-A), regardless of whether the Chambers licensee is yet operating near the border of CMA672-A, or else negotiate a different limit.
                </P>
                <P>
                    30. The Commission concludes that this approach provides the most efficient and effective means to foster the provision of additional advanced wireless service by a primary licensee to this Texas market and serves the public interest. In the event that mutually exclusive applications are accepted for this license, the Commission concludes that new 47 CFR 22.961, which the Commission adopts in this 
                    <E T="03">R&amp;O</E>
                     consistent with the Commission's proposal in the 
                    <E T="03">2012 NPRM,</E>
                     shall govern. The Commission directs the Bureau to proceed, within a reasonable time following the effective date of the final rules the Commission adopts in this 
                    <E T="03">R&amp;O,</E>
                     to release the appropriate public notice(s) to implement its decision regarding the Chambers license.
                </P>
                <HD SOURCE="HD3">2. Mutually Exclusive CGSA Expansion Applications</HD>
                <P>
                    31. The Commission emphasizes that, with this 
                    <E T="03">R&amp;O,</E>
                     the Commission is not eliminating the existing prohibition on CGSA overlaps. Accordingly, whenever CGSA-expansion or new-system CGSA applications are mutually exclusive with other pending proposed operations, they will continue to be set for resolution by competitive bidding in a closed auction unless the competing applicants are able to resolve the mutual exclusivity beforehand (for example, through settlement) in accordance with the Commission's rules. Consistent with the Commission's proposals in the 
                    <E T="03">2012 NPRM,</E>
                     the Commission adopts new 47 CFR 22.961 not only to govern the Chambers license, but also mutually exclusive Cellular Unserved Area applications, and the Commission consolidates into 47 CFR 22.961 certain other rules to eliminate redundancy and obsolescence in provisions addressing mutually exclusive Cellular Service applications.
                </P>
                <HD SOURCE="HD2">J. Other Amendments; Non-Relocation of Rules</HD>
                <P>
                    32. In this section, the Commission explains various other changes to its rules in Part 22, Subpart H, and provisions found elsewhere in Part 22 as well as in Part 1. The Commission urges all parties to review and become familiar with all final rules the Commission adopts in the 
                    <E T="03">R&amp;O</E>
                     in this proceeding, including the new and revised terms and definitions, all as set forth in Appendix A of this 
                    <E T="03">R&amp;O</E>
                     and which will take effect as specified in the pertinent Ordering Clauses.
                </P>
                <HD SOURCE="HD3">1. Obsolete or Outdated Terminology and Provisions</HD>
                <P>
                    33. As stated above in the context of its decision concerning the Chambers license, obsolete and outdated terms are pervasive in the current rules applicable to the Cellular Service. Consistent with the Commission's proposal in the 
                    <E T="03">2012 NPRM,</E>
                     a number of revised rules are being adopted in this 
                    <E T="03">R&amp;O</E>
                     solely to bring the rules up to date by eliminating legacy terminology and cross-references, and by replacing outdated terms. In addition, the Commission adopts revisions here to conform certain rules in Parts 1 and 22 to the other rule changes the Commission adopts, as described above in this 
                    <E T="03">R&amp;O.</E>
                </P>
                <P>34. Specifically, the Commission is deleting rules and adopting revised rules as follows: 47 CFR 1.929(b) (revised); 47 CFR 22.99 (deleting defined terms “Build-out transmitters,” “Five-year build-out period,” and “Partitioned Cellular market,” revising slightly the definitions for “Cellular Geographic Service Area,” “Extension,” and “Unserved Area,” and adding and defining the term “Cellular Market Area”); 47 CFR 22.131 (revising paragraphs (c)(3)(iii) and (d)(2)(iv)); 47 CFR 22.143 (revising paragraph (a)); 47 CFR 22.909 (revised); 47 CFR 22.911 (deleting paragraph (c) and revising paragraph (e)); 47 CFR 22.912 (revised); 47 CFR 22.946 (revised); 47 CFR 22.947 (deleted); 47 CFR 22.948 (revised); and 47 CFR 22.949 (revised). The Commission also proposed to delete 47 CFR 1.919(c) governing the reporting of Cellular cross-ownership interests, which is obsolete because the reporting requirement has sunset. Accordingly, the Commission deletes 47 CFR 1.919(c) as proposed. The Commission finds that adopting these rule changes serves the public interest and advances the Commission's regulatory reform agenda.</P>
                <HD SOURCE="HD3">2. AMPS-Related Data Collection</HD>
                <P>
                    35. The Commission noted in the 
                    <E T="03">2012 NPRM</E>
                     that, with sunset of the requirement to provide analog Cellular service, all of 47 CFR 22.901(b) had been rendered moot. Stating its belief that all Cellular licensees have had ample time to make their choice and file either the one-time AMPS sunset certification or the appropriate revised CGSA showing, the Commission proposed to terminate its collection of such certifications and to delete 47 CFR 22.901(b). Based on the record, the Commission finds that it serves the public interest to adopt revised 47 CFR 22.901, deleting paragraph (b) of the rule as proposed. As of the effective date of revised 47 CFR 22.901 that the Commission adopts in this 
                    <E T="03">R&amp;O,</E>
                     the Commission will cease collecting AMPS sunset certifications from Cellular licensees.
                </P>
                <HD SOURCE="HD3">3. Correction of Section 1.958(d)</HD>
                <P>
                    36. The Commission proposed in the 
                    <E T="03">2012 NPRM</E>
                     to correct a clerical error in the distance computation formula in 47 CFR 1.958(d)—an error that was introduced in the process of moving the provision containing the formula from Part 22 (then 47 CFR 22.157) to Subpart F of Part 1 of its rules. The error in this distance computation formula was inadvertent, and correction is obviously warranted. Accordingly, the Commission adopts the corrected rule as proposed.
                </P>
                <HD SOURCE="HD3">4. Non-Relocation of Part 22 Cellular and Part 24 PCS Rules to Part 27</HD>
                <P>
                    37. The Commission invited comment in the 
                    <E T="03">2012 NPRM</E>
                     on whether the revised Cellular Service-specific rules should be incorporated into Part 27. The Commission further suggested that, if the revised Cellular Service rules were to be moved into Part 27, then the rules for the Part 24 PCS, should also be moved into Part 27, and sought comment on optimal timing and whether a separate rulemaking should be launched to address any such relocations. The Commission concludes that relocating the Part 22, Subpart H Cellular Service rules is not appropriate. Moreover, the Commission also concludes that it is not appropriate to 
                    <PRTPAGE P="72149"/>
                    further consider relocation of the Part 24 PCS rules in this proceeding.
                </P>
                <HD SOURCE="HD2">K. Gulf of Mexico Service Area</HD>
                <P>
                    38. The Commission proposed in the 
                    <E T="03">2012 NPRM</E>
                     generally to exempt the Gulf from the licensing revisions being considered, except that it proposed to subject Gulf licensees to the same field strength limit as all other Cellular licensees and also to certain rule changes designed to update and streamline the Cellular licensing regime. The Commission has already described, earlier in this 
                    <E T="03">R&amp;O,</E>
                     its decision regarding field strength limit and the related issue of contractually negotiated SAB extensions with respect to the Gulf. The Commission concludes that, to the extent Gulf licensees are subject to Unserved Area licensing procedures under the current rules, consistent with the proposal in the 
                    <E T="03">2012 NPRM,</E>
                     it serves the public interest that Gulf licensees not be exempt from the revised rules and procedures that the Commission adopts in this 
                    <E T="03">R&amp;O</E>
                     to modernize and streamline the Cellular Unserved Area licensing model. This does not disrupt the Gulf regime.
                </P>
                <HD SOURCE="HD2">L. Freeze Order Lifted and Related Interim Procedures Terminated</HD>
                <P>
                    39. To permit the orderly and effective resolution of the changes and issues raised in the 
                    <E T="03">2012 NPRM,</E>
                     and consistent with numerous prior proceedings, the Commission adopted a companion 
                    <E T="03">Order</E>
                     imposing a freeze on the acceptance of certain Cellular applications and imposing other interim procedures. The freeze and related interim procedures were very limited so as to permit continued expansion of service to consumers by incumbents but nonetheless help the Commission identify Unserved Area in substantially licensed CMA Blocks for purposes of conducting the proposed overlay auction. Although the Commission is not concluding this proceeding with this 
                    <E T="03">R&amp;O,</E>
                     the Commission finds that it no longer serves the goals of this proceeding or the public interest to continue the freeze or the interim procedures. Accordingly, the freeze and the interim procedures that were imposed will no longer be in force as of the date specified in the pertinent Ordering Clause.
                </P>
                <HD SOURCE="HD1">III. Procedural Matters</HD>
                <HD SOURCE="HD2">A. Paperwork Reduction Act Analysis</HD>
                <P>
                    40. Three of the rule amendments adopted by this 
                    <E T="03">R&amp;O</E>
                    —47 CFR 22.165(e), 22.948, and 22.953—contain modified information collection requirements subject to the Paperwork Reduction Act of 1995 (“PRA”), Public Law 104-13. Those rule amendments will be submitted to the Office of Management and Budget (“OMB”) for review under section 3507(d) of the PRA. OMB, the general public, and other Federal agencies will be invited to comment on the modified information collection requirements. In addition, the Commission notes that pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4), the Commission previously sought specific comment on how the Commission might further reduce the information collection burden for small business concerns with fewer than 25 employees. The Commission has assessed the effects on small business concerns of the rule changes it is adopting by this 
                    <E T="03">R&amp;O</E>
                     and finds that businesses with fewer than 25 people will benefit from the elimination of certain filing requirements as well as from the streamlining and updating of various requirements applicable to all Cellular licensees.
                </P>
                <HD SOURCE="HD2">B. Congressional Review Act</HD>
                <P>
                    41. The Commission will send a copy of this 
                    <E T="03">R&amp;O</E>
                     to Congress and the Government Accountability Office pursuant to the Congressional Review Act.
                </P>
                <HD SOURCE="HD2">C. Final Regulatory Flexibility Analysis</HD>
                <P>
                    42. The Regulatory Flexibility Act of 1980 (“RFA”) requires that an agency prepare a regulatory flexibility analysis for notice and comment rulemakings, unless the agency certifies that “the rule will not, if promulgated, have a significant economic impact on a substantial number of small entities.” Accordingly, the Commission has prepared a Final Regulatory Flexibility Analysis (“FRFA”), set forth in Appendix C of the 
                    <E T="03">R&amp;O,</E>
                     concerning the possible impact of the rule changes contained in the 
                    <E T="03">R&amp;O.</E>
                </P>
                <HD SOURCE="HD2">D. Ex Parte Presentations</HD>
                <P>
                    43. 
                    <E T="03">Permit-But-Disclose.</E>
                     The Commission will continue to treat this proceeding as a “permit-but-disclose” proceeding in accordance with the Commission's 
                    <E T="03">ex parte</E>
                     rules. Persons making presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral 
                    <E T="03">ex parte</E>
                     presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the 
                    <E T="03">ex parte</E>
                     presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during 
                    <E T="03">ex parte</E>
                     meetings are deemed to be written 
                    <E T="03">ex parte</E>
                     presentations and must be filed consistent with rule 1.1206(b). In proceedings governed by rule 1.49(f) or for which the Commission has made available a method of electronic filing, written 
                    <E T="03">ex parte</E>
                     presentations and memoranda summarizing oral 
                    <E T="03">ex parte</E>
                     presentations, and all attachments thereto, must be filed through the Commission's Electronic Comment Filing System (“ECFS”) available for that proceeding, and must be filed in their native format (
                    <E T="03">e.g.,</E>
                     .doc, .xml, .ppt, searchable .pdf).
                </P>
                <P>
                    44. 
                    <E T="03">People with Disabilities.</E>
                     To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty).
                </P>
                <HD SOURCE="HD1">IV. Ordering Clauses</HD>
                <P>
                    45. Accordingly, 
                    <E T="03">it is ordered,</E>
                     pursuant to Sections 1, 2, 4(i), 4(j), 7, 301, 302, 303, 307, 308, 309, and 332 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 154(j), 157, 301, 302, 303, 307, 308, 309, and 332, that this 
                    <E T="03">report and order</E>
                     in WT Docket No. 12-40 
                    <E T="03">is adopted.</E>
                </P>
                <P>
                    46. 
                    <E T="03">It is further ordered</E>
                     that Parts 1 and 22 of the Commission's rules, 47 CFR parts 1 and 22, 
                    <E T="03">are amended,</E>
                     as specified in Appendix A, effective 30 days after publication in the 
                    <E T="04">Federal Register</E>
                     except as otherwise provided herein. It is the Commission's intention in adopting these rule changes that if any provision of the rules, or the application thereof to any person or circumstance, is held to be unlawful, the remaining portions of the rules not deemed unlawful, and the application of such rules to other persons or circumstances, shall remain in effect to the fullest extent permitted by law.
                </P>
                <P>
                    47. 
                    <E T="03">It is further ordered</E>
                     that the amendments adopted in the 
                    <E T="03">
                        report and 
                        <PRTPAGE P="72150"/>
                        order,
                    </E>
                     and specified in Appendix A, to Sections 22.165(e), 22.948, and 22.953 of the Commission's rules, 47 CFR 22.165(e), 22.948, and 22.953, which contain modified information collection requirements that require approval by the Office of Management and Budget under the Paperwork Reduction Act, 
                    <E T="03">will become effective</E>
                     after the Commission publishes a notice in the 
                    <E T="04">Federal Register</E>
                     announcing such approval and the relevant effective date.
                </P>
                <P>
                    48. 
                    <E T="03">It is futher ordered</E>
                     that, effective 30 days after publication in the 
                    <E T="04">Federal Register</E>
                     of a summary of this 
                    <E T="03">report and order,</E>
                     the freeze and interim procedures that were imposed as of the adoption date of the 2012 Notice of Proposed Rulemaking and Order in this WT Docket No. 12-40 
                    <E T="03">will no longer be in effect.</E>
                </P>
                <P>
                    49. 
                    <E T="03">It is further ordered</E>
                     that, pursuant to Section 801(a)(1)(A) of the Congressional Review Act, 5 U.S.C. 801(a)(1)(A), the Commission 
                    <E T="03">shall send</E>
                     a copy of this 
                    <E T="03">report and order</E>
                     to Congress and to the Government Accountability Office.
                </P>
                <P>
                    50. 
                    <E T="03">It is further ordered</E>
                     that the Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, 
                    <E T="03">shall send</E>
                     a copy of this 
                    <E T="03">report and order,</E>
                     including the Final Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>47 CFR Part 1</CFR>
                    <P>Telecommunications, Reporting and recordkeeping requirements.</P>
                    <CFR>47 CFR Part 22</CFR>
                    <P>Communications common carriers, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene H. Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Final Rules</HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR parts 1 and 22 as follows:</P>
                <REGTEXT TITLE="47" PART="1">
                    <PART>
                        <HD SOURCE="HED">PART 1—PRACTICE AND PROCEDURE</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 1 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             15 U.S.C. 79 
                            <E T="03">et seq.;</E>
                             47 U.S.C. 151, 154(i), 154(j), 155, 157, 225, 227, 303(r), 309, 1403, 1404, 1451, and 1452.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="1">
                    <AMDPAR>2. Section 1.919 is amended by removing and reserving paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.919 </SECTNO>
                        <SUBJECT>Ownership information.</SUBJECT>
                        <STARS/>
                        <P>(c) [Reserved]</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="1">
                    <AMDPAR>3. Section 1.929 is amended by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.929 </SECTNO>
                        <SUBJECT>Classification of filings as major or minor.</SUBJECT>
                        <STARS/>
                        <P>(b) In addition to those changes listed in paragraph (a) of this section, the following are major changes in the Cellular Radiotelephone Service:</P>
                        <P>(1) Application requesting authorization to expand the Cellular Geographic Service Area (CGSA) of an existing Cellular system or, in the case of an amendment, as previously proposed in an application to expand the CGSA; or</P>
                        <P>(2) Application or amendment requesting that a CGSA boundary or portion of a CGSA boundary be determined using an alternative method.</P>
                        <P>(3) [Reserved]</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="1">
                    <AMDPAR>4. Section 1.958 is amended by revising paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.958 </SECTNO>
                        <SUBJECT>Distance computation.</SUBJECT>
                        <STARS/>
                        <P>(d) Calculate the number of kilometers per degree of longitude difference for the mean geodetic latitude calculated in paragraph (b) of this section as follows:</P>
                        <FP SOURCE="FP-2">
                            KPD
                            <E T="52">lon</E>
                             = 111.41513 cos ML − 0.09455 cos 3ML + 0.00012 cos 5ML
                        </FP>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <PART>
                        <HD SOURCE="HED">PART 22—PUBLIC MOBILE SERVICES</HD>
                    </PART>
                    <AMDPAR>5. The authority citation for part 22 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 222, 303, 309 and 332.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>6. Section 22.99 is amended by:</AMDPAR>
                    <AMDPAR>a. Removing the definitions of “Build-out transmitters,” “Five year build-out period,” “Partitioned Cellular market”, and “Unserved Areas”.</AMDPAR>
                    <AMDPAR>b. Revising the definitions of “Cellular Geographic Service Area,” “Cellular markets” and “Extension”.</AMDPAR>
                    <AMDPAR>c. Adding the new definitions, “Cellular Market Area” and “Unserved Area”.</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 22.99</SECTNO>
                        <SUBJECT> Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Cellular Geographic Service Area (CGSA).</E>
                             The licensed geographic area within which a Cellular system is entitled to protection and adverse effects are recognized, for the purpose of determining whether a petitioner has standing, in the Cellular Radiotelephone Service, and within which the Cellular licensee is permitted to transmit, or consent to allow other Cellular licensees to transmit, electromagnetic energy and signals on the assigned channel block, in order to provide Cellular service. 
                            <E T="03">See</E>
                             § 22.911.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Cellular Market Area (CMA).</E>
                             A standard geographic area used by the FCC for administrative convenience in the licensing of Cellular systems; a more recent term for “Cellular market” (and includes Metropolitan Statistical Areas (MSAs) and Rural Service Areas (RSAs)). 
                            <E T="03">See</E>
                             § 22.909.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Cellular markets.</E>
                             This term is obsolescent. 
                            <E T="03">See</E>
                             definition for “Cellular Market Area (CMA).”
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Extension.</E>
                             In the Cellular Radiotelephone Service, an area within the service area boundary (calculated using the methodology of § 22.911) of a Cellular system but outside the licensed Cellular Geographic Service Area boundary. 
                            <E T="03">See</E>
                             §§ 22.911 and 22.912.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Unserved Area.</E>
                             With regard to a channel block allocated for assignment in the Cellular Radiotelephone Service: Geographic area in the District of Columbia, or any State, Territory or Possession of the United States of America that is not within any Cellular Geographic Service Area of any Cellular system authorized to transmit on that channel block. With regard to a channel allocated for assignment in the Paging and Radiotelephone service: Geographic area within the District of Columbia, or any State, Territory or possession of the United States of America that is not within the service contour of any base transmitter in any station authorized to transmit on that channel.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>7. Section 22.131 is amended by revising paragraphs (c)(3)(iii) and (d)(2)(iv) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.131 </SECTNO>
                        <SUBJECT>Procedures for mutually exclusive applications.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(3) * * *</P>
                        <P>(iii) If all of the mutually exclusive applications filed on the earliest filing date are applications for initial authorization, a 30-day notice and cut-off filing group is used.</P>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>
                            (2) * * *
                            <PRTPAGE P="72151"/>
                        </P>
                        <P>
                            (iv) Any application to expand the Cellular Geographic Service Area of an existing Cellular system. 
                            <E T="03">See</E>
                             § 22.911.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>8. Section 22.143 is amended by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.143 </SECTNO>
                        <SUBJECT>Construction prior to grant of application.</SUBJECT>
                        <STARS/>
                        <P>
                            (a) 
                            <E T="03">When applicants may begin construction.</E>
                             An applicant may begin construction of a facility 35 days after the date of the Public Notice listing the application for that facility as acceptable for filing.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>9. Section 22.165 is amended by revising paragraph (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.165</SECTNO>
                        <SUBJECT> Additional transmitters for existing systems.</SUBJECT>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Cellular Radiotelephone Service.</E>
                             The service area boundaries (SABs) of the additional transmitters, as calculated by the method set forth in § 22.911(a), must not cause an expansion of the Cellular Geographic Service Area (CGSA), and must not extend outside the CGSA boundary into Unserved Area unless such extension is less than 130 contiguous square kilometers (50 contiguous square miles). The licensee must seek prior approval (using FCC Form 601) regarding any transmitters to be added under this section that would cause an expansion of the CGSA, or an SAB extension of 130 contiguous square kilometers (50 contiguous square miles) or more, into Unserved Area. 
                            <E T="03">See</E>
                             §§ 22.912, 22.953.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <SECTION>
                        <SECTNO>§ 22.228 </SECTNO>
                        <SUBJECT>[Removed]</SUBJECT>
                    </SECTION>
                    <AMDPAR>10. Remove § 22.228.</AMDPAR>
                    <AMDPAR>11. Revise § 22.901 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.901</SECTNO>
                        <SUBJECT> Cellular service requirements and limitations.</SUBJECT>
                        <P>The licensee of each Cellular system is responsible for ensuring that its Cellular system operates in compliance with this section. Each Cellular system must provide either mobile service, fixed service, or a combination of mobile and fixed service, subject to the requirements, limitations and exceptions in this section. Mobile service provided may be of any type, including two-way radiotelephone, dispatch, one-way or two-way paging, and personal communications services (as defined in part 24 of this chapter). Fixed service is considered to be primary service, as is mobile service. When both mobile and fixed services are provided, they are considered to be co-primary services. In providing Cellular service, each Cellular system may incorporate any technology that meets all applicable technical requirements in this part.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>12. Section 22.909 is amended by revising the introductory text to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.909 </SECTNO>
                        <SUBJECT>Cellular Market Areas (CMAs).</SUBJECT>
                        <P>
                            Cellular Market Areas (CMAs) are standard geographic areas used by the FCC for administrative convenience in the licensing of Cellular systems. CMAs comprise Metropolitan Statistical Areas (MSAs) and Rural Service Areas (RSAs). All CMAs and the counties they comprise are listed in: “Common Carrier Public Mobile Services Information, Cellular MSA/RSA Markets and Counties,” 
                            <E T="03">Public Notice,</E>
                             Rep. No. CL-92-40, 7 FCC Rcd 742 (1992).
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>13. Section 22.911 is amended by revising the introductory text of paragraph (a), by removing and reserving paragraph (c), and by revising paragraphs (d) and (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.911 </SECTNO>
                        <SUBJECT>Cellular geographic service area.</SUBJECT>
                        <STARS/>
                        <P>
                            (a) 
                            <E T="03">CGSA determination.</E>
                             The CGSA is the composite of the service areas of all of the cells in the system, excluding any Unserved Area (even if it is served on a secondary basis) or area within the CGSA of another Cellular system. The service area of a cell is the area within its service area boundary (SAB). The distance to the SAB is calculated as a function of effective radiated power (ERP) and antenna center of radiation height above average terrain (HAAT), height above sea level (HASL), or height above mean sea level (HAMSL).
                        </P>
                        <STARS/>
                        <P>(c) [Reserved]</P>
                        <P>
                            (d) 
                            <E T="03">Protection afforded.</E>
                             Cellular systems are entitled to protection only within the CGSA (as determined in accordance with this section) from co-channel and first-adjacent channel interference and from capture of subscriber traffic by adjacent systems on the same channel block. Licensees must cooperate in resolving co-channel and first-adjacent channel interference by changing channels used at specific cells or by other technical means.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Unserved Area.</E>
                             Unserved Area is area outside of all existing CGSAs on either of the channel blocks, to which the Communications Act of 1934, as amended, is applicable.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>14. Revise § 22.912 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.912 </SECTNO>
                        <SUBJECT>Service area boundary extensions.</SUBJECT>
                        <P>This section contains rules governing service area boundary (SAB) extensions. SAB extensions are areas (calculated using the methodology of § 22.911) that extend outside of the licensee's Cellular Geographic Service Area (CGSA) boundary into Unserved Area or into the CGSA of a neighboring co-channel licensee. Service within SAB extensions is not protected from interference or capture under § 22.911(d) unless and until the area within the SAB extension becomes part of the CGSA in compliance with all applicable rules.</P>
                        <P>
                            (a) 
                            <E T="03">Extensions into Unserved Area.</E>
                             Subject to paragraph (c) of this section, the licensee of a Cellular system may, at any time, extend its SAB into Unserved Area and provide service on a secondary basis only, provided that the extension area comprises less than 130 contiguous square kilometers (50 contiguous square miles). If more than one licensee of a Cellular system extends into all or a portion of the same Unserved Area under this section, all such licensees may provide service in such Unserved Area on a shared secondary (unprotected) basis only.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Contract extensions.</E>
                             The licensee of any Cellular system may, at any time, enter into a contract with an applicant for, or a licensee of, a Cellular system on the same channel block to allow one or more SAB extensions into its CGSA (not into Unserved Area).
                        </P>
                        <P>
                            (c) 
                            <E T="03">Gulf of Mexico Service Area.</E>
                             Land-based Cellular system licensees may not extend their SABs into the Gulf of Mexico Exclusive Zone (GMEZ) absent written contractual consent of the co-channel GMEZ licensee. GMEZ licensees may not extend their SABs into the CGSA of a licensee on the same channel block in an adjacent CMA or the Gulf of Mexico Coastal Zone absent written contractual consent of the co-channel licensee.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <SECTION>
                        <SECTNO>§ 22.929</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>15. Remove and reserve § 22.929.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>16. Revise § 22.946 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.946</SECTNO>
                        <SUBJECT> Construction period for Unserved Area authorizations.</SUBJECT>
                        <P>
                            The construction period applicable to new or modified Cellular facilities for which an authorization is granted pursuant to the Unserved Area process is one year, beginning on the date the authorization is granted. To satisfy this requirement, a Cellular system must be providing service to mobile stations operated by subscribers and roamers. The licensee must notify the FCC (FCC Form 601) after the requirements of this section are met. 
                            <E T="03">See</E>
                             § 1.946 of this chapter. 
                            <E T="03">See also</E>
                             § 22.949.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <SECTION>
                        <SECTNO>§ 22.947 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>17. Remove and reserve § 22.947.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <PRTPAGE P="72152"/>
                    <AMDPAR>18. Revise § 22.948 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.948</SECTNO>
                        <SUBJECT> Geographic partitioning and spectrum disaggregation; spectrum leasing.</SUBJECT>
                        <P>Cellular licensees may apply to partition any portion of their licensed Cellular Geographic Service Area (CGSA) or to disaggregate their licensed spectrum at any time following the grant of their authorization(s). Parties seeking approval for partitioning and disaggregation shall request from the FCC an authorization for partial assignment of a license pursuant to § 1.948 of this chapter. See also paragraph (d) of this section regarding spectrum leasing.</P>
                        <P>
                            (a) 
                            <E T="03">Partitioning, disaggregation, or combined partitioning and disaggregation.</E>
                             Applicants must file FCC Form 603 (“Assignment of Authorization and Transfer of Control”) pursuant to § 1.948 of this chapter, as well as GIS map files and a reduced-size PDF map pursuant to § 22.953 for both the assignor and assignee.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Field strength limit.</E>
                             For purposes of partitioning and disaggregation, Cellular systems must be designed so as to comply with § 22.983.
                        </P>
                        <P>
                            (c) 
                            <E T="03">License term.</E>
                             The license term for a partitioned license area and for disaggregated spectrum will be the remainder of the original license term.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Spectrum leasing.</E>
                             Cellular spectrum leasing is subject to all applicable provisions of subpart X of part 1 of this chapter as well as the provisions of paragraph (a) of this section, except that applicants must file FCC Form 608 (“Application or Notification for Spectrum Leasing Arrangement or Private Commons Arrangement”), not FCC Form 603.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>19. Revise § 22.949 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.949</SECTNO>
                        <SUBJECT> Unserved Area licensing; minimum coverage requirements.</SUBJECT>
                        <P>(a) The Unserved Area licensing process described in this section is on-going and applications may be filed at any time, subject to the following coverage requirements:</P>
                        <P>(1) Applicants for authority to operate a new Cellular system or expand an existing Cellular Geographic Service Area (CGSA) in Unserved Area must propose a CGSA or CGSA expansion of at least 130 contiguous square kilometers (50 contiguous square miles) using the methodology of § 22.911.</P>
                        <P>(2) Applicants for authority to operate a new Cellular system must not propose coverage of water areas only (or water areas and uninhabited islands or reefs only), except for Unserved Area in the Gulf of Mexico Service Area.</P>
                        <P>(b) There is no limit to the number of Unserved Area applications that may be granted on each channel block of each CMA that is subject to the procedures of this section. Consequently, Unserved Area applications are mutually exclusive only if the proposed CGSAs would overlap. Mutually exclusive applications are processed using the general procedures under § 22.131.</P>
                        <P>(c) Unserved Area applications under this section may propose a CGSA covering more than one CMA. Each Unserved Area application must request authorization for only one CGSA and must not propose a CGSA overlap with an existing CGSA.</P>
                        <P>(d) Settlements among some, but not all, applicants with mutually exclusive applications for Unserved Area (partial settlements) under this section are prohibited. Settlements among all applicants with mutually exclusive applications under this section (full settlements) are allowed and must be filed no later than the date that the FCC Form 175 (short-form) is filed.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>20. Section 22.950 is amended by revising paragraphs (c) and (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.950</SECTNO>
                        <SUBJECT> Provision of service in the Gulf of Mexico Service Area (GMSA).</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Gulf of Mexico Exclusive Zone (GMEZ).</E>
                             GMEZ licensees have an exclusive right to provide Cellular service in the GMEZ, and may add, modify, or remove facilities anywhere within the GMEZ without prior FCC approval. There is no Unserved Area licensing procedure for the GMEZ.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Gulf of Mexico Coastal Zone (GMCZ).</E>
                             The GMCZ is subject to the Unserved Area licensing procedures set forth in § 22.949.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <SECTION>
                        <SECTNO>§ 22.951 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>21. Remove and reserve § 22.951.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>22. Section 22.953 is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.953</SECTNO>
                        <SUBJECT> Content and form of applications for Cellular Unserved Area authorizations.</SUBJECT>
                        <P>Applications for authority to operate a new Cellular system or to modify an existing Cellular system must comply with the specifications in this section.</P>
                        <P>
                            (a) 
                            <E T="03">New Systems.</E>
                             In addition to information required by subpart B of this part and by FCC Form 601, applications for an Unserved Area authorization to operate a Cellular system must comply with all applicable requirements set forth in part 1 of this chapter, including the requirements specified in §§ 1.913, 1.923, and 1.924, and must include the information listed below. Geographical coordinates must be correct to ±1 second using the NAD 83 datum.
                        </P>
                        <P>
                            (1) 
                            <E T="03">Exhibit I—Geographic Information System (GIS) map files.</E>
                             Geographic Information System (GIS) map files must be submitted showing the entire proposed CGSA, the new cell sites (transmitting antenna locations), and the service area boundaries of additional and modified cell sites that extend into Unserved Area being claimed as CGSA. 
                            <E T="03">See</E>
                             § 22.911. The FCC will specify the file format required for the GIS map files, which are to be submitted electronically via the Universal Licensing System (ULS).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Exhibit II—Reduced-size PDF map.</E>
                             This map must be 8
                            <FR>1/2</FR>
                             x 11 inches (if possible, a proportional reduction of a 1:500,000 scale map). The map must have a legend, a distance scale, and correctly labeled latitude and longitude lines. The map must be clear and legible. The map must accurately show the entire proposed CGSA, the new cell sites (transmitting antenna locations), the service area boundaries of additional and modified cell sites that extend beyond the CGSA, and the relevant portions of the CMA boundary. 
                            <E T="03">See</E>
                             § 22.911.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Exhibit III—Technical Information.</E>
                             In addition, upon request by an applicant, licensee, or the FCC, a Cellular applicant or licensee of whom the request is made shall furnish the antenna type, model, the name of the antenna manufacturer, antenna gain in the maximum lobe, the beam width of the maximum lobe of the antenna, a polar plot of the horizontal gain pattern of the antenna, antenna height to tip above ground level, the height of the center of radiation of the antenna above the average terrain, the maximum effective radiated power, and the electric field polarization of the wave emitted by the antenna when installed as proposed to the requesting party within ten (10) days of receiving written notification.
                        </P>
                        <P>(4)-(10) [Reserved]</P>
                        <P>
                            (11) 
                            <E T="03">Additional information.</E>
                             The FCC may request information not specified in FCC Form 601 or in paragraphs (a)(1) through (a)(3) of this section as necessary to process an application.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Existing systems—major modifications.</E>
                             Licensees making major modifications pursuant to § 1.929(a) and (b) of this chapter must file FCC Form 601 and comply with the requirements of paragraph (a) of this section.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Existing systems—minor modifications.</E>
                             Licensees making minor modifications pursuant to § 1.929(k) of this chapter, must file FCC Form 601 or FCC Form 603. 
                            <E T="03">See also</E>
                             § 22.169. If the modification involves a contract SAB extension into or from the Gulf of Mexico Exclusive Zone, it must include 
                            <PRTPAGE P="72153"/>
                            a certification that the required written consent has been obtained. 
                            <E T="03">See</E>
                             § 22.912(c).
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>23. Revise § 22.960 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.960</SECTNO>
                        <SUBJECT> Cellular operations in the Chambers, TX CMA (CMA672-A).</SUBJECT>
                        <P>This section applies only to Cellular systems operating on channel block A of the Chambers, Texas CMA (CMA672-A).</P>
                        <P>(a) The geographic boundary of CMA672-A is deemed to be the Cellular Geographic Service Area (CGSA) boundary. This CGSA boundary is not determined using the methodology of § 22.911. The licensee of CMA672-A may not propose an expansion of this CGSA into another CMA unless and until it meets the construction requirement set forth in paragraph (b)(2) of this section.</P>
                        <P>(b) A licensee that holds the license for CMA672-A must be providing signal coverage and offering service as follows (and in applying these geographic construction benchmarks, the licensee is to count total land area):</P>
                        <P>(1) To at least 35% of the geographic area of CMA672-A within four years of the grant of such authorization; and</P>
                        <P>(2) To at least 70% of the geographic area of its license authorization by the end of the license term.</P>
                        <P>
                            (c) After it has met each of the requirements of paragraphs (b)(1) and (b)(2), respectively, of this section, the licensee that holds the license for CMA672-A must notify the FCC that it has met the requirement by submitting FCC Form 601, including GIS map files and other supporting documents showing compliance with the requirement. 
                            <E T="03">See</E>
                             § 1.946 of this chapter. 
                            <E T="03">See also</E>
                             § 22.953.
                        </P>
                        <P>(d) Failure to meet the construction requirements set forth in paragraphs (b)(1) and (b)(2) of this section by each of the applicable deadlines will result in automatic termination of the license for CMA672-A and its return to the Commission for future re-licensing subject to competitive bidding procedures. The licensee that fails to meet each requirement of this section by the applicable deadline set forth in paragraphs (b)(1) and (b)(2) shall be ineligible to regain the license for CMA672-A.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>24. Add § 22.961 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.961 </SECTNO>
                        <SUBJECT>Cellular licenses subject to competitive bidding.</SUBJECT>
                        <P>(a) The following applications for Cellular licensed area authorizations are subject to competitive bidding:</P>
                        <P>(1) Mutually exclusive applications for Unserved Area filed after July 26, 1993; and</P>
                        <P>(2) Mutually exclusive applications for the initial authorization for CMA672-A (Chambers, TX).</P>
                        <P>(b) The competitive bidding procedures set forth in § 22.229 and the general competitive bidding procedures set forth in subpart Q of part 1 of this chapter will apply.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <SECTION>
                        <SECTNO>§ 22.969 </SECTNO>
                        <SUBJECT>[Removed]</SUBJECT>
                    </SECTION>
                    <AMDPAR>25. Remove § 22.969.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="22">
                    <AMDPAR>26. Add § 22.983 to subpart H to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 22.983</SECTNO>
                        <SUBJECT> Field strength limit.</SUBJECT>
                        <P>(a) Subject to paragraphs (b) and (c) of this section, a licensee's predicted or measured median field strength limit must not exceed 40 dBµV/m at any given point along the Cellular Geographic Service Area (CGSA) boundary of a neighboring licensee on the same channel block, unless the affected licensee of the neighboring CGSA on the same channel block agrees to a different field strength. This also applies to CGSAs partitioned pursuant to § 22.948.</P>
                        <P>
                            (b) 
                            <E T="03">Gulf of Mexico Service Area.</E>
                             Notwithstanding the field strength limit provision set forth in paragraph (a) of this section, licensees in or adjacent to the Gulf of Mexico Exclusive Zone are subject to § 22.912(c) regarding service area boundary extensions. 
                            <E T="03">See</E>
                             § 22.912(c).
                        </P>
                        <P>(c) Cellular licensees shall be subject to all applicable provisions and requirements of treaties and other international agreements between the United States government and the governments of Canada and Mexico, notwithstanding paragraphs (a) and (b) of this section.</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28151 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 73</CFR>
                <DEPDOC>[MB Docket No. 14-46, RM-11717, DA 14-1334]</DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Rough Rock, Arizona</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>At the request of The Navajo Nation, the Audio Division amends the FM Table of Allotments, by allotting FM Channel 258C2 at Rough Rock, Arizona, as a first local Tribal Allotment and a first local service to the community. A staff engineering analysis confirms that Channel 258C2 can be allotted to Rough Rock consistent with the minimum distance separation requirements of the Commission's Rules with the imposition of a site restriction 7.1 km (4.4 miles) southeast of the community. The reference coordinates are 36-21-08 NL and 109-49-54 WL.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective December 5, 2014, and applicable October 31, 2014.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rolanda F. Smith, Media Bureau, (202) 418-2700.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's 
                    <E T="03">Report and Order,</E>
                     MB Docket No. 14-46, adopted September 15, 2014, and released September 16, 2014. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center at Portals II, CY-A257, 445 12th Street SW., Washington, DC 20554. This document may also be purchased from the Commission's duplicating contractors, Best Copy and Printing, Inc., 445 12th Street SW., Room CY-B402, Washington, DC 20554, telephone 1-800-378-3160 or via email 
                    <E T="03">www.BCPIWEB.com.</E>
                     This document does not contain information collection requirements subject to the Paperwork Reduction Act of 1995, Public Law 104-13. The Commission will send a copy of the 
                    <E T="03">Report and Order</E>
                     in a report to be sent to Congress and the Government Accountability Office pursuant to the Congressional Review Act, 
                    <E T="03">see</E>
                     5 U.S.C. 801(a)(1)(A).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
                    <P>Radio, Radio broadcasting.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Nazifa Sawez,</NAME>
                    <TITLE>Assistant Chief, Audio Division, Media Bureau.</TITLE>
                </SIG>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 73 as follows:</P>
                <REGTEXT TITLE="47" PART="73">
                    <PART>
                        <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 73 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>47 U.S.C. 154, 303, 334, 336 and 339.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 73.202 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under Arizona, is amended by adding Rough Rock, Channel 258C2.</AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28589 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="72154"/>
                <AGENCY TYPE="F">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 117</CFR>
                <DEPDOC>[Docket No. USCG-2014-0365]</DEPDOC>
                <RIN>RIN 1625-AA09</RIN>
                <SUBJECT>Drawbridge Operation Regulation: Illinois Waterway, Joliet, IL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                         The Coast Guard announces a public meeting to receive comments on a notice of proposed rulemaking (NPRM) entitled “Drawbridge Operation Regulation; Illinois Waterway, Joliet, IL” that was published in the 
                        <E T="04">Federal Register</E>
                         on August 27, 2014. As stated in the NPRM, the Coast Guard proposes to modify the operating regulations for six drawbridges, located between river mile 285.8 and river mile 288.7, across the Illinois Waterway, at Joliet, Illinois. The NPRM proposes to consolidate the current operating regulation, which includes five on-site bridge tender control stations, into one centralized control point for all five drawbridges. The NPRM also proposes to add a sixth drawbridge that will also operate under the centralized control point. The proposed action is intended to improve navigational safety and operational efficiency in the Joliet area.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>A public meeting will be held on Tuesday, December 16, 2014, from 3 p.m. until 6 p.m. We are also re-opening the comment period for this proposed rule. Comments and related material submitted after the meeting must be received by the Coast Guard on or before December 26, 2014.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public meeting will be held at City of Joliet, City Hall, 150 West Jefferson Street, Planning Conference Room, Joliet, IL 60432.</P>
                    <P>You may submit written comments identified by docket number USCG-2014-0365 before or after the meeting using any one of the following methods:</P>
                    <P>
                        (1) 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail:</E>
                         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-0001.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Hand delivery:</E>
                         Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329.
                    </P>
                    <P>
                        To avoid duplication, please use only one of these four methods. Our online docket for this rulemaking is available on the Internet at 
                        <E T="03">http://www.regulations.gov</E>
                         under docket number USCG-2014-0365.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions concerning the meeting or the proposed rule, please call or email Mr. Eric Washburn, Bridge Administrator, Western Rivers, (314) 269-2378, email 
                        <E T="03">eric.washburn@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Cheryl Collins, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <P>
                    We published a NPRM in the 
                    <E T="04">Federal Register</E>
                     on August 27, 2014 (79 FR 51132), entitled “Drawbridge Operation Regulation; Illinois Waterway, Joliet, IL.” We did not plan to hold a public meeting, but we received several valid requests for one and have concluded that a public meeting would aid this proposed rulemaking.
                </P>
                <P>In the NPRM, we proposed to modify the operating regulations for six drawbridges in the Joliet Harbor, based on an Illinois Department of Transportation request.</P>
                <P>
                    You may view the NPRM in our online docket and comments submitted thus far by going to 
                    <E T="03">http://www.regulations.gov.</E>
                     Once there, insert “USCG-2014-0365” in the “Keyword” box and click “Search.” You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. We have an agreement with the Department of Transportation to use the Docket Management Facility.
                </P>
                <P>
                    We encourage you to participate in this rulemaking by submitting comments either orally at the meeting or in writing before or at the meeting. If you bring written comments to the meeting, you may submit them to Coast Guard personnel specified at the meeting to receive written comments. These comments will be posted to the public docket for this proposed rulemaking. All comments received will be posted without change to 
                    <E T="03">http://www.regulations.gov</E>
                     and will include any personal information you have provided.
                </P>
                <P>
                    Comments submitted after the meeting must reach the Coast Guard on or before December 26, 2014. If you submit a comment online via 
                    <E T="03">http://www.regulations.gov,</E>
                     it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility.
                </P>
                <P>
                    Anyone can search the electronic form of comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD1">Information on Service for Individuals With Disabilities</HD>
                <P>
                    For information on facilities or services for individuals with disabilities or to request special assistance at the public meeting, contact Mr. Eric Washburn at the telephone number or email address indicated under the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document.
                </P>
                <HD SOURCE="HD1">Public Meeting</HD>
                <P>
                    The Coast Guard will hold a public meeting regarding its Drawbridge Operation Regulation; Illinois Waterway, Joliet, IL proposed rule on Tuesday, December 16, 2014, from 3 p.m. until 6 p.m. at City of Joliet, City Hall, 150 West Jefferson Street, Planning Conference Room, Joliet, IL 60432. We plan to record this meeting using an 
                    <PRTPAGE P="72155"/>
                    audio-digital recorder and then make that audio recording available through a link in our online docket. We will also provide a written summary of the meeting and comments and will place that summary in the docket.
                </P>
                <SIG>
                    <DATED>Dated: November 25, 2014.</DATED>
                    <NAME>Kevin S. Cook,</NAME>
                    <TITLE>Rear Admiral, Commander, U.S. Coast Guard, Eighth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28608 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2014-0718]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone: Gallant Channel, Beaufort, NC</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard proposes to establish a temporary safety zone on the waters of the Gallant Channel at Beaufort, North Carolina. The safety zone is necessary to provide for the safety of mariners on navigable waters during construction of the new U.S. 70 Fixed Bridge crossing the Gallant Channel, mile 203.8, at Beaufort, North Carolina. The safety zone will temporarily restrict vessel movement within the designated area.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and related material must be received by the Coast Guard on or before January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by docket number using any one of the following methods:</P>
                    <P>
                        (1) 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail or Delivery:</E>
                         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-0001. Deliveries accepted between 9 a.m. and 5 p.m., Monday through Friday, except federal holidays. The telephone number is 202-366-9329.
                    </P>
                    <P>
                        See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below for further instructions on submitting comments. To avoid duplication, please use only one of these three methods. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         If you have questions on this rulemaking, call or email LT Derek J. Burrill, U.S. Coast Guard Sector North Carolina; telephone 910-772-2230, email 
                        <E T="03">Derek.J.Burrill@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Cheryl Collins, Program Manager, Docket Operations, telephone (202) 366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Acronyms</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of Proposed Rulemaking</FP>
                </EXTRACT>
                <HD SOURCE="HD1">A. Public Participation and Request for Comments</HD>
                <P>
                    We encourage you to participate in this rulemaking by submitting comments and related materials. All comments received will be posted without change to 
                    <E T="03">http://www.regulations.gov</E>
                     and will include any personal information you have provided.
                </P>
                <HD SOURCE="HD2">1. Submitting Comments</HD>
                <P>
                    If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online at 
                    <E T="03">http://www.regulations.gov,</E>
                     or by fax, mail, or hand delivery, but please use only one of these means. If you submit a comment online, it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility. We recommend that you include your name and a mailing address, an email address, or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                </P>
                <P>
                    To submit your comment online, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     type the docket number [USCG-2014-0718] in the “SEARCH” box and click “SEARCH.” Click on “Submit a Comment” on the line associated with this rulemaking.
                </P>
                <P>
                    If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
                    <FR>1/2</FR>
                     by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope. We will consider all comments and material received during the comment period and may change the rule based on your comments.
                </P>
                <HD SOURCE="HD2">2. Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as documents mentioned in this preamble as being available in the docket, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     type the docket number (USCG-2014-0718) in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                </P>
                <HD SOURCE="HD2">3. Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD2">4. Public Meeting</HD>
                <P>
                    We do not now plan to hold a public meeting. But you may submit a request for one, using one of the methods specified under 
                    <E T="02">ADDRESSES</E>
                    . Please explain why you believe a public meeting would be beneficial. If we determine that one would aid this rulemaking, we will hold one at a time and place announced by a later notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">B. Basis and Purpose</HD>
                <P>The legal basis for this rule is found in 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; and Department of Homeland Security Delegation No. 0170.1, which collectively authorize the Coast Guard to propose, establish, and define regulatory safety zones.</P>
                <P>This safety zone is necessary to ensure public and maritime safety from the potential hazards associated with bridge construction work.</P>
                <HD SOURCE="HD1">C. Discussion of Proposed Rule</HD>
                <P>
                    North Carolina Department of Transportation has awarded a contract to Conti Enterprises, Inc of Edison, New Jersey and Orion Marine Construction, 
                    <PRTPAGE P="72156"/>
                    Inc. (OMCI) of Houston, Texas to perform construction work that will take place at the Gallant's Channel and surrounding area of that Waterway, mile 203.8, Beaufort, North Carolina. The contract involves pile driving, concrete placement, girder setting and post tensioning assistance to commence on January 15, 2015 with a completion date of September 30, 2015. The contractor will utilize a 40 foot by 60 foot barge as a work platform and for equipment staging. This safety zone will provide a safety buffer to transiting vessels as bridge construction work presents potential hazards to mariners and property due to reduction in horizontal clearance.
                </P>
                <P>The proposed temporary safety zone will encompass the waters directly under the new U.S. 70 Fixed Bridge crossing the Gallant Channel, mile 203.8, at Beaufort, North Carolina (34°43′16″ N, 076°41′37″ W). All vessels transiting this section of the waterway requiring a horizontal clearance of greater than 40 feet will be required to make a two hour advanced notification to the work supervisor while the safety zone is in effect. This zone will be in effect daily, 7 a.m. to 5:30 p.m., from January 15, 2015 through September 30, 2015.</P>
                <HD SOURCE="HD1">D. Regulatory Analyses</HD>
                <P>We developed this proposed rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes or executive orders.</P>
                <HD SOURCE="HD2">1. Regulatory Planning and Review</HD>
                <P>This proposed 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 Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders. This rule does not restrict traffic from transiting the designated portion of the Atlantic Intracoastal Waterway; it imposes a two hour notification to ensure the waterway is clear of impediments to passage of vessels requiring a horizontal clearance of greater than 40 feet.</P>
                <HD SOURCE="HD2">2. Impact on Small Entities</HD>
                <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. 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. The Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule will not have a significant economic impact on a substantial number of small entities.</P>
                <P>This proposed rule would affect the following entities, some of which may be small entities: The owners or operators of commercial tug and barge companies, recreational and commercial fishing vessels intending to transit the specified portion of Atlantic Intracoastal Waterway, 7 a.m. to 5:30 p.m., from January 15, 2015 through September 30, 2015.</P>
                <P>This safety zone would not have a significant economic impact on a substantial number of small entities for the following reasons. Although the safety zone will apply to this section of the Gallant Channel, vessel traffic requiring a horizontal clearance of greater than 40 feet will be able to request passage by providing a two hour advanced notification to the work supervisor. All those requiring less than 40 feet may pass at any time. Before the effective period, the Coast Guard will issue maritime advisories widely available to the users of the waterway.</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">3. 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 want to assist small entities in understanding this proposed rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , above. The Coast Guard will not retaliate against small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD2">4. Collection of Information</HD>
                <P>This proposed rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520.).</P>
                <HD SOURCE="HD2">5. Federalism</HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has 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. We have analyzed this proposed rule under that Order and determined that this rule does not have implications for federalism.</P>
                <HD SOURCE="HD2">6. Protest Activities</HD>
                <P>
                    The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section to coordinate protest activities so that your message can be received without jeopardizing the safety or security of people, places or vessels.
                </P>
                <HD SOURCE="HD2">7. 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 proposed rule would not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
                <HD SOURCE="HD2">8. Taking of Private Property</HD>
                <P>This proposed rule would 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">9. Civil Justice Reform</HD>
                <P>This proposed 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">10. Protection of Children From Environmental Health Risks</HD>
                <P>
                    We have analyzed this proposed rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This proposed rule is not an economically significant rulemaking and would not create an environmental risk to health or risk to safety that might disproportionately affect children.
                    <PRTPAGE P="72157"/>
                </P>
                <HD SOURCE="HD2">11. Indian Tribal Governments</HD>
                <P>This proposed rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would 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">12. Energy Effects</HD>
                <P>This proposed rule is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.</P>
                <HD SOURCE="HD2">13. Technical Standards</HD>
                <P>This proposed rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
                <HD SOURCE="HD2">14. Environment</HD>
                <P>
                    We have analyzed this proposed 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 made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This proposed rule involves the establishment of a temporary safety zone. This rulemaking is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. A preliminary environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are available in the docket where indicated under 
                    <E T="02">ADDRESSES</E>
                    . We seek any comments or information that may lead to the discovery of a significant environmental impact from this proposed rule.
                </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 proposes to amend 33 CFR part 165 as follows:</P>
                <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>
                <AMDPAR>2. Add temporary § 165.T05-0718 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 165.T05-0718 </SECTNO>
                    <SUBJECT>Safety Zone, Gallant Channel; Beaufort, NC.</SUBJECT>
                    <P>(a) Regulated Area. The following area is a safety zone: This zone includes the waters directly under and 100 yards either side of the new U.S. 70 Fixed Bridge crossing the Gallant Channel, mile 203.8, at Beaufort, North Carolina (34°43′16″ N, 076°41′37″ W).</P>
                    <P>(b) Regulations. The general safety zone regulations found in 33 CFR 165.23 apply to the safety zone created by this temporary section, § 165.T05-0718. In addition, the following regulations apply:</P>
                    <P>(1) All vessels requiring greater than 40 feet horizontal clearance to safely transit through the new U.S. 70 Fixed Bridge crossing the Atlantic Intracoastal Waterway, mile 203.8, at Beaufort, North Carolina must contact the work supervisor tender on VHF-FM marine band radio channels 10 and 13 or at (732) 520-5000 two hours in advance of intended transit.</P>
                    <P>(2) All Coast Guard assets enforcing this safety zone can be contacted on VHF-FM marine band radio channels 13 and 16.</P>
                    <P>(3) The operator of any vessel within or in the immediate vicinity of this safety zone shall: (i) Stop the vessel immediately upon being directed to do so by any commissioned, warrant or petty officer on board a vessel displaying a Coast Guard Ensign, and</P>
                    <P>(ii) Proceed as directed by any commissioned, warrant or petty officer on board a vessel displaying a Coast Guard Ensign.</P>
                    <P>(c) Definitions.</P>
                    <P>(1) Captain of the Port North Carolina means the Commander, Coast Guard Sector North Carolina.</P>
                    <P>(2) Designated representative means any Coast Guard commissioned, warrant, or petty officer who has been authorized by the Captain of the Port North Carolina to assist in enforcing the safety zone described in paragraph (a) of this section.</P>
                    <P>(3) Work Supervisor means the contractors' on site representative.</P>
                    <P>(d) Enforcement. The U.S. Coast Guard may be assisted by Federal, State and local agencies in the patrol and enforcement of the zone.</P>
                    <P>(e) Enforcement period. This section will be enforced daily 7 a.m. to 5:30 p.m., from January 15, 2015 through September 30, 2015 unless cancelled earlier by the Captain of the Port.</P>
                </SECTION>
                <SIG>
                    <DATED>Dated: November 17, 2014.</DATED>
                    <NAME>S. R. Murtagh,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port North Carolina.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28604 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 167</CFR>
                <DEPDOC>[USCG-2014-0941]</DEPDOC>
                <SUBJECT>Port Access Route Study: In the Chukchi Sea, Bering Strait and Bering Sea</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of study; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This study is a continuation of and an expansion of scope to the Port Access Route Study (PARS) the Coast Guard announced in 2010. Based on comments received from the 2010 notice the Coast Guard has developed a potential vessel routing system for the area. The Coast Guard requests comments on how consolidating vessel traffic into a defined vessel routing system may impact or benefit the region. The goal of the study is to help reduce the risk of marine casualties and increase the efficiency of vessel traffic in the region. The recommendations of the study may lead to future rulemaking action or appropriate international agreements.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 3, 2015.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P SOURCE="NPAR">
                        <E T="03">Schematic of proposed vessel routing system:</E>
                         A chart showing the Coast Guard's proposed two-way route can be downloaded from 
                        <E T="03">http://www.regulations.gov</E>
                        , type “USCG-2014-0941” into the search bar and click search, next to the displayed search results click “Open Docket Folder”, which will display all comments and documents associated with this docket.
                    </P>
                    <P>
                        <E T="03">Comment submission:</E>
                         You may submit comments identified by docket number USCG-2014-0941 using any one of the following methods:
                        <PRTPAGE P="72158"/>
                    </P>
                    <P>
                        (1) 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail:</E>
                         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-0001.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Hand delivery:</E>
                         Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329.
                    </P>
                    <P>
                        To avoid duplication, please use only one of these four methods. See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below for instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this notice of study, call or email LT Kody Stitz, Seventeenth Coast Guard District (dpw); telephone (907) 463-2270; email 
                        <E T="03">Kody.J.Stitz@uscg.mil</E>
                         or Mr. David Seris, Seventeenth Coast Guard District (dpw); telephone (907) 463-2267; email 
                        <E T="03">David.M.Seris@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Cheryl F. Collins, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>
                    We encourage you to participate in this study by submitting comments and related materials. All comments received will be posted without change to 
                    <E T="03">http://www.regulations.gov</E>
                     and will include any personal information you have provided.
                </P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    If you submit a comment, please include the docket number for this notice of availability (USCG-2014-0941), indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online (via 
                    <E T="03">http://www.regulations.gov</E>
                    ) or by fax, mail, or hand delivery, but please use only one of these means. If you submit a comment online via 
                    <E T="03">www.regulations.gov,</E>
                     it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility. We recommend that you include your name and a mailing address, an email address, or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.
                </P>
                <P>
                    To submit your comment online, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     type “USCG-2014-0941” into the search bar and click search, next to the displayed search results click “Comment Now”, which will open the comment page for this study. If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8.5 by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope. We will consider all comments and material received during the comment period.
                </P>
                <HD SOURCE="HD1">Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as documents mentioned in this preamble as being available in the docket, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     type “USCG-2014-0941” into the search bar and click search, next to the displayed search results click “Open Docket Folder”, which will display all comments and documents associated with this docket. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. We have an agreement with the Department of Transportation to use the Docket Management Facility.
                </P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD1">Public Meeting</HD>
                <P>
                    The Coast Guard will hold public meeting(s) if there is sufficient demand to warrant holding a meeting. You must submit a request for one on or before Month Day, Year (30 days from publish date) using one of the four methods specified under 
                    <E T="02">ADDRESSES</E>
                    . Please explain why you believe a public meeting would be beneficial. If we determine that a public meeting would aid in the study, we will hold a meeting at a time and place announced by a later notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Definitions</HD>
                <P>
                    The following definitions (except “Regulated Navigation Area”) are from the International Maritime Organization's (IMO's) publication “
                    <E T="03">Ships' Routeing</E>
                    ” Tenth Edition 2010 and should help you review this notice:
                </P>
                <P>
                    <E T="03">Area to be avoided (ATBA)</E>
                     means a routing measure comprising an area within defined limits in which either navigation is particularly hazardous or it is exceptionally important to avoid casualties and which should be avoided by all ships, or certain classes of ships.
                </P>
                <P>
                    <E T="03">Deep-water route</E>
                     means a route within defined limits, which has been accurately surveyed for clearance of sea bottom and submerged obstacles as indicated on the chart.
                </P>
                <P>
                    <E T="03">Inshore traffic zone</E>
                     means a routing measure comprising a designated area between the landward boundary of a traffic separation scheme and the adjacent coast, to be used in accordance with the provisions of Rule 10(d), as amended, of the International Regulations for Preventing Collisions at Sea, 1972 (COLREGS).
                </P>
                <P>
                    <E T="03">Precautionary area</E>
                     means a routing measure comprising an area within defined limits where ships must navigate with particular caution and within which the direction of traffic flow may be recommended.
                </P>
                <P>
                    <E T="03">Recommended route</E>
                     means a route of undefined width, for the convenience of ships in transit, which is often marked by centerline buoys.
                </P>
                <P>
                    <E T="03">Recommended track</E>
                     is a route which has been specially examined to ensure so far as possible that it is free of dangers and along which vessels are advised to navigate.
                </P>
                <P>
                    <E T="03">Regulated Navigation Area (RNA)</E>
                     means a water area within a defined boundary for which regulations for vessels navigating within the area have been established under 33 CFR part 165.
                </P>
                <P>
                    <E T="03">Roundabout</E>
                     means a routing measure comprising a separation point or circular separation zone and a circular traffic lane within defined limits. Traffic within the roundabout is separated by moving in a counterclockwise direction around the separation point or zone.
                </P>
                <P>
                    <E T="03">Separation zone or separation line</E>
                     means a zone or line separating the traffic lanes in which ships are proceeding in opposite or nearly opposite directions; or separating a traffic lane from the adjacent sea area; or separating traffic lanes designated for particular classes of ship proceeding in the same direction.
                    <PRTPAGE P="72159"/>
                </P>
                <P>
                    <E T="03">Traffic lane</E>
                     means an area within defined limits in which one-way traffic is established. Natural obstacles, including those forming separation zones, may constitute a boundary.
                </P>
                <P>
                    <E T="03">Traffic Separation Scheme (TSS)</E>
                     means a routing measure aimed at the separation of opposing streams of traffic by appropriate means and by the establishment of traffic lanes.
                </P>
                <P>
                    <E T="03">Two-way route</E>
                     means a route within defined limits inside which two-way traffic is established, aimed at providing safe passage of ships through waters where navigation is difficult or dangerous.
                </P>
                <P>
                    <E T="03">Vessel routing system</E>
                     means any system of one or more routes or routing measures aimed at reducing the risk of casualties; it includes traffic separation schemes, two-way routes, recommended tracks, areas to be avoided, no anchoring areas, inshore traffic zones, roundabouts, precautionary areas, and deep-water routes.
                </P>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <HD SOURCE="HD1">Requirement for Port Access Route Studies</HD>
                <P>Under the Ports and Waterways Safety Act (PWSA) (33 U.S.C. 1223(c)), the Commandant of the Coast Guard may designate necessary fairways and traffic separation schemes (TSSs) to provide safe access routes for vessels proceeding to and from U.S. ports.</P>
                <HD SOURCE="HD1">Port Access Route Study to Date</HD>
                <P>
                    The Coast Guard announced a port access route study in the 
                    <E T="04">Federal Register</E>
                     on November 8, 2010 (75 FR 68568). The purpose of the PARS was to solicit public comments on whether a vessel routing system such as a fairway or TSS was needed and if it could increase vessel safety in the area. The 2010 PARS was limited geographically in scope to a section of water extending approximately 100 nautical miles north of the Bering Strait into the Chukchi Sea to approximately 30 nautical miles south of St. Lawrence Island in the Bering Sea. At that time the Coast Guard did not propose a specific vessel routing system, but instead sought more general comments about whether a vessel routing system was needed or advisable in the study area. The Coast Guard received twenty five comments, and after reviewing them, determined that a vessel route needed to be proposed so more specific comments and concerns could be gathered and evaluated before determining if a routing system would be beneficial. The Coast Guard further determined that the study area should include a larger geographic area than was initially studied before finalizing the study and publishing the results.
                </P>
                <HD SOURCE="HD1">Vessel Routing Comments to Date</HD>
                <P>The Coast Guard received twenty five public comments during the open comment period associated with the 2010 announcement. Nearly all of the comments that addressed vessel routing were supportive of the Coast Guard creating and implementing some form of vessel routing measure in the area. Since no specific routing measure was proposed in 2010, the comments received did note that precise concerns and impacts could only be identified after a specific route or measure was proposed.</P>
                <HD SOURCE="HD1">Reopening of the Comment Period</HD>
                <P>
                    This 
                    <E T="04">Federal Register</E>
                     notice announces the Coast Guard's intent to continue the PARS started in 2010, expand the study area and release the Coast Guard's proposed vessel routing system for comment. The Coast Guard's goal of the study remains the same in that the study is focused on gathering factual and relevant information to aid the Coast Guard in reducing the risk of marine casualties and increasing the efficiency of vessel traffic in the region.
                </P>
                <P>The study will assess whether the creation of a vessel routing system is advisable to increase the predictability of vessel movements, which may decrease the potential for collisions, oil spills, and other events that could threaten the marine environment.</P>
                <P>Based on comments received to date there is a general sense that a designated traffic route could improve traffic predictability thereby reducing marine casualties and oil spills; however, a few comments received did note that a designated traffic route (depending on location) could adversely impact subsistence hunting, marine mammals and other wildlife more so than widely dispersed vessel traffic. Therefore, the Coast Guard puts forth a potential two-way route as a starting point for analyzing where to put a vessel traffic route should one be deemed needed and beneficial to the region.</P>
                <P>The Coast Guard will analyze vessel traffic density, agency and stakeholder experience in vessel traffic management, navigation, ship handling, the effects of weather, impacts to subsistence hunting, impacts to marine mammals and other wildlife concerns into the decision making process of the study. We encourage you to participate in the study process by submitting comments in response to this notice.</P>
                <P>The expanded study area is described as an area bounded by a line connecting the following geographic positions:</P>
                <P>• 67°30′ N, 168°58′37″ W;</P>
                <P>• 67°30′ N, 167°30′ W;</P>
                <P>• 54°50′ N, 164°40′ W;</P>
                <P>• 54°03′ N, 166°25′ W;</P>
                <P>• 63°20′ N, 173°43′ W; thence following the Russian Federation/United States maritime boundary line to the first geographical position.</P>
                <P>The proposed ship routing measures are described as follows:</P>
                <P>(1) A four nautical mile wide, two-way route extending from Unimak Pass in the Aleutian Islands that proceeds Northward through the Bering Sea and Bering Strait before terminating in the Chukchi Sea.</P>
                <P>(2) A four nautical mile wide, two-way route extending from a location North of the Western side of St. Lawrence Island and near the U.S./Russian Federation maritime border, then proceeding Northeast to a junction with the first two way route located to the West of King Island.</P>
                <P>(3) A total of four precautionary areas, each circular and 8 nautical miles wide in diameter. Three of these precautionary areas will be located at the starting/ending points of the two-way routes, and the fourth will be located at the junction of the recommended two-way routes.</P>
                <P>
                    See the 
                    <E T="02">ADDRESSES</E>
                     section for where to obtain a copy of the chart showing the exact location of the proposed route.
                </P>
                <P>Timeline, Study Area, and Process of this PARS: The Seventeenth Coast Guard District will conduct this PARS. The study will continue upon publication of this notice and may take 24 months to complete.</P>
                <P>
                    We will publish the results of the PARS in the 
                    <E T="04">Federal Register</E>
                    . It is possible that the study may validate the status quo (no routing measures) and conclude that no changes are necessary. It is also possible that the study may recommend one or more changes to enhance navigational safety and the efficiency of vessel traffic management. The recommendations may lead to future rulemakings or appropriate international agreements.
                </P>
                <SIG>
                    <DATED>Dated: November 14, 2014.</DATED>
                    <NAME>D. B. Abel,</NAME>
                    <TITLE>Rear Admiral, U.S. Coast Guard, Commander, Seventeenth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28672 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="72160"/>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 63</CFR>
                <DEPDOC>[EPA-HQ-OAR-2010-0895; FRL-9920-03-OAR]</DEPDOC>
                <RIN>RIN 2060-AQ11</RIN>
                <SUBJECT>National Emission Standards for Hazardous Air Pollutants: Ferroalloys Production; Extension of Comment Period</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Supplemental notice of proposed rulemaking; extension of public comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency (EPA) is announcing that the period for providing public comments on the October 6, 2014, supplemental proposed rule titled “National Emission Standards for Hazardous Air Pollutants: Ferroalloys Production” is being extended an additional 11 days.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public comment period for the supplemental proposed rule published October 6, 2014 (79 FR 60238), and initially extended by 18 days on November 14, 2014 (79 FR 68152), is being extended an additional 11 days to December 19, 2014, in order to provide the public additional time to submit comments and supporting information. The EPA received a request for an extension from ERAMET Marietta, Incorporated to gather and analyze data and formulate their comments on the supplemental proposed amendments.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written comments on the supplemental proposed rule may be submitted to EPA electronically, by mail, by facsimile or through hand delivery/courier. Please refer to the supplemental proposal (79 FR 60238) for the addresses and detailed instructions.</P>
                    <P>
                        <E T="03">Docket.</E>
                         Publicly available documents relevant to this action are available for public inspection either electronically at 
                        <E T="03">http://www.regulations.gov</E>
                         or in hard copy at the EPA Docket Center, Room 3334, 1301 Constitution Avenue NW., Washington, DC. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. A reasonable fee may be charged for copying. The official public docket for this rulemaking is Docket No. EPA-HQ-OAR-2010-0895.
                    </P>
                    <P>
                        <E T="03">World Wide Web.</E>
                         The EPA Web site for this rulemaking is at 
                        <E T="03">http://www.epa.gov/ttn/atw/ferroa/ferropg.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Phil Mulrine, Metals and Inorganic Chemicals Group (D243-02), Sector Policies and Programs Division, Office of Air Quality Planning and Standards, U.S. Environmental Protection Agency, Research Triangle Park, North Carolina 27711; Telephone number: (919) 541-5289; Fax number (919) 541-3207; Email address: 
                        <E T="03">mulrine.phil@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comment Period</HD>
                <P>After considering the request received from ERAMET Marietta, Incorporated to extend the public comment period, the EPA has decided to extend the public comment period for an additional 11 days. Therefore, the public comment period will end on December 19, 2014, rather than December 8, 2014.</P>
                <SIG>
                    <DATED>Dated: November 25, 2014.</DATED>
                    <NAME>Mary E. Henigin,</NAME>
                    <TITLE>Acting Director, Office of Air Quality Planning and Standards. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28387 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Indian Health Service</SUBAGY>
                <CFR>42 CFR Part 136</CFR>
                <RIN>RIN 0917-AA12</RIN>
                <SUBJECT>Payment for Physician and Other Health Care Professional Services Purchased by Indian Health Programs and Medical Charges Associated With Non-Hospital-Based Care</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Indian Health Service, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This proposed rule would amend Indian Health Service (IHS) Purchased and Referred Care (PRC), formally known as the Contract Health Services (CHS), regulations to apply Medicare payment methodologies to all physician and other health care professional services and non-hospital-based services that are either authorized under such regulations or purchased by urban Indian organizations. Specifically, it proposes that the health programs operated by IHS, Tribe, Tribal organization, or urban Indian organization (collectively, I/T/U programs) will pay the lowest of the amount provided for under the applicable Medicare fee schedule, prospective payment system, or Medicare waiver; the amount negotiated by a repricing agent, if available; or the usual and customary billing rate. Repricing agents may be used to determine whether IHS may benefit from savings by utilizing negotiated rates offered through commercial health care networks. This proposed rule seeks comment on how to establish reimbursement that is consistent across Federal health care programs, aligns payment with inpatient services, and enables the IHS to expand beneficiary access to medical care.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before January 20, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        In commenting, please refer to file code [
                        <E T="04">Federal Register</E>
                         insert No.]. Because of staff and resource limitations, we cannot accept comments by facsimile (FAX) transmission. You may submit comments in one of four ways (please choose only one of the ways listed):
                    </P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may submit electronic comments on this regulation to 
                        <E T="03">http://regulations.gov.</E>
                         Follow the “Submit a Comment” instructions.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address ONLY: Betty Gould, Regulations Officer, Indian Health Service, 801 Thompson Avenue, TMP STE 450, Rockville, Maryland 20852.
                    </P>
                    <P>Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>
                    <P>
                        3. 
                        <E T="03">By express or overnight mail.</E>
                         You may send written comments to the above address.
                    </P>
                    <P>
                        4. 
                        <E T="03">By hand or courier.</E>
                         If you prefer, you may deliver (by hand or courier) your written comments before the close of the comment period to the address above.
                    </P>
                    <P>If you intend to deliver your comments to the Rockville address, please call telephone number (301) 443-1116 in advance to schedule your arrival with a staff member.</P>
                    <P>Comments will be made available for public inspection at the Rockville address from 8:30 a.m. to 5 p.m., Monday-Friday, approximately three weeks after publication of this notice.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Carl Harper, Director, Office of Resource Access and Partnerships, Indian Health Service, 801 Thompson Avenue, Rockville, Maryland 20852. Telephone: (301) 443-1553.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Consolidated Appropriation Act of 2014 signed by President Obama in January, 2014, adopted a new name, Purchased/Referred Care (PRC), for the CHS program. The name change was official with passage of the FY 2014 appropriation. The new name better describes the purpose of the program funding, which is for both purchased 
                    <PRTPAGE P="72161"/>
                    care and referred care outside of IHS. The name change does not change the program, and all current policies, practices, will continue and is not intended to have any effect on the laws that govern or apply to CHS. IHS will administer PRC in accordance with all laws applicable to CHS. This proposed rule will use the term PRC. For the purposes of this rule, the terms provider of services (or “provider”) and supplier have the same meaning as the terms defined at 42 U.S.C. 1395x.
                </P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>This proposed rule would amend the IHS medical regulations at 42 CFR part 136 to apply Medicare payment methodologies to all physician and other health professional services and non-hospital-based services provided through Contract Health Services (CHS), now Purchased Referred Care (PRC), or purchased by urban Indian organizations, and that are not otherwise subject to Medicare payment rates by law. Under 42 CFR 136.23, when necessary health services are not reasonably accessible or available to IHS beneficiaries, the IHS and Tribes are authorized to pay for medical care provided to IHS beneficiaries by non-IHS or Tribal, public or private health care providers, depending on the availability of funds. Similarly, under section 503 of the Indian Health Care Improvement Act (IHCIA), 25 U.S.C. 1653, urban Indian organizations may refer eligible urban Indians, as defined under section 4 of the IHCIA, to non-I/T/U public and private health care providers and, depending on the availability of funds, may also cover the cost of care.</P>
                <P>Sec. 506 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003 (MMA) (Pub. L. 108-173) authorized the Secretary to establish a payment methodology, payment rates, and admissions practices for Medicare-participating hospitals that furnish inpatient services applicable when such hospitals provide to an eligible American Indian/Alaskan Native (AI/AN) beneficiary medical care authorized by an I/T/U. As implemented in 42 CFR part 136 subpart D, Medicare-participating hospitals, including Critical Access Hospitals (CAHs), are reimbursed by I/T/Us using “Medicare-like” rates that generally correspond to the applicable Medicare payment methodology for the medical service. In instances where Medicare-participating hospitals furnish inpatient services, but are exempt from Medicare's Prospective Payment System (PPS) and receive reimbursement based on reasonable costs (for example, CAHs, children's hospitals, cancer hospitals, and certain other hospitals reimbursed by Medicare under special arrangements), payment is made per discharge based on the reasonable cost methods established under 42 CFR part 413, except that the interim payment rate, under 42 CFR part 413 subpart E, constitutes payment in full for authorized charges. Notwithstanding, if an amount has been negotiated with the hospital or its agent by the I/T/U, the I/T/U will pay the lesser of the amount determined under the PPS or the amount negotiated with the hospital or its agent.</P>
                <P>
                    The Medicare-like rate methodology established by 42 CFR part 136 subpart D does not apply to non-hospital services, including physician and other health professional services, services provided by a comprehensive outpatient rehabilitation facility, a home health agency, or a hospice, or other non-hospital-based items and services. Rather, I/T/Us reimburse for authorized services at the rates provided by contracts negotiated at the local level with individual providers or according to a provider's billed charges. Given the small market share of individual I/T/U programs, I/T/Us historically have paid rates in substantial excess of Medicare's allowable rates or rates paid by private insurers for the same services. Despite establishing medical priorities to cover the most necessary care, IHS is still unable to provide care to all of its beneficiaries. The demand for PRC care consistently exceeds available funding. IHS recently reported to Congress that IHS and tribal PRC programs denied an estimated $760,855,000 for an estimated 146,928 contract care services needed by eligible beneficiaries in FY 2013.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Congress FY 2015 Congressional Justification Purchased/Referred Care Program Description and Accomplishments page 92-95, available online at: 
                        <E T="03">http://www.ihs.gov/budgetformulation/congressionaljustifications/</E>
                        .
                    </P>
                </FTNT>
                <P>
                    Based on an audit of fiscal year 2012, the Government Accountability Office (GAO) estimated that, by implementing a Medicare-like rate methodology, the IHS PRC programs could have saved $32 million on physician services alone, not including additional savings for other non-hospital services, or savings accrued to Tribal PRC programs. Government Accountability Office, 
                    <E T="03">Indian Health Service: Capping Payment Rates for Non-Hospital Services Could Save Millions of Dollars for Contract Health Services</E>
                     (April 2013) (“April 2013 Study”). The GAO concluded that by setting PRC physician and other non-hospital payments at rates consistent with Medicare and other Federal agencies, the IHS could expand IHS beneficiary access to care. These findings and recommendations are substantiated by a report from the Department of Health and Human Services' Office of the Inspector General. Department of Health and Human Services, Office of Inspector General, 
                    <E T="03">IHS Contract Health Services Program: Overpayments and Potential Savings</E>
                     (Sept. 2009).
                </P>
                <HD SOURCE="HD1">II. Provisions of the Proposed Rule</HD>
                <P>
                    This proposed rule is promulgated pursuant to 42 U.S.C. 2001(b), which provides that the Secretary “[i]n carrying out [her] functions, responsibilities, authorities, and duties under [the Transfer Act] . . . is authorized, with the consent of the Indian people served, to contract with private or other non-Federal health agencies or organizations for the provision of health services to such people on a fee-for-service basis or on a prepayment or other basis” and pursuant to 42 U.S.C. 2003, which authorizes the Secretary to promulgate regulations to carry out the Transfer Act. It amends the IHS regulation at 42 CFR part 136 by adding a new subpart I that applies “Medicare-like” rate payment methodologies to all physicians and health care professional services and all non-hospital-based services that are not covered currently under 42 CFR part 136 subpart D. The proposed rule is similar to payment methodologies promulgated in other Federal health care programs, including the Department of Veterans Affairs, by applying a consistent reimbursement policy across Federal health care programs. The proposed rule provides that the I/T/U will pay the lowest of the amount provided under the applicable Medicare fee schedule, prospective payment system, or Medicare waiver; the amount negotiated by a repricing agent,
                    <SU>2</SU>
                    <FTREF/>
                     if available; or the usual and customary billing rate. In the absence of a Medicare rate or Medicare waiver, or agreement, payment will be made at the amount that the provider or supplier bills the general public for the same service. The rule specifies the circumstances in which a non-hospital health care provider or supplier will be deemed to have accepted the rates established herein.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         A repricing agent discounts rates charged by a health care provider to rates that the agent may have established with the health care provider as a condition of participating in the agent's provider network.
                    </P>
                </FTNT>
                <P>
                    The rule caps the rate that I/T/Us are authorized to pay non-I/T/U health care providers and suppliers for services and leaves no discretion for the I/T/U and the health care provider to negotiate higher rates. The IHS recognizes this 
                    <PRTPAGE P="72162"/>
                    constraint could impact the delivery of patient care, particularly in circumstances where the I/T/U cannot find a health care provider or supplier willing to accept the payment rates established herein or the patient receives emergency services from a provider or supplier that refuses to accept the rate. Under 25 U.S.C. 1621u, a patient who receives authorized contract care may not be held liable for the payment of any charges. If the medical provider or supplier does not agree to accept the payment rate as payment in full, the I/T/U is effectively precluded from authorizing the care or paying the health care provider or supplier for services rendered to a beneficiary. In such circumstances, the I/T/U will not authorize payment and the patient may be held financially responsible by the provider or supplier of care for the charges. The IHS also notes that, while Medicare-participating hospitals are required to accept payment rates set forth in 42 CFR part 136 subpart D for facility services, subpart D does not apply to the professional service provided by a physician or practitioner through the hospital. To the extent the physician or practitioner does not agree to accept the rates established by this regulation, the I/T/U will not authorize payment for the service. The IHS seeks comment on whether exceptions should be incorporated into the rule to permit an I/T/U to pay in excess of the calculated rate in circumstances where it may be appropriate for the I/T/U to retain more flexibility over the payment rate. For example, a specialist that does not accept reduced rates and to access this specialty at a reduced rate it is located in another State. The travel costs and burden on the patient is too great to access the needed specialty care.
                </P>
                <P>The proposed rule also specifies that payments made in accordance with the described methodology shall constitute payment in full and that, in accordance with 25 U.S.C. 1621u, the provider, supplier or their agent, may not impose additional charge on an individual for I/T/U authorized items and services. Consistent with IHS regulations, the rule further provides that, if an I/T/U has authorized payment for PRC services provided to an individual who is eligible for benefits under Medicare, Medicaid, or another third party payer, the I/T/U shall be the payer of last resort in accordance with 25 U.S.C. 1623(b). If there are any third party payers, the I/T/U will pay the amount for which the patient is being held responsible after the provider or supplier of services has coordinated benefits and all other alternate resources have been considered and paid, including applicable co-payments, deductibles, and coinsurance owed by the patient. For purposes of the payment methodology specified in § 136.30(a), required co-payments, deductibles, and coinsurance are those that would have been owed by a Medicare beneficiary under the proposed methodology. Because the patient may not be held liable for the payment of costs or charges under 25 U.S.C. 1621u, the I/T/U will assume these costs to the extent all payments made by any payer, do not in aggregate, exceed the maximum payment rate set forth § 136.201(a).</P>
                <HD SOURCE="HD1">III. Collection of Information Requirements</HD>
                <P>These regulations do not impose any new information collection requirements. The requirements for submitting a claim are currently approved under Office and Management and Budget approval number 0917-0002, IHS Contract Health Services Report (Expires: 02/28/2016). Providers and suppliers will not be required to update information technology systems as a result of the provisions of this proposed rule. Claims will be re-priced by the IHS Fiscal Intermediary or the appropriate Tribal administrator according to the methodology adopted herein.</P>
                <HD SOURCE="HD1">IV. Regulatory Impact Statement</HD>
                <P>The IHS has examined the impact of this final rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, and the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4).</P>
                <P>Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any one year). The April 2013 Study released by the GAO found that if federal PRC programs had paid Medicare rates for physicians services in 2010, they could have realized an estimated $32 million in annual savings to pay for additional services. Although the analysis did not include other types of non-hospital services or funding that goes to tribal PRC programs, the increase in purchasing power brought about by this proposed rule would be unlikely to exceed $100 million annually. OMB has determined that this is a significant regulatory action under Executive Order 12866.</P>
                <P>The Secretary hereby proposes to certify that this proposed rule will not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601 through 612. The proposed rule will not cause significant economic impact on health care providers, suppliers, or entities since only a small portion of the business of such entities concerns IHS beneficiaries. The April 2013 Study released by the GAO found that of the physicians sampled, the PRC program represented a small portion of their practice and was not a significant source of revenue. Although the sampling of physicians was small, all of the sampled physicians were in the top 25% in terms of volume of paid services covered by PRC. IHS believes the sample to be representative of higher volume practitioners currently providing services paid for by PRC. Accordingly, pursuant to 5 U.S.C. 605(b), the proposed rule is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604.</P>
                <P>In addition, section 1102(b) of the Act requires IHS to prepare a RIA if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 603 of the RFA. For purposes of section 1102(b) of the Act, IHS defines a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. For the reasons provided above, IHS has determined that this rule will not have a significant impact on the operations of a substantial number of small rural hospitals. Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule whose requirements mandate expenditure in any one year by State, local, or Tribal governments, in the aggregate, or by the private sector, of $141 million. This proposal would not impose substantial Federal mandates on State, local or Tribal governments or private sector.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 42 CFR Part 136</HD>
                    <P>Alaska Natives, American Indian, Health, Medicare.</P>
                </LSTSUB>
                <SIG>
                    <PRTPAGE P="72163"/>
                    <DATED>Dated: November 6, 2014 . </DATED>
                    <NAME>Yvette Roubideaux,</NAME>
                    <TITLE>Acting Director, Indian Health Service.</TITLE>
                    <DATED>Dated: November 18, 2014. </DATED>
                    <NAME>Sylvia M. Burwell,</NAME>
                    <TITLE>Secretary, Health and Human Services.</TITLE>
                </SIG>
                <P>For the reasons set forth in the preamble, the Indian Health Service proposes to amend 42 CFR chapter I as set forth below:</P>
                <PART>
                    <HD SOURCE="HED">PART 136—INDIAN HEALTH</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 136 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>25 U.S.C. 13; 42 U.S.C. 1395cc(a)(1)(U), 42 U.S.C. 2001 and 2003, unless otherwise noted.</P>
                </AUTH>
                <AMDPAR>2. Add new subpart I consisting of §§ 136.201 and 136.202, to read as follows:</AMDPAR>
                <SUBPART>
                    <HD SOURCE="HED">Subpart I—Limitation on Charges for Health Care Professional Services and Non-Hospital-Based Care</HD>
                </SUBPART>
                <CONTENTS>
                    <SECHD>Sec.</SECHD>
                    <SECTNO>136.201 </SECTNO>
                    <SUBJECT>Payment for physician and other health care professional services purchased by Indian health programs and other medical charges associated with non-hospital-based care.</SUBJECT>
                    <SECTNO>136.202 </SECTNO>
                    <SUBJECT>Authorization by urban Indian organizations.</SUBJECT>
                </CONTENTS>
                <SECTION>
                    <SECTNO>§ 136.201 </SECTNO>
                    <SUBJECT>Payment for physician and other health care professional services purchased by Indian health programs and other medical charges associated with non-hospital-based care.</SUBJECT>
                    <P>
                        (a) Payment to physicians and health care professionals and all other non-hospital-based entities, for any level of care authorized under part 136, subpart C by a Purchased/Referred Care (PRC) program of the Indian Health Service (IHS); or authorized by a Tribe or Tribal organization carrying out a PRC program of the IHS under the Indian Self-Determination and Education Assistance Act, as amended, Public Law 93-638, 25 U.S.C. 450 
                        <E T="03">et seq.;</E>
                         or authorized for purchase under § 136.31 by an urban Indian organization (as that term is defined in 25 U.S.C. 1603(h)) (hereafter “I/T/U”), shall be determined based on the applicable method in this section: The I/T/U will pay the lowest of the following amounts:
                    </P>
                    <P>(1) The applicable Medicare payment amount, including payment according to a fee schedule, a prospective payment system or based on reasonable cost (“Medicare rate”) for the period in which the service was provided), or in the event of a Medicare waiver, the payment amount will be calculated in accordance with such waiver.</P>
                    <P>(2) An amount that has been negotiated with a specific provider or its agent, or supplier or its agent by the I/T/U or the amount negotiated by a repricing agent if the provider or supplier is participating within the repricing agent's network and an I/T/U has a pricing arrangement or contract with that repricing agent. For the purposes of this section, repricing agent means an entity that seeks to connect I/T/U with discounted rates from non-I/T/U public and private providers as a result of existing contracts that the non-I/T/U public or private provider may have within the commercial health care industry.</P>
                    <P>(3) The amount that the provider or supplier bills the general public for the same service.</P>
                    <P>(b) Coordination of benefits and limitation on recovery: If an I/T/U has authorized payment for items and services provided to an individual who is eligible for benefits under Medicare, Medicaid, or another third party payer—</P>
                    <P>(1) The I/T/U is the payer of last resort under 25 U.S.C. 1623(b);</P>
                    <P>(2) If there are any third party payers, the I/T/U will pay the amount for which the patient is being held responsible after the provider or supplier of services has coordinated benefits and all other alternate resources have been considered and paid, including applicable co-payments, deductibles, and coinsurance that are owed by the patient; and</P>
                    <P>(3) The maximum payment by the I/T/U will be only that portion of the payment amount determined under this section not covered by any other payer; and</P>
                    <P>(4) The I/T/U payment will not exceed the rate calculated in accordance with paragraph (a) of this section (plus applicable cost sharing); and</P>
                    <P>(5) When payment is made by Medicaid it is considered payment in full and there will be no additional payment made by the I/T/U to the amount paid by Medicaid.</P>
                    <P>(c) Authorized services: Payment shall be made only for those items and services authorized by an I/T/U consistent with part 136 of this title or section 503(a) of the Indian Health Care Improvement Act (IHCIA), Public Law 94-437, as amended, 25 U.S.C. 1653(a).</P>
                    <P>(d) No additional charges.</P>
                    <P>(1) The health care provider or supplier shall be deemed to have accepted the applicable Medicare payment amount, including payment according to a fee schedule, a prospective payment system or based on reasonable cost (“Medicare rate”) for the period in which the service was provided), as payment in full if:</P>
                    <P>(i) The services were provided based on a PRC referral authorized for payment; or,</P>
                    <P>(ii) The health care provider or supplier submits a Notification of a Claim for payment to the I/T/U; or</P>
                    <P>(iii) The health care provider or supplier accepts payment for the provision of services from the I/T/U.</P>
                    <P>(2) A payment made and accepted in accordance with this section shall constitute payment in full and the provider or its agent, or supplier or its agent, may not impose any additional charge—</P>
                    <P>(i) On the individual for I/T/U authorized items and services; or</P>
                    <P>(ii) For information requested by the I/T/U or its agent or fiscal intermediary for the purposes of payment determinations or quality assurance.</P>
                    <P>(e) For physicians and health care professionals and all other non-hospital-based entities required by law to accept the rates specified in this section, the applicable rate shall be the lowest of any amount calculated under paragraph (a)(1) of this section, without regard to paragraph (d)(1) of this section.</P>
                    <P>(f) No service shall be authorized and no payment shall be issued in excess of the rate authorized by this subpart.</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 136.202 </SECTNO>
                    <SUBJECT>Authorization by an urban Indian organization.</SUBJECT>
                    <P>An urban Indian organization may authorize for purchase items and services for an eligible urban Indian (as those terms are defined in 25 U.S.C. 1603(f) and (h)) according to section 503 of the IHCIA and applicable regulations. Services and items furnished by physicians and other health care professionals and non-hospital-based entities shall be subject to the payment methodology set forth in § 136.30.</P>
                </SECTION>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28508 Filed 12-3-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4165-16-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="72164"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments regarding (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques and other forms of information technology.</P>
                <P>
                    Comments regarding this information collection received by January 5, 2015 will be considered. Written comments should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), New Executive Office Building, 725 17th Street NW., Washington, DC 20503. Commentors are encouraged to submit their comments to OMB via email to: 
                    <E T="03">OIRA_Submission@omb.eop.gov</E>
                     or fax (202) 395-5806 and to Departmental Clearance Office, USDA, OCIO, Mail Stop 7602, Washington, DC 20250-7602. Copies of the submission(s) may be obtained by calling (202) 720-8681.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Forest Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Generic Clearance for Large Scale Collaborative Project Socio-economic Monitoring.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0596—NEW.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Forest Landscape Restoration Act of 2009 (16 U.S.C. 7303) requires the Forest Service to monitor socio-economic impacts of collaborative restoration activities within the project site. In addition, the 2012 Planning Rule (36 CFR part 219) requires a transparent, collaborative and informed planning process. Large scale collaborative projects involve interested parties, such as neighboring land owners, state, local and tribal government representatives, businesses, interest groups and nonprofit organizations working with a federal government agency to find common ground pertaining to geographically extensive land management, often across multiple jurisdictions. Bureau of Land Management (BLM) and U.S. Forest Service (FS) collaboration on large scale projects also extends beyond Collaborative Forest Landscape Restoration and Management Plans.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     Data will be collected through a variety of methods, including: A census survey of partners/participants of a collaborative project; mail-survey of residents in the large scale collaborative project or planning areas; survey of spending habits of restoration workers; and key informant interviews with business, community, stakeholder leaders in collaborative project and planning areas. Results will assist program managers in evaluating the positive and negative social and economic effects of collaborative project implementation and assist FS and BLM forest planners in meeting collaborative and public input requirement of the 2012 Forest Planning Rule.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals; Business or other for-profit; Not-for-profit institutions; State, Local or Tribal Governments.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     48,800.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Annually.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     38,800.
                </P>
                <HD SOURCE="HD1">Forest Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Generic Clearance for the Stewardship Mapping and Assessment Project (STEW-MAP).
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0596—NEW.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Cooperative Forestry Assistance Act of 1978 (Pub. L. 113-79) Section 9(a); (b)(8); (c) and (d); The Forest and Rangeland Renewable Resources Research Act of 1978 and the National Environmental Policy Act of 1969 authorize the Forest Service to expand and strengthen existing research, education, technical assistance and public information and participation in tree planting and maintenance programs through stewardship. Civic environmental stewards are involved in a range of activities like planting trees, organizing community gardens, offering environment-themed classes, leading local conservation efforts, monitoring plants and animals, and cleaning up nearby parks or natural areas. These stewards may be nonprofit organizations, formal or informal community groups, faith-based organizations, or academic institutions. STEW-MAP will create a publicly available database and map of stewardship groups, their activities, and where they work.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     Information will be gathered on civic stewardship groups and their efforts such as where they work, the types of projects they focus on, and how they are organized. There are three phases to a STEW-MAP project: (1) A census to put together a master list of known stewardship groups and their contact information in the target city or region; (2) a survey distributed to all of the organizations identified in phase one to collect information about what they work on, structure of the group and what other groups they collaborate with; and (3) follow-up interviews with key longstanding organizations identified during phase two, to collect more detailed information about organizational histories.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Business or other for-profit; Not-for-profit institutions; State, Local or Tribal Governments.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     15,900.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: Annually.
                    <PRTPAGE P="72165"/>
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     7,925.
                </P>
                <SIG>
                    <NAME>Charlene Parker,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28552 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Commission Business Meeting.</P>
                </ACT>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date and Time:</E>
                         Friday, December 12, 2014; 9:30 a.m. EST.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Place:</E>
                         1331 Pennsylvania Ave. NW., Suite 1150, Washington, DC.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lenore Ostrowsky, Acting Chief, Public Affairs Unit (202) 376-8591.</P>
                    <P>
                        Hearing-impaired persons who will attend the briefing and require the services of a sign language interpreter should contact Pamela Dunston at (202) 376-8105 or at 
                        <E T="03">signlanguage@usccr.gov</E>
                         at least seven business days before the scheduled date of the meeting.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Meeting Agenda</HD>
                <P>This meeting is open to the public.</P>
                <FP SOURCE="FP-2">I. Approval of Agenda</FP>
                <FP SOURCE="FP-2">II. Program Planning</FP>
                <FP SOURCE="FP1-2">• Review and Vote of the 2015 Statutory Enforcement Report Discovery Plan</FP>
                <FP SOURCE="FP1-2">• Discussion and Vote on Updating Select Commission Reports</FP>
                <FP SOURCE="FP-2">III. Management and Operations</FP>
                <FP SOURCE="FP1-2">• Presentations from the Illinois and Georgia SAC Chairs on their Immigration Projects</FP>
                <FP SOURCE="FP1-2">• Staff Director's Report</FP>
                <FP SOURCE="FP-2">IV. State Advisory Committee (SAC) Appointments</FP>
                <FP SOURCE="FP1-2">• Indiana</FP>
                <FP SOURCE="FP-2">V. Adjourn Meeting</FP>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Marlene Sallo,</NAME>
                    <TITLE>Staff Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28649 Filed 12-3-14; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 6335-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[B-55-2014]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone 221—Mesa, Arizona; Authorization of Production Activity; Apple Inc./GTAT Corp. (Components for Consumer Electronics); Mesa, Arizona</SUBJECT>
                <P>On July 31, 2014, the City of Mesa, grantee of FTZ 221, submitted a notification of proposed production activity to the Foreign-Trade Zones (FTZ) Board on behalf of Apple Inc./GTAT Corp., within Subzone 221A, in Mesa, Arizona.</P>
                <P>
                    The notification was processed in accordance with the regulations of the FTZ Board (15 CFR part 400), including notice in the 
                    <E T="04">Federal Register</E>
                     inviting public comment (79 FR 47088-47089, 8-12-2014). The FTZ Board has determined that no further review of the activity is warranted at this time. The production activity described in the notification is authorized, subject to the FTZ Act and the Board's regulations, including Section 400.14.
                </P>
                <SIG>
                    <DATED>Dated: November 28, 2014.</DATED>
                    <NAME>Andrew McGilvray,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28582 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-904]</DEPDOC>
                <SUBJECT>Certain Activated Carbon From the People's Republic of China: Notice of Court Decision Not in Harmony With Final Results of Administrative Review and Notice of Amended Final Results of Antidumping Duty Administrative Review; 2009-2010</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On November 24, 2014, the United States Court of International Trade (“the Court”) issued final judgment in 
                        <E T="03">Albemarle Corp. et al.</E>
                         v.
                        <E T="03"> United States,</E>
                         Consol. Court No. 11-00451, sustaining the Department of Commerce's (“the Department”) final results of redetermination pursuant to remand (“Remand”).
                        <SU>1</SU>
                        <FTREF/>
                         In the Remand, the Department recalculated the weighted-average dumping margin for Calgon Carbon (Tianjin) Co., Ltd.'s (“Calgon Tianjin”) using revised surrogate values for coal and fine by-products.
                        <SU>2</SU>
                        <FTREF/>
                         The Department also recalculated in the Remand the dumping margin for three respondents not selected for individual examination (
                        <E T="03">i.e.,</E>
                         the separate rate)—Ningxia Guanghua Cherishmet Activated Carbon Co., Ltd. (“Ningxia Guanghua”) and its affiliate Beijing Pacific Activated Carbon Products Co., Ltd. (“Beijing Pacific”) (together, “Cherishmet”),
                        <SU>3</SU>
                        <FTREF/>
                         as well as Shanxi DMD Corporation (“Shanxi DMD”).
                        <SU>4</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See</E>
                             Final Results Of Redetermination Pursuant To Court Remand, Consol. Court No. 11-00451, Slip Op. 13-106 (CIT August 15, 2013), dated January 9, 2014, available at 
                            <E T="03">http://enforcement.trade.gov/remands/13-106.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">Id.</E>
                             at 8-10. As we explain below, the Department's recalculation of these surrogate values continued to yield a 
                            <E T="03">de minimis</E>
                             weighted-average dumping margin for Calgon Tianjin. Thus, consistent with our practice, the Department has not amended the final results with respect to Calgon Tianjin.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             The Department found Ningxia Guanghua and Beijing Pacific to be affiliated and a single entity in 
                            <E T="03">First Administrative Review of Certain Activated Carbon From the People's Republic of China: Final Results of Antidumping Duty Administrative Review,</E>
                             74 FR 57995, 57998 (November 10, 2009).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See</E>
                             Remand at 10-13.
                        </P>
                    </FTNT>
                    <P>
                        Consistent with the decision of the United States Court of Appeals for the Federal Circuit (“CAFC”) in 
                        <E T="03">Timken Co.</E>
                         v.
                        <E T="03"> United States,</E>
                         893 F.2d 337 (Fed. Cir. 1990) (“
                        <E T="03">Timken</E>
                        ”), as clarified by 
                        <E T="03">Diamond Sawblades Mfrs. Coalition</E>
                         v.
                        <E T="03"> United States,</E>
                         626 F.3d 1374 (Fed. Cir. 2010), the Department is notifying the public that the final judgment in this case is not in harmony with the Department's final results of the antidumping duty administrative review of the antidumping duty order on certain activated carbon from the People's Republic of China (“PRC”) covering the period of review (“POR”) April 1, 2009, through March 31, 2010, and is amending the final results with respect to the weighted-average dumping margins assigned to Ningxia Guanghua, Beijing Pacific, and Shanxi DMD.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">See Certain Activated Carbon From the People's Republic of China: Final Results and Partial Rescission of Third Antidumping Duty Administrative Review,</E>
                             76 FR 67142 (October 31, 2011) (“
                            <E T="03">AR3 Final Results”</E>
                            ) and the accompanying Issues and Decision Memorandum.
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03"> Effective Date:</E>
                         December 4, 2014.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert Palmer, AD/CVD Operations Office V, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-9068.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <PRTPAGE P="72166"/>
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On October 31, 2011, the Department issued 
                    <E T="03">AR3 Final Results.</E>
                    <SU>6</SU>
                    <FTREF/>
                     Cherishmet and Shanxi DMD, exporters of subject merchandise, timely filed complaints with the Court. Albemarle Corporation (“Albemarle”), a U.S. importer of subject merchandise, and Ningxia Huahui Activated Carbon Co., Ltd. (“Huahui”), an exporter of subject merchandise, also timely filed a complaint with the Court. Together, these parties challenged four aspects of the Department's final results: (1) The surrogate value for Calgon Tianjin's carbonized material; (2) the surrogate values for Calgon Tianjin's coal and fine by-products; (3) the dumping margins assigned to Huahui, Shanxi DMD, Ningxia Guanghua, and Beijing Pacific, which were not selected for individual examination in the review; and (4) the use of a per-unit assessment rate for Shanxi DMD's entries. On August 15, 2013, the Court remanded the Department's 
                    <E T="03">AR3 Final Results</E>
                     and instructed the Department to reconsider each of these issues.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Albemarle Corp.</E>
                         v.
                        <E T="03"> United States,</E>
                         931 F. Supp. 2d 1280 (CIT 2013). The Court reserved judgment on the dumping margin assigned to Huahui, which was different from the margin that the Department assigned to Shanxi DMD, Ningxia Guanghua, and Beijing Pacific. 
                        <E T="03">Id.</E>
                         It explained that the Department could, but was not required to, reconsider Huahui's margin on remand. 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    On January 9, 2014, the Department filed the Remand with the Court. First, the Department continued to calculate Calgon Tianjin's surrogate value for carbonized material with the same data that it used in 
                    <E T="03">AR3 Final Results.</E>
                    <SU>8</SU>
                    <FTREF/>
                     Second, the Department recalculated Calgon Tianjin's surrogate values for coal and fine by-products by capping those values at the value assigned to their main input, carbonized material.
                    <SU>9</SU>
                    <FTREF/>
                     The Department's recalculation of the by-products surrogate values continued to yield a 
                    <E T="03">de minimis</E>
                     weighted-average dumping margin for Calgon Tianjin.
                    <SU>10</SU>
                    <FTREF/>
                     Third, and under protest, the Department averaged the zero and 
                    <E T="03">de minimis</E>
                     rates calculated for the two mandatory respondents in this administrative review (
                    <E T="03">i.e.,</E>
                     Jacobi Carbons AB and Calgon Tianjin) and assigned the resulting zero dumping margin to Ningxia Guanghua, Beijing Pacific, and Shanxi DMD.
                    <SU>11</SU>
                    <FTREF/>
                     Finally, the Department determined that the issue concerning the use of a per-unit assessment rate for Shanxi DMD's entries was moot, given that the Department assigned Shanxi DMD a dumping margin of zero.
                    <SU>12</SU>
                    <FTREF/>
                     On November 24, 2014, the Court entered judgment sustaining the Remand.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Remand at 3-8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                         at 10.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         at 10-13. The Department did not change the dumping margin assigned to Huahui. 
                        <E T="03">Id.</E>
                         at 22.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                         at 13-15.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Albemarle Corp. et al.</E>
                         v.
                        <E T="03"> United States,</E>
                         Consol. Court No. 11-00451 (CIT November 24, 2014).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Timken Notice</HD>
                <P>
                    In its decision in 
                    <E T="03">Timken,</E>
                     893 F.2d at 341, as clarified by 
                    <E T="03">Diamond Sawblades,</E>
                     the CAFC held that, pursuant to section 516A(e) of the Tariff Act of 1930, as amended (“the Act”), the Department must publish a notice of a court decision that is not “in harmony” with a Department determination and must suspend liquidation of entries pending a “conclusive” court decision. The Court's November 24, 2014, judgment sustaining the Remand constitutes a final decision of the Court that is not in harmony with the Department's 
                    <E T="03">AR3 Final Results.</E>
                     This notice is published in fulfillment of the publication requirement of 
                    <E T="03">Timken.</E>
                </P>
                <HD SOURCE="HD1">Amended Final Results</HD>
                <P>
                    Because there is now a final court decision, the Department amends 
                    <E T="03">AR3 Final Results</E>
                     with respect to Cherishmet and Shanxi DMD. The revised weighted-average dumping margins for these exporters during the period April 1, 2009, through March 31, 2010, follow:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s75,16">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter name</CHED>
                        <CHED H="1">
                            Weighted average
                            <LI>dumping margin</LI>
                            <LI>(dollars per</LI>
                            <LI>kilogram)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            Ningxia Guanghua Cherishmet Activated Carbon Co., Ltd 
                            <SU>14</SU>
                        </ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shanxi DMD Corporation</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Accordingly,
                    <FTREF/>
                     the Department will continue the suspension of liquidation of the subject merchandise pending the expiration of the period of appeal or, if appealed, pending a final and conclusive court decision. In the event the Court's ruling is not appealed or, if appealed, upheld by the CAFC, the Department will instruct U.S. Customs and Border Protection to assess antidumping duties on unliquidated entries of subject merchandise exported by Cherishmet and Shanxi DMD using the assessment rate calculated by the Department in the Remand and listed above.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         This dumping margin also applies to Beijing Pacific. 
                        <E T="03">See supra</E>
                         note 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The cash deposit rate for Cherishmet will remain the respondent-specific rate established for the subsequent and most-recent period during which the respondent was reviewed, which is $0.04 per kilogram.
                    <SU>15</SU>
                    <FTREF/>
                     The cash deposit rate for the PRC-wide rate, which now includes Shanxi DMD, will remain the PRC-wide entity rate established for the subsequent and most-recent period during which the PRC-wide entity was reviewed, which is 2.42 U.S. dollars per kilogram.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See Certain Activated Carbon From the People's Republic of China: Final Results of Antidumping Duty Administrative Review; 2012-2013,</E>
                         79 FR 70163, 70165 (November 25, 2014).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice is issued and published in accordance with sections 516A(e), 751(a)(1), and 777(i)(1) of the Act.</P>
                <SIG>
                    <DATED> Dated: December 1, 2014.</DATED>
                    <NAME>Paul Piquado,</NAME>
                    <TITLE>Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28577 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-924]</DEPDOC>
                <SUBJECT>Polyethylene Terephthalate Film, Sheet, and Strip From the People's Republic of China: Preliminary Results of Antidumping Duty Administrative Review, Preliminary Determination of No Shipments and Partial Rescission of Review; 2012-2013</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Commerce (“the Department”) is conducting an administrative review of the antidumping duty order on polyethylene terephthalate film, sheet, and strip (“PET film”) from the People's Republic of China (“PRC”). The period of review (“POR”) is November 1, 2012, through October 31, 2013. The Department initiated the review with respect to five companies. We preliminarily find that two of the mandatory respondents, Shaoxing Xiangyu Green Packing Co., Ltd. and Tianjin Wanhua Co., Ltd. made sales of subject merchandise at less than normal value (“NV”). We are rescinding the review with respect to Huangshi Yucheng Trade Co. Ltd. (“Yucheng”). Further, we preliminarily find that 
                        <PRTPAGE P="72167"/>
                        Fuwei Films (Shandong) Co., Ltd. (“Fuwei Films”) and Sichuan Dongfang Insulating Material Co., Ltd., (“Dongfang”), did not have any reviewable transactions during the POR. Interested parties are invited to comment on these preliminary results.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         December 5, 2014.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jonathan Hill or Thomas Martin, AD/CVD Operations, Office IV, Enforcement &amp; Compliance, International Trade Administration, Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-3518 or (202) 482-3936, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The products covered by the order are all gauges of raw, pre-treated, or primed PET film, whether extruded or co-extruded.
                    <SU>1</SU>
                    <FTREF/>
                     PET film is classifiable under subheading 3920.62.00.90 of the Harmonized Tariff Schedule of the United States (“HTSUS”). Although the HTSUS subheadings are provided for convenience and customs purposes, our written description of the scope of the order is dispositive.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         For a complete description of the scope of the order, 
                        <E T="03">see</E>
                         “Decision Memorandum for the Preliminary Results of 2012-2013 Antidumping Duty Administrative Review of Polyethylene Terephthalate Film, Sheet, and Strip From the People's Republic of China” from Christian Marsh, Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations to Paul Piquado, Assistant Secretary for Enforcement and Compliance, dated concurrently with this notice (“Preliminary Decision Memorandum”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Preliminary Determination of No Shipments</HD>
                <P>
                    Based on our analysis of U.S. Customs and Border Protection (“CBP”) information and information provided by Fuwei Films and Dongfang, we preliminarily determine that Fuwei Films and Dongfang did not have any reviewable transactions during the POR. For additional information regarding this determination, 
                    <E T="03">see</E>
                     the Preliminary Decision Memorandum.
                </P>
                <HD SOURCE="HD1">Partial Rescission</HD>
                <P>On December 2, 2013, Now Plastics Inc. (“Now Plastics”) requested an administrative review of subject merchandise exported by Yucheng. Subsequently, on February 12, 2014, Now Plastics timely withdrew its request for an administrative review of Yucheng's exports. No other parties requested a review of Yucheng. The Department, pursuant to 19 CFR 351.213 (d)(1), is therefore rescinding this administrative review with respect to Yucheng.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>The Department conducted this review in accordance with section 751(a)(1)(A) of the Tariff Act of 1930, as amended (“the Act”). We calculated export prices in accordance with section 772 of the Act. Because the PRC is a non-market economy (“NME”) within the meaning of section 771(18) of the Act, we calculated NV in accordance with section 773(c) of the Act.</P>
                <P>
                    For a full description of the methodology underlying our conclusions, 
                    <E T="03">see</E>
                     the Preliminary Decision Memorandum, which is hereby adopted by this notice. The Preliminary Decision Memorandum is a public document and is on file electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (“ACCESS”).
                    <SU>2</SU>
                    <FTREF/>
                     ACCESS is available to registered users at 
                    <E T="03">http://access.trade.gov.</E>
                     The Preliminary Decision Memorandum is also available in the Central Records Unit, room 7046 of the main Department of Commerce building. In addition, a complete version of the Preliminary Decision Memorandum can be accessed directly at 
                    <E T="03">http://enforcement.trade.gov/frn/index.html.</E>
                     The signed Preliminary Decision Memorandum and the electronic version of the Preliminary Decision Memorandum are identical in content.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         “On November 24, 2014, Enforcement and Compliance changed the name of Enforcement and Compliance's AD and CVD Centralized Electronic Service System (“IA Access”) to AD and CVD Centralized Electronic Service System (“Access”). The Web site location was changed from 
                        <E T="03">http://iaaccess.trade.gov</E>
                         to 
                        <E T="03">http://access.trade.gov.</E>
                         The Final Rule changing the references to the Regulations can be found at 79 FR 69046 (November 20, 2014.”
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Preliminary Results of Review</HD>
                <P>The Department preliminarily determines that the following weighted-average dumping margins exist for the POR:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s75,16">
                    <TTITLE/>
                    <BOXHD>
                        <CHED H="1">Exporter</CHED>
                        <CHED H="1">
                            Weighted-average 
                            <LI>dumping margin</LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Shaoxing Xiangyu Green Packing Co., Ltd</ENT>
                        <ENT>35.10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tianjin Wanhua Co., Ltd</ENT>
                        <ENT>67.69</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Disclosure and Public Comment</HD>
                <P>
                    The Department intends to disclose calculations performed for these preliminary results to the parties within five days of the date of publication of this notice in accordance with 19 CFR 351.224(b). Interested parties may submit case briefs no later than 30 days after the date of publication of these preliminary results of review.
                    <SU>3</SU>
                    <FTREF/>
                     Rebuttal briefs may be filed no later than five days after case briefs are filed and may respond only to arguments raised in the case briefs.
                    <SU>4</SU>
                    <FTREF/>
                     A table of contents, list of authorities used and an executive summary of issues should accompany any briefs submitted to the Department. This summary should be limited to five pages total, including footnotes.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.309(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.309(d).
                    </P>
                </FTNT>
                <P>
                    Interested parties who wish to request a hearing must submit a written request to the Assistant Secretary for Enforcement &amp; Compliance, U.S. Department of Commerce, within 30 days after the date of publication of this notice.
                    <SU>5</SU>
                    <FTREF/>
                     Requests should contain the party's name, address, and telephone number, the number of participants, and a list of the issues to be discussed. Oral argument presentations will be limited to issues raised in the briefs. If a request for a hearing is made, the Department intends to hold the hearing at the U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230, at a date and time to be determined.
                    <SU>6</SU>
                    <FTREF/>
                     Parties should confirm by telephone the date, time, and location of the hearing two days before the scheduled date.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.310(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.310(d).
                    </P>
                </FTNT>
                <P>
                    All submissions, with limited exceptions, must be filed electronically using ACCESS.
                    <SU>7</SU>
                    <FTREF/>
                     An electronically filed document must be received successfully in its entirety by the Department's electronic records system, ACCESS, by 5 p.m. Eastern Time (“ET”) on the due date. Documents excepted from the electronic submission requirements must be filed manually (
                    <E T="03">i.e.,</E>
                     in paper form) with the APO/Dockets Unit in Room 1870 and stamped with the date and time of receipt by 5 p.m. ET on the due date.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See, generally,</E>
                         19 CFR 351.303.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Antidumping and Countervailing Duty Proceedings: Electronic Filing Procedures; Administrative Protective Order Procedures,</E>
                         76 FR 39263 (July 6, 2011).
                    </P>
                </FTNT>
                <P>The Department intends to issue the final results of this administrative review, which will include the results of its analysis of issues raised in any briefs, within 120 days of publication of these preliminary results, pursuant to section 751(a)(3)(A) of the Act.</P>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    Upon issuance of the final results of this review, the Department will determine, and CBP shall assess, antidumping duties on all appropriate 
                    <PRTPAGE P="72168"/>
                    entries covered by this review.
                    <SU>9</SU>
                    <FTREF/>
                     The Department intends to issue assessment instructions to CBP 15 days after the publication date of the final results of this review. Where either a respondent's weighted-average dumping margin is zero or 
                    <E T="03">de minimis,</E>
                     or an importer-specific assessment rate is zero or 
                    <E T="03">de minimis,</E>
                     we will instruct CBP to liquidate the appropriate entries without regard to antidumping duties. For any individually examined respondent and its importer(s) where neither of those situations is the case, in the final results of this review we will calculate an importer-specific per-unit assessment rate by dividing the total dumping margins for reviewed sales to the importer by the total sales quantity associated with those sales.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.212(b)(1).
                    </P>
                </FTNT>
                <P>
                    On October 24, 2011, the Department announced a refinement to its assessment practice in NME antidumping duty cases.
                    <SU>10</SU>
                    <FTREF/>
                     Pursuant to this refinement in practice, for merchandise that was not reported in the U.S. sales databases submitted by an exporter individually examined during this review, but that entered under the case number of that exporter (
                    <E T="03">i.e.,</E>
                     at the individually-examined exporter's cash deposit rate), the Department will instruct CBP to liquidate such entries at the PRC-wide rate. Additionally, pursuant to this refinement, if the Department determines that an exporter under review had no shipments of the subject merchandise, any suspended entries that entered under that exporter's case number will be liquidated at the PRC-wide rate.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Non-Market Economy Antidumping Proceedings: Assessment of Antidumping Duties,</E>
                         76 FR 65694 (October 24, 2011), for a full discussion of this practice.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following cash deposit requirements will be effective upon publication of the final results of this administrative review for shipments of the subject merchandise from the PRC entered, or withdrawn from warehouse, for consumption on or after the publication date, as provided by sections 751(a)(2)(C) of the Act: (1) For the exporters listed above, the cash deposit rate will be equal to the weighted-average dumping margin established in the final results of this review (except, if the rate is zero or 
                    <E T="03">de minimis,</E>
                     then the cash deposit rate will be zero for that exporter); (2) for previously investigated or reviewed PRC and non-PRC exporters not listed above that have separate rates, the cash deposit rate will continue to be the exporter-specific rate published for the most recently completed segment of this proceeding; (3) for all PRC exporters of subject merchandise which have not been found to be entitled to a separate rate, the cash deposit rate will be the rate for the PRC-wide entity, 76.72 percent; and (4) for all non-PRC exporters of subject merchandise which have not received their own rate, the cash deposit rate will be the rate applicable to the PRC exporter that supplied that non-PRC exporter. These deposit requirements, when imposed, shall remain in effect until further notice.
                </P>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice also serves as a preliminary reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Department's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <P>We are issuing and publishing these results in accordance with sections 751(a)(1) and 777(i)(1) of the Act and 19 CFR 351.213.</P>
                <SIG>
                    <DATED>Dated: November 28, 2014.</DATED>
                    <NAME>Ronald K. Lorentzen,</NAME>
                    <TITLE>Acting Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix—List of Topics Discussed in the Preliminary Decision Memorandum</HD>
                <EXTRACT>
                    <P>1. Summary</P>
                    <P>2. Background</P>
                    <P>3. Scope of the Order</P>
                    <P>4. Preliminary Determination of No Shipments</P>
                    <P>5. Selection of Respondents</P>
                    <P>6. Non-Market Economy Country</P>
                    <P>7. Separate Rate</P>
                    <P>8. Surrogate Country</P>
                    <P>9. Date of Sale</P>
                    <P>10. Fair Value Comparisons</P>
                    <P>11. U.S. Price</P>
                    <P>12. Normal Value</P>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28579 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-580-809]</DEPDOC>
                <SUBJECT>Circular Welded Non-Alloy Steel Pipe From the Republic of Korea: Preliminary Results and Partial Rescission of Antidumping Duty Administrative Review; 2012-2013</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Commerce (the Department) is conducting an administrative review of the antidumping duty order on circular welded non-alloy steel pipe (CWP) from the Republic of Korea (Korea).
                        <SU>1</SU>
                        <FTREF/>
                         The period of review (POR) is November 1, 2012, through October 31, 2013. This review covers eight producers or exporters of the subject merchandise, Husteel Co., Ltd. (Husteel), Hyundai HYSCO (HYSCO), Dongbu Steel Co., Ltd., SeAH Steel Corporation, A-JU Besteel Co., Ltd., Kumkang Industrial Co., Ltd., Nexteel Co., Ltd., and Union Steel Co., Ltd. We preliminarily find that Husteel and HYSCO have made sales of the subject merchandise at prices below normal value. We are rescinding this review for the remaining six producers or exporters. Interested parties are invited to comment on these preliminary results.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews and Request for Revocation in Part,</E>
                             78 FR 79392 (December 30, 2013).
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         December 5, 2014.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jennifer Meek or Joseph Shuler, AD/CVD Operations, Office I, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington DC 20230; telephone (202) 482-2778 or (202) 482-1293, respectively.</P>
                    <HD SOURCE="HD1">Scope of the Order</HD>
                    <P>
                        The merchandise subject to the order is circular welded non-alloy steel pipe and tube. The product is currently classifiable under the following Harmonized Tariff Schedule of the United States (HTSUS) numbers: 7306.30.1000, 7306.30.5025, 7306.30.5032, 7306.30.5040, 7306.30.5055, 7306.30.5085, and 7306.30.5090. Although the HTSUS numbers are provided for convenience and customs purposes, the written 
                        <PRTPAGE P="72169"/>
                        product description remains dispositive.
                        <SU>2</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             For a full description of the scope of the order, see the Memorandum from Gary Taverman, Associate Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations, to Ronald K. Lorentzen, Acting Assistant Secretary for Enforcement and Compliance, “Decision Memorandum for the Preliminary Results of Antidumping Duty Administrative Review: Circular Welded Non-Alloy Steel Pipe from the Republic of Korea: 2012-2013” (Preliminary Decision Memorandum), dated concurrently with these results and hereby adopted by this notice.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Partial Rescission of Administrative Review</HD>
                    <P>
                        Pursuant to 19 CFR 351.213(d)(1), we are rescinding this administrative review with respect to the following parties because the review requests were timely withdrawn: Dongbu Steel Co., Ltd., SeAH Steel Corporation, A-JU Besteel Co., Ltd., Kumkang Industrial Co., Ltd., Nexteel Co., Ltd., and Union Steel Co., Ltd.
                        <SU>3</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">See</E>
                             Letter from Wheatland Tube Company (Wheatland) to the Department, “Circular Welded Non-Alloy Steel Pipe from Republic of Korea/Partial Withdrawal of Request for Administrative Review,” dated March 31, 2014 and Letter from United States Steel Corporation (U.S. Steel) to the Department, “Circular Welded Non-Alloy Steel Pipe from Korea,” dated March 31, 2014.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Methodology</HD>
                    <P>The Department has conducted this review in accordance with section 751(a)(2) of the Tariff Act of 1930, as amended (the Act). Constructed export price is calculated in accordance with section 772 of the Act. Normal value is calculated in accordance with section 773 of the Act.</P>
                    <P>
                        For a full description of the methodology underlying our conclusions, 
                        <E T="03">see</E>
                         the Preliminary Decision Memorandum. The Preliminary Decision Memorandum is a public document and is on file electronically 
                        <E T="03">via</E>
                         Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS).
                        <SU>4</SU>
                        <FTREF/>
                         ACCESS is available to registered users at 
                        <E T="03">http://access.trade.gov,</E>
                         and is available to all parties in the Central Records Unit, Room 7046 of the main Department of Commerce building. In addition, a complete version of the Preliminary Decision Memorandum can be accessed directly at 
                        <E T="03">http://trade.gov/enforcement.</E>
                         The signed Preliminary Decision Memorandum and the electronic versions of the Preliminary Decision Memorandum are identical in content.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             On November 24, 2014, Enforcement and Compliance changed the name of Enforcement and Compliance's AD and CVD Centralized Electronic Service System (IA ACCESS) to AD and CVD Centralized Electronic Service System (ACCESS). The Web site location was changed from 
                            <E T="03">http://iaaccess.trade.gov</E>
                             to 
                            <E T="03">http://access.trade.gov.</E>
                             The Final Rule changing the references to the Regulations can be found at 79 FR 69046 (November 20, 2014).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Preliminary Results of the Review</HD>
                    <P>As a result of this review, we preliminarily determine that the following weighted-average dumping margins exist for the respondents for the period November 1, 2012, through October 31, 2013.</P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s75,16">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Producer or exporter </CHED>
                            <CHED H="1">
                                Weighted-average
                                <LI>dumping margin </LI>
                                <LI>(percent)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Husteel Co., Ltd</ENT>
                            <ENT>1.15</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hyundai HYSCO</ENT>
                            <ENT>2.02</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Disclosure and Public Comment</HD>
                    <P>
                        The Department intends to disclose to interested parties the calculations performed in connection with these preliminary results within five days of the date of publication of this notice.
                        <SU>5</SU>
                        <FTREF/>
                         Interested parties may submit case briefs no later than 30 days after the date of publication of the preliminary results.
                        <SU>6</SU>
                        <FTREF/>
                         Rebuttal briefs, limited to the issues raised in the case briefs, may be filed no later than five days after the submission of case briefs.
                        <SU>7</SU>
                        <FTREF/>
                         Parties who submit case briefs or rebuttal briefs in this proceeding are encouraged to submit with each argument: (1) A statement of the issue; (2) a brief summary of the argument; and (3) a table of authorities.
                        <SU>8</SU>
                        <FTREF/>
                         All case and rebuttal briefs must be filed electronically using ACCESS, and must also be served on interested parties.
                        <SU>9</SU>
                        <FTREF/>
                         An electronically filed document must be received successfully in its entirety by the Department's electronic records system, ACCESS, by 5:00 p.m. Eastern Standard Time on the date that the document is due. Executive summaries should be limited to five pages total, including footnotes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.224(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.309(c)(1)(ii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.309(d)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.309(c)(2) and (d)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.303(f).
                        </P>
                    </FTNT>
                    <P>
                        Interested parties who wish to request a hearing, or to participate if one is requested, must submit a written request to the Assistant Secretary for Enforcement and Compliance, U.S. Department of Commerce, using Enforcement and Compliance's ACCESS system within 30 days of publication of this notice.
                        <SU>10</SU>
                        <FTREF/>
                         Hearing requests should contain the party's name, address, and telephone number, the number of participants, and a list of the issues to be discussed. If a request for a hearing is made, we will inform parties of the scheduled date for the hearing which will be held at the U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230, at a time and location to be determined. Parties should confirm by telephone the date, time, and location of the hearing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See</E>
                             19 CFR 351.310(c).
                        </P>
                    </FTNT>
                    <P>Unless the deadline is extended pursuant to section 751(a)(2)(B)(iv) of the Act and 19 CFR 351.213(h)(2), the Department intends to issue the final results of this administrative review, including the results of our analysis of the issues raised by the parties in their case and rebuttal briefs, within 120 days after the publication of these preliminary results, pursuant to section 751(a)(3)(A) of the Act and 19 CFR 351.213(h)(1).</P>
                    <HD SOURCE="HD1">Assessment Rates</HD>
                    <P>
                        For Husteel and HYSCO, upon issuance of the final results, the Department shall determine, and U.S. Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries covered by this review. Both Husteel and HYSCO reported the name of the importer of record and the entered value for all of their sales to the United States during the POR. If Husteel and HYSCO's weighted-average dumping margins are not zero or 
                        <E T="03">de minimis</E>
                         (
                        <E T="03">i.e.,</E>
                         less than 0.50 percent) in the final results of this review, we will calculate importer-specific assessment rates on the basis of the ratio of the total amount of dumping calculated for each importer's examined sales and the total entered value of those sales in accordance with 19 CFR 351.212(b)(1).
                    </P>
                    <P>
                        We will instruct CBP to assess antidumping duties on all appropriate entries covered by this review when the importer-specific assessment rate calculated in the final results of this review is not zero or 
                        <E T="03">de minimis.</E>
                         Where either the respondent's weighted-average dumping margin is zero or 
                        <E T="03">de minimis,</E>
                        <SU>11</SU>
                        <FTREF/>
                         or an importer-specific assessment rate is zero or 
                        <E T="03">de minimis,</E>
                         we will instruct CBP to liquidate the appropriate entries without regard to antidumping duties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">See Antidumping Proceedings: Calculation of the Weighted-Average Dumping Margin and Assessment Rate in Certain Antidumping Duty Proceedings; Final Modification,</E>
                             77 FR 8101, 8102 (February 14, 2012).
                        </P>
                    </FTNT>
                    <P>
                        The Department clarified its “automatic assessment” regulation on May 6, 2003. This clarification will apply to entries of subject merchandise during the POR produced by Husteel and HYSCO for which they did not know its merchandise was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the all-others rate 
                        <PRTPAGE P="72170"/>
                        if there is no rate for the intermediate company(ies) involved in the transaction. For a full discussion of this clarification, 
                        <E T="03">see Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties,</E>
                         68 FR 23954 (May 6, 2003).
                    </P>
                    <P>For Husteel and HYSCO, we intend to issue instructions to CBP 15 days after publication of the final results of this review.</P>
                    <P>For the companies for which the review has been rescinded, antidumping duties shall be assessed at rates equal to the rates for the cash deposit of estimated antidumping duties required at the time of entry, or withdrawal from warehouse, for consumption, in accordance with 19 CFR 351.212(c)(1)(i). The Department intends to issue appropriate assessment instructions to CBP 15 days after the date of publication of this notice.</P>
                    <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                    <P>
                        The following cash deposit requirements for estimated antidumping duties will be effective upon publication of the notice of final results of administrative review for all shipments of CWP from Korea entered, or withdrawn from warehouse, for consumption on or after the date of publication as provided by section 751(a)(2) of the Act: (1) The cash deposit rate for HYSCO and Husteel will be equal to the weighted-average dumping margins established in the final results of this administrative review; (2) for merchandise exported by producers or exporters not covered in this review but covered in a prior completed segment of the proceeding, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, a prior review, or the original investigation but the producer has been covered in a prior complete segment of this proceeding, the cash deposit rate will be the rate established for the most recent period for the producer of the merchandise; (4) the cash deposit rate for all other producers or exporters will continue to be 4.80 percent, the “all others” rate established in the order.
                        <SU>12</SU>
                        <FTREF/>
                         These cash deposit requirements, when imposed, shall remain in effect until further notice.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See Notice of Antidumping Duty Orders: Certain Circular Welded Non-Alloy Steel Pipe from Brazil, the Republic of Korea (Korea), Mexico, and Venezuela, and Amendment to Final Determination of Sales at Less Than Fair Value: Certain Circular Welded Non-Alloy Steel Pipe from Korea,</E>
                             57 FR 49453 (November 2, 1992).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Notification to Importers</HD>
                    <P>This notice serves as a preliminary reminder and, with respect to companies which we rescind in part as a final reminder, to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                    <P>The Department is issuing and publishing these results in accordance with sections 751(a)(1) and 777(i)(1) of the Act.</P>
                    <SIG>
                        <DATED>Dated: November 28, 2014.</DATED>
                        <NAME>Ronald K. Lorentzen,</NAME>
                        <TITLE>Acting Assistant Secretary for Enforcement and Compliance.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Appendix</HD>
                    <EXTRACT>
                        <HD SOURCE="HD1">List of Topics Discussed in the Preliminary Decision Memorandum</HD>
                        <FP SOURCE="FP-2">I. Summary</FP>
                        <FP SOURCE="FP-2">II. Background</FP>
                        <FP SOURCE="FP-2">III. Scope of Order</FP>
                        <FP SOURCE="FP-2">IV. Rescission of Review In Part</FP>
                        <FP SOURCE="FP-2">V. Discussion of the Methodology</FP>
                        <FP SOURCE="FP1-2">1. Comparison to Normal Value</FP>
                        <FP SOURCE="FP1-2">2. Product Comparisons</FP>
                        <FP SOURCE="FP1-2">3. Treatment of Grade as a Physical Characteristic</FP>
                        <FP SOURCE="FP1-2">4. Level of Trade/Constructed Export Price Offset</FP>
                        <FP SOURCE="FP1-2">5. Constructed Export Price</FP>
                        <FP SOURCE="FP1-2">6. Normal Value</FP>
                        <FP SOURCE="FP1-2">7. Currency Conversion</FP>
                        <FP SOURCE="FP-2">VI. Recommendation</FP>
                    </EXTRACT>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28580 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-552-801]</DEPDOC>
                <SUBJECT>Certain Frozen Fish Fillets From the Socialist Republic of Vietnam: Rescission of Antidumping Duty New Shipper Review; 2013-2014</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In response to a request from BASA Joint Stock Company (“BASACO”), the Department of Commerce (“Department”) initiated a new shipper review of the antidumping duty order on certain frozen fish fillets from the Socialist Republic of Vietnam (“Vietnam”) covering the period August 1, 2013, through July 31, 2014.
                        <SU>1</SU>
                        <FTREF/>
                         On November 4, 2014, BASACO timely withdrew its request for a new shipper review. Accordingly, the Department is rescinding the new shipper review with respect to BASACO.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See Certain Frozen Fish Fillets from the Socialist Republic of Vietnam: Initiation of Antidumping Duty New Shipper Review; 2013-2014,</E>
                             79 FR 59476 (October 2, 2014) (“
                            <E T="03">Initiation Notice</E>
                            ”).
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         December 5, 2014.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Alexander Montoro, AD/CVD Operations, Office V, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-0238.</P>
                    <HD SOURCE="HD1">Rescission of New Shipper Review</HD>
                    <P>
                        On September 24, 2014, the Department initiated a new shipper review of BASACO.
                        <SU>2</SU>
                        <FTREF/>
                         On November 4, 2014, BASACO withdrew its new shipper review request.
                        <SU>3</SU>
                        <FTREF/>
                         19 CFR 351.214(f)(1) provides that the Department may rescind a new shipper review if the party that requested the review withdraws its request for review within 60 days of the date of publication of the notice of initiation of the requested review in the 
                        <E T="04">Federal Register</E>
                        . Because BASACO timely withdrew its request for a new shipper review (
                        <E T="03">i.e.,</E>
                         33 days after the date of publication of the notice of initiation of the requested review), the Department is rescinding the new shipper review of the antidumping duty order on certain frozen fish fillets from Vietnam with respect to BASACO. Consequently, BASACO will remain part of the Vietnam-wide entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">See</E>
                             letter from BASACO entitled “Withdrawal of Request for New Shipper Review: Certain Frozen Fish Fillets from the Socialist Republic of Vietnam: Review Period—8/1/13-7/31/14,” dated November 4, 2014.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Assessment</HD>
                    <P>
                        Because BASACO remains part of the Vietnam-wide entity, it remains under review in the ongoing administrative review of the antidumping duty order of certain frozen fish fillets from Vietnam covering the period August 1, 2013, to July 31, 2014.
                        <SU>4</SU>
                        <FTREF/>
                         Therefore, the Department will not order liquidation of entries for BASACO. The Department intends to issue liquidation instructions for the Vietnam-wide entity, which will cover any entries by BASACO, 15 days after publication of the final results of the administrative review covering the 
                        <PRTPAGE P="72171"/>
                        period August 1, 2013, to July 31, 2014 in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                             79 FR 58729, 58731 (Sept. 30, 2014).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Cash Deposit</HD>
                    <P>
                        The Department will notify U.S. Customs and Border Protection (“CBP”) that bonding is no longer permitted to fulfill security requirements for subject merchandise produced and exported by BASACO that is entered, or withdrawn from warehouse, for consumption in the United States on or after the publication of this rescission notice in the 
                        <E T="04">Federal Register</E>
                        . The Department will notify CBP that a cash deposit of 2.11 U.S. Dollars per kilogram should be collected for all shipments of subject merchandise by BASACO entered, or withdrawn from warehouse, for consumption in the United States on or after the publication of this rescission notice.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">See Certain Frozen Fish Fillets from the Socialist Republic of Vietnam: Amended Final Results of Antidumping Duty Administrative Review; 2011-2012,</E>
                             79 FR 37714, 37715 (July 2, 2014).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Notifications to Interested Parties</HD>
                    <P>This notice serves as a reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                    <P>This notice also serves as a reminder to parties subject to administrative protective order (“APO”) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a). Timely written notification of the return or destruction of APO materials, or conversion to judicial protective order, is hereby requested. Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                    <P>We are issuing and publishing this rescission and notice in accordance with sections 751(a)(2)(B) and 777(i) of the Act and 19 CFR 351.214(f)(3).</P>
                    <SIG>
                        <DATED>Dated: November 20, 2014.</DATED>
                        <NAME>Gary Taverman,</NAME>
                        <TITLE>Associate Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28583 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N"> COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED</AGENCY>
                <SUBJECT>Procurement List; Proposed Additions and Deletion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed additions to and deletion from the Procurement List.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Committee is proposing to add products and services to the Procurement List that will be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities and delete a service previously provided by such agency.</P>
                    <P>
                        <E T="03">Comments Must Be Received on or Before:</E>
                         1/5/2015.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, 1401 S. Clark Street, Suite 10800, Arlington, Virginia 22202-4149.</P>
                </ADD>
                <PREAMHD>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION OR TO SUBMIT COMMENTS CONTACT:</HD>
                    <P>
                        Barry S. Lineback, Telephone: (703) 603-7740, Fax: (703) 603-0655, or email 
                        <E T="03">CMTEFedReg@AbilityOne.gov.</E>
                    </P>
                </PREAMHD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published pursuant to 41 U.S.C. 8503(a)(2) and 41 CFR 51-2.3. Its purpose is to provide interested persons an opportunity to submit comments on the proposed actions.</P>
                <HD SOURCE="HD1">Additions</HD>
                <P>If the Committee approves the proposed additions, the entities of the Federal Government identified in this notice will be required to procure the products and services listed below from nonprofit agencies employing persons who are blind or have other severe disabilities.</P>
                <P>The following products and services are proposed for addition to the Procurement List for production by the nonprofit agencies listed:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Products</HD>
                    <HD SOURCE="HD2">Toner Cartridge, Remanufactured, Lexmark</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-0212—Optra T630/T632/T634 Series Compatible.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-1010—Optra T644/X644/X646 Series Compatible.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-1060—E260/E360/E460/E462 Series Compatible.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-1061—E360/E460/E462 Series Compatible.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-1063—Multiple T &amp; X Series, Compatible, 25,000 page.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         7510-00-NSH-1064—Multiple T &amp; X Compatible, 36,000 page.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         TRI Industries NFP, Chicago, IL.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         General Services Administration, New York, NY.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Coverage:</E>
                         A-List for the Total Government Requirement as aggregated by the General Services Administration, New York, NY.
                    </FP>
                    <HD SOURCE="HD1">Services</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Locations:</E>
                         Custodial Service.
                    </FP>
                    <FP SOURCE="FP1-2">U.S. Navy, Naval Air Station Oceana and Naval Auxiliary  Landing Field Fentress, U.S. Navy, Dam Neck Annex, 1750 Tomcat Boulevard, Virginia Beach, VA.</FP>
                    <FP SOURCE="FP1-2">U.S. Navy, Naval Weapons Station, U.S. Navy, Cheatham Annex, 160 Main Road, Yorktown, VA.</FP>
                    <FP SOURCE="FP1-2">U.S. Navy, Norfolk Naval Shipyard and St. Juliens Creek Annex, Cassin Ave and Hitchcock Street, Portsmouth, VA.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Didlake, Inc., Manassas, VA.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         Dept of the Navy, Naval FAC Engineering CMD MID LANT, Norfolk, VA.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Location:</E>
                         Operations and Maintenance.
                    </FP>
                    <FP SOURCE="FP1-2">Bureau of Engraving and Printing, Western Currency Facility,  9000 Blue Mound Road, Fort Worth, TX.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         PRIDE Industries, Roseville, CA.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         Dept of Treasury, Bureau of Engraving and Printing, Washington, DC.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Locations:</E>
                         Facility Support Service.
                    </FP>
                    <FP SOURCE="FP1-2">Department of Homeland Security, ICE, Enforcement and Removal Operations Buffalo Command Center, 205 Oak Street, Batavia, NY.</FP>
                    <FP SOURCE="FP1-2">Buffalo Federal Detention Facility, 4250 Federal Drive, Batavia, NY.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         New Dynamics Corporation, Middletown, NY.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         U.S. Immigration and Customs Enforcement, Detention Management—DC Office, Washington, DC.
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">Deletion</HD>
                <P>The following service is proposed for deletion from the Procurement List:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Service</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Location:</E>
                         Mess Attendant Service.
                    </FP>
                    <FP SOURCE="FP1-2">121st Air Refueling Wing, 7370 Minuteman Way, Redtail Dining Facility, Bldg. 917, Columbus, OH.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         First Capital Enterprises, Inc., Chillicothe, OH.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         Dept of the Army, W7NU USPFO ACTIVITY OH ARNG, Columbus, OH.
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Barry S. Lineback,</NAME>
                    <TITLE>Director, Business Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28563 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S"> COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED</AGENCY>
                <SUBJECT>Procurement List; Addition</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="72172"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Addition to the Procurement List.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action adds a product to the Procurement List that will be furnished by the nonprofit agency employing persons who are blind or have other severe disabilities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         1/5/2015.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, 1401 S. Clark Street, Suite 10800, Arlington, Virginia 22202-4149.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Barry S. Lineback, Telephone: (703) 603-7740, Fax: (703) 603-0655, or email 
                        <E T="03">CMTEFedReg@AbilityOne.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Addition</HD>
                <P>On 10/31/2014 (79 FR 64754), the Committee for Purchase From People Who Are Blind or Severely Disabled published notice of proposed addition to the Procurement List.</P>
                <P>After consideration of the material presented to it concerning capability of qualified nonprofit agency to provide the product and impact of the addition on the current or most recent contractors, the Committee has determined that the product listed below is suitable for procurement by the Federal Government under 41 U.S.C. 8501-8506 and 41 CFR 51-2.4.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification</HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were:</P>
                <P>1. The action will not result in any additional reporting, recordkeeping or other compliance requirements for small entity other than the small organization that will furnish the product to the Government.</P>
                <P>2. The action will result in authorizing small entity to furnish the product to the Government.</P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 8501-8506) in connection with the product proposed for addition to the Procurement List.</P>
                <HD SOURCE="HD1">End of Certification</HD>
                <P>Accordingly, the following product is added to the Procurement List:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Product</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">NSN:</E>
                         8520-01-432-2618—Hand Soap, Liquid, Biobased.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         TRI Industries NFP, Chicago, IL.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         General Services Administration, Fort Worth, TX.
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Coverage:</E>
                         A-List for the Total Government Requirement as aggregated by the General Services Administration, Fort Worth, TX.
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Barry S. Lineback,</NAME>
                    <TITLE>Director, Business Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28567 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[ER-FRL-9018-3]</DEPDOC>
                <SUBJECT>Environmental Impact Statements; Notice of Availability</SUBJECT>
                <P>
                    <E T="03">Responsible Agency:</E>
                     Office of Federal Activities, General Information (202) 564-7146 or 
                    <E T="03">http://www.epa.gov/compliance/nepa/</E>
                    .
                </P>
                <FP SOURCE="FP-1">Weekly receipt of Environmental Impact Statements</FP>
                <FP SOURCE="FP-1">Filed 11/24/2014 Through 11/28/2014.</FP>
                <FP SOURCE="FP-1">Pursuant to 40 CFR 1506.9.</FP>
                <P>
                    <E T="03">Notice</E>
                    : Section 309(a) of the Clean Air Act requires that EPA make public its comments on EISs issued by other Federal agencies. EPA's comment letters on EISs are available at: 
                    <E T="03">http://www.epa.gov/compliance/nepa/eisdata.html</E>
                    .
                </P>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140339, Draft EIS, BLM, NV</E>
                    , Carson City District Draft Resource Management Plan, Comment Period Ends: 03/27/2015, Contact: Colleen Sievers 775-885-6168,
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140340, Final EIS, USFS, SC</E>
                    , Chester County Stream and Riparian/Restoration.
                </FP>
                <P>
                    <E T="03">Enhancement Project, Review Period Ends</E>
                    : 01/05/2015, Contact: Jim Knibbs 803-561-4078.
                </P>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140341, Final EIS, USFWS, CA</E>
                    , Maricopa Sun Solar Complex Habitat Conservation Plan, Review Period Ends: 01/05/2015, Contact: Mike Thomas 916-414-6600.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140342, Final EIS, USFS, WY</E>
                    , Teckla-Osage-Rapid City 230 kV Transmission Line Project, Review Period Ends: 01/05/2015, 
                    <E T="03">Contact:</E>
                     Edward Fischer 605-673-9207.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140343, Final EIS, NPS, OH</E>
                    , Cuyahoga Valley National Park, White-tailed Deer Management Plan, Review Period Ends: 01/05/2015, 
                    <E T="03">Contact:</E>
                     Craig Kenkel 330-657-2752.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140344, Final EIS, FHWA, TX</E>
                    , US 181 Harbor Bridge, Review Period Ends: 01/05/2015, Contact: Gregory S. Punske, 512-536-5960.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140345, Final EIS, FEMA, CA</E>
                    , East Bay Hills, Final Hazardous Fire Risk Reduction, Review Period Ends: 01/07/2015, 
                    <E T="03">Contact:</E>
                     Alessandro Amaglio 510-627-7222.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140346, Final EIS, USDA, AZ</E>
                    , Four-Forest Restoration Initiative, Coconino and Kaibab National Forests, Review Period Ends: 01/20/2015, Contact: Annette Fredette, 928-226-4684.
                </FP>
                <HD SOURCE="HD1">Amended Notices</HD>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140275, Final EIS, FHWA, AZ</E>
                    , South Mountain Freeway (Loop 202), Review Period Ends: 12/26/2014, Contact: Alan Hansen, 602-382-8964. Revision to FR Notice Published 09/24/2014; Extending Review Period from 11/25/2014 to 12/26/2014
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140297, Draft EIS, USFS, OR</E>
                    , Kahler Dry Forest Restoration Project, Comment Period Ends: 12/29/2014, Contact: John Evans, 541-278-3869. Revision to FR Notice Published 09/24/2014; Extending Review Period from 11/25/2014 to 12/26/2014
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140298, Draft EIS, USACE, WA</E>
                    , Puget Sound Nearshore Ecosystem Restoration, 
                    <E T="03">Comment Period Ends:</E>
                     01/08/2015, Contact: Nancy Gleason 206-764-6577. Revision to FR Notice Published 11/28/2014; Correcting the Extended Comment Period to 01/08/2015.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 20140317, Final EIS, USACE, AL</E>
                    , Update of the Water Control Manual for the Alabama-Coosa-Tallapoosa River Basin in Georgia and Alabama, Review Period Ends: 02/05/2015, Contact: Lewis Sumner 251-694-3857. Revision to FR Notice Published 11/07/2014; Extending Review Period from 12/08/2014 to 02/05/2015.
                </FP>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Cliff Rader,</NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28576 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EXPORT-IMPORT BANK</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of an Open Meeting of the Board of Directors of the Export-Import Bank of the United States.</P>
                </ACT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND PLACE:</HD>
                    <P>Thursday, December 11, 2014 at 3:00 p.m. The meeting will be held at Ex-Im Bank in Room 1126, 811 Vermont Avenue NW., Washington, DC 20571.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">OPEN AGENDA ITEMS:</HD>
                    <P>Item No. 1 Ex-Im Bank Advisory Committee for 2015 (New Members)</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PUBLIC PARTICIPATION:</HD>
                    <P>The meeting will be open to public observation for Item No. 1 only.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">FURTHER INFORMATION:</HD>
                    <P>
                        Members of the public who wish to attend the meeting 
                        <PRTPAGE P="72173"/>
                        should call Joyce Stone, Office of the Secretary, 811 Vermont Avenue NW., Washington, DC 20571 (202) 565-3336 by close of business Tuesday, December 9, 2014.
                    </P>
                </PREAMHD>
                <SIG>
                    <NAME>Lloyd Ellis,</NAME>
                    <TITLE>Program Specialist, Office of the General Counsel.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28662 Filed 12-3-14; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FARM CREDIT ADMINISTRATION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Farm Credit Administration.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to the Government in the Sunshine Act, of the regular meeting of the Farm Credit Administration Board (Board).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date and Time:</E>
                         The regular meeting of the Board will be held at the offices of the Farm Credit Administration in McLean, Virginia, on December 11, 2014, from 9:00 a.m. until such time as the Board concludes its business.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dale L. Aultman, Secretary to the Farm Credit Administration Board, (703) 883-4009, TTY (703) 883-4056.</P>
                </FURINF>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Farm Credit Administration, 1501 Farm Credit Drive, McLean, Virginia 22102-5090. Submit attendance requests via email to 
                        <E T="03">VisitorRequest@FCA.gov.</E>
                         See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for further information about attendance requests.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Parts of this meeting of the Board will be open to the public (limited space available), and parts will be closed to the public. Please send an email to 
                    <E T="03">VisitorRequest@FCA.gov</E>
                     at least 24 hours before the meeting. In your email include: Name, postal address, entity you are representing (if applicable), and telephone number. You will receive an email confirmation from us. Please be prepared to show a photo identification when you arrive. If you need assistance for accessibility reasons, or if you have any questions, contact Dale L. Aultman, Secretary to the Farm Credit Administration Board, at (703) 883-4009. The matters to be considered at the meeting are:
                </P>
                <HD SOURCE="HD1">Open Session</HD>
                <HD SOURCE="HD2">A. Approval of Minutes</HD>
                <FP SOURCE="FP-1">• November 13, 2014</FP>
                <HD SOURCE="HD2">B. New Business</HD>
                <FP SOURCE="FP-1">• Organization, Mergers, Consolidations and Charter Amendments of Banks or Associations—Proposed Rule</FP>
                <HD SOURCE="HD2">C. Reports</HD>
                <FP SOURCE="FP-1">• Quarterly Report on Economic Conditions and Fcs Conditions</FP>
                <FP SOURCE="FP-1">• Semi-Annual Report on Office of Examination Operations</FP>
                <HD SOURCE="HD1">Closed Session*</HD>
                <HD SOURCE="HD2">Reports</HD>
                <FP SOURCE="FP-1">• Office of Examination Supervisory and Oversight Activities Report</FP>
                <EXTRACT>
                    <FP>* Session Closed-Exempt pursuant to 5 U.S.C. 552b(c)(8) and (9).</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Dale L. Aultman,</NAME>
                    <TITLE>Secretary, Farm Credit Administration Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28651 Filed 12-3-14; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 6705-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-0508; OMB 3060-0800; and OMB 3060-1058]</DEPDOC>
                <SUBJECT>Information Collections Being Reviewed by the Federal Communications Commission</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the Federal Communications Commission (FCC or Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collections. Comments are requested concerning: Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; the accuracy of the Commission's burden estimate; ways to enhance the quality, utility, and clarity of the information collected; ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and ways to further reduce the information collection burden on small business concerns with fewer than 25 employees. The FCC may not conduct or sponsor a collection of information unless it displays a currently valid OMB control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid OMB control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written PRA comments should be submitted on or before February 3, 2015. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email to 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">Cathy.Williams@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Cathy Williams at (202) 418-2918.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     3060-0508.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Parts 1 and 22 Reporting and Recordkeeping Requirements.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     Not applicable.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, Individuals or households, and State, Local or Tribal Governments.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     15,713 respondents; 15,713 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     15 minutes-10 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping requirement; On occasion, quarterly, and semi-annual reporting requirements.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection is contained in 47 U.S.C. 154, 222, 303, 309 and 332.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     4,894 hours.
                </P>
                <P>
                    <E T="03">Annual Cost Burden:</E>
                     $19,445,250.
                </P>
                <P>
                    <E T="03">Privacy Act Impact Assessment:</E>
                     Yes.
                </P>
                <P>
                    <E T="03">Nature and Extent of Confidentiality:</E>
                     There is no need for confidentiality with this collection of information. The information to be collected will be made available for public inspection. Applicants may request materials or information submitted to the Commission be given confidential treatment under 47 CFR 0.459 of the Commission's rules.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     Part 22 contains the technical and legal requirements for radio stations operating in the Public Mobile Services. The information collected is used to determine on a case-by-case basis, whether or not to grant licenses authorizing construction and operation of wireless telecommunications facilities to 
                    <PRTPAGE P="72174"/>
                    common carriers. Further, this information is used to develop statistics about the demand for various wireless licenses and/or the licensing process itself, and occasionally for rule enforcement purposes.
                </P>
                <P>This revised information collection reflects changes in rules applicable to Part 22 800 MHz Cellular Radiotelephone (“Cellular”) Service licensees and applicants, as adopted by the Commission in a Report and Order (“R&amp;O”) on November 7, 2014 (WT Docket No. 12-40; RM No. 11510; FCC 14-181). By the R&amp;O, the Commission eliminates or streamlines certain Cellular Service filing requirements, thereby reducing the information collection burdens for Cellular Service respondents.</P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     3060-0800.
                </P>
                <P>
                    <E T="03">Title:</E>
                     FCC Application for Assignments of Authorization and Transfers of Control: Wireless Telecommunications Bureau and/or Public Safety and Homeland Security Bureau.
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     FCC Form 603.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households; business or other for-profit entities; not-for-profit institutions; State, local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     2,447 respondents; 2,447 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     0.5-1.75 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping requirement; occasion reporting requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection of information is contained in 47 U.S.C. 4(i), 154(i), 303(r) and 309(j).
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     2,759 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $366,975.
                </P>
                <P>
                    <E T="03">Nature and Extent of Confidentiality:</E>
                     In general there is no need for confidentiality. On a case by case basis, the Commission may be required to withhold from disclosure certain information about the location, character, or ownership of a historic property, including traditional religious sites.
                </P>
                <P>
                    <E T="03">Privacy Act Impact Assessment:</E>
                     Yes.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     FCC Form 603 is a multi-purpose form used to apply for approval of assignment or transfer of control of licenses in the wireless services. The data collected on this form is used by the FCC to determine whether the public interest would be served by approval of the requested assignment or transfer. This form is also used to notify the Commission of consummated assignments and transfers of wireless and/or public safety licenses that have previously been consented to by the Commission or for which notification but not prior consent is required. This form is used by applicants/licensees in the Public Mobile Services, Personal Communications Services, General Wireless Communications Services, Private Land Mobile Radio Services, Broadcast Auxiliary Services, Broadband Radio Services, Educational Radio Services, Fixed Microwave Services, Maritime Services (excluding ships), and Aviation Services (excluding aircraft).
                </P>
                <P>The purpose of this form is to obtain information sufficient to identify the parties to the proposed assignment or transfer, establish the parties' basic eligibility and qualifications, classify the filing, and determine the nature of the proposed service. Various technical schedules are required along with the main form applicable to Auctioned Services, Partitioning and Disaggregation, Undefined Geographical Area Partitioning, Notification of Consummation or Request for Extension of Time for Consummation.</P>
                <P>This revised information collection reflects changes in rules applicable to Part 22 800 MHz Cellular Radiotelephone (“Cellular”) Service licensees and applicants, as adopted by the Commission in a Report and Order (“R&amp;O”) on November 7, 2014 (WT Docket No. 12-40; RM No. 11510; FCC 14-181). In addition to other rule revisions that do not affect this information collection, the Commission adopted a revised rule Section 22.948(a) to require the electronic submission of maps (in GIS format and PDF) when the Cellular applicant submits Form 603 to apply for Partitioning and Disaggregation. This requirement very slightly increases the total annual burden hours for this information collection. FCC Form 603 itself is not being revised.</P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     3060-1058.
                </P>
                <P>
                    <E T="03">Title:</E>
                     FCC Application or Notification for Spectrum Leasing Arrangement: Wireless Telecommunications Bureau and/or Public Safety and Homeland Security Bureau.
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     FCC Form 608.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities; not-for-profit institutions; State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     991 respondents; 991 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping requirement and on occasion reporting requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection of information is contained in 47 U.S.C. 151, 154(i), 154(j), 155, 158, 161, 301, 303(r), 308, 309, 310, 332 and 503.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     996 hours.
                </P>
                <P>
                    <E T="03">Annual Cost Burden:</E>
                     $1,282,075.
                </P>
                <P>
                    <E T="03">Nature and Extent of Confidentiality:</E>
                     In general there is no need for confidentiality. On a case by case basis, the Commission may be required to withhold from disclosure certain information about the location, character, or ownership of a historic property, including traditional religious sites.
                </P>
                <P>
                    <E T="03">Privacy Act Impact Assessment:</E>
                     Not applicable.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     FCC Form 608 is a multipurpose form. It is used to provide notification or request approval for any spectrum leasing arrangement (“Lease”) entered into between an existing licensee in certain wireless services and a spectrum lessee. This form also is required to notify or request approval for any spectrum subleasing arrangement (“Sublease”). The data collected on the form is used by the FCC to determine whether the public interest would be served by the Lease or Sublease. The form is also used to provide notification for any Private Commons Arrangement entered into between a licensee, lessee, or sublessee and a class of third-party users (as defined in Section 1.9080 of the Commission's Rules).
                </P>
                <P>
                    This revised information collection reflects changes in rules applicable to Part 22 800 MHz Cellular Radiotelephone (“Cellular”) Service licensees and applicants, as adopted by the Commission in a 
                    <E T="03">Report and Order</E>
                     (“
                    <E T="03">R&amp;O</E>
                    ”) on November 7, 2014 (WT Docket No. 12-40; RM No. 11510; FCC 14-181). In addition to other rule revisions that do not affect this information collection, the Commission adopted a revised rule Section 22.948(d) to require the electronic submission of maps (in GIS format and PDF) when the Cellular Service applicant submits Form 608.
                </P>
                <P>The requirement very slightly increases the total annual burden hours for this information collection. FCC Form 608 itself is not being revised.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene H. Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary, Office of Managing Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28581 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="72175"/>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <SUBJECT>Radio Broadcasting Services; AM or FM Proposals To Change The Community of License</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The following applicants filed AM or FM proposals to change the community of license: Marie H. Whitehead, Executrix, Station KWRW, Facility ID 17835, BPH-20140925ABH, From Rusk, TX, To Troup, TX; Top O Texas Educational Broadcasting Foundation, Station KASV, Facility ID 175031, BPED-20141104AEB, From Red River, NM, To Sanford, CO.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The agency must receive comments on or before February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Federal Communications Commission, 445 Twelfth Street SW., Washington, DC 20554.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Tung Bui, 202-418-2700.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The full text of these applications is available for inspection and copying during normal business hours in the Commission's Reference Center, 445 12th Street SW., Washington, DC 20554 or electronically via the Media Bureau's Consolidated Data Base System, 
                    <E T="03">http://svartifoss2.fcc.gov/prod/cdbs/pubacc/prod/cdbs_pa.htm.</E>
                </P>
                <P>
                    A copy of this application may also be purchased from the Commission's duplicating contractor, Best Copy and Printing, Inc., 445 12th Street SW., Room CY-B402, Washington, DC 20554, telephone 1-800-378-3160 or 
                    <E T="03">www.BCPIWEB.com.</E>
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>James D. Bradshaw,</NAME>
                    <TITLE>Deputy Chief, Audio Division, Media Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28509 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 14-15]</DEPDOC>
                <SUBJECT>Ngobros and Company Nigeria Limited v. Oceane Cargo Link, LLC, and Kingston Ansah, Individually; Notice of Filing of Complaint and Assignment</SUBJECT>
                <P>Notice is given that a complaint has been filed with the Federal Maritime Commission (Commission) by Ngobros and Company Nigeria Limited (NCNL), hereinafter “Complainant,” against Ocean Cargo Link, LLC (OCL) and Kingston Ansah, hereinafter “Respondents.” Complainant states that it is a Nigerian Limited Liability Company. Complainant alleges that Respondent OCL is a license ocean freight forwarder and non-vessel-operating common carrier and Respondent Kingston Ansah is a “member of OCL” and “has utilized OCL as his alter egos [sic].”</P>
                <P>Complainant alleges that Respondents have violated the Shipping Act, 46 U.S.C. 41102(c), in connection with the failed shipment of three vehicles from the United States to Nigeria. Complainant alleges that Respondent shipped the vehicles to the wrong destination resulting in the loss of the vehicles.</P>
                <P>Complainant seeks an Order holding that Respondents violated § 41102(c); an Order compelling Respondents “to make reparations to Complainant NCNL in the amount of $180,628.66 for shipping its goods intentionally or unintentionally to a wrong destination and abandoning it there”; “attorney's fees, interests and costs and expenses incurred in this matter”; and “such other and further relief as the Commission deems just and proper.”</P>
                <P>
                    The full text of the complaint can be found in the Commission's Electronic Reading Room at 
                    <E T="03">www.fmc.gov/14-15.</E>
                </P>
                <P>This proceeding has been assigned to the Office of Administrative Law Judges. The initial decision of the presiding officer in this proceeding shall be issued by December 1, 2015 and the final decision of the Commission shall be issued by June 1, 2016.</P>
                <SIG>
                    <NAME>Karen V. Gregory,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28538 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6730-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL MARITIME COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 14-16]</DEPDOC>
                <SUBJECT>Baltic Auto Shipping, Inc. v. Michael Hitrinov a/k/a Michael Khitrinov, Empire United Lines Co., Inc.; Notice of Filing of Complaint and Assignment</SUBJECT>
                <P>Notice is given that a complaint has been filed with the Federal Maritime Commission (Commission) by Baltic Auto Shipping, Inc., hereinafter “Complainant,” against Michael Hitrinov (“Hitrinov”) and Empire United Lines Co., Inc. (“EUL”), hereinafter “Respondents.” Complainant states that it is an Illinois corporation. Complainant alleges that Respondent EUL is a licensed NVOCC, and Respondent Hitrinov is “the sole principal and officer of EUL.”</P>
                <P>Complainant alleges that Respondents have violated the Shipping Act, 46 U.S.C. 41102, 41104, 40501, and 46 CFR part 515, in connection with shipment of over 4000 used automobiles over a five year period and charging rates “in excess of the amounts set forth in EUL's tariff.” Complainant alleges it “has sustained and continued to sustain injuries and damages in excess of $400,000.”</P>
                <P>Complainant seeks that Respondents “be required to answer the charges herein; that after due hearing, an order be made commanding said respondent to pay to Complainant by way of reparations for the unlawful conduct . . . with interest and attorney's fees or such other sum as the Commission may determine to be proper as an award of reparation; and that such other and further order or orders be made as the Commission determines to be proper in the premises.”</P>
                <P>
                    The full text of the complaint can be found in the Commission's Electronic Reading Room at 
                    <E T="03">www.fmc.gov/14-16.</E>
                </P>
                <P>This proceeding has been assigned to the Office of Administrative Law Judges. The initial decision of the presiding officer in this proceeding shall be issued by December 1, 2015 and the final decision of the Commission shall be issued by June 1, 2016.</P>
                <SIG>
                    <NAME>Karen V. Gregory,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28539 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6730-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL MARITIME COMMISSION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Maritime Commission.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P> December 10, 2014; 11:00 a.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P> 800 N Capitol Street NW., First Floor Hearing Room, Washington, DC.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>The first portion of the meeting will be held in Open Session; the second in Closed Session.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                </PREAMHD>
                <HD SOURCE="HD1">Open Session</HD>
                <P>1. Briefing on European Maritime Law Organization's (EMLO) Conference.</P>
                <P>2. Briefing on South Atlantic Port Forum held October 30th Concerning Causes and Implications of Congestion at U.S. Ports.</P>
                <P>
                    3. Briefing on Gulf Coast Port Forum held November 3rd Concerning Causes and Implications of Congestion at U.S. Ports.
                    <PRTPAGE P="72176"/>
                </P>
                <HD SOURCE="HD1">Closed Session</HD>
                <P>1. Staff Briefing Concerning International Affairs.</P>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P> Karen V. Gregory, Secretary, (202) 523 5725.</P>
                </PREAMHD>
                <SIG>
                    <NAME> Karen V. Gregory,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28726 Filed 12-3-14; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 6730-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Trade Commission (“FTC” or “Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The information collection requirements described below will be submitted to the Office of Management and Budget (“OMB”) for review, as required by the Paperwork Reduction Act (“PRA”). The FTC seeks public comments on proposed information requests by compulsory process to a combined ten or more of the largest cigarette manufacturers and smokeless tobacco manufacturers. The information sought would include, among other things, data on manufacturer annual sales and marketing expenditures. The current FTC clearance from the OMB to conduct such information collection expires January 31, 2015. The Commission intends to ask OMB for renewed three-year clearance to collect this information.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted by January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties may file a comment online or on paper, by following the instructions in the Request for Comment part of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below. Write “Tobacco Reports: Paperwork Comment, FTC File No. P054507” on your comment. File your comment online at 
                        <E T="03">https://ftcpublic.commentworks.com/ftc/tobaccoreportspra2</E>
                         by following the instructions on the web-based form. If you prefer to file your comment on paper, mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex J), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex J), Washington, DC 20024.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Requests for additional information should be addressed to Shira Modell, Division of Advertising Practices, Bureau of Consumer Protection, Federal Trade Commission, 600 Pennsylvania Avenue NW., Mailstop CC-10528, Washington, DC 20580. Telephone: (202) 326-3116.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     FTC Cigarette and Smokeless Tobacco Data Collection.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3084-0134.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of currently approved collection.
                </P>
                <P>
                    On August 13, 2014, the Commission sought comment on the information collection requirements associated with the Cigarette and Smokeless Tobacco Data Collection. 79 FR 47463 (“August 13, 2014 Notice”). Pursuant to the OMB regulations, 5 CFR part 1320, that implement the PRA, 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     the FTC is providing a second opportunity for the public to comment while seeking OMB approval to renew the pre-existing clearance for the information the FTC proposes to seek from cigarette manufacturers and smokeless tobacco manufacturers.
                </P>
                <P>In response to the August 13, 2014 Notice, the Commission received comments from Altria Client Services (“Altria”), the Campaign for Tobacco-Free Kids (“CTFK”), Legacy, and Professor M. Jane Lewis (“Lewis”) of the Rutgers School of Public Health.</P>
                <P>
                    Three of the comments (Legacy, Lewis, and CTFK) specifically noted the utility and importance of the Commission's Cigarette and Smokeless Tobacco Reports, and urged the agency to continue collection and reporting industry sales and marketing expenditure data.
                    <SU>1</SU>
                    <FTREF/>
                     Legacy and CTFK also noted that these data are not available from other sources.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         CTFK and Legacy also urged the Commission to collect and report sales and marketing data for cigars and electronic cigarettes, as well as for conventional tobacco cigarettes and smokeless tobacco. CTFK, at 2-3; Legacy, at 5-6. The Commission will consider those recommendations.
                    </P>
                </FTNT>
                <P>Three of the commenters (Altria, CTFK, and Legacy) responded to questions raised in the Commission's 60-day notice concerning the future collection of data on cigarette tar, nicotine, and carbon monoxide yields. Altria stated that the Commission should not require the manufacturers to provide yield data on all varieties of cigarettes they sell and should cease requiring the cigarette manufacturers to report any smoke constituent data, given the Food and Drug Administration's (“FDA”) new statutory authority to collect such data. Altria stated further that if the Commission retains or expands the existing reporting requirements (which require the companies to provide yield data only for those varieties for which such data already exist), it should require all cigarette manufacturers, not just the major companies, to submit those data. Altria, at 3.</P>
                <P>CTFK acknowledged that tar, nicotine, and carbon monoxide yield data may be important for researchers and regulatory agencies, but noted that “the tobacco industry's history of manipulating this self-reported data raises concerns about its accuracy and validity,” and urged the Commission to coordinate with FDA “to establish a coherent set of product testing requirements that will best serve the statutory missions of both agencies.” CTFK, at 3.</P>
                <P>Legacy encouraged the Commission to cease its collection and reporting of these cigarette yield data, citing their potential to mislead consumers about health risks, the limitations of existing testing methodologies to produce yield results consistent with those actually experienced by smokers, and the “potential unintended consequences among people of low literacy and low numeracy” to understand information on smoke constituent yields. Legacy, at 2-3. Instead, Legacy noted, the Commission and the FDA should work together to determine the best methodology for determining the yields of harmful or potentially harmful smoke constituents, and the best means of disseminating that information in a way that protects public health.</P>
                <P>
                    The FTC and FDA staff have long worked together on the many areas where the two agencies share jurisdiction, and the Commission fully expects this tradition to continue now that the agencies share jurisdiction over cigarettes and smokeless tobacco. The Commission further agrees that FDA should be the primary agency to determine the best test methodology. The Commission is not aware, however, of another means of preserving the existing record of cigarette yield trends unless it continues to collect these data. Freedom of Information Act requests filed with the Commission also suggest that researchers remain interested in these data. Accordingly, the Commission intends to continue collecting the data to the extent recipients of the 6(b) Orders possess them.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission will consider Altria's recommendation that all cigarette manufacturers be required to provide yield data if the major manufacturers are required to do so, although it believes that the five major cigarette manufacturers 
                        <PRTPAGE/>
                        that have received its Orders in recent years already represent at least 95% of domestic cigarette sales.
                    </P>
                </FTNT>
                <PRTPAGE P="72177"/>
                <P>Two commenters (CTFK and Lewis) suggested modifications to the Commission's reports. CTFK recommended that the Commission: (1) Report price discount expenditures for retailers and wholesalers separately; (2) clarify the definitions of certain expenditure categories—specifically, in which category coupons obtained online are to be counted; (3) report data on a company-specific or brand-specific basis, rather than on a fully aggregated basis, and on a state-level basis, as well as nationally; and (4) require manufacturers to report expenditures related to corporate sponsorships and advertisements, and expenditures related to promotion of their youth tobacco prevention programs. CTFK, at 2.</P>
                <P>
                    The Commission agrees that separating the existing category for price discounts (which have accounted for more than 70% of cigarette industry expenditures and more than 20% of smokeless tobacco industry expenditures in recent years) into two separate categories would be useful, and consistent with past decisions to disaggregate certain expenditure categories when they represent a significant proportion of overall spending.
                    <SU>3</SU>
                    <FTREF/>
                     Regarding CTFK's suggestion that data be reported on other than a fully aggregated, nationwide basis, the cigarette and smokeless tobacco companies assert that those data are confidential and, as CTFK acknowledges, the Commission cannot publicly release trade secrets or certain commercial or financial information. 
                    <E T="03">Id.</E>
                     at 2 n.2. CTFK's contention that much of the information that the companies claim to be confidential is actually available from other sources seems inconsistent with its assertion that:
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         For example, the Commission reported spending on a single “promotional allowances” category through 2001, at which time separate categories were created for price discounts and promotional allowances paid to retailers, wholesalers, and others.
                    </P>
                </FTNT>
                <EXTRACT>
                    <FP>The FTC is currently the primary source for data on cigarette and smokeless tobacco companies' marketing and promotional expenditures. No other agency collects and publishes such information directly from the companies, making the FTC reports the most accurate and reliable assessment of tobacco marketing and promotion expenditures available.</FP>
                </EXTRACT>
                <FP>
                    <E T="03">Id.</E>
                     at 1. Similarly, when the Commission has previously inquired about the feasibility of requiring expenditures to be reported on a state-by-state basis, rather than nationally, the major cigarette companies have stated that this was not possible. The Commission again asks for comment on this question.
                </FP>
                <P>
                    The Commission already requires the recipients of its 6(b) Orders to report certain expenditures made in the name of the company, rather than any of its brands,
                    <SU>4</SU>
                    <FTREF/>
                     although it does not include them in its Cigarette and Smokeless Tobacco Reports. The Commission will consider whether those expenditures should be reported in the future. Similarly, the companies do report to the Commission the amount they spend on advertising directed to youth or their parents that are intended to reduce youth smoking or smokeless tobacco use (depending on the Order). The Commission includes this information in the textual portions of its industry Reports (unless only one company reported such spending), not in the annual expenditure-by-category tables.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Both the cigarette and smokeless tobacco Orders require submission of data on “Public entertainment events (including, but not limited to, concerts and sporting events) bearing or otherwise displaying the name of the Company or any variation thereof but not bearing or otherwise displaying the name, logo, or an image of any portion of the package” of any of its cigarettes or smokeless tobacco products, or otherwise referring to those products.
                    </P>
                </FTNT>
                <P>
                    Lewis noted that the Commission's reports do not define the term “expenditure,” and she recommended that the reports clearly state what costs (
                    <E T="03">e.g.,</E>
                     contracted outside services, in-house costs, and personnel) are covered. Lewis, at 2. The Commission agrees that this would be a useful addition to its Reports.
                </P>
                <P>
                    Lewis stated that the Commission's reports underestimate direct mail spending because the costs of items distributed by direct mail (
                    <E T="03">e.g.,</E>
                     coupons and specialty items) are reported in other categories, and recommended that the Commission require the companies to include the costs of those items in their calculations of their direct mail expenditures.
                    <SU>5</SU>
                    <FTREF/>
                     Lewis also recommended that the Commission clarify whether spending for brand-specific Web sites should be reported as advertising on the company's Web site, or as spending on the Internet other than on the company's own Web site, and specify whether expenditures for electronic mail messages should be reported as direct mail or as advertising on the Internet other than on the company's own Internet Web site.
                    <SU>6</SU>
                    <FTREF/>
                     Lewis, at 2-3.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         As noted above, CTFK also asked about the reporting of coupons obtained online.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Lewis correctly noted that the category for spending other than on the company's Web site specifically references “direct mail advertising using electronic mail messages.” Based on her review of recent Commission reports, however, she questioned whether the companies might actually be reporting those costs as direct mail.
                    </P>
                </FTNT>
                <P>The Commission will clarify in future Orders that spending on brand-specific Web sites should be counted as spending on the company's Web sites. However, the Commission does not believe that its Orders should distinguish between, for example, expenditures on coupons delivered through direct mail and coupons delivered by other means. The full impact of couponing by the major cigarette and smokeless tobacco manufacturers can be seen only if expenditures for all coupons are reported together, regardless of how those coupons are delivered to consumers.</P>
                <P>
                    The Commission believes that its Orders have been clear that spending on electronic mail messages should be reported as advertising expenditures on the Internet other than on the company's Web site, and that the absence of reported expenditures does not mean that those costs are being categorized incorrectly.
                    <SU>7</SU>
                    <FTREF/>
                     However, Lewis's comment raises a question about whether spending on electronic mail messages should continue to be reported in the “other Internet” category or should be reported as direct mail expenditures. The Commission requests comment on that question.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         For example, companies do not report the costs of employing full-time employees. If those employees are producing the electronic mail messages, their salaries would not show up in the companies' submissions to the Commission.
                    </P>
                </FTNT>
                <P>Finally, the Commission requests comment on two additional subjects: (1) Its intention to have the cigarette and smokeless tobacco companies that receive these Orders submit two separate datafiles (one containing sales-related data, the other containing data on marketing expenditures), rather than one; and (2) whether it should cease collecting expenditure data on transit advertising.</P>
                <P>
                    The Commission's Orders require that sales data be reported in actual dollars, while advertising and promotional expenditures are reported in thousands of dollars; sales data are also reported for each individual variety of cigarette and smokeless tobacco sold by the company, while expenditure data are reported at the brand level. The Commission believes that requiring the recipients of these Orders to submit separate datafiles for sales and marketing expenditure data will both help avoid errors in the preparation of the companies' submissions and expedite the agency staff's processing of those data, without imposing additional costs on the Order recipients.
                    <PRTPAGE P="72178"/>
                </P>
                <P>
                    The Commission has collected and reported data on transit advertising (currently defined as “advertising on or within private or public vehicles and all advertisements placed at, on or within any bus stop, taxi stand, transportation waiting area, train station, airport or any other transportation facility”) for decades. However, the 1998 Tobacco Master Settlement Agreement prohibited transit advertising, and the major cigarette manufacturers have reported no such spending since 2000, while the major smokeless tobacco companies have never reported any transit spending.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Federal Trade Commission Cigarette Report for 2011 (2013), at Tables 2B—2E, 
                        <E T="03">available at http://www.ftc.gov/sites/default/files/documents/reports/federal-trade-commission-cigarette-report-2011/130521cigarettereport.pdf;</E>
                         Federal Trade Commission Smokeless Tobacco Report for 2011 (2013), at Tables 3B—3H, 
                        <E T="03">available at http://www.ftc.gov/reports/federal-trade-commission-smokeless-tobacco-report-2011.</E>
                    </P>
                </FTNT>
                <P>
                    <E T="03">Burden Statement:</E>
                     
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The details and assumptions underlying these estimates were set forth in the August 13, 2014 
                        <E T="04">Federal Register</E>
                         notice.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     2,100 hours.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The Commission intends to use this PRA clearance renewal to collect information from the companies concerning their marketing and sales activities for the years 2014, 2015, and 2016. The Commission expects to issue compulsory process orders seeking this information annually, but it is possible that orders might not be issued in any given year and that orders seeking information for two years would be issued the next year. The figures set forth in this notice for the estimated hours and labor costs associated with this information collection represent average annual burden over the course of the prospective PRA clearance.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     15 maximum.
                </P>
                <P>The estimated number of respondents include any time spent by separately incorporated subsidiaries and other entities affiliated with the ultimate parent company that has received the information request.</P>
                <P>
                    <E T="03">Estimated Average Burden per Year per Respondent:</E>
                     140 hours.
                </P>
                <P>(a) Information requests to the five largest cigarette companies and five largest smokeless tobacco companies, at a per company average each year of 180 hours = 1,800 hours, cumulatively, per year; and</P>
                <P>(b) Information requests to five additional respondents, of smaller size, at a per company average each year of 60 hours = 300 hours, cumulatively, per year.</P>
                <P>
                    <E T="03">Estimated Annual Labor Cost:</E>
                     $210,000.
                </P>
                <P>
                    <E T="03">Estimated Capital or Other Non-Labor Cost:</E>
                     de minimis.
                </P>
                <P>
                    <E T="03">Request for Comment:</E>
                </P>
                <P>
                    You can file a comment online or on paper. For the FTC to consider your comment, we must receive it on or before January 5, 2015. Write “Tobacco Reports: Paperwork Comment, FTC File No. P054507” on your comment. Your comment—including your name and your state—will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at 
                    <E T="03">http://www.ftc.gov/os/publiccomments.shtm.</E>
                     As a matter of discretion, the Commission tries to remove individuals' home contact information from comments before placing them on the Commission Web site.
                </P>
                <P>
                    Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, like anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any “[t]rade secret or any commercial or financial information which is obtained from any person and which is privileged or confidential . . ., ” as provided in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you have to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c).
                    <SU>11</SU>
                    <FTREF/>
                     Your comment will be kept confidential only if the FTC General Counsel grants your request in accordance with the law and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record. See FTC Rule 4.9(c), 16 CFR 4.9(c).
                    </P>
                </FTNT>
                <P>
                    Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comments online, or to send them to the Commission by courier or overnight service. To make sure that the Commission considers your online comment, you must file it at 
                    <E T="03">https://ftcpublic.commentworks.com/ftc/tobaccoreportspra2</E>
                     by following the instructions on the web-based form. If this Notice appears at 
                    <E T="03">http://www.regulations.gov/#!home,</E>
                     you also may file a comment through that Web site.
                </P>
                <P>If you file your comment on paper, write “Tobacco Reports: Paperwork Comment, FTC File No. P054507” on your comment and on the envelope, and mail it to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex J), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex J), Washington, DC 20024. If possible, submit your paper comment to the Commission by courier or overnight service.</P>
                <P>
                    The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before January 5, 2015. For information on the Commission's privacy policy, including routine uses permitted by the Privacy Act, see 
                    <E T="03">http://www.ftc.gov/ftc/privacy.htm.</E>
                     For supporting documentation and other information underlying the PRA discussion in this Notice, see 
                    <E T="03">http://www.reginfo.gov/public/jsp/PRA/praDashboard.jsp.</E>
                </P>
                <P>Comments on the information collection requirements subject to review under the PRA should additionally be submitted to OMB. If sent by U.S. mail, they should be addressed to Office of Information and Regulatory Affairs, Office of Management and Budget, Attention: Desk Officer for the Federal Trade Commission, New Executive Office Building, Docket Library, Room 10102, 725 17th Street NW., Washington, DC 20503. Comments sent to OMB by U.S. postal mail, however, are subject to delays due to heightened security precautions. Thus, comments instead should be sent by facsimile to (202) 395-5806.</P>
                <SIG>
                    <NAME>David C. Shonka,</NAME>
                    <TITLE>Principal Deputy General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28597 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6750-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[File No. 141 0141]</DEPDOC>
                <SUBJECT>GlaxoSmithKline, PLC and Novartis AG; Analysis of Proposed Consent Orders To Aid Public Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed Consent Agreement.</P>
                </ACT>
                <SUM>
                    <PRTPAGE P="72179"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The consent agreement in this matter settles alleged violations of federal law prohibiting unfair methods of competition. The attached Analysis to Aid Public Comment describes both the allegations in the draft complaint and the terms of the consent orders—embodied in the consent agreement—that would settle these allegations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before December 29, 2014.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties may file a comment at 
                        <E T="03">https://ftcpublic.commentworks.com/ftc/gsknovartisconsent</E>
                         online or on paper, by following the instructions in the Request for Comment part of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below. Write “GlaxoSmithKline, PLC and Novartis AG—Consent Agreement; File No. 141-01414” on your comment and file your comment online at 
                        <E T="03">https://ftcpublic.commentworks.com/ftc/gsknovartisconsent</E>
                         by following the instructions on the Web-based form. If you prefer to file your comment on paper, write “GlaxoSmithKline, PLC and Novartis AG—Consent Agreement; File No. 141-01414” on your comment and on the envelope, and mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex D), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex D), Washington, DC 20024.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mark Silvia, Bureau of Competition, (202-326-3291), 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to Section 6(f) of the Federal Trade Commission Act, 15 U.S.C. 46(f), and FTC Rule 2.34, 16 CFR 2.34, notice is hereby given that the above-captioned consent agreement containing consent orders to cease and desist, having been filed with and accepted, subject to final approval, by the Commission, has been placed on the public record for a period of thirty (30) days. The following Analysis to Aid Public Comment describes the terms of the consent agreement, and the allegations in the complaint. An electronic copy of the full text of the consent agreement package can be obtained from the FTC Home Page (for November 26, 2014), on the World Wide Web, at 
                    <E T="03">http://www.ftc.gov/os/actions.shtm.</E>
                </P>
                <P>
                    You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before December 29, 2014. Write “GlaxoSmithKline, PLC and Novartis AG—Consent Agreement; File No. 141-01414” on your comment. Your comment—including your name and your state—will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at 
                    <E T="03">http://www.ftc.gov/os/publiccomments.shtm.</E>
                     As a matter of discretion, the Commission tries to remove individuals' home contact information from comments before placing them on the Commission Web site.
                </P>
                <P>Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, like anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any “[t]rade secret or any commercial or financial information which . . . is privileged or confidential,” as discussed in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). In particular, do not include competitively sensitive information such as costs, sales statistics, inventories, formulas, patterns, devices, manufacturing processes, or customer names.</P>
                <P>
                    If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you have to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c).
                    <SU>1</SU>
                    <FTREF/>
                     Your comment will be kept confidential only if the FTC General Counsel, in his or her sole discretion, grants your request in accordance with the law and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record. 
                        <E T="03">See</E>
                         FTC Rule 4.9(c), 16 CFR 4.9(c).
                    </P>
                </FTNT>
                <P>
                    Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comments online. To make sure that the Commission considers your online comment, you must file it at 
                    <E T="03">https://ftcpublic.commentworks.com/ftc/gsknovartisconsent</E>
                     by following the instructions on the Web-based form. If this Notice appears at 
                    <E T="03">http://www.regulations.gov/#!home,</E>
                     you also may file a comment through that Web site.
                </P>
                <P>If you file your comment on paper, write “GlaxoSmithKline, PLC and Novartis AG—Consent Agreement; File No. 141-01414” on your comment and on the envelope, and mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex D), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex D), Washington, DC 20024. If possible, submit your paper comment to the Commission by courier or overnight service.</P>
                <P>
                    Visit the Commission Web site at 
                    <E T="03">http://www.ftc.gov</E>
                     to read this Notice and the news release describing it. The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before December 29, 2014. You can find more information, including routine uses permitted by the Privacy Act, in the Commission's privacy policy, at 
                    <E T="03">http://www.ftc.gov/ftc/privacy.htm.</E>
                </P>
                <HD SOURCE="HD1">Analysis of Agreement Containing Consent Orders To Aid Public Comment</HD>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>The Federal Trade Commission (“Commission”) has accepted, subject to final approval, an Agreement Containing Consent Orders (“Consent Agreement”) from Novartis AG (“Novartis”), which is designed to remedy the anticompetitive effects of Novartis's proposed consumer healthcare joint venture with GlaxoSmithKline, PLC (“GSK”).</P>
                <P>The proposed Consent Agreement has been placed on the public record for thirty days for receipt of comments from interested persons. Comments received during this period will become part of the public record. After thirty days, the Commission will again evaluate the proposed Consent Agreement, along with the comments received, in order to make a final decision as to whether it should withdraw from the proposed Consent Agreement, modify it, or make final the Decision and Order (“Order”).</P>
                <P>
                    Pursuant to a series of agreements dated April 22, 2014, GSK and Novartis intend to combine the GSK consumer healthcare business and most of the Novartis consumer healthcare business 
                    <PRTPAGE P="72180"/>
                    (excluding Novartis's nicotine replacement therapy (“NRT”) transdermal patch business) into a joint venture in which GSK will hold a 63.5% controlling share and Novartis will hold the remaining 36.5% share (the “Transaction”). Both parties sell over-the-counter (“OTC”) NRT transdermal patches in the United States. The Commission alleges in its Complaint that the Transaction, if consummated, would violate Section 7 of the Clayton Act, as amended, 15 U.S.C. 18, and Section 5 of the Federal Trade Commission Act, as amended, 15 U.S.C. 45, by lessening competition in the market for the manufacture, marketing, distribution, and sale of NRT transdermal patches. The proposed Consent Agreement will remedy the alleged violations by preserving the competition that would otherwise be eliminated by the Transaction. Specifically, under the terms of the Consent Agreement, Novartis would be required to divest all of its rights and assets related to U.S. NRT transdermal patches, including its branded product, Habitrol. Novartis has proposed Dr. Reddy's Laboratories (“Dr. Reddy's”) as the buyer of these assets.
                </P>
                <HD SOURCE="HD1">II. The Product and Structure of the Market</HD>
                <P>The proposed joint venture would likely substantially increase concentration in the market for NRT transdermal patches. Tobacco consumption introduces nicotine into the body, and nicotine addiction is a major contributor to addiction to tobacco. Nicotine replacement therapies work by providing nicotine to the body through sources other than smoking, thereby replacing the nicotine that would have come from tobacco and helping to ease tobacco cravings in those who are attempting to quit. Users of NRT products are therefore more likely to have success in quitting tobacco. NRT transdermal patches work by adhering to the skin, much like an adhesive bandage, and slowly providing a steady amount of nicotine through the skin over the course of a day. Patches are usually provided in decreasing dosages to help the user step down their nicotine intake over time.</P>
                <P>Novartis markets and sells the branded NRT transdermal patch Habitrol. The only other branded patch is GSK's NicoDerm CQ. Both companies also market private label versions of their branded patch. Private label products are competitive with the branded products, but there is only one other manufacturer of private label patches, Aveva Drug Delivery Systems. Therefore, without a remedy, the Transaction will consolidate the only two providers of branded NRT transdermal patches, and two of the three producers of private label NRT transdermal patches.</P>
                <HD SOURCE="HD1">III. Entry</HD>
                <P>Entry into the manufacture and sale of NRT transdermal patches would not be timely, likely, or sufficient in magnitude, character, and scope to deter or counteract the anticompetitive effects of the Transaction. Developing a patch that adheres to the skin and properly delivers nicotine to the body over time is expensive and time consuming, and has a high risk of failure. Even if an entrant is able to successfully develop a new patch, it must then obtain an FDA approval to market the product, which adds several years to the entry process.</P>
                <HD SOURCE="HD1">IV. Effects</HD>
                <P>The Transaction is likely to result in significant competitive harm in the market for NRT transdermal patches. Although the Novartis NRT patch business has been excluded from the consumer healthcare joint venture, GSK's patch business will be included. Thus, Novartis's partial interest in the joint venture means it will benefit from any sales lost to GSK NRT patches in the future. With an interest in its most significant competing product, Novartis would have an increased incentive to raise prices for its NRT patches post-transaction. The Transaction, by altering the interactions between Novartis's and GSK's branded and private label NRT transdermal patches, would likely result in price increases for NRT patches in several ways. First, the Transaction would reduce the competition between the only two branded NRT transdermal patches, and reduce the competition between Novartis's branded Habitrol product and GSK's private label patches, both of which would increase the likelihood that Novartis would increase the prices of Habitrol. Second, the Transaction would reduce the competition between Novartis's private label patches and GSK's NicoDerm CQ and private label patches, which would create incentives for Novartis to increase the price of its private label NRT transdermal patches.</P>
                <HD SOURCE="HD1">V. The Consent Agreement</HD>
                <P>The proposed Consent Agreement effectively remedies the Transaction's anticompetitive effects in the relevant market. Pursuant to the Consent Agreement, the parties are required to divest Novartis's rights and assets related to its U.S. NRT transdermal patch business to Dr. Reddy's. Further, the proposed Consent Agreement requires Novartis to assign to Dr. Reddy's its contract manufacturing agreements for the divested assets. Finally, Novartis will provide a short term packaging agreement to Dr. Reddy's for secondary packaging of the product while Dr. Reddy's seeks a contract packager. The parties must accomplish these divestitures and relinquish their rights no later than ten days after the Transaction is consummated.</P>
                <P>Dr. Reddy's is well positioned to assume Novartis's role in the NRT transdermal patch market. Dr. Reddy's manufactures a wide range of branded and private label OTC products for sale in the United States, including private label versions of popular allergy and gastrointestinal products. Thus, Dr. Reddy's is already a supplier to most major retailers of OTC consumer healthcare products. In addition, because Novartis will be transferring its existing contract manufacturing arrangement for its NRT transdermal patches, the divestiture to Dr. Reddy's will not require a transfer of manufacturing processes or facilities. Dr. Reddy's will therefore be able to step into Novartis's current position and immediately begin competing in the market for NRT transdermal patches.</P>
                <P>The Commission's goal in evaluating possible purchasers of divested assets is to maintain the competitive environment that existed prior to the Transaction. If the Commission determines that Dr. Reddy's is not an acceptable acquirer of the divested assets, or that the manner of the divestiture is not acceptable, the parties must unwind the sale of rights to Dr. Reddy's, and divest the U.S. NRT transdermal patch assets to a Commission-approved acquirer within six months of the date the Order becomes final. In that circumstance, the Commission may appoint a trustee to divest the product if the parties fail to divest the business as required.</P>
                <P>The proposed Consent Agreement contains several provisions to help ensure that the divestiture is successful. The Order requires Novartis to take all action necessary to maintain the economic viability, marketability, and competitiveness of the product to be divested until such time that they are transferred to a Commission-approved acquirer. The Order also requires that Novartis transfer all confidential business information, including customer information related to the divestiture product, to Dr. Reddy's.</P>
                <P>
                    The purpose of this analysis is to facilitate public comment on the proposed Consent Agreement, and it is not intended to constitute an official 
                    <PRTPAGE P="72181"/>
                    interpretation of the proposed Order or to modify its terms in any way.
                </P>
                <SIG>
                    <P>By direction of the Commission.</P>
                    <NAME>Donald S. Clark,</NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28605 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6750-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[File No. 141 0187]</DEPDOC>
                <SUBJECT>Medtronic, Inc. and Covidien plc; Analysis of Proposed Consent Order To Aid Public Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed consent agreement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The consent agreement in this matter settles alleged violations of federal law prohibiting unfair methods of competition. The attached Analysis to Aid Public Comment describes both the allegations in the draft complaint and the terms of the consent order—embodied in the consent agreement—that would settle these allegations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before December 29, 2014.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties may file a comment at 
                        <E T="03">https://ftcpublic.commentworks.com/ftc/covidienmedtronicconsent</E>
                         online or on paper, by following the instructions in the Request for Comment part of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below. Write “Medtronic and Covidien—Consent Agreement; File No. 141 0187” on your comment and file your comment online at 
                        <E T="03">https://ftcpublic.commentworks.com/ftc/covidienmedtronicconsent</E>
                         by following the instructions on the web-based form. If you prefer to file your comment on paper, write “Medtronic and Covidien—Consent Agreement; File No. 141 0187” on your comment and on the envelope, and mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex D), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex D), Washington, DC 20024.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christine E. Tasso, Bureau of Competition, (202-326-2232), 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to Section 6(f) of the Federal Trade Commission Act, 15 U.S.C. 46(f), and FTC Rule 2.34, 16 CFR 2.34, notice is hereby given that the above-captioned consent agreement containing consent order to cease and desist, having been filed with and accepted, subject to final approval, by the Commission, has been placed on the public record for a period of thirty (30) days. The following Analysis to Aid Public Comment describes the terms of the consent agreement, and the allegations in the complaint. An electronic copy of the full text of the consent agreement package can be obtained from the FTC Home Page (for November 26, 2014), on the World Wide Web, at 
                    <E T="03">http://www.ftc.gov/os/actions.shtm.</E>
                </P>
                <P>
                    You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before December 29, 2014. Write “Medtronic and Covidien—Consent Agreement; File No. 141 0187” on your comment. Your comment—including your name and your state—will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at 
                    <E T="03">http://www.ftc.gov/os/publiccomments.shtm.</E>
                     As a matter of discretion, the Commission tries to remove individuals' home contact information from comments before placing them on the Commission Web site.
                </P>
                <P>Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, like anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any “[t]rade secret or any commercial or financial information which . . . is privileged or confidential,” as discussed in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). In particular, do not include competitively sensitive information such as costs, sales statistics, inventories, formulas, patterns, devices, manufacturing processes, or customer names.</P>
                <P>
                    If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you have to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c).
                    <SU>1</SU>
                    <FTREF/>
                     Your comment will be kept confidential only if the FTC General Counsel, in his or her sole discretion, grants your request in accordance with the law and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record. 
                        <E T="03">See</E>
                         FTC Rule 4.9(c), 16 CFR 4.9(c).
                    </P>
                </FTNT>
                <P>
                    Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comments online. To make sure that the Commission considers your online comment, you must file it at 
                    <E T="03">https://ftcpublic.commentworks.com/ftc/covidienmedtronicconsent</E>
                     by following the instructions on the web-based form. If this Notice appears at 
                    <E T="03">http://www.regulations.gov/#!home,</E>
                     you also may file a comment through that Web site.
                </P>
                <P>If you file your comment on paper, write “Medtronic and Covidien—Consent Agreement; File No. 141 0187” on your comment and on the envelope, and mail your comment to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex D), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex D), Washington, DC 20024. If possible, submit your paper comment to the Commission by courier or overnight service.</P>
                <P>
                    Visit the Commission Web site at 
                    <E T="03">http://www.ftc.gov</E>
                     to read this Notice and the news release describing it. The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before December 29, 2014. You can find more information, including routine uses permitted by the Privacy Act, in the Commission's privacy policy, at 
                    <E T="03">http://www.ftc.gov/ftc/privacy.htm.</E>
                </P>
                <HD SOURCE="HD1">Analysis of Agreement Containing Consent Order To Aid Public Comment</HD>
                <P>
                    The Federal Trade Commission (“Commission”) has accepted from Medtronic, Inc. (“Medtronic”) and Covidien plc (“Covidien”), subject to final approval, an Agreement Containing Consent Order (“Consent Agreement”) designed to remedy the anticompetitive effects resulting from 
                    <PRTPAGE P="72182"/>
                    Medtronic's proposed acquisition of Covidien. Under the terms of the proposed Decision and Order (“Order”) contained in the Consent Agreement, the parties are required to divest Covidien's drug-coated balloon catheter business to The Spectranetics Corporation (“Spectranetics”).
                </P>
                <P>The Consent Agreement has been placed on the public record for 30 days to solicit comments from interested persons. Comments received during this period will become part of the public record. After 30 days, the Commission will again review the Consent Agreement and the comments received, and decide whether it should withdraw from the Consent Agreement, modify it, or make it final.</P>
                <P>Pursuant to a Transaction Agreement dated June 15, 2014, Medtronic proposes to merge with Covidien in exchange for cash and stock valued at approximately $42.9 billion (the “Proposed Acquisition”). The Commission's Complaint alleges that the Proposed Acquisition, if consummated, would violate Section 7 of the Clayton Act, as amended, 15 U.S.C. 18, and Section 5 of the Federal Trade Commission Act, as amended, 15 U.S.C. 45, by substantially lessening competition in the U.S. market for drug-coated balloon catheters indicated for the femoropopliteal (“fem-pop”) artery. The proposed Consent Agreement will remedy the alleged violations by preserving the competition that would otherwise be eliminated by the Proposed Acquisition.</P>
                <HD SOURCE="HD1">The Parties</HD>
                <P>Headquartered in Minneapolis, Minnesota, Medtronic is a global leader in medical technology that develops, manufactures, and sells device-based medical therapies. Medtronic is developing a drug-coated balloon catheter indicated for the fem-pop artery that is currently in the Food and Drug Administration (“FDA”) approval process.</P>
                <P>Headquartered in Dublin, Ireland, Covidien develops, manufactures, and sells medical devices and medical supplies. Like Medtronic, Covidien has a drug-coated balloon catheter indicated for the fem-pop artery under development for which it is seeking FDA approval.</P>
                <HD SOURCE="HD1">The Relevant Product and Market Structure</HD>
                <P>Drug-coated balloon catheters indicated for the fem-pop artery are used to treat peripheral arterial disease in the fem-pop artery, an artery located above the knee. Peripheral arterial disease results from atherosclerosis, the narrowing of blood vessels due to plaque buildup. Percutaneous transluminal angioplasty (“PTA”) balloon catheters are catheters with balloons that, once inserted into an artery, are expanded to push plaque against the artery's lumen wall to reopen blood flow. Drug-coated balloon catheters are a type of PTA balloon catheter that releases paclitaxel, a cell-proliferation inhibiting drug, into the artery wall during a medical procedure to prevent restenosis, or re-narrowing, of the artery.</P>
                <P>The United States is the relevant geographic market in which to assess the competitive effects of the Proposed Acquisition. Drug-coated balloon catheters are medical devices that are regulated by the FDA. As such, drug-coated balloon catheters sold outside the United States, but not approved for sale in the United States, do not provide viable competitive alternatives for U.S. consumers.</P>
                <P>The U.S. market for drug-coated balloon catheters indicated for the fem-pop artery is highly concentrated with only one current supplier, C.R. Bard, Inc. Medtronic and Covidien are likely to enter as the second and third U.S. suppliers, respectively. While there are other firms with drug-coated balloon catheters in development for sale in the U.S. market, Medtronic and Covidien are the only two anticipated market participants that have advanced to the clinical-trial stage of the FDA approval process for drug-coated balloon catheters indicated for the fem-pop artery.</P>
                <HD SOURCE="HD1">Entry</HD>
                <P>Entry into the U.S. market for drug-coated balloon catheters indicated for the fem-pop artery would not be timely, likely, or sufficient in magnitude, character, and scope to deter or counteract the anticompetitive effects of the Proposed Acquisition. The development process for a drug-coated balloon catheter is difficult, time-consuming, and expensive. It can take tens of millions of dollars of research and development, significant further funding for clinical trials, and an extensive amount of time to even reach the stage of applying to the FDA for approval. The regulatory approval process itself can also be time-consuming as the FDA reviews the volume of material and data a company submits in support of its application.</P>
                <HD SOURCE="HD1">Effects of the Acquisition</HD>
                <P>The Proposed Acquisition would cause significant competitive harm to consumers in the U.S. market for drug-coated balloon catheters indicated for the fem-pop artery. The merger would combine the second and third anticipated entrants into the market, likely prolonging a duopoly in the U.S. market for drug-coated balloon catheters indicated for the fem-pop artery. Because Medtronic and Covidien are the only two anticipated entrants that have advanced to the clinical trial stage of the FDA approval process, the consolidation of the two firms would deprive consumers of the benefits of a third competitive entrant into the market for a substantial period of time. As a result, the Proposed Acquisition likely would reduce the substantial additional price competition that would have resulted from an additional U.S. supplier of drug-coated balloon catheters indicated for the fem-pop artery. Further, the Proposed Acquisition likely would reduce innovation in the U.S. market for drug-coated balloon catheters indicated for the fem-pop artery.</P>
                <HD SOURCE="HD1">The Consent Agreement</HD>
                <P>The Consent Agreement eliminates the competitive concerns raised by Medtronic's proposed acquisition of Covidien by requiring the parties divest to Spectranetics all of the assets and resources needed for it to become an independent, viable, and effective competitor in the U.S. market for drug-coated balloon catheters indicated for the fem-pop artery.</P>
                <P>Spectranetics possesses the industry and regulatory experience to achieve FDA approval of Covidien's drug-coated balloon catheter and become the third entrant into the U.S. market. Headquartered in Colorado Springs, Colorado, Spectranetics is a leader in peripheral vascular solutions with a portfolio of products that is highly complementary to Covidien's drug-coated balloon catheter. Spectranetics manufactures and markets a range of devices to treat peripheral and coronary arterial disease and is well positioned to restore the benefits of competition that would be lost through the Proposed Acquisition.</P>
                <P>
                    Pursuant to the Order, Spectranetics will receive all rights and assets related to Covidien's drug-coated balloon catheter products, including all of the intellectual property used in the drug-coated balloon catheter business. In addition, Spectranetics will take over the manufacturing facility where Covidien currently coats the PTA balloon catheters with paclitaxel. The Order further requires that Covidien provide Spectranetics with a worldwide license to produce the PTA balloon catheters incorporated into the drug-coated balloon catheters. In order to 
                    <PRTPAGE P="72183"/>
                    ensure continuity of supply of a critical input, the Order requires that the parties supply Spectranetics with PTA balloon catheters for up to three years while Spectranetics transitions to independent manufacturing. This provision ensures that drug-coated balloon catheters will continue to be available for ongoing clinical trials while Spectranetics works to obtain FDA approval to manufacture the PTA balloon catheters independently.
                </P>
                <P>To ensure that the divestiture is successful, the Order requires the parties to enter into a transitional services agreement with Spectranetics to assist the company in establishing its manufacturing capabilities and securing all necessary FDA approvals. Further, the Order requires that the parties transfer all confidential business information to Spectranetics, as well as provide access to employees who possess or are able to identify such information. Spectranetics also will have the right to interview and offer employment to employees associated with Covidien's drug-coated balloon catheter business.</P>
                <P>The parties must accomplish the divestiture no later than ten days after the consummation of the Proposed Acquisition. If the Commission determines that Spectranetics is not an acceptable acquirer, or that the manner of the divestiture is not acceptable, the Order requires the parties to unwind the sale and accomplish the divestiture within 180 days of the date the Order becomes final to another Commission-approved acquirer.</P>
                <P>To ensure compliance with the Order, the Commission has agreed to appoint an Interim Monitor to ensure that Medtronic and Covidien comply with all of their obligations pursuant to the Consent Agreement and to keep the Commission informed about the status of the transfer of the rights and assets to Spectranetics. Further, the Order allows the Commission to appoint a Divestiture Trustee to accomplish the divestiture should the parties fail to comply with their divestiture obligations. Lastly, the Order terminates after ten years.</P>
                <P>The purpose of this analysis is to facilitate public comment on the Consent Agreement, and it is not intended to constitute an official interpretation of the proposed Decision and Order or to modify its terms in any way.</P>
                <SIG>
                    <P>By direction of the Commission.</P>
                    <NAME>Donald S. Clark,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28609 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6750-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[CMS-6056-N]</DEPDOC>
                <SUBJECT>Medicare, Medicaid, and Children's Health Insurance Programs; Provider Enrollment Application Fee Amount for Calendar Year 2015</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces a $553.00 calendar year (CY) 2015 application fee for institutional providers that are initially enrolling in the Medicare or Medicaid program or the Children's Health Insurance Program (CHIP); revalidating their Medicare, Medicaid, or CHIP enrollment; or adding a new Medicare practice location. This fee is required with any enrollment application submitted on or after January 1, 2015 and on or before December 31, 2015.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This notice is effective on January 1, 2015.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION:</HD>
                    <P>Frank Whelan, (410) 786-1302 for Medicare enrollment issues. Alvin Anderson, (410) 786-2188 for Medicaid and CHIP enrollment issues.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    In the February 2, 2011 
                    <E T="04">Federal Register</E>
                     (76 FR 5862), we published a final rule with comment period titled “Medicare, Medicaid, and Children's Health Insurance Programs; Additional Screening Requirements, Application Fees, Temporary Enrollment Moratoria, Payment Suspensions and Compliance Plans for Providers and Suppliers.” This rule finalized, among other things, provisions related to the submission of application fees as part of the Medicare, Medicaid, and CHIP provider enrollment processes. As provided in section 1866(j)(2)(C)(i) of the Social Security Act (as amended by section 6401 of the Affordable Care Act) and in 42 CFR 424.514, “institutional providers” that are initially enrolling in the Medicare, Medicaid, or CHIP program, revalidating their enrollment, or adding a new Medicare practice location are required to submit a fee with their enrollment application. An “institutional provider” for purposes of Medicare is defined at § 424.502 as “(a)ny provider or supplier that submits a paper Medicare enrollment application using the CMS-855A, CMS-855B (not including physician and non-physician practitioner organizations), CMS-855S, or associated Internet-based PECOS enrollment application.” As we explained in the February 2, 2011 final rule (76 FR 5914), in addition to the providers and suppliers subject to the application fee under Medicare, Medicaid-only, and CHIP-only institutional providers would include nursing facilities, intermediate care facilities for persons with mental retardation (ICF/MR), psychiatric residential treatment facilities, and may include other institutional provider types designated by a state in accordance with their approved state plan.
                </P>
                <P>As indicated in §§ 424.514 and 455.460, the application fee is not required for either of the following:</P>
                <P>• A Medicare physician or non-physician practitioner submitting a CMS-855I.</P>
                <P>• A prospective or revalidating Medicaid or CHIP provider—</P>
                <P>++ Who is an individual physician or non-physician practitioner; or</P>
                <P>++ That is enrolled in Title XVIII of the Act or another state's Title XIX or XXI plan and has paid the application fee to a Medicare contractor or another state.</P>
                <HD SOURCE="HD1">II. Provisions of the Notice</HD>
                <HD SOURCE="HD2">A. CY 2014 Fee Amount</HD>
                <P>
                    In the December 2, 2013 
                    <E T="04">Federal Register</E>
                     (78 FR 72089), we published a notice announcing a fee amount for the period of January 1, 2014 through December 31, 2014 of $542.00. This figure was calculated as follows:
                </P>
                <P>• Section 1866(j)(2)(C)(i)(I) of the Act established a $500 application fee for institutional providers in CY 2010.</P>
                <P>• Consistent with section 1866(j)(2)(C)(i)(II) of the Act, § 424.514(d)(2) states that for CY 2011 and subsequent years, the preceding year's fee will be adjusted by the percentage change in the consumer price index (CPI) for all urban consumers (all items; United States city average, CPI-U) for the 12-month period ending on June 30 of the previous year.</P>
                <P>• The CPI-U increase for CY 2011 was 1.0 percent, based on data obtained from the Bureau of Labor Statistics (BLS). This resulted in an application fee amount for CY 2011 of $505 (or $500 × 1.01).</P>
                <P>
                    • The CPI-U increase for the period of July 1, 2010 through June 30, 2011 was 3.54 percent, based on BLS data. This resulted in an application fee amount for CY 2012 of $522.87 (or $505 × 1.0354). In the aforementioned February 2, 2011 final rule, we stated 
                    <PRTPAGE P="72184"/>
                    that if the adjustment sets the fee at an uneven dollar amount, we would round the fee to the nearest whole dollar amount. Accordingly, the application fee amount for CY 2012 was rounded to the nearest whole dollar amount, or $523.00.
                </P>
                <P>• The CPI-U increase for the period of July 1, 2011 through June 30, 2012 was 1.664 percent, based on BLS data. This resulted in an application fee amount for CY 2013 of $531.70 ($523 × 1.01664). Rounding this figure to the nearest whole dollar amount resulted in a CY 2013 application fee amount of $532.00.</P>
                <P>• The CPI-U increase for the period of July 1, 2012 through June 30, 2013 was 1.8 percent, based on BLS data. This resulted in an application fee amount for CY 2014 of $541.576 ($532 × 1.018). Rounding this figure to the nearest whole dollar amount resulted in a CY 2014 application fee amount of $542.00.</P>
                <HD SOURCE="HD2">B. CY 2015 Fee Amount</HD>
                <P>Using BLS data, the CPI-U increase for the period of July 1, 2013 through June 30, 2014 was 2.1 percent. This results in a CY 2015 application fee amount of $553.382 ($542 × 1.021). As we must round this to the nearest whole dollar amount, the resultant application fee amount for CY 2015 is $553.00. This represents a $6.00 difference from the $547 application fee amount that we had originally projected for CY 2015 in the February 2, 2011 final rule.</P>
                <HD SOURCE="HD1">III. Collection of Information Requirements</HD>
                <P>This document does not impose information collection requirements, that is, reporting, recordkeeping or third-party disclosure requirements. Consequently, there is no need for review by the Office of Management and Budget under the authority of the Paperwork Reduction Act of 1995. However, it does reference previously approved information collections. The forms CMS-855A, CMS-855B, and CMS-855I are approved under OMB control number 0938-0685; the CMS-855S is approved under OMB control number 0938-1056.</P>
                <HD SOURCE="HD1">IV. Regulatory Impact Statement</HD>
                <HD SOURCE="HD2">A. Background</HD>
                <P>We have examined the impact of this notice as required by Executive Order 12866 on Regulatory Planning and Review (September 30, 1993), Executive Order 13563 on Improving Regulation and Regulatory Review (January 18, 2011), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, section 202 of the Unfunded Mandates Reform Act of 1995 (March 22, 1995; Pub. L. 104-4), Executive Order 13132 on Federalism (August 4, 1999), and the Congressional Review Act (5 U.S.C. 804(2)).</P>
                <P>Executive 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. A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year). As explained in this section of the notice, we estimate that the total cost of the increase in the application fee will not exceed $100 million. Therefore, this notice does not reach the $100 million economic threshold and is not considered a major notice.</P>
                <HD SOURCE="HD2">B. Costs</HD>
                <P>The costs associated with this notice involve the increase in the application fee amount that certain providers and suppliers must pay in CY 2015.</P>
                <HD SOURCE="HD3">1. Initial Estimates in February 2011 Final Rule</HD>
                <P>In the RIA for the February 2, 2011 final rule, as indicated earlier, we estimated the total amount of application fees for CYs 2011 through 2015. For CY 2015, and based on a projected $547 application fee amount, we estimated in Tables 11 and 12 (76 FR 5955 and 5956) a total cost in fees of $63,465,675 ($17,066,400 + $46,399,275) for 116,025 affected Medicare institutional providers (31,200 newly enrolling + 84,825 revalidating). We also projected in Tables 13 and 14 (76 FR 5957 and 5958) a total cost in CY 2015 application fees of $13,748,298 ($4,615,586 + $9,132,712) for 25,134 affected Medicaid and CHIP providers (8,438 newly enrolling + 16,696 revalidating).</P>
                <HD SOURCE="HD3">2. Estimates of Number of Affected Institutional Providers in December 2, 2013 Fee Notice</HD>
                <P>In the December 2, 2013 application fee notice, we estimated that—</P>
                <P>• 4,800 newly enrolling Medicare institutional providers would be subject to an application fee in CY 2014. This was based on CMS statistics for the final quarter of CY 2012 and represented a substantial decrease from our estimate in the February 2, 2011 final rule of 31,200 affected, newly enrolling institutional providers for CY 2014.</P>
                <P>• 580,000 Medicare providers and suppliers would be subject to revalidation in CY 2014, of which 116,000 would be institutional providers required to pay a fee.</P>
                <P>• 27,859 Medicaid and CHIP providers (8,438 newly enrolling + 19,421 revalidating) would be subject to an application fee in CY 2014.</P>
                <HD SOURCE="HD3">3. CY 2015 Estimates</HD>
                <HD SOURCE="HD3">a. Medicare</HD>
                <P>Based on CMS data, we estimate that in CY 2015 approximately—</P>
                <P>• 10,000 newly enrolling institutional providers will pay an application fee; and</P>
                <P>• 35,000 institutional providers will be subject to revalidation and will pay an application fee.</P>
                <P>Using a figure of 45,000 (10,000 newly enrolling + 35,000 revalidating) institutional providers, we estimate an increase in the cost of the Medicare application fee requirement in CY 2015 of $270,000 (or 45,000 x $6.00) from the CY 2015 projections we had made in the February 2, 2011 final rule.</P>
                <HD SOURCE="HD3">b. Medicaid and CHIP</HD>
                <P>As we did for CY 2014, we continue to estimate that 27,859 (8,438 newly enrolling + 19,421 revalidating) Medicaid and CHIP providers would be subject to an application fee in CY 2015. Using this figure, we project an increase in the cost of the Medicaid and CHIP application fee requirement in CY 2015 of $167,154 (27,859 x $6.00) from the CY 2014 projections we had made in the February 2, 2011 final rule.</P>
                <HD SOURCE="HD3">c. Total</HD>
                <P>Based on the foregoing, we estimate the total increase in the cost of the application fee requirement for Medicare, Medicaid, and CHIP providers and suppliers in CY 2015 to be $437,154 ($270,000 + $167,154) from the CY 2015 projections we had made in the February 2, 2011 final rule.</P>
                <P>
                    The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of less than $7.5 million to $38.5 million in any 1 year. Individuals and states are not included in the definition of a small entity. As we stated in the RIA for the February 2, 2011 final rule with comment period (76 FR 5952), we do not believe that the application fee 
                    <PRTPAGE P="72185"/>
                    will have a significant impact on small entities.
                </P>
                <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area for Medicare payment regulations and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we have determined, and the Secretary certifies, that this notice would not have a significant impact on the operations of a substantial number of small rural hospitals.</P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. In 2014, that threshold is approximately $141 million. The Agency has determined that there will be minimal impact from the costs of this notice, as the threshold is not met under the UMRA.</P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on state and local governments, preempts state law, or otherwise has federalism implications. Since this notice does not impose substantial direct costs on state or local governments, the requirements of Executive Order 13132 are not applicable.</P>
                <P>In accordance with the provisions of Executive Order 12866, this notice was reviewed by the Office of Management and Budget.</P>
                <SIG>
                    <DATED>Dated: October 22, 2014.</DATED>
                    <NAME>Marilyn Tavenner,</NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28503 Filed 12-2-14; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2014-D-1891]</DEPDOC>
                <SUBJECT>How To Obtain a Letter From the Food and Drug Administration Stating That Bioequivalence Study Protocols Contain Safety Protections Comparable to Applicable Risk Evaluation and Mitigation Strategies for Reference Listed Drugs; Draft Guidance for Industry; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a draft guidance for industry entitled “How to Obtain a Letter from FDA Stating that Bioequivalence Study Protocols Contain Safety Protections Comparable to Applicable REMS for RLD.” This draft guidance describes how a prospective abbreviated new drug application (ANDA) applicant may request a letter stating that FDA has determined the following: The potential applicant's bioequivalence (BE) study protocol contains safety protections comparable to those in the risk evaluation and mitigation strategy (REMS) with elements to assure safe use (ETASU) applicable to the reference listed drug (RLD) and FDA will not consider it a violation of the REMS for the RLD sponsor to provide a sufficient quantity of the RLD to the interested generic firm or its agent to allow the firm to perform the testing necessary to support its ANDA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Although you can comment on any guidance at any time (see 21 CFR 10.115(g)(5)), to ensure that the Agency considers your comment on this draft guidance before it begins work on the final version of the guidance, submit either electronic or written comments on the draft guidance by February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written requests for single copies of the draft guidance to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 2201, Silver Spring, MD 20993-0002. Send one self-addressed adhesive label to assist that office in processing your requests. See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the guidance document.
                    </P>
                    <P>
                        Submit electronic comments on the guidance to 
                        <E T="03">http://www.regulations.gov.</E>
                         Submit written comments to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Giaquinto, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 75, Rm. 1670, Silver Spring, MD 20993, 240-402-7930, 
                        <E T="03">Elizabeth.Giaquinto@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FDA is announcing the availability of a draft guidance for industry entitled “How to Obtain a Letter from FDA Stating that Bioequivalence Study Protocols Contain Safety Protections Comparable to Applicable REMS for RLD.” Section 505-1(a)(1) of the FD&amp;C Act authorizes FDA to require applicants to submit a proposed REMS as a part of the relevant application 
                    <SU>1</SU>
                    <FTREF/>
                     if FDA determines that a REMS is necessary to ensure that the benefits of a drug outweigh its risks (21 U.S.C. 355-1(a)(1)). A REMS is a required risk management plan that uses tools beyond routine professional labeling (such as a medication guide, a patient package insert, and/or a communication plan) to ensure that the benefits of a drug outweigh its risks (section 505-1(f) of the FD&amp;C Act). In addition, FDA may require ETASU in some circumstances when such elements are necessary to mitigate the risks associated with the drug. ETASU may include, for example, requirements that health care providers who prescribe or administer the drug have particular training or certification; that patients using the drug be monitored and/or enrolled in a registry; or that pharmacies, practitioners, or health care settings that dispense the drug be specially certified.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Section 505-1 of the FD&amp;C Act applies to any application for approval of a prescription drug submitted under section 505(b) or (j) of the FD&amp;C Act (including both NDAs submitted under section 505(b)(2) and ANDAs submitted under section 505(j)), as well as applications submitted under section 351 of the Public Health Service Act (42 U.S.C. 262).
                    </P>
                </FTNT>
                <P>
                    FDA is aware of instances in which an RLD sponsor has refused to sell drug products to a prospective ANDA applicant seeking to conduct the testing needed to obtain approval, and the RLD sponsor has cited the REMS ETASU as justification. In the interest of facilitating prospective generic applicants' access to RLD products to conduct the testing necessary to support ANDA approval, FDA has, on request, reviewed the BE study protocols proposed by a prospective ANDA 
                    <PRTPAGE P="72186"/>
                    applicant to assess whether they provide safety protections comparable to those in the applicable REMS ETASU. When the Agency has determined that comparable protections existed, FDA has issued letters to the RLD sponsor stating so, and indicating that FDA would not consider it to be a violation of the REMS for the RLD sponsor to provide drug product to the prospective ANDA applicant or its agent.
                </P>
                <P>Requesting or obtaining such a letter from FDA is not a legal requirement. If a prospective ANDA applicant chooses to request such a letter, this guidance is intended to clarify the process for doing so.</P>
                <P>This draft guidance is being issued consistent with FDA's good guidance practices regulation (21 CFR 10.115). The guidance represents the Agency's current thinking on how a prospective generic applicant can obtain a letter stating that its BE study protocols contain safety protections comparable to those in the applicable REMS for the RLD. It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.</P>
                <HD SOURCE="HD1">II. Comments</HD>
                <P>
                    Interested persons may submit either electronic comments regarding this document to 
                    <E T="03">http://www.regulations.gov</E>
                     or written comments to the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ). It is only necessary to send one set of comments. Identify comments with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday, and will be posted to the docket at 
                    <E T="03">http://www.regulations.gov.</E>
                </P>
                <HD SOURCE="HD1">III. The Paperwork Reduction Act of 1995</HD>
                <P>This guidance refers to previously approved collections of information that are subject to review by the Office of Management and Budget under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). The collections of information in 21 CFR parts 312 and 314 have been approved under OMB control numbers 0910-0014 and 0910-0001.</P>
                <HD SOURCE="HD1">IV. Electronic Access</HD>
                <P>
                    Persons with access to the Internet may obtain the document at either 
                    <E T="03">http://www.fda.gov/Drugs/GuidanceComplianceRegulatoryInformation/Guidances/default.htm</E>
                     or 
                    <E T="03">http://www.regulations.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Leslie Kux,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28540 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2014-N-1795]</DEPDOC>
                <SUBJECT>Mallinckrodt Inc. et al.; Withdrawal of Approval of 23 New Drug Applications and 68 Abbreviated New Drug Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is withdrawing approval of 23 new drug applications (NDAs) and 68 abbreviated new drug applications (ANDAs) from multiple applicants. The holders of the applications notified the Agency in writing that the drug products were no longer marketed and requested that the approval of the applications be withdrawn.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         January 5, 2015.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Florine P. Purdie, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6248, Silver Spring, MD 20993-0002, 301-796-3601.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The holders of the applications listed in table 1 in this document have informed FDA that these drug products are no longer marketed and have requested that FDA withdraw approval of the applications pursuant to the process in § 314.150(c) (21 CFR 314.150(c)). The applicants have also, by their requests, waived their opportunity for a hearing. Withdrawal of approval of an application or abbreviated application under § 314.150(c) is without prejudice to refiling.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="xs60,r100,r100">
                    <TTITLE>Table 1</TTITLE>
                    <BOXHD>
                        <CHED H="1">Application No.</CHED>
                        <CHED H="1">Drug</CHED>
                        <CHED H="1">Applicant</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">NDA 002852</ENT>
                        <ENT>Plexofer (multivitamins) Syrup</ENT>
                        <ENT>Mallinckrodt Inc., 675 McDonnell Blvd., Hazelwood, MO 63042.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 008719</ENT>
                        <ENT>Levo-Dromoran (levorphanol tartrate) Injection, 2 milligrams (mg)/milliliter (mL)</ENT>
                        <ENT>Valeant Pharmaceuticals North America LLC, 400 Somerset Corporate Blvd., Bridgewater, NJ 08807.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 008720</ENT>
                        <ENT>Levo-Dromoran (levorphanol tartrate) Tablets, 2 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 011777</ENT>
                        <ENT>Sodium Phosphate P 32 Solution</ENT>
                        <ENT>Mallinckrodt Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 012366</ENT>
                        <ENT>Soma Compound with Codeine (carisoprodol, aspirin, and codeine phosphate)</ENT>
                        <ENT>Meda Pharmaceuticals Inc., 265 Davidson Ave., Suite 300, Somerset, NJ 08873-4120.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 012708</ENT>
                        <ENT>Diutensen-R (methyclothiazide and reserpine) Tablets, 2.5 mg/0.1 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 016245</ENT>
                        <ENT>Vercyte (pipobroman) Tablets</ENT>
                        <ENT>AbbVie, Inc., 1 North Waukegan Rd., Dept. PA 77/Bldg. AP30, North Chicago, IL 60064.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 017463</ENT>
                        <ENT>Motrin (ibuprofen) Tablets, 300 mg, 400 mg, 600 mg, and 800 mg</ENT>
                        <ENT>McNeil Consumer Healthcare Division of McNeil-PPC, Inc., 7050 Camp Hill Rd., Fort Washington, PA 19034-2299.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 018310</ENT>
                        <ENT>Lymphazurin (isosulfan blue), 1%</ENT>
                        <ENT>Covidien, 60 Middletown Ave., North Haven, CT 06473.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 018340</ENT>
                        <ENT>
                            Aerobid (flunisolide) Inhalation Aerosol 
                            <SU>1</SU>
                        </ENT>
                        <ENT>Roche Palo Alto LLC, c/o Genentech Inc., 1 DNA Way, South San Francisco, CA 94080-4990.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 018731</ENT>
                        <ENT>Buspar (buspirone hydrochloride (HCl)) Tablets, 5 mg, 10 mg, 15 mg, and 30 mg</ENT>
                        <ENT>Bristol-Myers Squibb Co., P.O. Box 4000, Princeton, NJ 08543-4000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 019453</ENT>
                        <ENT>Drixoral (dexbrompheniramine maleate, pseudoephedrine sulfate, and acetaminophen) Extended-Release Tablets, 3 mg, 60 mg, and 500 mg</ENT>
                        <ENT>Merck Consumer Care, 556 Morris Ave., Summit, NJ 07901.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="72187"/>
                        <ENT I="01">NDA 019842</ENT>
                        <ENT>Motrin (ibuprofen) Suspension, 100 mg/5 mL</ENT>
                        <ENT>McNeil Consumer Healthcare Division of McNeil-PPC, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020150</ENT>
                        <ENT>Nicotrol TD (nicotine transdermal system), 5 mg/16 hour (hr), 10 mg/16 hr, and 15 mg/16 hr</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 020707</ENT>
                        <ENT>Skelid (tiludronate disodium) Tablets</ENT>
                        <ENT>Sanofi-Aventis U.S. LLC, 55 Corporate Dr., Mailstop 55C-205A, Bridgewater, NJ 08807.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021043</ENT>
                        <ENT>RID Mousse (pyrethrins 0.33% and piperonyl butoxide 4.0%) Topical Aerosol</ENT>
                        <ENT>Bayer Healthcare LLC, 100 Bayer Blvd., Whippany, NJ 07981-0915.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021082</ENT>
                        <ENT>Tavist Allergy Sinus Headache (clemastine fumarate, pseudoephedrine HCl, and acetaminophen) Tablets, 0.335 mg, 30 mg, and 500 mg</ENT>
                        <ENT>Novartis Consumer Health, Inc., 200 Kimball Dr., Parsippany, NJ 07054.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021190</ENT>
                        <ENT>Buspar (buspirone HCl) Capsules, 5 mg, 7.5 mg, 10 mg, and 15 mg</ENT>
                        <ENT>Bristol-Myers Squibb Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021335</ENT>
                        <ENT>Gleevac (imatinib mesylate) Capsules, 50 mg and 100 mg</ENT>
                        <ENT>Novartis Pharmaceuticals Corp., One Health Plaza, East Hanover, NJ 07936.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 021745</ENT>
                        <ENT>Ryzolt (tramadol HCl) Extended-Release Tablets, 100 mg, 200 mg, and 300 mg</ENT>
                        <ENT>Purdue Pharma Products L.P., One Stamford Forum, Stamford, CT 06901-3431.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022217</ENT>
                        <ENT>Valturna (aliskiren and valsartan) Tablets</ENT>
                        <ENT>Novartis Pharmaceuticals Corp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 022470</ENT>
                        <ENT>Nexcede (ketoprofen) Oral Soluble Films, 12.5 mg</ENT>
                        <ENT>Novartis Consumer Health, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 040034</ENT>
                        <ENT>Theophylline Extended-Release Tablets, 450 mg</ENT>
                        <ENT>Inwood Laboratories, Inc., Subsidiary of Forest Laboratories, Inc., Harborside Financial Center, Plaza Five, Suite 1900, Jersey City, NJ 07311.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 040052</ENT>
                        <ENT>Theophylline Extended-Release Capsules, 100 mg, 125 mg, 200 mg, and 300 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 040365</ENT>
                        <ENT>Dextroamphetamine Sulfate Tablets, 5 mg</ENT>
                        <ENT>Nesher Pharmaceutical (USA) LLC, 13910 Saint Charles Rock Rd., Bridgeton, MO 63044.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 040367</ENT>
                        <ENT>Dextroamphetamine Sulfate Tablets, 10 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 060578</ENT>
                        <ENT>Mycostatin Topical Powder (nystatin topical powder USP) 100,000 units/gram (g)</ENT>
                        <ENT>Delcor Asset Corp., c/o Prestium Pharma Inc., 411 South State St., Suite E-100, Newtown, PA 18940.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062162</ENT>
                        <ENT>Erythromycin Estolate Capsules USP, 125 mg and 250 mg</ENT>
                        <ENT>Barr Laboratories, Inc., Subsidiary of Teva Pharmaceuticals USA, 400 Chestnut Ridge Rd., Woodcliff Lake, NJ 07677.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062256</ENT>
                        <ENT>Erythromycin Ethylsuccinate Tablets USP, 400 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062773</ENT>
                        <ENT>Cephalexin Capsules USP 250 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062850</ENT>
                        <ENT>Cephradine Capsules USP 250 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062851</ENT>
                        <ENT>Cephradine Capsules USP 500 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062858</ENT>
                        <ENT>Cephradine for Oral Suspension USP 125 mg/5 mL</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 062859</ENT>
                        <ENT>Cephradine for Oral Suspension USP, 250 mg/5 mL</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 063016</ENT>
                        <ENT>Cefazolin for Injection USP 250 mg/vial, 500 mg/vial, and 1 g/vial</ENT>
                        <ENT>Teva Pharmaceuticals USA, 425 Privet Rd., Horsham, PA 19044.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 063028</ENT>
                        <ENT>Erythromycin Delayed-Release Tablets USP, 333 mg</ENT>
                        <ENT>Barr Laboratories, Inc., Subsidiary of Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 063086</ENT>
                        <ENT>Erythromycin Delayed-Release Tablets, 333 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 063098</ENT>
                        <ENT>Erythromycin Delayed-Release Capsules USP, 250 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 063179</ENT>
                        <ENT>Erythromycin Stearate Tablets USP 500 mg</ENT>
                        <ENT>ANI Pharmaceuticals, Inc., 210 Main St. West, Baudette, MN 56623.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 064191</ENT>
                        <ENT>Cefuroxime for Injection USP 7.5 g/vial</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 064192</ENT>
                        <ENT>Cefuroxime for Injection USP 750 mg/vial and 1.5 g/vial</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 065032</ENT>
                        <ENT>Doxycycline Capsules USP 50 mg and 100 mg</ENT>
                        <ENT>Sandoz Inc., 4700 Sandoz Dr., Wilson, NC 27893.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 065227</ENT>
                        <ENT>Ceftriaxone for Injection USP, 250 mg/vial, 500 mg/vial, 1 g/vial, and 2 g/vial</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 065262</ENT>
                        <ENT>Ceftriaxone for Injection USP, 1 g/vial and 2 g/vial</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 065274</ENT>
                        <ENT>Ceftriaxone for Injection USP, 10 g/vial</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 070034</ENT>
                        <ENT>Sulfamethoxazole and Trimethoprim Tablets USP 400 mg/80 mg</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 070216</ENT>
                        <ENT>Sulfamethoxazole and Trimethoprim Tablets USP 800 mg/160 mg</ENT>
                        <ENT>Barr Laboratories Inc., Subsidiary of Teva Pharmaceuticals.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072410</ENT>
                        <ENT>Indomethacin Extended-Release Capsules, 75 mg</ENT>
                        <ENT>Inwood Laboratories, Inc., Subsidiary of Forest Laboratories, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072499</ENT>
                        <ENT>Propranolol HCl Extended-Release Capsules, 60 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072500</ENT>
                        <ENT>Propranolol HCl Extended-Release Capsules, 80 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072501</ENT>
                        <ENT>Propranolol HCl Extended-Release Capsules, 120 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072502</ENT>
                        <ENT>Propranolol HCl Extended-Release Capsules, 160 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072619</ENT>
                        <ENT>Albuterol Sulfate Tablets USP 2 mg</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 072620</ENT>
                        <ENT>Albuterol Sulfate Tablets USP 4 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 073095</ENT>
                        <ENT>Clemastine Fumerate Syrup, 0.5 mg/5 mL</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 073531</ENT>
                        <ENT>Potassium Chloride Extended-Release Capsules USP, 8 milliequivalents (mEq)</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 073532</ENT>
                        <ENT>Potassium Chloride Extended-Release Capsules USP, 10 mEq</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 073667</ENT>
                        <ENT>Nortriptyline HCl Capsules, 10 mg, 25 mg, 50 mg, and 75 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074043</ENT>
                        <ENT>Piroxicam Capsules USP, 10 mg and 20 mg</ENT>
                        <ENT>Mylan Pharmaceuticals, Inc., 781 Chestnut Ridge Rd., P.O. Box 4310, Morgantown, WV 26505.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="72188"/>
                        <ENT I="01">ANDA 074126</ENT>
                        <ENT>Atenolol Tablets USP, 25 mg, 50 mg, and 100 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074589</ENT>
                        <ENT>Minoxidil Topical Solution, 2%</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074828</ENT>
                        <ENT>Acyclovir Capsules, 200 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074849</ENT>
                        <ENT>Clomipramine HCl Capsules, 25 mg, 50 mg, and 75 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074879</ENT>
                        <ENT>Ketoprofen Extended-Release Capsules, 200 mg</ENT>
                        <ENT>Alkermes Gainesville LLC, 1300 Gould Dr., Gainesville, GA 30504.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074976</ENT>
                        <ENT>Acyclovir Tablets USP, 400 mg and 800 mg</ENT>
                        <ENT>Mylan Pharmaceuticals, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 074977</ENT>
                        <ENT>Acyclovir Capsules USP, 200 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 075161</ENT>
                        <ENT>Ticlopidine HCl Tablets USP, 250 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 075472</ENT>
                        <ENT>Enalapril Maleate Tablets USP, 2.5 mg, 5 mg, 10 mg, and 20 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 075934</ENT>
                        <ENT>Nizatidine Capsules USP, 150 mg and 300 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 076036</ENT>
                        <ENT>Quinapril Tablets USP, 5 mg, 10 mg, 20 mg, and 40 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 076969</ENT>
                        <ENT>Metoprolol Succinate Extended-Release Tablets USP, 25 mg, 50 mg, 100 mg, and 200 mg</ENT>
                        <ENT>Sandoz, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077136</ENT>
                        <ENT>Terbinafine HCl Tablets, 250 mg</ENT>
                        <ENT>Mylan Pharmaceuticals, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077163</ENT>
                        <ENT>Sumatriptan Succinate Tablets, 25 mg, 50 mg, and 100 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077254</ENT>
                        <ENT>Divalproex Sodium Delayed-Release Tablets USP, 125 mg, 250 mg, and 500 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077486</ENT>
                        <ENT>Glimepiride Tablets USP, 1 mg, 2 mg, and 4 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077705</ENT>
                        <ENT>Fosinopril Sodium and Hydrochlorothiazide Tablets, 10 mg/12.5 mg and 20 mg/12.5 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077934</ENT>
                        <ENT>Meloxicam Tablets USP, 7.5 mg and 15 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 077976</ENT>
                        <ENT>Cromolyn Sodium Nasal Solution USP, 5.2 mg/1 spray</ENT>
                        <ENT>HH &amp; P LLC, c/o Kuker Regulatory Consulting, LLC, 18 Dunbar Way, Mahtomedi, MN 55115.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 078638</ENT>
                        <ENT>Alendronate Sodium Tablets USP, 35 mg and 70 mg</ENT>
                        <ENT>Mylan Pharmaceuticals, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 078731</ENT>
                        <ENT>Levetiracetam Tablets, 250 mg, 500 mg, 750 mg, and 1,000 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 079184</ENT>
                        <ENT>Ursodiol Tablets USP, 250 mg and 500 mg</ENT>
                        <ENT>Teva Pharmaceuticals USA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 081295</ENT>
                        <ENT>Estradiol Tablets USP, 0.5 mg</ENT>
                        <ENT>Bristol-Myers Squibb Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 084499</ENT>
                        <ENT>Estradiol Tablets USP, 1 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 084500</ENT>
                        <ENT>Estradiol Tablets USP, 2 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 085794</ENT>
                        <ENT>Acetaminophen and Codeine Phosphate Tablets USP, 300 mg/30 mg</ENT>
                        <ENT>Mutual Pharmaceutical Co., Inc., 1100 Orthodox St., Philadelphia, PA 19124.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 085795</ENT>
                        <ENT>Acetaminophen and Codeine Phosphate Tablets USP, 300 mg/15 mg</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 087176</ENT>
                        <ENT>Chlorthalidone Tablets USP, 50 mg</ENT>
                        <ENT>Ivax Pharmaceuticals, Inc., Subsidiary of Teva Pharmaceuticals USA, 400 Chestnut Ridge Rd., Woodcliff Lake, NJ 07677.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 087653</ENT>
                        <ENT>Acetaminophen and Codeine Phosphate Tablets USP, 300 mg/60 mg</ENT>
                        <ENT>Mutual Pharmaceutical Co., Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 088833</ENT>
                        <ENT>Triprolidine HCl, pseudoephedrine HCl, and Codeine Phosphate Cough Syrup, 1.25 mg/5 mL, 30 mg/5 mL, and 10 mg/5 mL</ENT>
                        <ENT>Wockhardt Bio AG, c/o Morton Grove Pharmaceuticals, Inc., 6451 Main St., Morton Grove, IL 60053.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDA 088896</ENT>
                        <ENT>Promethazine VC with Codeine (promethazine HCl, phenylephrine HCl, and codeine phosphate) Cough Syrup, 6.25 mg/5 mL, 5 mg/5 mL, and 10 mg/5 mL</ENT>
                        <ENT>Do.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NDA 202343</ENT>
                        <ENT>Juvisync (sitagliptin and simvastatin) Tablets, 100 mg/10 mg, 100 mg/20 mg, and 100 mg/40 mg</ENT>
                        <ENT>Merck Sharp &amp; Dohme Corp., 351 North Sumneytown Pike, P.O. Box 1000, UG2CD-015, North Wales, PA 19454.</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         This product included an oral pressurized metered-dose inhaler that contained chlorofluorocarbons (CFCs) as a propellant. CFCs may no longer be used as a propellant for any flunisolide metered-dose inhalers (see 75 FR 19213, April 14, 2010).
                    </TNOTE>
                </GPOTABLE>
                <P>
                    Therefore, under section 505(e) of the Federal Food, Drug, and Cosmetic Act (the FD&amp;C Act) (21 U.S.C. 355(e)) and under authority delegated to the Director, Center for Drug Evaluation and Research, by the Commissioner, approval of the applications listed in table 1 in this document, and all amendments and supplements thereto, is hereby withdrawn, effective January 5, 2015. Introduction or delivery for introduction into interstate commerce of products without approved new drug applications violates section 301(a) and (d) of the FD&amp;C Act (21 U.S.C. 331(a) and (d)). Drug products that are listed in Table 1 that are in inventory on the date that this notice becomes effective (see the 
                    <E T="02">DATES</E>
                     section) may continue to be dispensed until the inventories have been depleted or the drug products have reached their expiration dates or otherwise become violative, whichever occurs first.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Leslie Kux,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28541 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission to OMB for Review and Approval; Public Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with Section 3507(a)(1)(D) of the Paperwork 
                        <PRTPAGE P="72189"/>
                        Reduction Act of 1995, the Health Resources and Services Administration (HRSA) has submitted an Information Collection Request (ICR) to the Office of Management and Budget (OMB) for review and approval. Comments submitted during the first public review of this ICR will be provided to OMB. OMB will accept further comments from the public during the review and approval period.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this ICR should be received no later than January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, including the Information Collection Request Title, to the desk officer for HRSA, either by email to 
                        <E T="03">OIRA_submission@omb.eop.gov</E>
                         or by fax to 202-395-5806.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request a copy of the clearance requests submitted to OMB for review, email the HRSA Information Collection Clearance Officer at 
                        <E T="03">paperwork@hrsa.gov</E>
                         or call (301) 443-1984.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Information Collection Request Title:</E>
                     Health Professions Student Loan (HPSL) Program and Nursing Student Loan (NSL) Program Administrative Requirements (Regulations and Policy).
                </P>
                <P>OMB No. 0915-0047—Extension.</P>
                <P>
                    <E T="03">Abstract:</E>
                     The statutory authorities for the Health Professions Student Loan (HPSL) Program, as authorized by Public Health Service (PHS) Act sections 721-722, and 725-735, and the Nursing Student Loan (NSL) Program, as authorized by PHS Act sections 835-842, contain a number of recordkeeping and reporting requirements for academic institutions and loan applicants. The applicable regulations for these programs under 42 CFR part 57 details the various requirements (see chart below).
                </P>
                <P>
                    <E T="03">Need and Proposed Use of the Information:</E>
                     The requirements are essential for assuring that borrowers are aware of their rights and responsibilities, academic institutions have accurate records of the history and status of each loan account in order to pursue aggressive collection efforts to reduce default rates, and that academic institutions maintain adequate records for audit and assessment purposes to help the U.S. Department of Health and Human Services safeguard federal funds made through the Federal Capital Contribution (FCC). Academic institutions are free to use improved information technology to manage the information required by the regulations.
                </P>
                <P>
                    <E T="03">Likely Respondents:</E>
                     Financial Aid Directors working at institutions participating in the HPSL and NSL Programs.
                </P>
                <P>
                    <E T="03">Burden Statement:</E>
                     Burden in this context means the time expended by persons to generate, maintain, retain, disclose or provide the information requested. This includes the time needed to review instructions; to develop, acquire, install and utilize technology and systems for the purpose of collecting, validating and verifying information, processing and maintaining information, and disclosing and providing information; to train personnel and to be able to respond to a collection of information; to search data sources; to complete and review the collection of information; and to transmit or otherwise disclose the information. The total annual burden hours estimated for this ICR are summarized in the table below.
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,12,12,12">
                    <TTITLE>Total Estimated Annualized Burden—Hours</TTITLE>
                    <TTITLE>Recordkeeping Requirements</TTITLE>
                    <BOXHD>
                        <CHED H="1">Regulatory/section requirements</CHED>
                        <CHED H="1">Number of record keepers</CHED>
                        <CHED H="1">Hours per year</CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">HPSL Program:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.206(b)(2), Documentation of Cost of Attendance</ENT>
                        <ENT>50</ENT>
                        <ENT>325</ENT>
                        <ENT>16,250</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.208(a), Promissory Note</ENT>
                        <ENT>90</ENT>
                        <ENT>325</ENT>
                        <ENT>29,250</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210((b)(1)(i), Documentation of Entrance Interview</ENT>
                        <ENT>40</ENT>
                        <ENT>325</ENT>
                        <ENT>13,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(ii), Documentation of Exit Interview</ENT>
                        <ENT>80</ENT>
                        <ENT>334</ENT>
                        <ENT>26,720</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.215(a)&amp;(d), Program Records</ENT>
                        <ENT>140</ENT>
                        <ENT>334</ENT>
                        <ENT>46,760</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.215(b), Student Records</ENT>
                        <ENT>70</ENT>
                        <ENT>334</ENT>
                        <ENT>23,380</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">57.215(c), Repayment Records</ENT>
                        <ENT>150</ENT>
                        <ENT>334</ENT>
                        <ENT>50,100</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="05">HPSL Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>205,460</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">NSL Program:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.306(b)(2)(ii), Documentation of Cost of Attendance</ENT>
                        <ENT>16.0</ENT>
                        <ENT>282</ENT>
                        <ENT>4,512</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.308(a), Promissory Note</ENT>
                        <ENT>4.5</ENT>
                        <ENT>282</ENT>
                        <ENT>1,269</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(i), Documentation of Entrance Interview</ENT>
                        <ENT>1.5</ENT>
                        <ENT>282</ENT>
                        <ENT>423</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(ii), Documentation of Exit Interview</ENT>
                        <ENT>1.5</ENT>
                        <ENT>348</ENT>
                        <ENT>522</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.315(a)(1)&amp;(a)(4), Program Records</ENT>
                        <ENT>21.0</ENT>
                        <ENT>348</ENT>
                        <ENT>7,308</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.315(a)(2), Student Records</ENT>
                        <ENT>8.5</ENT>
                        <ENT>348</ENT>
                        <ENT>2,958</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">57.315(a)(3), Repayment Records</ENT>
                        <ENT>5.0</ENT>
                        <ENT>348</ENT>
                        <ENT>1,740</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">NSL Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>18,732</ENT>
                    </ROW>
                    <TNOTE>* Includes active and closing schools.</TNOTE>
                    <TNOTE>HPSL data includes active and closing Loans for Disadvantaged Students (LDS) program schools.</TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12,12,12,12,12">
                    <TTITLE>Reporting Requirements</TTITLE>
                    <BOXHD>
                        <CHED H="1">Regulatory/section requirements</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Responses per 
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Total hour 
                            <LI>burden</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">HPSL Program:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.206(a)(2), Student Financial Aid Transcript</ENT>
                        <ENT>n/a</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.208(c), Loan Information Disclosure</ENT>
                        <ENT>325</ENT>
                        <ENT>299.5</ENT>
                        <ENT>97,338</ENT>
                        <ENT>0.63</ENT>
                        <ENT>60,836</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(i), Entrance Interview</ENT>
                        <ENT>325</ENT>
                        <ENT>139.5</ENT>
                        <ENT>45,338</ENT>
                        <ENT>0.50</ENT>
                        <ENT>22,669</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(ii), Exit Interview</ENT>
                        <ENT>334</ENT>
                        <ENT>113.5</ENT>
                        <ENT>37,909</ENT>
                        <ENT>1.00</ENT>
                        <ENT>37,909</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="72190"/>
                        <ENT I="03">57.210(b)(1)(iii), Notification of Repayment</ENT>
                        <ENT>334</ENT>
                        <ENT>862.5</ENT>
                        <ENT>288,075</ENT>
                        <ENT>0.38</ENT>
                        <ENT>108,028</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(iv), Notification During Deferment</ENT>
                        <ENT>334</ENT>
                        <ENT>17.0</ENT>
                        <ENT>5,678</ENT>
                        <ENT>0.63</ENT>
                        <ENT>3,549</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(vi), Notification of Delinquent Accounts</ENT>
                        <ENT>334</ENT>
                        <ENT>172.5</ENT>
                        <ENT>57,615</ENT>
                        <ENT>1.25</ENT>
                        <ENT>72,019</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(1)(x), Credit Bureau Notification</ENT>
                        <ENT>334</ENT>
                        <ENT>6</ENT>
                        <ENT>2,004</ENT>
                        <ENT>0.50</ENT>
                        <ENT>1,002</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.210(b)(4)(i), Write-off of Uncollectible Loans</ENT>
                        <ENT>5</ENT>
                        <ENT>1</ENT>
                        <ENT>5</ENT>
                        <ENT>3.00</ENT>
                        <ENT>15</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.211(a) Disability Cancellation</ENT>
                        <ENT>3</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>1.00</ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.215(a)(2), Administrative Hearings</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">57.215(a)(d), Administrative Hearings</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="05">HPSL Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>306,029</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">NSL Program:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.306(a)(2), Student Financial Aid Transcript</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(i), Entrance Interview</ENT>
                        <ENT>282</ENT>
                        <ENT>17.5</ENT>
                        <ENT>4,935</ENT>
                        <ENT>0.42</ENT>
                        <ENT>2,048</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(ii), Exit Interview</ENT>
                        <ENT>348</ENT>
                        <ENT>9.0</ENT>
                        <ENT>3,132</ENT>
                        <ENT>0.42</ENT>
                        <ENT>1,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.301(b)(1)(iii), Notification of Repayment</ENT>
                        <ENT>348</ENT>
                        <ENT>9.0</ENT>
                        <ENT>3,132</ENT>
                        <ENT>0.27</ENT>
                        <ENT>830</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(iv), Notification During Deferment</ENT>
                        <ENT>348</ENT>
                        <ENT>1.5</ENT>
                        <ENT>522</ENT>
                        <ENT>0.29</ENT>
                        <ENT>151</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(vi), Notification of Delinquent Accounts</ENT>
                        <ENT>348</ENT>
                        <ENT>42.5</ENT>
                        <ENT>14,790</ENT>
                        <ENT>0.04</ENT>
                        <ENT>592</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(1)(x), Credit Bureau Notification</ENT>
                        <ENT>348</ENT>
                        <ENT>709.0</ENT>
                        <ENT>246,732</ENT>
                        <ENT>0.00</ENT>
                        <ENT>86</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.310(b)(4)(i), Write-off of Uncollectible Loans</ENT>
                        <ENT>23</ENT>
                        <ENT>1.0</ENT>
                        <ENT>23</ENT>
                        <ENT>3.00</ENT>
                        <ENT>69</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.311(a), Disability Cancellation</ENT>
                        <ENT>16</ENT>
                        <ENT>1.0</ENT>
                        <ENT>16</ENT>
                        <ENT>1.00</ENT>
                        <ENT>16</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">57.315(a)(1)(ii), Administrative Hearings</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">57.316(a)(d), Administrative Hearings</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">NSL Subtotal</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>5,092</ENT>
                    </ROW>
                    <TNOTE>*Includes active and closing schools.</TNOTE>
                </GPOTABLE>
                <SIG>
                    <NAME>Jackie Painter,</NAME>
                    <TITLE>Acting Director, Division of Policy and Information Coordination.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28555 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4165-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Cancer Institute; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings. </P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; Outstanding Investigator Award 2.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 24-26, 2015.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6:00 p.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Gaithersburg Marriott Washingtonian Center, 9751 Washingtonian Boulevard, Gaithersburg, MD 20878.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Peter J. Wirth, Ph.D., Scientific Review Officer, Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, 9609 Medical Center Drive, Room 7W154, Rockville, MD 20850, 240-276-6434, 
                        <E T="03">pw2q@nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; Outstanding Investigator Award 1.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 24-26, 2015.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6:00 p.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Gaithersburg Marriott Washingtonian Center, 9751 Washingtonian Boulevard, Gaithersburg, MD 20878.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Michael B. Small, Ph.D., Chief, Program and Review Extramural Staff Training Office, Division of Extramural Activities, National Cancer Institute, 9609 Medical Center Drive, Room 7W412, Rockville, MD 20850, 240-276-6438, 
                        <E T="03">smallm@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; Outstanding Investigator Award 3.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         March 24-26, 2015.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6:00 p.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Gaithersburg Marriott Washingtonian Center, 9751 Washingtonian Boulevard, Gaithersburg, MD 20878.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Shamala K. Srinivas, Ph.D., Scientific Review Officer, Office of Referral, Review, and Program Coordination, Division of Extramural Activities, National Cancer Institute, NIH, 9609 Medical Center Drive, 7W530, Rockville, MD 20850, 240-276-6442, 
                        <E T="03">ss537t@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        Information is also available on the Institute's/Center's home page: 
                        <E T="03">http://deainfo.nci.nih.gov/advisory/sep/sep.htm,</E>
                         where an agenda and any additional information for the meeting will be posted when available.
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Melanie J. Gray,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28530 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Human Genome Research Institute; Notice of Meeting</SUBJECT>
                <P>
                    Pursuant to section 10(d) of the Federal Advisory Committee Act, as 
                    <PRTPAGE P="72191"/>
                    amended (5 U.S.C. App.), notice is hereby given of a meeting of the Board of Scientific Counselors, National Human Genome Research Institute.
                </P>
                <P>The meeting will be open to the public as indicated below, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
                <P>The meeting will be closed to the public as indicated below in accordance with the provisions set forth in section 552b(c)(6), Title 5 U.S.C., as amended for the review, discussion, and evaluation of individual intramural programs and projects conducted by the National Human Genome Research Institute, including consideration of personnel qualifications and performance, and the competence of individual investigators, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Board of Scientific Counselors, National Human Genome Research Institute.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         December 10-11, 2014.
                    </P>
                    <P>
                        <E T="03">Closed:</E>
                         December 10, 2014, 5:00 p.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate personal qualifications and performance, and competence of individual investigators.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Open:</E>
                         December 10, 2014, 7:00 p.m. to 9:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To discuss matters of program relevance.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Open:</E>
                         December 11, 2014, 8:00 a.m. to 1:45 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To discuss matters of program relevance.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Natcher Conference Center, Room F1/F2 (lower level), 45 Center Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Closed:</E>
                         December 11, 2014, 1:45 p.m. to 3:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate personal qualifications and performance, and competence of individual investigators.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Natcher Conference Center, Room F1/F2 (lower level), 45 Center Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Open:</E>
                         December 11, 2014, 3:30 p.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         Closing Keynote.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Natcher Conference Center, Room F1/F2 (lower level), 45 Center Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Monica Berger, Executive Secretary, Office of the Scientific Director, National Human Genome Research Institute, 50 South Drive, Bldg. 50, Rm. 5222, Bethesda, MD 20892, 301-294-6873, 
                        <E T="03">bergerm@mail.nih.gov</E>
                        .
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the urgent need to meet timing limitations imposed by the intramural research review cycle.</P>
                    <P>In the interest of security, NIH has instituted stringent procedures for entrance onto the NIH campus. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.</P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.172, Human Genome Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: December 1, 2014.</DATED>
                    <NAME>David Clary,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28529 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Clinical Center; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the Board of Scientific Counselors of the NIH Clinical Center.</P>
                <P>The meeting will be closed to the public as indicated below in accordance with the provisions set forth in section 552b(c)(6), Title 5 U.S.C., as amended for the review, discussion, and evaluation of individual intramural programs and projects conducted by the CLINICAL CENTER, including consideration of personnel qualifications and performance, and the competence of individual investigators, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Board of Scientific Counselors of the NIH Clinical Center.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         January 5-6, 2015.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:00 a.m. to 4:45 p.m.; 8:00 a.m. to 11:45 a.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate the Bioethics Department.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Building 10, 4-2551, 10 Center Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mary Sparks, Nurse Consultant for the Deputy Director for Clinical Care, Office of the Deputy Director, Clinical Center, National Institutes of Health, Building 10, Room 6-3521, Bethesda, MD 20892, (301) 496-3515.
                    </P>
                    <P>In the interest of security, NIH has instituted stringent procedures for entrance onto the NIH campus. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.</P>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Michelle Trout,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28527 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Cognition, Diabetic Neuropathy and Metabolomics.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         December 19, 2014.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         3:00 p.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Suzan Nadi, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5217B, MSC 7846, Bethesda, MD 20892, 301-435-1259, 
                        <E T="03">nadis@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="72192"/>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Melanie J. Gray,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28528 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>United States Immigration and Customs Enforcement</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Extension, With Changes, of an Existing Information Collection; Comment Request</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-Day notice of information collection for review; Form No. I-901; fee remittance for certain F, J and M non-immigrants; OMB Control No. 1653-0034.</P>
                </ACT>
                <P>
                    The Department of Homeland Security, U.S. Immigration and Customs Enforcement (USICE), is submitting the following information collection request for review and clearance in accordance with the Paperwork Reduction Act of 1995. The information collection is published in the 
                    <E T="04">Federal Register</E>
                     to obtain comments from the public and affected agencies. The information collection was previously published in the 
                    <E T="04">Federal Register</E>
                     on September 25, 2014, Vol. 79 No. 22829 allowing for a 60 day comment period. No comments were received on this information collection. The purpose of this notice is to allow an additional 30 days for public comments.
                </P>
                <P>
                    Written comments and suggestions regarding items contained in this notice and especially with regard to the estimated public burden and associated response time should be directed to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the OMB Desk Officer for U.S. Immigration and Customs Enforcement, Department of Homeland Security, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov</E>
                     or faxed to (202) 395-5806.
                </P>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information should address one or more of the following four points:</P>
                <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of the agencies estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <HD SOURCE="HD1">Overview of This Information Collection</HD>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Extension, with changes, of a currently approved information collection.
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Fee Remittance for Certain F, J and M Non-immigrants.
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the Department of Homeland Security sponsoring the collection:</E>
                     Form I-901, U.S. Immigration and Customs Enforcement.
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                     Primary: Individuals or households. Public Law 104-208, Subtitle D, Section 641 directs the Attorney General, in consultation with the Secretary of State and the Secretary of Education, to develop and conduct a program to collect information on nonimmigrant foreign students and exchange visitors from approved institutions of higher education, as defined in section 101(a) of the Higher Education Act of 1965, as amended or in a program of study at any other DHS approved academic or language-training institution, to include approved private elementary and secondary schools and public secondary schools, and from approved exchange visitor program sponsors designated by the Department of State (DOS). It also authorized a fee, not to exceed $200, to be collected from these students and exchange visitors to support this information collection program. DHS has implemented the Student and Exchange Visitor Information System (SEVIS) to carry out this statutory requirement.
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                     805,786 responses at 15 minutes (.25 hours) per response.
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>
                     The burden figures have been updated since the publication of the 60 day 
                    <E T="04">Federal Register</E>
                     notice to provide better estimates—201,447 annual burden hours.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Scott Elmore,</NAME>
                    <TITLE>Program Manager, Forms Management Office, Office of the Chief Information Officer, U.S. Immigration and Customs Enforcement, Department of Homeland Security.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28504 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9111-28-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5752-N-102]</DEPDOC>
                <SUBJECT>30-Day Notice of Proposed Information Collection: Survey Questions for Small Contractor Marketplace</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD has submitted the proposed information collection requirement described below to the Office of Management and Budget (OMB) for review, in accordance with the Paperwork Reduction Act. The purpose of this notice is to allow for an additional 30 days of public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         January 5, 2015.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control Number and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; fax: 202-395-5806. Email: 
                        <E T="03">OIRA_Submission@omb.eop.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colette Pollard, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street SW., Washington, DC 20410; email at 
                        <E T="03">ColettePollard@hud.gov</E>
                         or telephone 202-402-3400. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at (800) 877-8339. This is not a toll-free number. Copies of available documents submitted to OMB may be obtained from Ms. Pollard.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice informs the public that HUD has submitted to OMB a request for approval of the information collection described in Section A.</P>
                <P>
                    The 
                    <E T="04">Federal Register</E>
                     notice that solicited public comment on the 
                    <PRTPAGE P="72193"/>
                    information collection for a period of 60 days was published on September 29, 2014.
                </P>
                <HD SOURCE="HD1">A. Overview of Information Collection</HD>
                <P>
                    <E T="03">Title of Information Collection:</E>
                     Survey Form for Small Contractor Initiative.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2506—New.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     New collection.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Description of the need for the information and proposed use:</E>
                     Survey collection form for the Small Contractor Initiative. HUD is partnering with the U.S. Small Business Administration (SBA) and BusinessUSA to promote the HUD Small Contractor Initiative through the BusinessUSA FBOpen Web site. The Web site will be used by HUD and other federal agencies to notify small contractors for bid opportunities nationwide in one place online. Surveys will be collected from grantees in the BusinessUSA online system and follow-up user surveys for different user groups such as HUD grantees, contracting companies, lenders, surety bond agents, and business counseling organizations.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     (
                    <E T="03">i.e.</E>
                     affected public): State, local, and tribal governments. HUD grantees, contracting companies, lenders, surety bond agents, and business counseling organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     5,000.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     20,000.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     4.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     1.
                </P>
                <P>
                    <E T="03">Total Estimated Burdens:</E>
                     20,000.
                </P>
                <GPOTABLE COLS="08" OPTS="L2,tp0,i1" CDEF="s50,12,12,12,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Information collection</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">Responses per annum</CHED>
                        <CHED H="1">Burden hour per response</CHED>
                        <CHED H="1">Annual burden hours</CHED>
                        <CHED H="1">Hourly cost per response</CHED>
                        <CHED H="1">Annual cost</CHED>
                    </BOXHD>
                    <ROW RUL="n,s">
                        <ENT I="01">Survey Form</ENT>
                        <ENT>5,000</ENT>
                        <ENT>4</ENT>
                        <ENT>20,000</ENT>
                        <ENT>1</ENT>
                        <ENT>20,000</ENT>
                        <ENT>$0</ENT>
                        <ENT>$0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>5,000</ENT>
                        <ENT>4</ENT>
                        <ENT>20,000</ENT>
                        <ENT>1</ENT>
                        <ENT>20,000</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">B. Solicitation of Public Comment</HD>
                <P>This notice is soliciting comments from members of the public and affected parties concerning the collection of information described in Section A on the following:</P>
                <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) The accuracy of the agency's estimate of the burden of the proposed collection of information;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Ways to minimize the burden of the collection of information on those who are to respond; including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>HUD encourages interested parties to submit comment in response to these questions.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. Chapter 35.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: November 28, 2014.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Department Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28621 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5752-N-101]</DEPDOC>
                <SUBJECT>30-Day Notice of Proposed Information Collection: Use Restriction Agreement Monitoring and Compliance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD has submitted the proposed information collection requirement described below to the Office of Management and Budget (OMB) for review, in accordance with the Paperwork Reduction Act. The purpose of this notice is to allow for an additional 30 days of public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         January 5, 2015.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control Number and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; fax: 202-395-5806. Email: 
                        <E T="03">OIRA_Submission@omb.eop.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colette Pollard, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street SW., Washington, DC 20410; email at 
                        <E T="03">Colette Pollard@hud.gov</E>
                         or telephone 202-402-3400. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at (800) 877-8339. This is not a toll-free number. Copies of available documents submitted to OMB may be obtained from Ms. Pollard.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice informs the public that HUD has submitted to OMB a request for approval of the information collection described in Section A.</P>
                <P>
                    The 
                    <E T="04">Federal Register</E>
                     notice that solicited public comment on the information collection for a period of 60 days was published on June 25, 2014.
                </P>
                <HD SOURCE="HD1">A. Overview of Information Collection</HD>
                <P>
                    <E T="03">Title of Information Collection:</E>
                     Use Restriction Agreement Monitoring and Compliance.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0577.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision or extension of currently approved collection.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     (HUD-90060, HUD-90061, HUD-90065, HUD-90066, HUD-93140, HUD-93142, HUD-93143, HUD-93144, HUD-90067, HUD-90068, HUD-90069, HUD-90070, HUD-93150, HUD-93155, HUD-90075).
                </P>
                <P>
                    <E T="03">Description of the need for the information and proposed use:</E>
                     This information is necessary for HUD to ensure that owners of certain multifamily housing projects comply with use restriction requirements once the mortgage agreement is terminated. This information is also used to monitor owner compliance with the Use Restriction Agreement provisions.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     Non-profit institutions.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     848.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     848.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     1.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     2.
                </P>
                <P>
                    <E T="03">Total Estimated Burdens:</E>
                     1,696.
                </P>
                <HD SOURCE="HD1">B. Solicitation of Public Comment</HD>
                <P>
                    This notice is soliciting comments from members of the public and affected parties concerning the collection of 
                    <PRTPAGE P="72194"/>
                    information described in Section A on the following:
                </P>
                <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) The accuracy of the agency's estimate of the burden of the proposed collection of information;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Ways to minimize the burden of the collection of information on those who are to respond; including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>HUD encourages interested parties to submit comment in response to these questions.</P>
                <AUTH>
                    <HD SOURCE="HED"> Authority:</HD>
                    <P> Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. Chapter 35.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: November 26, 2014.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Department Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28629 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5756-N-41]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Application for Energy Innovation Fund—Multifamily Pilot Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Housing—Federal Housing Commissioner, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD is seeking approval from the Office of Management and Budget (OMB) for the information collection described below. In accordance with the Paperwork Reduction Act, HUD is requesting comment from all interested parties on the proposed collection of information. The purpose of this notice is to allow for 60 days of public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         February 3, 2015.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control Number and should be sent to: Colette Pollard, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street SW., Room 4176, Washington, DC 20410-5000; telephone 202-402-3400 (this is not a toll-free number) or email at 
                        <E T="03">Colette.Pollard@hud.gov</E>
                         for a copy of the proposed forms or other available information. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at (800) 877-8339.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office Of Portfolio Management, Claude Dickson, Bonds and Appeals Manager, Office of Multifamily Housing, 
                        <E T="03">claude.c.dickson@hud.gov,</E>
                         Phone Number: (202) 402-8372, Department of Housing and Urban Development, 451 7th Street SW., Washington, DC 20410. This is not a toll-free number. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at (800) 877-8339.
                    </P>
                    <P>Copies of available documents submitted to OMB may be obtained from Ms. Pollard.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice informs the public that HUD is seeking approval from OMB for the information collection described in Section A.</P>
                <HD SOURCE="HD1">A. Overview of Information Collection</HD>
                <P>
                    <E T="03">Title of Information Collection:</E>
                     Application for Energy Innovation Fund—Multifamily Pilot Program.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0599.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of currently approved collection.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     Sample Final Report.
                </P>
                <P>
                    <E T="03">Description of the need for the information and proposed use:</E>
                     Application information will be used to evaluate, score and rank applications for grant funds.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     12.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     120.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     4.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     25.
                </P>
                <P>
                    <E T="03">Total Estimated Burdens:</E>
                     464.
                </P>
                <HD SOURCE="HD1">B. Solicitation of Public Comment</HD>
                <P>This notice is soliciting comments from members of the public and affected parties concerning the collection of information described in Section A on the following:</P>
                <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) The accuracy of the agency's estimate of the burden of the proposed collection of information;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Ways to minimize the burden of the collection of information on those who are to respond; including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>HUD encourages interested parties to submit comment in response to these questions.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. Chapter 35.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Laura M. Marin</NAME>
                    <TITLE>Associate General Deputy Assistant Secretary for Housing-Associate Deputy Federal Housing Commissioner.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28594 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5752-N-100]</DEPDOC>
                <SUBJECT>30-Day Notice of Proposed Information Collection: Multifamily Insurance Benefits Claims Package</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD has submitted the proposed information collection requirement described below to the Office of Management and Budget (OMB) for review, in accordance with the Paperwork Reduction Act. The purpose of this notice is to allow for an additional 30 days of public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         January 5, 2015.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control Number and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; fax: 202-395-5806. Email: 
                        <E T="03">OIRA_Submission@omb.eop.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colette Pollard, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street SW., Washington, DC 20410; email at 
                        <E T="03">Colette Pollard@hud.gov</E>
                         or telephone 202-402-3400. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at (800) 877-8339. This is not a toll-free number. Copies of available documents submitted to OMB may be obtained from Ms. Pollard.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <PRTPAGE P="72195"/>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice informs the public that HUD has submitted to OMB a request for approval of the information collection described in Section A.</P>
                <P>
                    The 
                    <E T="04">Federal Register</E>
                     notice that solicited public comment on the information collection for a period of 60 days was published on August 21, 2014.
                </P>
                <HD SOURCE="HD1">A. Overview of Information Collection</HD>
                <P>
                    <E T="03">Title of Information Collection:</E>
                     Multifamily Insurance Benefits Claims Package.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0418.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of currently approved collection.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     HUD-2741, HUD-2742, HUD-2744A, HUD-2744B, HUD-2744C,  HUD-2744D, HUD-2744E, HUD-434, HUD-1044D.
                </P>
                <P>
                    <E T="03">Description of the need for the information and proposed use:</E>
                     We need this information to pay a claim. This has to do with all the backup paperwork to pay a complete and accurate claim for the mortgagee company.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     125.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     4.25.
                </P>
                <P>
                    <E T="03">Total Estimated Burdens:</E>
                     531.25.
                </P>
                <HD SOURCE="HD1">B. Solicitation of Public Comment</HD>
                <P>This notice is soliciting comments from members of the public and affected parties concerning the collection of information described in Section A on the following:</P>
                <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(2) The accuracy of the agency's estimate of the burden of the proposed collection of information;</P>
                <P>(3) Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Ways to minimize the burden of the collection of information on those who are to respond; including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>HUD encourages interested parties to submit comment in response to these questions.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. Chapter 35.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: November 26, 2014.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Department Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28631 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5750-N-49]</DEPDOC>
                <SUBJECT>Federal Property Suitable as Facilities To Assist the Homeless</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Community Planning and Development, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This Notice identifies unutilized, underutilized, excess, and surplus Federal property reviewed by HUD for suitability for use to assist the homeless.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Juanita Perry, Department of Housing and Urban Development, 451 Seventh Street SW., Room 7266, Washington, DC 20410; telephone (202) 402-3970; TTY number for the hearing- and speech-impaired (202) 708-2565 (these telephone numbers are not toll-free), or call the toll-free Title V information line at 800-927-7588.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with 24 CFR part 581 and section 501 of the Stewart B. McKinney Homeless Assistance Act (42 U.S.C. 11411), as amended, HUD is publishing this Notice to identify Federal buildings and other real property that HUD has reviewed for suitability for use to assist the homeless. The properties were reviewed using information provided to HUD by Federal landholding agencies regarding unutilized and underutilized buildings and real property controlled by such agencies or by GSA regarding its inventory of excess or surplus Federal property. This Notice is also published in order to comply with the December 12, 1988 Court Order in 
                    <E T="03">National Coalition for the Homeless</E>
                     v.
                    <E T="03"> Veterans Administration,</E>
                     No. 88-2503-OG (D.D.C.).
                </P>
                <P>Properties reviewed are listed in this Notice according to the following categories: Suitable/available, suitable/unavailable, and suitable/to be excess, and unsuitable. The properties listed in the three suitable categories have been reviewed by the landholding agencies, and each agency has transmitted to HUD: (1) Its intention to make the property available for use to assist the homeless, (2) its intention to declare the property excess to the agency's needs, or (3) a statement of the reasons that the property cannot be declared excess or made available for use as facilities to assist the homeless.</P>
                <P>Properties listed as suitable/available will be available exclusively for homeless use for a period of 60 days from the date of this Notice. Where property is described as for “off-site use only” recipients of the property will be required to relocate the building to their own site at their own expense. Homeless assistance providers interested in any such property should send a written expression of interest to HHS, addressed to Theresa Ritta, Ms. Theresa M. Ritta, Chief Real Property Branch, the Department of Health and Human Services, Room 5B-17, Parklawn Building, 5600 Fishers Lane, Rockville, MD 20857, (301) 443-6672 (This is not a toll-free number). HHS will mail to the interested provider an application packet, which will include instructions for completing the application. In order to maximize the opportunity to utilize a suitable property, providers should submit their written expressions of interest as soon as possible. For complete details concerning the processing of applications, the reader is encouraged to refer to the interim rule governing this program, 24 CFR part 581.</P>
                <P>For properties listed as suitable/to be excess, that property may, if subsequently accepted as excess by GSA, be made available for use by the homeless in accordance with applicable law, subject to screening for other Federal use. At the appropriate time, HUD will publish the property in a Notice showing it as either suitable/available or suitable/unavailable.</P>
                <P>For properties listed as suitable/unavailable, the landholding agency has decided that the property cannot be declared excess or made available for use to assist the homeless, and the property will not be available.</P>
                <P>
                    Properties listed as unsuitable will not be made available for any other purpose for 20 days from the date of this Notice. Homeless assistance providers interested in a review by HUD of the determination of unsuitability should call the toll free information line at 1-800-927-7588 for detailed instructions or write a letter to Ann Marie Oliva at the address listed at the beginning of this Notice. Included in the request for review should be the property address (including zip code), the date of publication in the 
                    <E T="04">Federal Register</E>
                    , the landholding agency, and the property number.
                </P>
                <P>
                    For more information regarding particular properties identified in this Notice (
                    <E T="03">i.e.,</E>
                     acreage, floor plan, existing sanitary facilities, exact street address), providers should contact the appropriate landholding agencies at the following addresses: 
                    <E T="03">Army:</E>
                     Ms. Veronica Rines, Office of the Assistant Chief of Staff for Installation Management, Department of Army, Room 5A128, 600 Army Pentagon, 
                    <PRTPAGE P="72196"/>
                    Washington, DC 20310, (571) 256-8145; (This is not a toll-free number).
                </P>
                <SIG>
                    <DATED>Dated: November 25, 2014.</DATED>
                    <NAME>Brian P. Fitzmaurice,</NAME>
                    <TITLE>Director, Division of Community Assistance, Office of Special Needs Assistance Programs.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">TITLE V, FEDERAL SURPLUS PROPERTY PROGRAM, FEDERAL REGISTER REPORT FOR 12/05/2014</HD>
                    <HD SOURCE="HD1">Suitable/Available Properties</HD>
                    <HD SOURCE="HD2">Building</HD>
                    <HD SOURCE="HD3">Arizona</HD>
                    <FP SOURCE="FP-1">Building 90890</FP>
                    <FP SOURCE="FP-1">Fort Huachuca</FP>
                    <FP SOURCE="FP-1">Fort Huachuca AZ 85613</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440051</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 40 sq. ft.; 80+ months vacant; repairs needed; contact Army for more information</FP>
                    <HD SOURCE="HD3">California</HD>
                    <FP SOURCE="FP-1">Building 00054</FP>
                    <FP SOURCE="FP-1">Los Alamitos Joint Forces Training Base</FP>
                    <FP SOURCE="FP-1">Los Alamitos CA 90720</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440019</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation extremely difficult due to size/type; 13,680 sq. ft.; national guard readiness center; very poor conditions; contact Army for more information</FP>
                    <HD SOURCE="HD3">Colorado</HD>
                    <FP SOURCE="FP-1">Building 01431</FP>
                    <FP SOURCE="FP-1">6101 Wetzel Ave.</FP>
                    <FP SOURCE="FP-1">Ft. Carson CO 80913</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440050</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 202 sq. ft.; 4+ months vacant; repair needed; contact Army for more information</FP>
                    <HD SOURCE="HD3">Georgia</HD>
                    <FP SOURCE="FP-1">Building 7097</FP>
                    <FP SOURCE="FP-1">Fort Stewart</FP>
                    <FP SOURCE="FP-1">Ft. Stewart GA 31314</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440007</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation difficult due to size/type; 9,520 sq. ft.; child development center; 6+ months vacant; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">100</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield GA 31409</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440008</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; relocation extremely difficult due to size; 13,331 sq. ft.; classroom; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">1020</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield GA 31409</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440009</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation extremely difficult due to size/type; 39,653 sq.; storage; 1+ month vacant; contact Army for more information</FP>
                    <FP SOURCE="FP-1">9002</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield</FP>
                    <FP SOURCE="FP-1">Hunter Army Airfield GA 31406</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440010</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation difficult due to type; 221 sq. ft.; 12+ months vacant; poor conditions; asbestos; contact Army for more information</FP>
                    <FP SOURCE="FP-1">5 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Benning</FP>
                    <FP SOURCE="FP-1">Ft. Benning GA 31905</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440013</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Directions: 8744; 8780; 8782; 8787; 9045</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; sq. ft. varies; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">Building 8510</FP>
                    <FP SOURCE="FP-1">5037 Moye Rd.</FP>
                    <FP SOURCE="FP-1">Fort Benning GA 31905</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440014</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 10,800 sq. ft.; relocation extremely difficult due to size/type; 8+ yrs.-old; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Benning</FP>
                    <FP SOURCE="FP-1">Ft. Benning GA 31905</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440016</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Directions: 9208; 9211</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation difficult due to size/type; sq. ft. varies; poor conditions; secured area; contact Army for more information</FP>
                    <HD SOURCE="HD3">Tennessee</HD>
                    <FP SOURCE="FP-1">9 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440002</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Directions: 00039; 00846; 05123; 05638; 05640; 05641; 05646; 07540; 07811</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; relocation may be extremely difficult due to size/type; sq. ft. varies; poor conditions; contamination; contact Army for more information</FP>
                    <FP SOURCE="FP-1">09R28</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440003</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 552 sq. ft.; 26+ yrs.-old; range support facility; repairs needed; secured area; contact Army for more information</FP>
                    <FP SOURCE="FP-1">04R28</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440004</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 800 sq. ft.; 26+ yrs.-old; major repairs; secured area; contact Army for more information</FP>
                    <FP SOURCE="FP-1">03R28, 02r28, &amp; 01R28</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440005</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 552 sq. ft.; range support facility; major repairs; secured area; contact Army for more information</FP>
                    <FP SOURCE="FP-1">05127</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440058</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; 224 sq. ft.; storage; fair conditions; contact Army for more information on accessibility/removal requirements</FP>
                    <FP SOURCE="FP-1">4 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440059</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Directions: 05211 (320 sq. ft.); 05665 (800 sq. ft.); 00100 (800 sq. ft.); 01604 (126 sq. ft.)</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; fair conditions; usage varies; contact Army for more information on a specific property</FP>
                    <HD SOURCE="HD3">Texas</HD>
                    <FP SOURCE="FP-1">07133</FP>
                    <FP SOURCE="FP-1">Fort Bliss</FP>
                    <FP SOURCE="FP-1">Ft. Bliss TX 79916</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440011</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation difficult due to size/type; 12,178 sq. ft.; storage; 120+ months vacant; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">5 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Bliss</FP>
                    <FP SOURCE="FP-1">Ft. Bliss TX 79916</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440012</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 07134; 07142; 07153; 07162; 07178</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation difficult due to size/type; sq. ft. varies; 120+ months vacant; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">05095</FP>
                    <FP SOURCE="FP-1">Fort Bliss</FP>
                    <FP SOURCE="FP-1">Ft. Bliss TX 79916</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440022</FP>
                    <FP SOURCE="FP-1">
                        Status: Unutilized
                        <PRTPAGE P="72197"/>
                    </FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 12+ months vacant; good conditions; secured area; contact Army for more information</FP>
                    <FP SOURCE="FP-1">07113</FP>
                    <FP SOURCE="FP-1">Fort Bliss</FP>
                    <FP SOURCE="FP-1">Ft. Bliss TX 79916</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440023</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; 8,855 sq. ft.; no future agency need; relocation difficult due to size/type; 120+ months vacant; child-care center; poor conditions; contact Army for more information</FP>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Yoakum USARC</FP>
                    <FP SOURCE="FP-1">Yoakum TX 77995</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440035</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Directions: P1005; P1006</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; 30 sq. ft.; storage for flammable materials; 53+ yrs.-old; remediation needed; contact Army for more information</FP>
                    <FP SOURCE="FP-1">01113</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Texarkana TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440043</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; 257 sq. ft.; access control facility; 50+ yrs.-old; contact Army for more information</FP>
                    <FP SOURCE="FP-1">00940</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Texarkana TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440044</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; 200 sq. ft.; break room; extensive deterioration; 19+ yrs.-old; secured area; contact Army for more information</FP>
                    <FP SOURCE="FP-1">00930</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Texarkana TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440046</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; 200 sq. ft.; ammunition storage; 31+ yrs.-old; extensive deterioration; secured area; contact Army for more information</FP>
                    <HD SOURCE="HD3">Washington</HD>
                    <FP SOURCE="FP-1">Building 02080</FP>
                    <FP SOURCE="FP-1">Joint Base Lewis McChord</FP>
                    <FP SOURCE="FP-1">JBLM WA 98433</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440048</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation may be difficult due to type/size; 2,031 sq. ft.; storage; 1+ month vacant; major repairs needed; contact Army for more information</FP>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Joint Base Lewis McChord</FP>
                    <FP SOURCE="FP-1">JBLM WA 98433</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440057</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Directions: 01036; 01037</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation extremely difficult due to size; 8,142 sq. ft. for each; major repairs needed; contact Army for more information</FP>
                    <HD SOURCE="HD3">Wisconsin</HD>
                    <FP SOURCE="FP-1">7 Buildings</FP>
                    <FP SOURCE="FP-1">Fort McCoy</FP>
                    <FP SOURCE="FP-1">Ft. McCoy WI 54656</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440053</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 00822; 01146; 01350; 02559; 02866; 09020; 09030</FP>
                    <FP SOURCE="FP-1">Comments: Off-site removal only; no future agency need; relocation may be difficult due to size/type; contamination; poor conditions; sq. varies; secured area; contact Army for more info.</FP>
                    <HD SOURCE="HD1">Unsuitable Properties</HD>
                    <HD SOURCE="HD2">Building</HD>
                    <HD SOURCE="HD3">Alabama</HD>
                    <FP SOURCE="FP-1">C1310</FP>
                    <FP SOURCE="FP-1">Fort McClellan</FP>
                    <FP SOURCE="FP-1">Ft. McClellan AL 36205</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440032</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">7134</FP>
                    <FP SOURCE="FP-1">Redstone Arsenal</FP>
                    <FP SOURCE="FP-1">Redstone Arsenal AL 35898</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440038</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Documented deficiencies: suffered severe flood damage; severe structural damage; clear threat to physical safety</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">4812</FP>
                    <FP SOURCE="FP-1">Redstone Arsenal</FP>
                    <FP SOURCE="FP-1">Redstone Arsenal AL 35898</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440039</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Documented deficiencies: suffered major damage from tornado; roof torn completely off; clear threat to physical safety</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Arkansas</HD>
                    <FP SOURCE="FP-1">5 Buildings</FP>
                    <FP SOURCE="FP-1">Pine Bluff Arsenal</FP>
                    <FP SOURCE="FP-1">Pine Bluff AR 71602</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440045</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 32070; 33150; 34133; 51650; 55040</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Colorado</HD>
                    <FP SOURCE="FP-1">Building 07303</FP>
                    <FP SOURCE="FP-1">Fort Carson</FP>
                    <FP SOURCE="FP-1">Ft. Carson CO 80913</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440020</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Illinois</HD>
                    <FP SOURCE="FP-1">343</FP>
                    <FP SOURCE="FP-1">USAG-Rock Island Arsenal</FP>
                    <FP SOURCE="FP-1">Rock Island Arsenal IL 61299</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440037</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Maryland</HD>
                    <FP SOURCE="FP-1">10 Buildings</FP>
                    <FP SOURCE="FP-1">Aberdeen Proving Ground</FP>
                    <FP SOURCE="FP-1">Aberdeen MD 21005</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440025</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 00351; 00379; 00893; E2570; E3365; E4100; E4162; E5307; E5359; E6000</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">E6100</FP>
                    <FP SOURCE="FP-1">Aberdeen Proving Ground</FP>
                    <FP SOURCE="FP-1">Abingdon MD 21009</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440027</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Entire property located w/in floodway where it has not been contained or corrected</FP>
                    <FP SOURCE="FP-1">Reasons: Floodway</FP>
                    <FP SOURCE="FP-1">6 Buildings</FP>
                    <FP SOURCE="FP-1">Aberdeen Proving Ground</FP>
                    <FP SOURCE="FP-1">Aberdeen MD 21010</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440028</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: E6101; E6102; E6105; E6110; E6111; E6112</FP>
                    <FP SOURCE="FP-1">Comments: Entire property located in a floodway where it has not been contained/corrected; public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Floodway; Secured Area</FP>
                    <HD SOURCE="HD3">Missouri</HD>
                    <FP SOURCE="FP-1">13 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood MO 65473</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440024</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 02431; 02433; 02435; 02462; 02464; 02466; 02468; 02470; 02472; 02474; 02476; 02478;02480</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">Building 00500</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood MO 65049</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">
                        Property Number: 21201440026
                        <PRTPAGE P="72198"/>
                    </FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">11 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood MO 65473</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440029</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 02461; 02463; 02465; 02467; 02469; 02471; 02473; 02475; 02477; 02479; 02481</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">3 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood MO 65473</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440030</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 02430; 02432; 02434</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood Lake of Ozarks Rec. Area</FP>
                    <FP SOURCE="FP-1">Fort Leonard Wood MO 65473</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440031</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 00550; 00500</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">New Jersey</HD>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Picatinny Arsenal</FP>
                    <FP SOURCE="FP-1">Dover NJ 07806</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440056</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 3208B; 3208G</FP>
                    <FP SOURCE="FP-1">Comments: Documented deficiencies: roof caving in; walls are rotted; overgrown vegetation; clear threat to physical safety</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <HD SOURCE="HD3">North Carolina</HD>
                    <FP SOURCE="FP-1">4 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Bragg</FP>
                    <FP SOURCE="FP-1">Ft. Bragg NC 28310</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440001</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: M6450; M2346; 14865; 03554</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">7 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Bragg</FP>
                    <FP SOURCE="FP-1">Ft. Bragg NC 28310</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440021</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Directions: 12732; 69262; 69357; 85703; 85706; 86103; 42102</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Oklahoma</HD>
                    <FP SOURCE="FP-1">Buildings</FP>
                    <FP SOURCE="FP-1">Fort Sill</FP>
                    <FP SOURCE="FP-1">Ft. Sill OK 73503</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440054</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 6280; 6281; 6283; 6292; 6295; 6293</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Pennsylvania</HD>
                    <FP SOURCE="FP-1">6 Buildings</FP>
                    <FP SOURCE="FP-1">Tobyhanna Army Depot</FP>
                    <FP SOURCE="FP-1">Tobyhanna PA 18466</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440036</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: 00046; 00245; 00246; A0031; A0132; S0051</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Rhode Island</HD>
                    <FP SOURCE="FP-1">Building 000P2</FP>
                    <FP SOURCE="FP-1">570 Read Schoolhouse Rd.</FP>
                    <FP SOURCE="FP-1">NG Coventry RI 02816</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440049</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">Building OSKRG</FP>
                    <FP SOURCE="FP-1">Camp Fogarty</FP>
                    <FP SOURCE="FP-1">East Greenwich RI 02818</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440052</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Documented Deficiencies: structural damage; several large holes; severely rotten foundation; extreme rodent infestation; clear threat to physical safety</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Tennessee</HD>
                    <FP SOURCE="FP-1">19 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Campbell</FP>
                    <FP SOURCE="FP-1">Ft. Campbell TN 42223</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440055</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Directions: A5212; 06099; 05860; 05800; 05223; 05217; 05668; 05214; 05213; 05212; 05160; 05128; 05125; 05121; 03068; 02604; 00893; 00892; 00849</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Texas</HD>
                    <FP SOURCE="FP-1">01445</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Texarkana TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440040</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security; documented deficiencies: roof caving-in; clear threat to physical safety</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration; Secured Area</FP>
                    <FP SOURCE="FP-1">3 Buildings</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Red River Army Depot TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440041</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Directions: 01161; 01162; 01165</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">01154</FP>
                    <FP SOURCE="FP-1">Red River Army Depot</FP>
                    <FP SOURCE="FP-1">Texarkana TX 75507</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440042</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Virginia</HD>
                    <FP SOURCE="FP-1">5 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Pickett Training Center</FP>
                    <FP SOURCE="FP-1">Blackstone VA 23824</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440006</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Directions: T2362; T2363; T2364; T2411; T2603</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">6 Buildings</FP>
                    <FP SOURCE="FP-1">Fort Belvoir</FP>
                    <FP SOURCE="FP-1">Ft. Belvoir VA 22060</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440017</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Directions: 1151; 1906; 1141; 1186; 1194; 1195</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">2 Buildings</FP>
                    <FP SOURCE="FP-1">Defense Distribution San Joaquin</FP>
                    <FP SOURCE="FP-1">Tracy Site 00046, 0234A</FP>
                    <FP SOURCE="FP-1">Tracy VA 95304</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440018</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Washington</HD>
                    <FP SOURCE="FP-1">23 Buildings</FP>
                    <FP SOURCE="FP-1">Joint Base Lewis McChord</FP>
                    <FP SOURCE="FP-1">JBLM WA 98433</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440047</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">
                        Directions: 07517; 07514; 07507; 07500; 03422; 03421; 03420; 03419; 03416; 03415; 03414; 03413; 03412; 03324; 03287; 03286; 03279; 03278; 03277; 03214;03212; 03213; 03080
                        <PRTPAGE P="72199"/>
                    </FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <HD SOURCE="HD3">Wisconsin</HD>
                    <FP SOURCE="FP-1">09003</FP>
                    <FP SOURCE="FP-1">Fort McCoy</FP>
                    <FP SOURCE="FP-1">Ft. McCoy WI 54656</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Army</FP>
                    <FP SOURCE="FP-1">Property Number: 21201440034</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comments: Public access denied and no alternative method to gain access w/out compromising national security</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28336 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[156D0102DM/DS64600000/DLSN00000.000000/DX.64601]</DEPDOC>
                <SUBJECT>Notice of Senior Executive Service Performance Review Board Appointments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice provides the names of individuals who have been appointed to serve as members of the Department of the Interior Senior Executive Service (SES) Performance Review Board.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        These appointments are effective upon publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas Mulhern, Director, Office of Human Resources, Office of the Secretary, Department of the Interior, 1849 C Street NW., Washington, DC 20240, Telephone Number: (202) 208-6761.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The members of the Department of the Interior SES Performance Review Board are as follows:</P>
                <HD SOURCE="HD1">Name</HD>
                <FP SOURCE="FP-1">ALTEMUS, MICHELE J.</FP>
                <FP SOURCE="FP-1">ANDERSON, ALLYSON K.</FP>
                <FP SOURCE="FP-1">ANDREW, JONATHAN M.</FP>
                <FP SOURCE="FP-1">APPLEGATE, JAMES D. R.</FP>
                <FP SOURCE="FP-1">ARROYO, BRYAN</FP>
                <FP SOURCE="FP-1">ATKINSON, KAREN J</FP>
                <FP SOURCE="FP-1">AUSTIN, STANLEY J.</FP>
                <FP SOURCE="FP-1">AWNI, MUHAMMAD H.</FP>
                <FP SOURCE="FP-1">BALES, JERAD D.</FP>
                <FP SOURCE="FP-1">BARCHENGER, ERVIN J</FP>
                <FP SOURCE="FP-1">BATHRICK, MARK L.</FP>
                <FP SOURCE="FP-1">BAYANI, THERESA WALSH</FP>
                <FP SOURCE="FP-1">BEALL, JAMES W</FP>
                <FP SOURCE="FP-1">BEAN, MICHAEL J.</FP>
                <FP SOURCE="FP-1">BEARPAW, GEORGE WATIE</FP>
                <FP SOURCE="FP-1">BEAUDREAU, TOMMY P.</FP>
                <FP SOURCE="FP-1">BECK, RICHARD T.</FP>
                <FP SOURCE="FP-1">BELIN, ALLETTA D.</FP>
                <FP SOURCE="FP-1">BERRIGAN, MICHAEL J.</FP>
                <FP SOURCE="FP-1">BIRDSONG, BRET CREECH</FP>
                <FP SOURCE="FP-1">BLACK, MICHAEL S.</FP>
                <FP SOURCE="FP-1">BLAIR, JOHN WATSON</FP>
                <FP SOURCE="FP-1">BLANCHARD, MARY JOSIE</FP>
                <FP SOURCE="FP-1">BLEDSOE DOWNES, ANN MARIE</FP>
                <FP SOURCE="FP-1">BOLING, EDWARD A.</FP>
                <FP SOURCE="FP-1">BOLTON, HANNIBAL</FP>
                <FP SOURCE="FP-1">BOWKER, BRYAN L.</FP>
                <FP SOURCE="FP-1">BROUN, LAURENCE I.</FP>
                <FP SOURCE="FP-1">BROWN, LAURA B.</FP>
                <FP SOURCE="FP-1">BROWN, WILLIAM Y</FP>
                <FP SOURCE="FP-1">BUFFA, NICOLE NMN</FP>
                <FP SOURCE="FP-1">BURCH, MELVIN E.</FP>
                <FP SOURCE="FP-1">BURCKMAN, JAMES N.</FP>
                <FP SOURCE="FP-1">BURDEN, JOHN W.</FP>
                <FP SOURCE="FP-1">BURNS, SYLVIA W.</FP>
                <FP SOURCE="FP-1">CALDWELL, MICHAEL A.</FP>
                <FP SOURCE="FP-1">CARAMANIAN, LORI L.</FP>
                <FP SOURCE="FP-1">CARL, LEON M.</FP>
                <FP SOURCE="FP-1">CARTER-PFISTERER, CAROLE</FP>
                <FP SOURCE="FP-1">CLARK, HORACE G.</FP>
                <FP SOURCE="FP-1">CLEMENT, JOEL P.</FP>
                <FP SOURCE="FP-1">COLANDER, BRANDI ADELE</FP>
                <FP SOURCE="FP-1">COMPTON, JEFFREY S.</FP>
                <FP SOURCE="FP-1">CONNELL, JAMIE E.</FP>
                <FP SOURCE="FP-1">CORDOVA-HARRISON, ELIZABE</FP>
                <FP SOURCE="FP-1">CRAFF, ROBERT C.</FP>
                <FP SOURCE="FP-1">CRIBLEY, BUD C</FP>
                <FP SOURCE="FP-1">CRUICKSHANK, WALTER D.</FP>
                <FP SOURCE="FP-1">CRUZAN, DARREN A.</FP>
                <FP SOURCE="FP-1">DARNELL, JOSEPH D.</FP>
                <FP SOURCE="FP-1">DAVIS, MARK H</FP>
                <FP SOURCE="FP-1">DEAN, FRANCIS J.</FP>
                <FP SOURCE="FP-1">DEERINWATER, DANIEL J.</FP>
                <FP SOURCE="FP-1">DICKINSON, WILLIAM K.</FP>
                <FP SOURCE="FP-1">DOHNER, CYNTHIA</FP>
                <FP SOURCE="FP-1">DOUGLAS, JAMES C.</FP>
                <FP SOURCE="FP-1">DREHER, ROBERT GEOFFREY</FP>
                <FP SOURCE="FP-1">DUTSCHKE, AMY L.</FP>
                <FP SOURCE="FP-1">EDSALL, DONNA LYNN</FP>
                <FP SOURCE="FP-1">ELLIS, STEVEN A</FP>
                <FP SOURCE="FP-1">ESQUIVEL, FRANCIS O.</FP>
                <FP SOURCE="FP-1">ESTENOZ, SHANNON A.</FP>
                <FP SOURCE="FP-1">ETHRIDGE, MAX M.</FP>
                <FP SOURCE="FP-1">FAETH, LORRAINE V.</FP>
                <FP SOURCE="FP-1">FARBER, MICHAEL D</FP>
                <FP SOURCE="FP-1">FERRITER, OLIVIA B.</FP>
                <FP SOURCE="FP-1">FLANAGAN, DENISE A.</FP>
                <FP SOURCE="FP-1">FORD, JEROME E.</FP>
                <FP SOURCE="FP-1">FORREST, VICKI L.</FP>
                <FP SOURCE="FP-1">FRAZER, GARY D.</FP>
                <FP SOURCE="FP-1">FREEMAN, SHAREE M.</FP>
                <FP SOURCE="FP-1">FREIHAGE, JASON E.</FP>
                <FP SOURCE="FP-1">FROST, HERBERT C.</FP>
                <FP SOURCE="FP-1">FULP, TERRANCE J</FP>
                <FP SOURCE="FP-1">GALLAGHER, KEVIN T</FP>
                <FP SOURCE="FP-1">GIDNER, JEROLD L.</FP>
                <FP SOURCE="FP-1">GIMBEL, JENNIFER L</FP>
                <FP SOURCE="FP-1">GLENN, DOUGLAS A</FP>
                <FP SOURCE="FP-1">GLOMB, STEPHEN J.</FP>
                <FP SOURCE="FP-1">GOKLANY, INDUR M.</FP>
                <FP SOURCE="FP-1">GOLDFUSS, CHRISTINA WHITE</FP>
                <FP SOURCE="FP-1">GONZALES-SCHREINER, ROSEA</FP>
                <FP SOURCE="FP-1">GOODWIN, JANET A.</FP>
                <FP SOURCE="FP-1">GOULD, GREGORY J.</FP>
                <FP SOURCE="FP-1">GOULD, ROWAN W.</FP>
                <FP SOURCE="FP-1">GRAZIANO, ANGELA V.</FP>
                <FP SOURCE="FP-1">GREENBERGER, SARAH D.</FP>
                <FP SOURCE="FP-1">GROSS, LAWRENCE NMN JR.</FP>
                <FP SOURCE="FP-1">GUERTIN, STEPHEN D.</FP>
                <FP SOURCE="FP-1">HAINES, DAVID ELSWORTH</FP>
                <FP SOURCE="FP-1">HAMLEY, JEFFREY L.</FP>
                <FP SOURCE="FP-1">HANNA, JEANETTE D.</FP>
                <FP SOURCE="FP-1">HARRIS, SARAH E</FP>
                <FP SOURCE="FP-1">HART, PAULA L.</FP>
                <FP SOURCE="FP-1">HARTLEY, DEBORAH J.</FP>
                <FP SOURCE="FP-1">HASKETT, GEOFFREY L.</FP>
                <FP SOURCE="FP-1">HAUGRUD, KEVIN JACK</FP>
                <FP SOURCE="FP-1">HAWBECKER, KAREN S.</FP>
                <FP SOURCE="FP-1">HERBST, LARS T.</FP>
                <FP SOURCE="FP-1">HILDEBRANDT, BETSY J.</FP>
                <FP SOURCE="FP-1">HOSKINS, DAVID WILLIAM</FP>
                <FP SOURCE="FP-1">HUMBERT, HARRY L</FP>
                <FP SOURCE="FP-1">IMPSON, ROBERT K.</FP>
                <FP SOURCE="FP-1">ISEMAN, THOMAS M</FP>
                <FP SOURCE="FP-1">IUDICELLO, FAY S.</FP>
                <FP SOURCE="FP-1">JAMES, JAMES D. JR.</FP>
                <FP SOURCE="FP-1">JOHNSTON, MICHAEL J.</FP>
                <FP SOURCE="FP-1">JUEN, JESSE J.</FP>
                <FP SOURCE="FP-1">KEABLE, EDWARD T.</FP>
                <FP SOURCE="FP-1">KELLY, FRANCIS P.</FP>
                <FP SOURCE="FP-1">KELLY, KATHERINE P</FP>
                <FP SOURCE="FP-1">KENDALL, JAMES J. JR.</FP>
                <FP SOURCE="FP-1">KENNA, JAMES G</FP>
                <FP SOURCE="FP-1">KIMBALL, SUZETTE M.</FP>
                <FP SOURCE="FP-1">KINSINGER, ANNE E.</FP>
                <FP SOURCE="FP-1">KLEIN, ELIZABETH A.</FP>
                <FP SOURCE="FP-1">KNOX, VICTOR W.</FP>
                <FP SOURCE="FP-1">KURTH, JAMES W.</FP>
                <FP SOURCE="FP-1">LAIRD, JOSHUA RADBILL</FP>
                <FP SOURCE="FP-1">LANCE, LINDA L</FP>
                <FP SOURCE="FP-1">LAPOINTE, TIMOTHY L.</FP>
                <FP SOURCE="FP-1">LAROCHE, DARRELL WILLIAM</FP>
                <FP SOURCE="FP-1">LAURO, SALVATORE R.</FP>
                <FP SOURCE="FP-1">LEE, LORRI J</FP>
                <FP SOURCE="FP-1">LEHNERTZ, CHRISTINE S.</FP>
                <FP SOURCE="FP-1">LOFTIN, MELINDA J.</FP>
                <FP SOURCE="FP-1">LOHOEFENER, RENNE R.</FP>
                <FP SOURCE="FP-1">LOPEZ, ESTEVAN R</FP>
                <FP SOURCE="FP-1">LORDS, DOUGLAS A.</FP>
                <FP SOURCE="FP-1">LOUDERMILK, WELDON B.</FP>
                <FP SOURCE="FP-1">LUEBKE, THOMAS A</FP>
                <FP SOURCE="FP-1">LUEDERS, AMY L.</FP>
                <FP SOURCE="FP-1">LYONS, JAMES R</FP>
                <FP SOURCE="FP-1">MABRY, SCOTT L.</FP>
                <FP SOURCE="FP-1">MASICA, SUE E.</FP>
                <FP SOURCE="FP-1">MCCAFFERY, JAMES G.</FP>
                <FP SOURCE="FP-1">MCDOWALL, LENA E</FP>
                <FP SOURCE="FP-1">MCKEOWN, MATTHEW J.</FP>
                <FP SOURCE="FP-1">MEHLHOFF, JOHN J.</FP>
                <FP SOURCE="FP-1">MELIUS, THOMAS O</FP>
                <FP SOURCE="FP-1">MENTORE-SMITH, HOPE Y.</FP>
                <FP SOURCE="FP-1">MILAKOFSKY, BENJAMIN E</FP>
                <FP SOURCE="FP-1">MONACO, JENNIFER ROMERO</FP>
                <FP SOURCE="FP-1">MORRIS, DOUGLAS W.</FP>
                <FP SOURCE="FP-1">MOSS, ADRIANNE L.</FP>
                <FP SOURCE="FP-1">MULHERN, THOMAS A.</FP>
                <FP SOURCE="FP-1">MULLER, BRUCE C JR</FP>
                <FP SOURCE="FP-1">MURILLO, DAVID G.</FP>
                <FP SOURCE="FP-1">MURPHY, TIMOTHY M.</FP>
                <FP SOURCE="FP-1">MUSSENDEN, PAUL A.</FP>
                <FP SOURCE="FP-1">NEDD, MICHAEL D.</FP>
                <FP SOURCE="FP-1">NEIMEYER, SARAH C</FP>
                <FP SOURCE="FP-1">
                    NEUBACHER, DONALD L.
                    <PRTPAGE P="72200"/>
                </FP>
                <FP SOURCE="FP-1">O'DELL, MARGARET G.</FP>
                <FP SOURCE="FP-1">ONEILL, KEITH JAMES</FP>
                <FP SOURCE="FP-1">ORR, L. RENEE</FP>
                <FP SOURCE="FP-1">ORTIZ, HANKIE P.</FP>
                <FP SOURCE="FP-1">OWENS, GLENDA HUDSON</FP>
                <FP SOURCE="FP-1">PALMA, JUAN M</FP>
                <FP SOURCE="FP-1">PAYNE, GRAYFORD F.</FP>
                <FP SOURCE="FP-1">PEREZ, JEROME E</FP>
                <FP SOURCE="FP-1">PETERSON, PENNY LYNN</FP>
                <FP SOURCE="FP-1">PIMLEY, LOWELL D.</FP>
                <FP SOURCE="FP-1">PINTO, SHARON ANN</FP>
                <FP SOURCE="FP-1">PLETCHER, MARY F.</FP>
                <FP SOURCE="FP-1">PRINCE, VENUS MCGHEE</FP>
                <FP SOURCE="FP-1">PULA, NIKOLAO IULI</FP>
                <FP SOURCE="FP-1">QUINLAN, MARTIN J.</FP>
                <FP SOURCE="FP-1">QUINT, ROBERT J</FP>
                <FP SOURCE="FP-1">RAUCH, PAUL A.</FP>
                <FP SOURCE="FP-1">REYNOLDS, MICHAEL T.</FP>
                <FP SOURCE="FP-1">REYNOLDS, THOMAS G.</FP>
                <FP SOURCE="FP-1">RIDEOUT, STERLING J. JR</FP>
                <FP SOURCE="FP-1">ROBERSON, EDWIN L</FP>
                <FP SOURCE="FP-1">ROBERTS, LAWRENCE SCOTT</FP>
                <FP SOURCE="FP-1">RODI, JOHN L.</FP>
                <FP SOURCE="FP-1">ROESSEL, CHARLES M.</FP>
                <FP SOURCE="FP-1">ROSEN, DIANE K.</FP>
                <FP SOURCE="FP-1">ROSS, JOHN W</FP>
                <FP SOURCE="FP-1">ROTH, BARRY N.</FP>
                <FP SOURCE="FP-1">ROUNTREE, CARL D.</FP>
                <FP SOURCE="FP-1">RUGEN, CATHERINE E.</FP>
                <FP SOURCE="FP-1">RUHS, JOHN F</FP>
                <FP SOURCE="FP-1">RUSS, DAVID P.</FP>
                <FP SOURCE="FP-1">RYAN, MICHAEL J.</FP>
                <FP SOURCE="FP-1">SALERNO, BRIAN M</FP>
                <FP SOURCE="FP-1">SALOTTI, CHRISTOPHER P.</FP>
                <FP SOURCE="FP-1">SARRI, KRISTEN JOAN</FP>
                <FP SOURCE="FP-1">SCHNEIDER, MARGARET N.</FP>
                <FP SOURCE="FP-1">SCHOCK, JAMES H.</FP>
                <FP SOURCE="FP-1">SHEEHAN, DENISE E.</FP>
                <FP SOURCE="FP-1">SHOLLY, CAMERON H</FP>
                <FP SOURCE="FP-1">SHOPE, THOMAS D.</FP>
                <FP SOURCE="FP-1">SIMMONS, SHAYLA F.</FP>
                <FP SOURCE="FP-1">SIMPSON, DONALD A</FP>
                <FP SOURCE="FP-1">SINGER, MICHELE F.</FP>
                <FP SOURCE="FP-1">SLACK, JAMES J.</FP>
                <FP SOURCE="FP-1">SMILEY, KARLA J.</FP>
                <FP SOURCE="FP-1">SMITH, MICHAEL R.</FP>
                <FP SOURCE="FP-1">SOGGE, MARK K.</FP>
                <FP SOURCE="FP-1">SONDERMAN, DEBRA E.</FP>
                <FP SOURCE="FP-1">SOUZA, PAUL</FP>
                <FP SOURCE="FP-1">SPEAKS, STANLEY M.</FP>
                <FP SOURCE="FP-1">STEVENS, BARTHOLOMEW S.</FP>
                <FP SOURCE="FP-1">STEWARD, JAMES D.</FP>
                <FP SOURCE="FP-1">SUAZO, RAYMOND</FP>
                <FP SOURCE="FP-1">TABER, TERESA RENEE</FP>
                <FP SOURCE="FP-1">TAYLOR, WILLIE R.</FP>
                <FP SOURCE="FP-1">TEITZ, ALEXANDRA ELIZABET</FP>
                <FP SOURCE="FP-1">THOMPSON, THOMAS D</FP>
                <FP SOURCE="FP-1">THORNHILL, ALAN D.</FP>
                <FP SOURCE="FP-1">THORSEN, KIMBERLEY A.</FP>
                <FP SOURCE="FP-1">THORSON, ROBYN</FP>
                <FP SOURCE="FP-1">TOOTHMAN, STEPHANIE S.</FP>
                <FP SOURCE="FP-1">TSCHUDY, DEBORAH GIBBS</FP>
                <FP SOURCE="FP-1">TUGGLE, BENJAMIN N.</FP>
                <FP SOURCE="FP-1">UBERUAGA, DAVID V.</FP>
                <FP SOURCE="FP-1">VELA, RAYMOND DAVID</FP>
                <FP SOURCE="FP-1">VELASCO, JANINE M.</FP>
                <FP SOURCE="FP-1">VOGEL, ROBERT A.</FP>
                <FP SOURCE="FP-1">WAINMAN, BARBARA W.</FP>
                <FP SOURCE="FP-1">WALKER, WILLIAM T.</FP>
                <FP SOURCE="FP-1">WALSH, NOREEN E.</FP>
                <FP SOURCE="FP-1">WARD, JOSEPH M JR</FP>
                <FP SOURCE="FP-1">WASHBURN, ELIZABETH R</FP>
                <FP SOURCE="FP-1">WASHBURN, JULIA L.</FP>
                <FP SOURCE="FP-1">WAYSON, THOMAS C.</FP>
                <FP SOURCE="FP-1">WEAVER, JESS D.</FP>
                <FP SOURCE="FP-1">WEBER, WENDI</FP>
                <FP SOURCE="FP-1">WELCH, RUTH L.</FP>
                <FP SOURCE="FP-1">WENK, DANIEL N.</FP>
                <FP SOURCE="FP-1">WERKHEISER, WILLIAM H.</FP>
                <FP SOURCE="FP-1">WHITE, JOHN ETHAN</FP>
                <FP SOURCE="FP-1">WHITTINGTON, SAMUEL Q.</FP>
                <FP SOURCE="FP-1">WILLIAMS, LC</FP>
                <FP SOURCE="FP-1">WILLIAMS, MARGARET C.</FP>
                <FP SOURCE="FP-1">WOLF, ROBERT W</FP>
                <FP SOURCE="FP-1">WOODY, WILLIAM C.</FP>
                <FP SOURCE="FP-1">WORONKA, THEODORE</FP>
                <FP SOURCE="FP-1">YU, DONALD YOON</FP>
                <SIG>
                    <NAME>Thomas Mulhern,</NAME>
                    <TITLE>Director, Office of Human Resources.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28568 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4334-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                <DEPDOC>[DR.5B711.IA000815]</DEPDOC>
                <SUBJECT>Indian Gaming</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Tribal-State Class III Gaming Compact taking effect.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice publishes the Class III Amended and Restated Tribal-State Compact between the Viejas Band of Kumeyaay Indians 
                        <SU>1</SU>
                        <FTREF/>
                         and the State of California taking effect.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The Tribe is identified as the Viejas (Baron Long) Group of Capitan Grande Band of Mission Indians of the Viejas Reservation in the Department's List of Indian Entities Recognized and Eligible to Receive Services from the United States Bureau of Indian Affairs, 79 FR 4748, 4749 (January 29, 2014).
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective December 5, 2014.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Paula L. Hart, Director, Office of Indian Gaming, Office of the Deputy Assistant Secretary—Policy and Economic Development, Washington, DC 20240, (202) 219-4066.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under section 11 of the Indian Gaming Regulatory Act (IGRA), Public Law 100-497, 25 U.S.C. 2701 
                    <E T="03">et seq.,</E>
                     the Secretary of the Interior shall publish in the 
                    <E T="04">Federal Register</E>
                     notice of approved Tribal-State compacts for the purpose of engaging in Class III gaming activities on Indian lands. The Amended and Restated Tribal-State Compact (Compact) between the State of California (State) and the Viejas Band of Kumeyaay Indians (Tribe) modifies the revenue sharing requirements. The expiration date of the Compact was not extended and remains December 31, 2030. The Secretary took no action on the Compact within 45 days of its submission by the Tribe and the State. Therefore, the compact is considered to have been approved, but only to the extent that the Compact is consistent with IGRA. 
                    <E T="03">See</E>
                     25 U.S.C. 2710(d)(8)(C).
                </P>
                <SIG>
                    <DATED> Dated: December 1, 2014.</DATED>
                    <NAME>Kevin K. Washburn,</NAME>
                    <TITLE>Assistant Secretary—Indian Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28600 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-4N-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NRNHL-17160; PPWOCRADI0, PCU00RP14.R50000]</DEPDOC>
                <SUBJECT>National Register of Historic Places; Notification of Pending Nominations and Related Actions</SUBJECT>
                <P>Nominations for the following properties being considered for listing or related actions in the National Register were received by the National Park Service before November 7, 2014. Pursuant to section 60.13 of 36 CFR part 60, written comments are being accepted concerning the significance of the nominated properties under the National Register criteria for evaluation. Comments may be forwarded by United States Postal Service, to the National Register of Historic Places, National Park Service, 1849 C St. NW., MS 2280, Washington, DC 20240; by all other carriers, National Register of Historic Places, National Park Service, 1201 Eye St. NW., 8th floor, Washington, DC 20005; or by fax, 202-371-6447. Written or faxed comments should be submitted by December 22, 2014. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
                <SIG>
                    <PRTPAGE P="72201"/>
                    <DATED>Dated: November 17, 2014.</DATED>
                    <NAME>J. Paul Loether,</NAME>
                    <TITLE>Chief, National Register of Historic Places/National Historic Landmarks Program.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">ILLINOIS</HD>
                    <HD SOURCE="HD1">Cook County</HD>
                    <FP SOURCE="FP-1">Polish National Alliance Headquarters, (Ethnic (European) Historic Settlement in the city of Chicago 1860-1930 MPS), 1514-1520 W. Division St., Chicago, 14001063</FP>
                    <FP SOURCE="FP-1">Robertson, John, Jr., House, 145 W. Main St., Barrington, 14001064</FP>
                    <FP SOURCE="FP-1">Strauss, Jesse L., Estate, 110 Maple Hill Rd., Glencoe, 14001065</FP>
                    <HD SOURCE="HD1">Du Page County</HD>
                    <FP SOURCE="FP-1">Coffeen, William and Helen, House, 306 S. Garfield, Hinsdale, 14001066</FP>
                    <HD SOURCE="HD1">Kane County</HD>
                    <FP SOURCE="FP-1">Elgin Downtown Commercial District, Roughly bound by Division, Villa Center, Fulton &amp; Grove, Elgin, 14001067</FP>
                    <HD SOURCE="HD1">Whiteside County</HD>
                    <FP SOURCE="FP-1">Martin House, 707 10th Ave., Fulton, 14001068</FP>
                    <HD SOURCE="HD1">IOWA</HD>
                    <HD SOURCE="HD1">Lee County</HD>
                    <FP SOURCE="FP-1">Park-to-Park Residential Historic District, 400-1100 blks. of Ave. F &amp; 400-1100 blks. of Ave. E, Fort Madison, 14001069</FP>
                    <HD SOURCE="HD1">MARYLAND</HD>
                    <HD SOURCE="HD1">Baltimore Independent city</HD>
                    <FP SOURCE="FP-1">Brewers Hill Historic District, Roughly bounded by Eastern Ave., S. Conkling, S. Haven &amp; Dillon Sts., Baltimore, 14001070</FP>
                    <HD SOURCE="HD1">MISSOURI</HD>
                    <HD SOURCE="HD1">St. Louis Independent city</HD>
                    <FP SOURCE="FP-1">General Electric Supply Corporation Building, 2653 Locust St., St. Louis (Independent City), 14001071</FP>
                    <HD SOURCE="HD1">NEW YORK</HD>
                    <HD SOURCE="HD1">Rensselaer County</HD>
                    <FP SOURCE="FP-1">Marsh-Link-Pollock Farm, 66 White Church Ln., Brunswick, 14001072</FP>
                    <HD SOURCE="HD1">OHIO</HD>
                    <HD SOURCE="HD1">Cuyahoga County</HD>
                    <FP SOURCE="FP-1">Hubbard Cooke Block, 2206-2220 Superior Viaduct, Cleveland, 14001073</FP>
                    <FP SOURCE="FP-1">Liquid Carbonic Corporation Dry Ice Plant, 1318 W. 58th St., Cleveland, 14001074</FP>
                    <HD SOURCE="HD1">Hamilton County</HD>
                    <FP SOURCE="FP-1">St. Aloysius-on-the-Ohio, 134 Whipple &amp; 6207, 6214 &amp; 6218 Portage Sts., 6206 Gracely Dr., Cincinnati, 14001075</FP>
                    <HD SOURCE="HD1">OREGON</HD>
                    <HD SOURCE="HD1">Multnomah County</HD>
                    <FP SOURCE="FP-1">Rutherford House, 833 NE. Shaver St., Portland, 14001076</FP>
                    <HD SOURCE="HD1">RHODE ISLAND</HD>
                    <HD SOURCE="HD1">Kent County</HD>
                    <FP SOURCE="FP-1">Cedar Hill, 4157 Post Rd., Warwick, 14001077</FP>
                    <HD SOURCE="HD1">Providence County</HD>
                    <FP SOURCE="FP-1">Edgewood Historic District—Taft Estate Plat (Boundary Increase), (Edgewood Neighborhood, Cranston, R.I. MPS), E. side of Narragansett Blvd. between Windsor Rd. &amp; Ocean Ave., Cranston, 14001078</FP>
                    <HD SOURCE="HD1">VIRGINIA</HD>
                    <HD SOURCE="HD1">Fairfax County</HD>
                    <FP SOURCE="FP-1">Great Falls Park Historic District, Bounded by Potomac R., Georgetown Pike &amp; River Bend Rd., Great Falls, 14001079</FP>
                    <HD SOURCE="HD1">WYOMING</HD>
                    <HD SOURCE="HD1">Converse County</HD>
                    <FP SOURCE="FP-1">Dorr Ranch, Approx. 5 mi. NE. of Woody Creek &amp; Steinle Rds., Bill, 14001080</FP>
                    <P>A request for removal has been received for the following resources:</P>
                    <HD SOURCE="HD1">IOWA</HD>
                    <HD SOURCE="HD1">Boone County</HD>
                    <FP SOURCE="FP-1">Boone Bridge, Old US 30 over Des Moines R., Boone, 98000761</FP>
                    <HD SOURCE="HD1">Pottawattamie County</HD>
                    <FP SOURCE="FP-1">Hancock Savings Bank, 311 Main St., Hancock, 83000401</FP>
                    <HD SOURCE="HD1">Scott County</HD>
                    <FP SOURCE="FP-1">Cook, Clarissa C., Library—Blue Ribbon News Building, 528 Brady St., Davenport, 83002415</FP>
                    <FP SOURCE="FP-1">Lend-A-Hand Club, 105 S. Main St., Davenport, 84001459</FP>
                    <FP SOURCE="FP-1">Petersen's, J. H. C., Sons Wholesale Building, 122-124 W. River Dr., Davenport, 83002484</FP>
                    <FP SOURCE="FP-1">Riepe Drug Store—G. Ott Block, 403 W. 2nd St., Davenport, 83002493</FP>
                    <FP SOURCE="FP-1">Schauder Hotel, 126 W. River Dr., Davenport, 83002495</FP>
                    <FP SOURCE="FP-1">Schick's Express and Transfer Co., 118-120 W. River Dr., Davenport, 83002497</FP>
                    <FP SOURCE="FP-1">Young, Col. Joseph, Block, 502 Brady St., Davenport, 83002526</FP>
                    <HD SOURCE="HD1">Washington County</HD>
                    <FP SOURCE="FP-1">Johnson, Thomas, Polygonal Barn, (Iowa Round Barns: The Sixty Year Experiment TR), Off IA 114, Wellman, 86001451</FP>
                    <HD SOURCE="HD1">Winneshiek County</HD>
                    <FP SOURCE="FP-1">Big Stone Mills, 113 N. Main St., Spillville, 09000516 </FP>
                </EXTRACT>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28537 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-51-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Reclamation</SUBAGY>
                <DEPDOC>[RR02331000, 14XR0680A4, RX.00224994.2000000]</DEPDOC>
                <SUBJECT>Notice of Proposed New Fee Site, Stony Gorge Reservoir, Elk Creek, California; Federal Lands Recreation Enhancement Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Reclamation, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Reclamation is proposing to charge and retain fees for overnight camping at Stony Gorge Reservoir. Special Recreation Event authorization fees are also proposed to be retained under this authority.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments on the new fee site on or before June 3, 2015. New fees are scheduled to begin on this date. Public meeting dates and locations will be announced locally.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send written comments on the proposed new fee site to Brian Person, Area Manager, Northern California Area Office, Bureau of Reclamation, 16349 Shasta Dam Boulevard, Shasta Lake, California 96019.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Richard Robertson, Chief, Water and Lands Division, P.O. Box 988, Willows, California 95988-0988; or call 530-934-1383. Information about proposed fee changes can also be found on the Bureau of Reclamation, Northern California Area Office Web site: 
                        <E T="03">http://www.usbr.gov/mp/ncao.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The proposed fee for overnight camping will be $15 per site per night for all non-group site camping. Group site overnight fees will be $75. Interagency Senior Passes will be accepted for individual overnight camping. An analysis of the nearby Federal and state recreation offerings with similar amenities shows that the proposed fees are reasonable and typical of similar sites in the area. Funds from fees will be used for the continued operation, maintenance, and improvements of the reservoir area recreation amenities and related programs.</P>
                <P>
                    The Federal Lands Recreation Enhancement Act (Title VII, Pub. L. 108-447) directed the Secretary of the Interior to publish a 6-month advance notice in the 
                    <E T="04">Federal Register</E>
                     whenever new recreation fee areas are established. Once public involvement is complete, these new fees will be reviewed by the Bureau of Reclamation Mid-Pacific Regional Director prior to a final decision and implementation. People wanting to reserve these recreation sites would need to do so through the National Recreation Reservation Service at 
                    <E T="03">www.recreation.gov,</E>
                     or by calling 1-877-444-6777 when it becomes available.
                </P>
                <HD SOURCE="HD1">Public Disclosure</HD>
                <P>
                    Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may 
                    <PRTPAGE P="72202"/>
                    be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME> Brian Person, </NAME>
                    <TITLE>Area Manager, Northern California Area Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28569 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4332-90-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 731-TA-1020 (Second Review)]</DEPDOC>
                <SUBJECT>Barium Carbonate From China; Revised Schedule for the Subject Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective December 2, 2014.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Keysha Martinez (202-205-2136) or Douglas Corkran (202-205-3057), Office of Investigations, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436. Hearing-impaired persons can obtain information on this matter by contacting the Commission's TDD terminal on 202-205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at 202-205-2000. General information concerning the Commission may also be obtained by accessing its internet server (
                        <E T="03">http://www.usitc.gov</E>
                        ). The public record for this review may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">http://edis.usitc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">Background.</E>
                    —On July 24, 2014, the Commission established a schedule for the conduct of this review (79 FR 44864, August 1, 2014). Subsequently, counsel for the domestic interested party filed a request to appear at the hearing and for consideration of cancellation of the hearing. Counsel indicated a willingness to submit written testimony and responses to any Commission questions in lieu of an actual hearing. No other party filed a timely request to appear at the hearing. Consequently, the public hearing in connection with this review, scheduled to begin at 9:30 a.m. on December 3, 2014, at the U.S. International Trade Commission Building, is cancelled. Parties to this review should respond to any written questions posed by the Commission in their posthearing briefs, which are due to be filed on December 12, 2014.
                </P>
                <P>For further information concerning this review see the Commission's notice cited above and the Commission's Rules of Practice and Procedure, part 201, subparts A through E (19 CFR part 201), and part 207, subparts A and C (19 CFR part 207).</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>This review is being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to section 207.62 of the Commission's rules.</P>
                </AUTH>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: December 2, 2014.</DATED>
                    <NAME>Lisa R. Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28574 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation Nos. 701-TA-524-525 and 731-TA-1260-1261 (Preliminary)]</DEPDOC>
                <SUBJECT>Certain Welded Line Pipe From Korea and Turkey</SUBJECT>
                <HD SOURCE="HD1">Determinations</HD>
                <P>
                    On the basis of the record 
                    <SU>1</SU>
                    <FTREF/>
                     developed in the subject investigations, the United States International Trade Commission (“Commission”) determines, pursuant to sections 703(a) and 733(a) of the Tariff Act of 1930 (19 U.S.C. 1671b(a) and 1673b(a)) (“the Act”), that there is a reasonable indication that an industry in the United States is materially injured by reason of imports from Korea and Turkey of certain welded line pipe, provided for in subheadings 7305.11, 7305.12, 7305.19, and 7306.19 of the Harmonized Tariff Schedule of the United States, that are alleged to be sold in the United States at less than fair value (“LTFV”), and that are allegedly subsidized by the governments of Korea and Turkey.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The record is defined in sec. 207.2(f) of the Commission's Rules of Practice and Procedure (19 CFR 207.2(f)).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Commencement of Final Phase Investigations</HD>
                <P>
                    Pursuant to section 207.18 of the Commission's rules, the Commission also gives notice of the commencement of the final phase of its investigations. The Commission will issue a final phase notice of scheduling, which will be published in the 
                    <E T="04">Federal Register</E>
                     as provided in section 207.21 of the Commission's rules, upon notice from the Department of Commerce (“Commerce”) of affirmative preliminary determinations in the investigations under sections 703(b) or 733(b) of the Act, or, if the preliminary determinations are negative, upon notice of affirmative final determinations in those investigations under sections 705(a) or 735(a) of the Act. Parties that filed entries of appearance in the preliminary phase of the investigations need not enter a separate appearance for the final phase of the investigations. Industrial users, and, if the merchandise under investigation is sold at the retail level, representative consumer organizations have the right to appear as parties in Commission antidumping and countervailing duty investigations. The Secretary will prepare a public service list containing the names and addresses of all persons, or their representatives, who are parties to the investigations.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>On October 16, 2014, a petition was filed with the Commission and Commerce by American Cast Iron Pipe Company, Birmingham, Alabama; Energex, a division of JMC Steel Group, Chicago, Illinois; Maverick Tube Corporation, Houston, Texas; Northwest Pipe Company, Vancouver, Washington; Stupp Corporation, Baton Rouge, Louisiana; Tex-Tube Company, Houston, Texas; TMK IPSCO, Houston, Texas; and Welspun Tubular LLC USA, Little Rock, Arkansas, alleging that an industry in the United States is materially injured or threatened with material injury by reason of subsidized imports of certain welded line pipe from Korea and Turkey and LTFV imports of certain welded line pipe from Korea and Turkey. Accordingly, effective October 16, 2014, the Commission instituted countervailing duty investigation Nos. 701-TA-524-525 and antidumping duty investigation Nos. 731-TA-1260-1261 (Preliminary).</P>
                <P>
                    Notice of the institution of the Commission's investigations and of a public conference to be held in connection therewith was given by posting copies of the notice in the Office of the Secretary, U.S. International Trade Commission, Washington, DC, and by publishing the notice in the 
                    <E T="04">Federal Register</E>
                     of October 23, 2013 (79 FR 63438). The conference was held in Washington, DC, on November 6, 2014, and all persons who requested the opportunity were permitted to appear in person or by counsel.
                </P>
                <P>
                    The Commission transmitted its determinations in these investigations to the Secretary of Commerce on December 1, 2014. The views of the Commission 
                    <PRTPAGE P="72203"/>
                    are contained in USITC Publication 4505 (December 2014), entitled 
                    <E T="03">Certain Welded Line Pipe from Korea and Turkey: Investigation Nos. 701-524-525 and 731-1260-1261 (Preliminary).</E>
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: December 1, 2014.</DATED>
                    <NAME>Lisa R. Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28533 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>United States v. Nexstar Broadcasting Group, Inc., Mission Broadcasting, Inc., Communications Corporation of America and Silver Point Capital Fund, L.P.; Proposed Final Judgment and Competitive Impact Statement</SUBJECT>
                <P>
                    Notice is hereby given pursuant to the Antitrust Procedures and Penalties Act, 15 U.S.C. 16(b)-(h), that a proposed Final Judgment, Hold Separate Stipulation and Order, and Competitive Impact Statement have been filed with the United States District Court for the District of Columbia in 
                    <E T="03">United States of America</E>
                     v. 
                    <E T="03">Nexstar Broadcasting Group, Inc., Mission Broadcasting, Inc., Communications Corporation of America and Silver Point Capital Fund, L.P.,</E>
                     Civil Action No. 1:14-cv-02007. On November 26, 2014, the United States filed a Complaint alleging that Nexstar's proposed acquisition of Communications Corporation of America (CCA), by the acquisition of control of WEVV-TV in Evansville, Indiana, would violate Section 7 of the Clayton Act, 15 U.S.C. 18. The proposed Final Judgment, filed the same time as the Complaint, requires Nexstar to divest WEVV-TV to Bayou City Broadcasting Evansville, Inc. or an alternative buyer approved by the United States.
                </P>
                <P>
                    Copies of the Complaint, proposed Final Judgment and Competitive Impact Statement are available for inspection at the Department of Justice, Antitrust Division, Antitrust Documents Group, 450 Fifth Street NW., Suite 1010, Washington, DC 20530 (telephone: 202-514-2481), on the Department of Justice's Web site at 
                    <E T="03">http://www.usdoj.gov/atr,</E>
                     and at the Office of the Clerk of the United States District Court for the District of Columbia. Copies of these materials may be obtained from the Antitrust Division upon request and payment of the copying fee set by Department of Justice regulations.
                </P>
                <P>
                    Public comment is invited within 60 days of the date of this notice. Such comments, including the name of the submitter, and responses thereto, will be posted on the Department of Justice, Antitrust Division's internet Web site, filed with the Court and, under certain circumstances, published in the 
                    <E T="04">Federal Register</E>
                    . Comments should be directed to Scott A. Scheele, Chief, Telecommunications &amp; Media Enforcement Section, Antitrust Division, Department of Justice, Washington, DC 20530 (telephone: 202-514-5621).
                </P>
                <SIG>
                    <NAME>Patricia A. Brink,</NAME>
                    <TITLE>Director of Civil Enforcement.</TITLE>
                </SIG>
                <HD SOURCE="HD1">IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">UNITED STATES OF AMERICA,</FP>
                    <FP SOURCE="FP-1">Department of Justice, Antitrust Division</FP>
                    <FP SOURCE="FP-1">450 5th Street N.W., Suite 7000</FP>
                    <FP SOURCE="FP-1">Washington, D.C. 20530</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Plaintiff,</E>
                    </FP>
                    <FP SOURCE="FP-1">v. </FP>
                    <FP SOURCE="FP-1">NEXSTAR BROADCASTING GROUP, INC., </FP>
                    <FP SOURCE="FP-1">545 E. John Carpenter Freeway, Suite 700 </FP>
                    <FP SOURCE="FP-1">Irving, Texas 75062</FP>
                    <FP SOURCE="FP-1">MISSION BROADCASTING, INC.,</FP>
                    <FP SOURCE="FP-1">30400 Detroit Road</FP>
                    <FP SOURCE="FP-1">Westlake, Ohio 44145</FP>
                    <FP SOURCE="FP-1">CORPORATION OF AMERICA,</FP>
                    <FP SOURCE="FP-1">700 Saint John Street</FP>
                    <FP SOURCE="FP-1">Suite 300</FP>
                    <FP SOURCE="FP-1">Lafayette, Louisiana 70501</FP>
                    <FP SOURCE="FP-1">and</FP>
                    <FP SOURCE="FP-1">SILVER POINT CAPITAL FUND, L.P., </FP>
                    <FP SOURCE="FP-1">2 Greenwich Plaza, 1st Floor</FP>
                    <FP SOURCE="FP-1">Greenwich, Connecticut 06830</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Defendants.</E>
                    </FP>
                    <FP SOURCE="FP-1">Case: 1:14-cv-02007</FP>
                </EXTRACT>
                <HD SOURCE="HD1">COMPLAINT</HD>
                <P>The United States of America, acting under the direction of the Attorney General of the United States, brings this civil action to enjoin the proposed acquisition of Communications Corporation of America (CCA), a wholly-owned subsidiary of Silver Point Capital Fund, L.P., by Nexstar Broadcasting, Inc. (Nexstar) and Mission Broadcasting, Inc. (Mission) (Nexstar and Mission are referred to collectively as the Buyers), and to obtain other equitable relief. The transaction would likely lessen competition substantially in the sale of broadcast television spot advertising in the Evansville, Indiana Designated Marketing Area (DMA) of the United States in violation of Section 7 of the Clayton Act, 15 U.S.C. 18. The United States alleges as follows:</P>
                <HD SOURCE="HD1">I. NATURE OF THE ACTION</HD>
                <P>1. Pursuant to a Stock Purchase Agreement dated April 24, 2013, Nexstar and Mission will acquire all of the issued and outstanding voting securities of CCA for $270 million. Both Nexstar and CCA own or operate many broadcast television stations in multiple television DMAs across the United States. Through various local services agreements, Nexstar sells the advertising for all of the television stations owned by Mission, which Nexstar effectively controls.</P>
                <P>2. In Evansville, Indiana, Nexstar owns and operates WEHT, an ABC broadcast network affiliate. As the owner-operator of that station, Nexstar sells WEHT's advertising. Pursuant to a local services agreement, Nexstar also sells the advertising of WTVW, a CW broadcast network affiliate in Evansville that is owned by Mission. Accordingly, WEHT and WTVW do not meaningfully compete with one another for advertisers.</P>
                <P>3. In Evansville, CCA owns and operates WEVV, a CBS broadcast network affiliate. WEVV also operates a digital subchannel on which it runs television programming affiliated with the FOX broadcast network. Although Nexstar and Mission intend to transfer CCA's WEVV license to a related third party, the third party is expected to have Nexstar sell its advertising pursuant to a local services or similar agreement. Nexstar would likely have effective control of this third party as it does of Mission.</P>
                <P>4. Currently, Nexstar (on behalf of WEHT and WTVW) and CCA (on behalf of WEVV) compete for the business of local and national advertisers that seek spot advertising on broadcast television stations in the Evansville, Indiana DMA. Advertisers benefit from this competition.</P>
                <P>5. If consummated, Nexstar's acquisition of control of CCA's advertising would result in Nexstar controlling the sale of advertising for three out of four major broadcast network affiliates (WEHT (ABC) and WEVV (CBS &amp; FOX)) and a fourth network affiliation (WTVW (CW)) in the Evansville, Indiana DMA. Nexstar's already high market share of spot advertising in the DMA would increase from approximately 42 to 60 percent.</P>
                <P>6. The transaction would eliminate head-to-head competition between Nexstar and CCA and all the benefits from this competition. Unless the transaction is blocked, it will lead to higher prices for broadcast television spot advertising in the Evansville, Indiana DMA in violation of Section 7 of the Clayton Act, 15 U.S.C. 18.</P>
                <HD SOURCE="HD1">II. JURISDICTION AND VENUE</HD>
                <P>7. The United States brings this action pursuant to Section 15 of the Clayton Act, as amended, 15 U.S.C. 25, to prevent and restrain Defendants from violating Section 7 of the Clayton Act, 15 U.S.C. 18.</P>
                <P>
                    8. Nexstar and CCA sell broadcast television spot advertising, a commercial activity that substantially 
                    <PRTPAGE P="72204"/>
                    affects, and is in the flow of, interstate commerce. The Court has subject-matter jurisdiction over this action pursuant to Section 15 of the Clayton Act, 15 U.S.C. 25, and 28 U.S.C. 1331, 1337(a), and 1345.
                </P>
                <P>9. Nexstar transacts business and is found in the District of Columbia. Defendants have consented to venue and personal jurisdiction in this District. Therefore, venue is proper in this District under Section 12 of the Clayton Act, 15 U.S.C. 22, and 28 U.S.C. 1391(c). Venue is also proper in the District of Columbia for defendant Nexstar under 28 U.S.C. 1391(d).</P>
                <HD SOURCE="HD1">III. THE DEFENDANTS</HD>
                <P>10. Nexstar, a Delaware corporation with headquarters in Irving, Texas, owns or operates 72 broadcast television stations located in 41 DMAs in 18 states. Nexstar reported revenues of $378 million for 2013.</P>
                <P>11. Mission, a Delaware corporation with headquarters in Westlake, Ohio, owns 17 broadcast television stations. Nexstar receives substantially all of Mission's available cash and is deemed to have a controlling interest in Mission under generally accepted accounting principles. Accordingly, Mission's economic incentives are aligned with Nexstar's.</P>
                <P>12. CCA, a Delaware corporation with headquarters in Lafayette, Louisiana, owns or operates 25 broadcast television stations in 10 DMAs throughout Louisiana, Texas, and Indiana. CCA reported revenues of $98.3 million for 2012.</P>
                <P>13. Silver Point Capital Fund, L.P., based in Greenwich, Connecticut, controls and is the ultimate parent entity of CCA.</P>
                <HD SOURCE="HD1">IV. TRADE AND COMMERCE</HD>
                <HD SOURCE="HD2">A. Broadcast Television Spot Advertising Is a Relevant Product Market</HD>
                <P>14. Broadcast television stations attract viewers through their programming, which is delivered for free over the air or retransmitted to viewers, mainly through wired cable or other terrestrial television systems and through satellite television systems. Broadcast television stations then sell advertising time to businesses that want to advertise their products to television viewers. Broadcast television “spot” advertising is sold directly by the station itself or through its national representative on a localized basis and is purchased by advertisers who want to target potential customers in specific geographic areas. Spot advertising differs from network and syndicated television advertising, which are sold by the major television networks and producers of syndicated programs on a nationwide basis and broadcast in every geographic area where the network or syndicated program is aired.</P>
                <P>15. Broadcast television spot advertising possesses a unique combination of attributes that sets it apart from advertising using other types of media. Television combines sight, sound, and motion, thereby creating a more memorable advertisement. Moreover, of all media, broadcast television spot advertising reaches the largest percentage of all potential customers in a particular target geographic market and is therefore especially effective in introducing, establishing, and maintaining the image of a product or service. For a significant number of advertisers, broadcast television spot advertising, because of its unique attributes, is an advertising medium for which there is no close substitute. Advertisers generally do not consider other media, such as radio, newspapers, or outdoor billboards, to be desirable substitutes for broadcast television advertising. None of these media can provide the important combination of sight, sound, and motion that makes television unique and impactful as a medium for advertising.</P>
                <P>
                    16. Like broadcast television, subscription television channels, such as those carried over cable or satellite television, combine elements of sight, sound, and motion, but they are not generally considered within the advertising industry as a desirable substitute for broadcast television spot advertising for two important reasons. First, satellite, cable, and other subscription content delivery systems do not generally have the “reach” of broadcast television. Typically in the United States, broadcast television can reach well over 90% of homes in a DMA, while cable television often reaches fewer homes. Second, because subscription services may offer more than 100 channels, they fragment the audience into small demographic segments. Because broadcast television programming typically has higher rating points than subscription television programming, broadcast television is generally viewed as providing a much easier and more efficient means for an advertiser to reach a high proportion of its target demographic. Generally in the industry, media buyers purchase time on subscription television channels not so much as a substitute for broadcast television, but rather to supplement a broadcast television message, to reach a narrow demographic (
                    <E T="03">e.g.,</E>
                     18-24 year olds) with greater frequency, or to target narrow geographic areas within a DMA.
                </P>
                <P>
                    17. Typically, advertisers do not consider internet-based media to be a substitute for broadcast television spot advertising. Although online video distributors (OVDs) such as Netflix and Hulu are important sources of video programming, as with cable television advertising, the local video advertising of OVDs lacks the reach of broadcast television spot advertising. And non-video internet advertising (
                    <E T="03">e.g.,</E>
                     Web site banner advertising) lacks the important combination of sight, sound, and motion that gives television its impact. Consequently, the typical local media advertiser purchases internet-based advertising primarily as a supplement to broadcast television spot advertising.
                </P>
                <P>18. Consequently, a small but significant increase in the price of broadcast television spot advertising is unlikely to cause a sufficient number of broadcast television spot advertising customers to switch enough of their advertising purchases to other media such that the price increase would be unprofitable.</P>
                <P>19. The sale of broadcast television spot advertising is a line of commerce under Section 7 of the Clayton Act and a relevant product market for purposes of analyzing the proposed transaction under Section 7 of the Clayton Act.</P>
                <HD SOURCE="HD2">B. The Evansville, Indiana DMA Is the Relevant Geographic Market</HD>
                <P>
                    20. A Designated Marketing Area or DMA is a geographic unit defined by A.C. Nielsen Company, a firm that surveys television viewers and furnishes broadcast television stations, advertisers, and advertising agencies in a particular area with data to aid in evaluating audience size and composition. The Evansville, Indiana DMA encompasses 21 counties in Indiana, Kentucky, and Illinois. Signals from broadcast television stations located in the Evansville, Indiana DMA reach viewers located throughout the DMA, but signals from broadcast television stations located outside the DMA reach few viewers within the DMA. DMAs are used to analyze revenues and shares of broadcast television stations in the 
                    <E T="03">Investing in Television BIA Market Report 2014</E>
                     (1st ed.), a standard industry reference.
                </P>
                <P>
                    21. Advertisers use broadcast television stations within the Evansville, Indiana DMA to reach the largest possible number of viewers within the entire DMA. Some of these advertisers are located in the Evansville, Indiana DMA and need to reach customers there; others are regional or national businesses that want to target 
                    <PRTPAGE P="72205"/>
                    consumers in the Evansville, Indiana DMA. Advertising on television stations outside the Evansville, Indiana DMA is not an alternative for these advertisers because such stations cannot be viewed by the vast majority of potential customers within the DMA. Thus, if there were a small but significant increase in broadcast television spot advertising prices within the Evansville, Indiana DMA, advertisers would not switch enough advertising purchases to television stations outside the Evansville, Indiana DMA to render the price increase unprofitable.
                </P>
                <P>22. The Evansville, Indiana DMA is a section of the country under Section 7 of the Clayton Act and a relevant geographic market for the sale of broadcast television spot advertising for the purposes of analyzing the proposed transaction under Section 7 of the Clayton Act.</P>
                <HD SOURCE="HD2">C. The Transaction Will Lead to Harm to Competition in the Evansville, Indiana DMA</HD>
                <P>23. Broadcast television stations compete for advertisers by offering programs that attract viewers to their stations. Broadcast television stations select programs that appeal to the greatest number of viewers and that differentiate their stations from other stations by appealing to specific demographic groups. Advertisers, in turn, are interested in using broadcast television spot advertising to reach a large audience, as well as to reach a high proportion of the type of viewers that are most likely to buy their products.</P>
                <P>24. By virtue of its ownership and operation of WEHT and the existing local services agreement with Mission to sell the advertising of WTVW, Nexstar currently controls the advertising of two broadcast television stations in the Evansville, Indiana DMA. Post-transaction, the market would effectively become a duopoly, with Nexstar controlling the advertising of three of the four major network affiliates (WEHT (ABC) and WEVV (CBS &amp; FOX)) and a fourth network affiliation (WTVW (CW)) in the Evansville, Indiana DMA. Nexstar's market share of broadcast television spot advertising revenue in the Evansville, Indiana DMA would increase from 42 to 60 percent. A single television station would control the vast majority of the remaining 40 percent.</P>
                <P>
                    25. Using the Herfindahl-Hirschman Index (HHI), a standard measure of market concentration (defined and explained in Appendix A), the proposed transaction would increase substantially the already high concentration in the Evansville, Indiana DMA broadcast television spot advertising market. The post-transaction HHI would be approximately 5100, representing an increase of about 1500 points. Under the 
                    <E T="03">Horizontal Merger Guidelines</E>
                     issued by the Department of Justice and Federal Trade Commission, mergers resulting in highly concentrated markets (with an HHI in excess of 2500) with an increase in the HHI of more than 200 points are presumed to be likely to enhance market power.
                </P>
                <P>26. In the Evansville, Indiana DMA, Nexstar and CCA compete head-to-head against each other in the sale of broadcast television spot advertising and are close substitutes for a significant number of advertisers. Advertisers benefit from this competition. The proposed transaction would end this competition and thereby adversely affect a substantial volume of interstate commerce.</P>
                <P>27. After the transaction, a significant number of Evansville, Indiana DMA advertisers would not be able to reach their desired audiences with equivalent efficacy unless they advertised on the television stations controlled by Nexstar. Advertisers would have available only one alternative broadcast channel. The transaction, therefore, will enable Nexstar unilaterally to raise prices. Given the structure of the Evansville, Indiana DMA, the economics of this industry suggest that the remaining major competitor will have substantial incentives to follow suit.</P>
                <HD SOURCE="HD2">D. Entry</HD>
                <P>28. De novo entry into the Evansville, Indiana DMA is unlikely as the Federal Communications Commission (FCC) regulates entry through the issuance of broadcast television spectrum licenses, which are difficult to obtain. Even if a new license became available, commercial success would come, at best, over a period of many years. Thus, entry into the Evansville, Indiana DMA broadcast television spot advertising market would not be timely, likely, or sufficient to deter post-merger anticompetitive effects.</P>
                <HD SOURCE="HD2">E. Absence of Efficiencies</HD>
                <P>29. Defendants cannot demonstrate cognizable, merger-specific efficiencies that are sufficient to reverse the anticompetitive effects of the proposed transaction.</P>
                <HD SOURCE="HD1">V. VIOLATION ALLEGED</HD>
                <P>30. The United States hereby repeats and realleges the allegations of paragraphs 1 through 29 as if fully set forth herein.</P>
                <P>31. The Buyers' proposed acquisition of CCA would likely lessen competition substantially in interstate trade and commerce in violation of Section 7 of the Clayton Act, 15 U.S.C. 18, and would likely have the following effects, among others:</P>
                <P>(a) Competition in the sale of broadcast television spot advertising in the Evansville, Indiana DMA would be lessened substantially;</P>
                <P>(b) Competition in the Evansville, Indiana DMA between Nexstar and CCA in the sale of broadcast television spot advertising would be eliminated; and</P>
                <P>(c) The prices for broadcast television spot advertising in the Evansville, Indiana DMA would likely increase.</P>
                <HD SOURCE="HD1">VI. REQUEST FOR RELIEF</HD>
                <P>32. The United States requests:</P>
                <P>(a) That the Court adjudge the proposed transaction to violate Section 7 of the Clayton Act, 15 U.S.C. 18;</P>
                <P>(b) That the Court permanently enjoin and restrain the Defendants from carrying out the proposed transaction or from entering into or carrying out any other agreement, understanding, or plan by which CCA would be acquired by, acquire, or merge with the Buyers;</P>
                <P>(c) That the Court award the United States the costs of this action; and</P>
                <P>(d) That the Court award such other relief to the United States as the Court may deem just and proper.</P>
                <P>Respectfully submitted,</P>
                <HD SOURCE="HD3">FOR PLAINTIFF UNITED STATES OF AMERICA:</HD>
                <EXTRACT>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>William J. Baer (D.C. Bar #324723)</FP>
                    <FP>
                        <E T="03">Assistant Attorney General</E>
                    </FP>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Leslie Overton (D.C. Bar #454493)</FP>
                    <FP>
                        <E T="03">Deputy Assistant Attorney General</E>
                    </FP>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Patricia A. Brink</FP>
                    <FP>
                        <E T="03">Director of Civil Enforcement</E>
                    </FP>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Scott A. Scheele (D.C. Bar #429061)</FP>
                    <FP>
                        <E T="03">Chief, Telecom &amp; Media Section</E>
                    </FP>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Lawrence M. Frankel (D.C. Bar #441532)</FP>
                    <FP>
                        <E T="03">Assistant Chief, Telecom &amp; Media Section</E>
                    </FP>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Matthew C. Hammond *</FP>
                    <FP>
                        <E T="03">Trial Attorney, Telecom &amp; Media Section.</E>
                    </FP>
                    <FP>
                        <E T="03">United States Department of Justice, Antitrust Division, 450 Fifth Street N.W., Suite 7000, Washington, D.C. 20530, Phone: 202-305-8541, Facsimile: 202-514-6381, Email: matthew.hammond@usdoj.gov.</E>
                    </FP>
                    <FP>
                        <E T="03">* Attorney of Record</E>
                    </FP>
                    <FP>Dated: November 26, 2014</FP>
                </EXTRACT>
                <APPENDIX>
                    <HD SOURCE="HED">APPENDIX A</HD>
                    <HD SOURCE="HD2">Herfindahl-Hirschman Index</HD>
                    <P>
                        The tern “HHI” means the Herfindahl-Hirschman Index, a commonly accepted 
                        <PRTPAGE P="72206"/>
                        measure of market concentration. The HHI is calculated by squaring the market share of each firm competing in the market and then summing the resulting numbers. For example, for a market consisting of four firms with shares of 30, 30, 20, and 20 percent, the HHI is 2,600 (30
                        <SU>2</SU>
                         + 30
                        <SU>2</SU>
                         + 20
                        <SU>2</SU>
                         + 20
                        <SU>2</SU>
                         = 2,600). The HHI takes into account the relative size distribution of the firms in a market. It approaches zero when a market is occupied by a large number of firms of relatively equal size and reaches its maximum of 10,000 points when a market is controlled by a single firm. The HHI increases both as the number of firms in the market decreases and as the disparity in size between those firms increases. Markets in which the HHI is between 1,500 and 2,500 points are considered to be moderately concentrated, and markets in which the HHI is in excess of 2,500 points are considered to be highly concentrated. 
                        <E T="03">See</E>
                         U.S. Department of Justice &amp; Federal Trade Commission, 
                        <E T="03">Horizontal Merger Guidelines</E>
                         § 5.3 (2010). Transactions that increase the HHI by more than 200 points in highly concentrated markets presumptively raise antitrust concerns under the 
                        <E T="03">Guidelines. See id.</E>
                    </P>
                    <HD SOURCE="HD1">IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA</HD>
                </APPENDIX>
                <EXTRACT>
                    <FP SOURCE="FP-1">UNITED STATES OF AMERICA,</FP>
                    <FP SOURCE="FP-1">Department of Justice, Antitrust Division</FP>
                    <FP SOURCE="FP-1">450 5th Street N.W., Suite 7000</FP>
                    <FP SOURCE="FP-1">Washington, D.C. 20530</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Plaintiff,</E>
                    </FP>
                    <FP SOURCE="FP-1">v.</FP>
                    <FP SOURCE="FP-1">NEXSTAR BROADCASTING GROUP, INC.,</FP>
                    <FP SOURCE="FP-1">545 E. John Carpenter Freeway, Suite 700</FP>
                    <FP SOURCE="FP-1">Irving, Texas 75062</FP>
                    <FP SOURCE="FP-1">MISSION BROADCASTING, INC.,</FP>
                    <FP SOURCE="FP-1">30400 Detroit Road</FP>
                    <FP SOURCE="FP-1">Westlake, Ohio 44145</FP>
                    <FP SOURCE="FP-1">COMMUNICATIONS CORPORATION OF AMERICA, </FP>
                    <FP SOURCE="FP-1">700 Saint John Street, Suite 300</FP>
                    <FP SOURCE="FP-1">Lafayette, Louisiana 70501</FP>
                    <FP SOURCE="FP-1">and</FP>
                    <FP SOURCE="FP-1">SILVER POINT CAPITAL FUND, L.P., </FP>
                    <FP SOURCE="FP-1">2 Greenwich Plaza, 1st Floor</FP>
                    <FP SOURCE="FP-1">Greenwich, Connecticut 06830</FP>
                    <FP SOURCE="FP-1">Defendants.</FP>
                    <FP SOURCE="FP-1">Case: 1:14-cv-02007</FP>
                    <HD SOURCE="HD1">COMPETITIVE IMPACT STATEMENT</HD>
                    <P>Plaintiff United States of America (United States), pursuant to Section 2(b) of the Antitrust Procedures and Penalties Act (APPA or the Tunney Act), 15 U.S.C. 16(b)-(h), files this Competitive Impact Statement relating to the proposed Final Judgment submitted for entry in this civil antitrust proceeding.</P>
                    <HD SOURCE="HD1">I. NATURE AND PURPOSE OF THE PROCEEDING</HD>
                    <P>Pursuant to a Stock Purchase Agreement dated April 24, 2013, Nexstar Broadcasting Group, Inc. (Nexstar) and Mission Broadcasting Inc. (Mission) will acquire all of the issued and outstanding voting securities of Communications Corporation of America (CCA) for $270 million. Both Nexstar and CCA own or operate many broadcast television stations in multiple television Designated Marketing Areas (DMAs) across the United States. Through various local services agreements, Nexstar sells the advertising for all of the television stations owned by Mission, which Nexstar effectively controls.</P>
                    <P>In Evansville, Indiana, Nexstar owns and operates WEHT, an ABC broadcast network affiliate. As the owner-operator of that station, Nexstar sells WEHT's advertising. Pursuant to a local services agreement, Nexstar also sells the advertising of WTVW, a CW broadcast network affiliate in Evansville that is owned by Mission. Accordingly, WEHT and WTVW do not meaningfully compete with one another for advertisers.</P>
                    <P>In Evansville, CCA owns and operates WEVV, a CBS broadcast network affiliate. WEVV also operates a digital subchannel on which it runs television programming affiliated with the FOX broadcast network. Although Nexstar and Mission intend to transfer CCA's WEVV license to a related third party, the third party is expected to have Nexstar sell its advertising pursuant to a local services or similar agreement. Nexstar would likely have effective control of this third party as it does of Mission.</P>
                    <P>Currently, Nexstar (on behalf of WEHT and WTVW) and CCA (on behalf of WEVV) compete for the business of local and national advertisers that seek spot advertising on broadcast television stations in the Evansville, Indiana DMA. Advertisers benefit from this competition. If consummated, Nexstar's acquisition of control of CCA's advertising would result in Nexstar controlling the sale of advertising for three out of four major broadcast network affiliates (WEHT (ABC) and WEVV (CBS &amp; FOX)) and a fourth network affiliation (WTVW (CW)) in the Evansville, Indiana DMA. Nexstar's already high market share of spot advertising in the DMA would increase from approximately 42 to 60 percent. Thus, the transaction would eliminate head-to-head competition between Nexstar and CCA and all the benefits from this competition, leading to higher prices for broadcast television spot advertising in the Evansville, Indiana DMA in violation of Section 7 of the Clayton Act, 15 U.S.C. 18.</P>
                    <P>The United States filed a civil antitrust Complaint on November 26, 2014, seeking to enjoin the proposed transaction. The Complaint alleges that the likely effect of this transaction would be to lessen competition substantially for broadcast television spot advertising in the Evansville, Indiana DMA in violation of Section 7 of the Clayton Act, 15 U.S.C. 18. This loss of competition likely would result in advertisers paying higher prices.</P>
                    <P>At the same time the Complaint was filed, the United States also filed a Hold Separate Stipulation and Order (Hold Separate Order) and proposed Final Judgment, which are designed to eliminate the anticompetitive effects of the transaction. Under the proposed Final Judgment, which is explained more fully below, Defendants are required to divest WEVV located in the Evansville, Indiana DMA. Under the terms of the Hold Separate Order, Defendants are required to take certain steps to ensure that WEVV is operated as a competitively independent, economically viable, and ongoing business concern, that will remain independent and uninfluenced by the consummation of the transaction, and that competition is maintained during the pendency of the ordered divestiture.</P>
                    <P>The United States and Defendants have stipulated that the proposed Final Judgment may be entered after compliance with the APPA. Entry of the proposed Final Judgment would terminate this action, except that the Court would retain jurisdiction to construe, modify, or enforce the provisions of the proposed Final Judgment and to punish violations thereof.</P>
                    <HD SOURCE="HD1">II. DESCRIPTION OF THE EVENTS GIVING RISE TO THE ALLEGED VIOLATION</HD>
                    <HD SOURCE="HD2">A. The Defendants and the Proposed Transaction</HD>
                    <P>Nexstar, a Delaware corporation with headquarters in Irving, Texas, owns or operates 72 broadcast television stations located in 41 DMAs in 18 states. Nexstar reported revenues of $378 million for 2013. Mission, a Delaware corporation with headquarters in Westlake, Ohio, owns 17 broadcast television stations. Nexstar receives substantially all of Mission's available cash and is deemed to have a controlling interest in Mission under generally accepted accounting principles. Accordingly, Mission's economic incentives are aligned with Nexstar's.</P>
                    <P>CCA, a Delaware corporation with headquarters in Lafayette, Louisiana, owns or operates 25 broadcast television stations in 10 DMAs throughout Louisiana, Texas, and Indiana. CCA reported revenues of $98.3 million for 2012. Silver Point Capital Fund, L.P., based in Greenwich, Connecticut, controls and is the ultimate parent entity of CCA.</P>
                    <P>The proposed transaction, as initially agreed to by Defendants, would lessen competition substantially in broadcast television spot advertising in the Evansville, Indiana DMA as a result of Nexstar's acquisition of CCA. This transaction is the subject of the Complaint and proposed Final Judgment filed by the United States on November 26, 2014.</P>
                    <HD SOURCE="HD2">B. Anticompetitive Consequences of the Proposed Transaction</HD>
                    <HD SOURCE="HD3">1. The Relevant Product Market</HD>
                    <P>The Complaint alleges that the sale of broadcast television spot advertising constitutes a relevant product market for analyzing this transaction under Section 7 of the Clayton Act. Broadcast television stations attract viewers through their programming, which is delivered for free over the air or retransmitted to viewers, mainly through wired cable or other terrestrial television systems and through satellite television systems. Broadcast television stations then sell advertising time to businesses that want to advertise their products to television viewers. Broadcast television “spot” advertising is sold directly by the station itself or through its national representative on a localized basis and is purchased by advertisers who want to target potential customers in specific geographic areas. Spot advertising differs from network and syndicated television advertising, which are sold by the major television networks and producers of syndicated programs on a nationwide basis and broadcast in every geographic area where the network or syndicated program is aired.</P>
                    <P>
                        Broadcast television spot advertising possesses a unique combination of attributes that sets it apart from advertising using other 
                        <PRTPAGE P="72207"/>
                        types of media. Television combines sight, sound, and motion, thereby creating a more memorable advertisement. Moreover, of all media, broadcast television spot advertising reaches the largest percentage of all potential customers in a particular target geographic market and is therefore especially effective in introducing, establishing, and maintaining the image of a product or service. For a significant number of advertisers, broadcast television spot advertising, because of its unique attributes, is an advertising medium for which there is no close substitute. Advertisers generally do not consider other media, such as radio, newspapers, or outdoor billboards, to be desirable substitutes for broadcast television advertising. None of these media can provide the important combination of sight, sound, and motion that makes television unique and impactful as a medium for advertising.
                    </P>
                    <P>
                        Like broadcast television, subscription television channels, such as those carried over cable or satellite television, combine elements of sight, sound, and motion, but they are not generally considered within the advertising industry as a desirable substitute for broadcast television spot advertising for two important reasons. First, satellite, cable, and other subscription content delivery systems do not generally have the “reach” of broadcast television. Typically in the United States, broadcast television can reach well over 90% of homes in a DMA, while cable television often reaches fewer homes. Second, because subscription services may offer more than 100 channels, they fragment the audience into small demographic segments. Because broadcast television programming typically has higher rating points than subscription television programming, broadcast television is generally viewed as providing a much easier and more efficient means for an advertiser to reach a high proportion of its target demographic. Generally in the industry, media buyers purchase time on subscription television channels not so much as a substitute for broadcast television, but rather to supplement a broadcast television message, to reach a narrow demographic (
                        <E T="03">e.g.,</E>
                         18-24 year olds) with greater frequency, or to target narrow geographic areas within a DMA.
                    </P>
                    <P>
                        Typically, advertisers do not consider internet-based media to be a substitute for broadcast television spot advertising. Although online video distributors (OVDs) such as Netflix and Hulu are important sources of video programming, as with cable television advertising, the local video advertising of OVDs lacks the reach of broadcast television spot advertising. And non-video internet advertising (
                        <E T="03">e.g.,</E>
                         Web site banner advertising) lacks the important combination of sight, sound, and motion that gives television its impact. Consequently, the typical local media advertiser purchases internet-based advertising primarily as a supplement to broadcast television spot advertising.
                    </P>
                    <P>Consequently, a small but significant price increase in broadcast television spot advertising is unlikely to cause enough advertising customers to switch advertising purchases to other media to make the price increase unprofitable.</P>
                    <HD SOURCE="HD3">2. The Relevant Geographic Market</HD>
                    <P>
                        The Complaint alleges that the Evansville, Indiana DMA constitutes a relevant geographic market for purposes of analyzing this acquisition under Section 7 of the Clayton Act. A Designated Marketing Area or DMA is a geographic unit defined by A.C. Nielsen Company, a firm that surveys television viewers and furnishes broadcast television stations, advertisers, and advertising agencies in a particular area with data to aid in evaluating audience size and composition. DMAs are used to analyze revenues and shares of broadcast television stations in the 
                        <E T="03">Investing in Television BIA Market Report 2014</E>
                         (1st ed.), a standard industry reference. The Evansville, Indiana DMA encompasses 21 counties in Indiana, Kentucky, and Illinois. Signals from broadcast television stations located in the Evansville, Indiana DMA reach viewers throughout the DMA, but signals from broadcast television stations located outside the DMA reach few viewers within the DMA.
                    </P>
                    <P>Advertisers can use television stations in the DMA to target the largest possible number of viewers within the DMA. Some of these advertisers are located in the Evansville, Indiana DMA and are trying to reach consumers that live in the DMA; others are regional or national businesses wanting to target consumers in the Evansville, Indiana DMA. Advertising on television stations outside each of the Evansville, Indiana DMA is not an alternative for either local, regional, or national advertisers, because signals from television stations outside of the DMA reach relatively few viewers within the DMA. Thus, advertising on those stations outside the Evansville, Indiana DMA does not reach a significant number of potential customers within the DMA.</P>
                    <P>Consequently, a small but significant increase in broadcast television spot advertising prices within the Evansville, Indiana DMA would not cause advertisers to switch enough advertising purchases to television stations outside the Evansville, Indiana DMA to render the price increase unprofitable.</P>
                    <HD SOURCE="HD3">3. Harm to Competition in the Evansville, Indiana DMA</HD>
                    <P>The Complaint alleges that the proposed acquisition would likely lessen competition substantially in interstate trade and commerce, in violation of Section 7 of the Clayton Act, 15 U.S.C. 18, and likely would have the following effects, among others:</P>
                    <P>(a) competition in the sale of broadcast television spot advertising in the Evansville, Indiana DMA would be lessened substantially;</P>
                    <P>(b) competition in the Evansville, Indiana DMA between Nexstar and CCA in the sale of broadcast television spot advertising would be eliminated; and</P>
                    <P>(c) the prices for broadcast television spot advertising on broadcast television stations in the Evansville, Indiana DMA likely would increase.</P>
                    <P>By virtue of its ownership and operation of WEHT and the existing local services agreement with Mission to sell the advertising of WTVW, Nexstar currently controls the advertising of two broadcast television stations in the Evansville, Indiana DMA. Post-transaction, the market would effectively become a duopoly, with Nexstar controlling the advertising of three of the four major network (WEHT (ABC) and WEVV (CBS &amp; FOX)) and a fourth network affiliation (WTVW (CW)) in the Evansville, Indiana DMA. Nexstar's market share of broadcast television spot advertising revenue in the DMA would increase from 42 to 60 percent. A single television station would control the vast majority of the remaining 40 percent.</P>
                    <P>
                        Using the Herfindahl-Hirschman Index (HHI), a standard measure of market concentration (defined and explained in Appendix A to the Complaint), the proposed transaction would increase substantially the already high concentration in the Evansville, Indiana DMA broadcast television spot advertising market. The post-transaction HHI would be approximately 5100, representing an increase of about 1500 points. Under the 
                        <E T="03">Horizontal Merger Guidelines</E>
                         issued by the Department of Justice and Federal Trade Commission, mergers resulting in highly concentrated markets (with an HHI in excess of 2500) with an increase in the HHI of more than 200 points are presumed to be likely to enhance market power.
                    </P>
                    <P>In the Evansville, Indiana DMA, Nexstar and CCA compete head-to-head against each other in the sale of broadcast television spot advertising. They are close substitutes for each other for a significant number of advertisers. Moreover, advertisers typically find it cost-effective to reach their target audience by buying time from multiple stations in a DMA. In negotiating rates with any one television station, advertisers benefit from competition between stations because they can put together an ad buy with the other stations in the DMA. The proposed transaction would end this type of competition between Nexstar and CCA and thereby adversely affect a substantial volume of interstate commerce. After the transaction, it is likely that a significant number of Evansville, Indiana DMA advertisers would not be able to reach their desired audiences with equivalent efficacy unless they advertised on the television stations controlled by Nexstar. By leaving advertisers with only one alternative broadcast channel, the transaction will enable Nexstar unilaterally to raise prices. Given the structure of the Evansville, Indiana DMA, the economics of this industry suggest that the remaining major competitor will have substantial incentives to follow suit.</P>
                    <HD SOURCE="HD3">4. Lack of Countervailing Factors</HD>
                    <P>
                        The Complaint alleges that entry in the Evansville, Indiana DMA's broadcast television spot advertising market would not be timely, likely, or sufficient to prevent any anticompetitive effects. New entry is unlikely since any new station would require a Federal Communications Commission (FCC) license, which is difficult to obtain. Even if a new station became operational, commercial success would come over a period of many years. In addition, there are no merger-specific efficiencies that would alleviate the harm from the transaction.
                        <PRTPAGE P="72208"/>
                    </P>
                    <HD SOURCE="HD1">III. EXPLANATION OF THE PROPOSED FINAL JUDGMENT</HD>
                    <P>The divestiture requirement of the proposed Final Judgment will eliminate the anticompetitive effects of the transaction in the Evansville, Indiana DMA by establishing a new, independent, and economically viable competitor, which will maintain the status quo in the DMA. The proposed Final Judgment requires Defendants to divest the Divestiture Assets to Bayou City Broadcasting Evansville, Inc. (Bayou City), an acquirer selected by Defendants and approved by the United States, in a manner consistent with the Final Judgment and the Hold Separate Order in this case. If Bayou City is unable to complete the purchase, the Defendants would be required to divest the Divestiture Assets to another buyer, approved by the United States in its sole discretion. Defendants are required to use their best efforts to accomplish the divestitures ordered by this Final Judgment as expeditiously as possible and in such a way as to satisfy the United States in its sole discretion that the operations can and will be operated by the purchaser as a viable, ongoing business that can compete effectively in the relevant market. Because the transfer of the Divestiture Assets to Bayou City requires Federal Communications Commission (FCC) approval, Defendants are specifically required to use their best efforts to obtain all necessary FCC approvals as expeditiously as possible. The divestiture pursuant to this Section shall take place within five (5) calendar days of entry of the Final Judgment or within 90 days of the filing of the Complaint, whichever is later. Defendants must take all reasonable steps necessary to accomplish the divestiture quickly and shall cooperate with prospective purchasers.</P>
                    <P>In the event that Defendants do not accomplish the divestiture within the periods prescribed in the proposed Final Judgment, or it becomes apparent that Bayou City is unwilling or unable to complete its purchase of the Divestiture Assets, the Final Judgment provides that the Court will appoint a trustee selected by the United States to effect the divestiture. The United States may, after three months, determine not to seek appointment of a trustee if it believes the circumstances warrant allowing the Defendants more time. Under such circumstances, however, the United States may, at any time, exercise its right to select a trustee for the Court to appoint. If a trustee is appointed, the proposed Final Judgment provides that Defendants will pay all costs and expenses of the trustee. The trustee's commission will be structured so as to provide an incentive for the trustee based on the price obtained and the speed with which the divestiture is accomplished. After his or her appointment becomes effective, the trustee will file monthly reports with the Court and the United States setting forth his or her efforts to accomplish the divestiture. At the end of six (6) months, if the divestiture has not been accomplished, the trustee and the United States will make recommendations to the Court, which shall enter such orders as appropriate, in order to carry out the purpose of the trust, including extending the trust or the term of the trustee's appointment.</P>
                    <P>The divestiture provisions of the proposed Final Judgment will eliminate the anticompetitive effects of the transaction in broadcast television spot advertising in the Evansville, Indiana DMA.</P>
                    <P>The proposed Final Judgment also bars Nexstar from reacquiring the Divestiture Assets for the ten-year period of the decree. Nexstar can only affiliate with either FOX or CBS (WEVV's current network affiliates) a year or more from the filing of the Complaint, contingent on the United States' approval in its sole discretion.</P>
                    <HD SOURCE="HD1">IV. REMEDIES AVAILABLE TO POTENTIAL PRIVATE LITIGANTS</HD>
                    <P>Section 4 of the Clayton Act, 15 U.S.C. 15, provides that any person who has been injured as a result of conduct prohibited by the antitrust laws may bring suit in federal court to recover three times the damages the person has suffered, as well as costs and reasonable attorneys' fees. Entry of the proposed Final Judgment will neither impair nor assist the bringing of any private antitrust damage action. Under the provisions of Section 5(a) of the Clayton Act, 15 U.S.C. 16(a), the proposed Final Judgment has no prima facie effect in any subsequent private lawsuit that may be brought against Defendants.</P>
                    <HD SOURCE="HD1">V. PROCEDURES AVAILABLE FOR MODIFICATION OF THE PROPOSED FINAL JUDGMENT</HD>
                    <P>The United States and Defendants have stipulated that the proposed Final Judgment may be entered by the Court after compliance with the provisions of the APPA, provided that the United States has not withdrawn its consent. The APPA conditions entry upon the Court's determination that the proposed Final Judgment is in the public interest.</P>
                    <P>
                        The APPA provides a period of at least sixty (60) days preceding the effective date of the proposed Final Judgment within which any person may submit to the United States written comments regarding the proposed Final Judgment. Any person who wishes to comment should do so within sixty (60) days of the date of publication of this Competitive Impact Statement in the 
                        <E T="04">Federal Register</E>
                        , or the last date of publication in a newspaper of the summary of this Competitive Impact Statement, whichever is later. All comments received during this period will be considered by the United States Department of Justice, which remains free to withdraw its consent to the proposed Final Judgment at any time prior to the Court's entry of judgment. The comments and the response of the United States will be filed with the Court. In addition, comments will be posted on the U.S. Department of Justice, Antitrust Division's internet Web site and, under certain circumstances, published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>Written comments should be submitted to: Scott A. Scheele, Chief, Telecom &amp; Media Enforcement Section, Antitrust Division, U.S. Department of Justice, 450 5th Street NW., Suite 7000, Washington, DC 20530.</P>
                    <P>The proposed Final Judgment provides that the Court retains jurisdiction over this action, and the parties may apply to the Court for any order necessary or appropriate for the modification, interpretation, or enforcement of the Final Judgment.</P>
                    <HD SOURCE="HD1">VI. ALTERNATIVES TO THE PROPOSED FINAL JUDGMENT</HD>
                    <P>The United States considered, as an alternative to the proposed Final Judgment, a full trial on the merits against Defendants. The United States could have continued the litigation and sought preliminary and permanent injunctions against the contemplated transaction. The United States is satisfied, however, that the divestiture of assets described in the proposed Final Judgment will preserve competition for the sale of broadcast television spot advertising in the Evansville, Indiana DMA. Thus, the proposed Final Judgment would achieve all or substantially all of the relief the United States would have obtained through litigation, but avoids the time, expense, and uncertainty of a full trial on the merits of the Complaint.</P>
                    <HD SOURCE="HD1">VII. STANDARD OF REVIEW UNDER THE APPA FOR THE PROPOSED FINAL JUDGMENT</HD>
                    <P>The Clayton Act, as amended by the APPA, requires that proposed consent judgments in antitrust cases brought by the United States be subject to a sixty-day comment period, after which the court shall determine whether entry of the proposed Final Judgment “is in the public interest.” 15 U.S.C. 16(e)(1). In making that determination, the court, in accordance with the statute as amended in 2004, is required to consider:</P>
                    <P>(A) the competitive impact of such judgment, including termination of alleged violations, provisions for enforcement and modification, duration of relief sought, anticipated effects of alternative remedies actually considered, whether its terms are ambiguous, and any other competitive considerations bearing upon the adequacy of such judgment that the court deems necessary to a determination of whether the consent judgment is in the public interest; and</P>
                    <P>(B) the impact of entry of such judgment upon competition in the relevant market or markets, upon the public generally and individuals alleging specific injury from the violations set forth in the complaint including consideration of the public benefit, if any, to be derived from a determination of the issues at trial.</P>
                    <FP>
                        15 U.S.C. 16(e)(1)(A) &amp; (B). In considering these statutory factors, the court's inquiry is necessarily a limited one as the government is entitled to “broad discretion to settle with the defendant within the reaches of the public interest.” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Microsoft Corp.,</E>
                         56 F.3d 1448, 1461 (D.C. Cir. 1995); 
                        <E T="03">see generally United States</E>
                         v. 
                        <E T="03">SBC Commc'ns, Inc.,</E>
                         489 F. Supp. 2d 1 (D.D.C. 2007) (assessing public interest standard under the Tunney Act); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">U.S. Airways Group, Inc.,</E>
                         No. 13-cv-1236(CKK), 2014-1Trade Cas. (CCH) ¶ 78,748, 2014 U.S. Dist. LEXIS 57801, at *7 (D.D.C. Apr. 25, 2014) (noting court has broad discretion to review adequacy of relief at issue); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">InBev N.V./S.A.,</E>
                         No. 08-1965(JR), 2009-2 Trade Cas. (CCH) ¶ 76,736, 2009 U.S. Dist. LEXIS 84787, at *3, (D.D.C. Aug. 11, 
                        <PRTPAGE P="72209"/>
                        2009) (noting that court's review of a consent judgment is limited and only inquires “into whether the government's determination that the proposed remedies will cure the antitrust violations alleged in the complaint was reasonable, and whether the mechanism to enforce the final judgment are clear and manageable”).
                        <SU>1</SU>
                        <FTREF/>
                    </FP>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The 2004 amendments to the APPA substituted “shall” for “may” in directing relevant factors for court to consider and amended the list of factors to focus on competitive considerations and to address potentially ambiguous judgment terms. 
                            <E T="03">Compare</E>
                             15 U.S.C. 16(e) (2004), 
                            <E T="03">with</E>
                             15 U.S.C. 16(e)(1) (2006); 
                            <E T="03">see also SBC Commc'ns,</E>
                             489 F. Supp. 2d at 11 (concluding that the 2004 amendments “effected minimal changes” to APPA review).
                        </P>
                    </FTNT>
                    <P>
                        As the United States Court of Appeals for the District of Columbia Circuit has held, under the APPA a court considers, among other things, the relationship between the remedy secured and the specific allegations set forth in the government's complaint, whether the decree is sufficiently clear, whether enforcement mechanisms are sufficient, and whether the decree may positively harm third parties. 
                        <E T="03">See Microsoft,</E>
                         56 F.3d at 1458-62. With respect to the adequacy of the relief secured by the decree, a court may not “engage in an unrestricted evaluation of what relief would best serve the public.” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">BNS, Inc.,</E>
                         858 F.2d 456, 462 (9th Cir. 1988) (quoting 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Bechtel Corp.,</E>
                         648 F.2d 660, 666 (9th Cir. 1981)); 
                        <E T="03">see also Microsoft,</E>
                         56 F.3d at 1460-62; 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Alcoa, Inc.,</E>
                         152 F. Supp. 2d 37, 40 (D.D.C. 2001); 
                        <E T="03">InBev,</E>
                         2009 U.S. Dist. LEXIS 84787, at *3. Courts have held that:
                    </P>
                    <P>
                        [t]he balancing of competing social and political interests affected by a proposed antitrust consent decree must be left, in the first instance, to the discretion of the Attorney General. The court's role in protecting the public interest is one of insuring that the government has not breached its duty to the public in consenting to the decree. The court is required to determine not whether a particular decree is the one that will best serve society, but whether the settlement is “
                        <E T="03">within the reaches of the public interest.”</E>
                         More elaborate requirements might undermine the effectiveness of antitrust enforcement by consent decree.
                    </P>
                    <FP>
                        <E T="03">Bechtel,</E>
                         648 F.2d at 666 (emphasis added) (citations omitted).
                        <SU>2</SU>
                        <FTREF/>
                         In determining whether a proposed settlement is in the public interest, a district court “must accord deference to the government's predictions about the efficacy of its remedies, and may not require that the remedies perfectly match the alleged violations.” 
                        <E T="03">SBC Commc'ns,</E>
                         489 F. Supp. 2d at 17; 
                        <E T="03">see also U.S. Airways,</E>
                         2014 U.S. Dist. LEXIS 57801, at *16 (noting that a court should not reject the proposed remedies because it believes others are preferable); 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1461 (noting the need for courts to be “deferential to the government's predictions as to the effect of the proposed remedies”); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Archer-Daniels-Midland Co.,</E>
                         272 F. Supp. 2d 1, 6 (D.D.C. 2003) (noting that the court should grant due respect to the United States' prediction as to the effect of proposed remedies, its perception of the market structure, and its views of the nature of the case).
                    </FP>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">Cf. BNS,</E>
                             858 F.2d at 464 (holding that the court's “ultimate authority under the [APPA] is limited to approving or disapproving the consent decree”); 
                            <E T="03">United States</E>
                             v. 
                            <E T="03">Gillette Co.,</E>
                             406 F. Supp. 713, 716 (D. Mass. 1975) (noting that, in this way, the court is constrained to “look at the overall picture not hypercritically, nor with a microscope, but with an artist's reducing glass”). 
                            <E T="03">See generally Microsoft,</E>
                             56 F.3d at 1461 (discussing whether “the remedies [obtained in the decree are] so inconsonant with the allegations charged as to fall outside of the `reaches of the public interest'”).
                        </P>
                    </FTNT>
                    <P>
                        Courts have greater flexibility in approving proposed consent decrees than in crafting their own decrees following a finding of liability in a litigated matter. “[A] proposed decree must be approved even if it falls short of the remedy the court would impose on its own, as long as it falls within the range of acceptability or is `within the reaches of public interest.'” 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Am. Tel. &amp; Tel. Co.,</E>
                         552 F. Supp. 131, 151 (D.D.C. 1982) (citations omitted) (quoting 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Gillette Co.,</E>
                         406 F. Supp. 713, 716 (D. Mass. 1975)), 
                        <E T="03">aff'd sub nom. Maryland</E>
                         v. 
                        <E T="03">United States,</E>
                         460 U.S. 1001 (1983); 
                        <E T="03">see also U.S. Airways,</E>
                         2014 U.S. Dist. LEXIS 57801, at *8 (noting that room must be made for the government to grant concessions in the negotiation process for settlements (citing 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1461); 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Alcan Aluminum Ltd.,</E>
                         605 F. Supp. 619, 622 (W.D. Ky. 1985) (approving the consent decree even though the court would have imposed a greater remedy). To meet this standard, the United States “need only provide a factual basis for concluding that the settlements are reasonably adequate remedies for the alleged harms.” 
                        <E T="03">SBC Commc'ns,</E>
                         489 F. Supp. 2d at 17.
                    </P>
                    <P>
                        Moreover, the court's role under the APPA is limited to reviewing the remedy in relationship to the violations that the United States has alleged in its Complaint, and does not authorize the court to “construct [its] own hypothetical case and then evaluate the decree against that case.” 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1459; 
                        <E T="03">see also U.S. Airways,</E>
                         2014 U.S. Dist. LEXIS 57801, at *9 (noting that the court must simply determine whether there is a factual foundation for the government's decisions such that its conclusions regarding the proposed settlements are reasonable); 
                        <E T="03">InBev,</E>
                         2009 U.S. Dist. LEXIS 84787, at *20 (“the `public interest' is not to be measured by comparing the violations alleged in the complaint against those the court believes could have, or even should have, been alleged”). Because the “court's authority to review the decree depends entirely on the government's exercising its prosecutorial discretion by bringing a case in the first place,” it follows that “the court is only authorized to review the decree itself,” and not to “effectively redraft the complaint” to inquire into other matters that the United States did not pursue. 
                        <E T="03">Microsoft,</E>
                         56 F.3d at 1459-60. As this Court confirmed in 
                        <E T="03">SBC Communications,</E>
                         courts “cannot look beyond the complaint in making the public interest determination unless the complaint is drafted so narrowly as to make a mockery of judicial power.” 
                        <E T="03">SBC Commc'ns,</E>
                         489 F. Supp. 2d at 15.
                    </P>
                    <P>
                        In its 2004 amendments to the APPA, Congress made clear its intent to preserve the practical benefits of utilizing consent decrees in antitrust enforcement, adding the unambiguous instruction that “[n]othing in this section shall be construed to require the court to conduct an evidentiary hearing or to require the court to permit anyone to intervene.” 15 U.S.C. 16(e)(2); 
                        <E T="03">see also U.S. Airways,</E>
                         2014 U.S. Dist. LEXIS 57801, at *9 (indicating that a court is not required to hold an evidentiary hearing or to permit intervenors as part of its review under the APPA). The language wrote into the statute what Congress intended when it enacted the APPA in 1974, as Senator Tunney explained: “[t]he court is nowhere compelled to go to trial or to engage in extended proceedings which might have the effect of vitiating the benefits of prompt and less costly settlement through the consent decree process.” 119 Cong. Rec. 24,598 (1973) (statement of Sen. Tunney). Rather, the procedure for the public interest determination is left to the discretion of the court, with the recognition that the court's “scope of review remains sharply proscribed by precedent and the nature of Tunney Act proceedings.” 
                        <E T="03">SBC Commc'ns,</E>
                         489 F. Supp. 2d at 11.
                        <SU>3</SU>
                        <FTREF/>
                         A court may make its public interest determination based on the competitive impact statement and response to public comments alone. 
                        <E T="03">U.S. Airways,</E>
                         2014 U.S. Dist. LEXIS 57801, at *9.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">See United States</E>
                             v. 
                            <E T="03">Enova Corp.,</E>
                             107 F. Supp. 2d 10, 17 (D.D.C. 2000) (noting that the “Tunney Act expressly allows the court to make its public interest determination on the basis of the competitive impact statement and response to comments alone”); 
                            <E T="03">United States</E>
                             v. 
                            <E T="03">Mid-Am. Dairymen, Inc.,</E>
                             No. 73-CV-681-W-1, 1977-1 Trade Cas. (CCH) ¶ 61,508, at 71,980, *22 (W.D. Mo. 1977) (“Absent a showing of corrupt failure of the government to discharge its duty, the Court, in making its public interest finding, should . . . carefully consider the explanations of the government in the competitive impact statement and its responses to comments in order to determine whether those explanations are reasonable under the circumstances.”); S. Rep. No. 93-298, at 6 (1973) (“Where the public interest can be meaningfully evaluated simply on the basis of briefs and oral arguments, that is the approach that should be utilized.”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">VIII. DETERMINATIVE DOCUMENTS</HD>
                    <P>There are no determinative materials or documents within the meaning of the APPA that were considered by the United States in formulating the proposed Final Judgment.</P>
                    <P>Respectfully submitted,</P>
                    <FP SOURCE="FP-DASH">/s/</FP>
                    <FP>Matthew C. Hammond</FP>
                    <FP>
                        <E T="03">Trial Attorney, U.S. Department of Justice, Antitrust Division, Telecom &amp; Media, 450 5th Street NW., Suite 7000, Washington, DC 20530, Phone: 202-305-8541, Fax: 202-514-6381, Email: matthew.hammond@usdoj.gov</E>
                    </FP>
                    <FP>
                        <E T="03">Counsel for Plaintiff United States of America</E>
                    </FP>
                    <FP>Dated: November 26, 2014</FP>
                    <HD SOURCE="HD1">IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA</HD>
                    <FP SOURCE="FP-1">UNITED STATES OF AMERICA,</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Plaintiff,</E>
                    </FP>
                    <FP SOURCE="FP-1">v.</FP>
                    <FP SOURCE="FP-1">NEXSTAR BROADCASTING GROUP, INC.,</FP>
                    <FP SOURCE="FP-1">MISSION BROADCASTING, INC., </FP>
                    <FP SOURCE="FP-1">COMMUNICATIONS CORPORATION OF AMERICA</FP>
                    <FP SOURCE="FP-1">and </FP>
                    <FP SOURCE="FP-1">SILVER POINT CAPITAL FUND, L.P.,</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Defendants.</E>
                    </FP>
                    <PRTPAGE P="72210"/>
                    <FP SOURCE="FP-1">Case: 1:14-cv-02007</FP>
                    <HD SOURCE="HD1">PROPOSED FINAL JUDGMENT</HD>
                    <P>WHEREAS, plaintiff, the United States of America, having filed its Complaint on __, and plaintiff and defendants Nexstar Broadcasting Group, Inc. (“Nexstar”); Mission Broadcasting, Inc. (“Mission”); Communications Corporation of America (“CCA”) and Silver Point Capital Fund, L.P., by their respective attorneys, having consented to the entry of this Final Judgment without trial or adjudication of any issue of fact or law herein, and without this Final Judgment constituting any evidence against or an admission by any party with respect to any issue of law or fact herein;</P>
                    <P>AND WHEREAS, defendants have agreed to be bound by the provisions of this Final Judgment pending its approval by the Court;</P>
                    <P>AND WHEREAS, the essence of this Final Judgment is the prompt and certain divestiture of the Divestiture Assets to assure that competition is not substantially lessened;</P>
                    <P>AND WHEREAS, the United States requires certain divestitures to be made for the purpose of remedying the loss of competition alleged in the Complaint;</P>
                    <P>AND WHEREAS, defendants have represented to the United States that the divestitures required below can and will be made, and that defendants will later raise no claim of hardship or difficulty as grounds for asking the Court to modify any of the divestiture provisions contained below;</P>
                    <P>NOW, THEREFORE, before any testimony is taken, without trial or adjudication of any issue of fact or law, and upon consent of the parties, it is hereby ORDERED, ADJUDGED, AND DECREED:</P>
                    <HD SOURCE="HD1">I. Jurisdiction</HD>
                    <P>This Court has jurisdiction over each of the parties hereto and over the subject matter of this action. The Complaint states a claim upon which relief may be granted against defendants under Section 7 of the Clayton Act, as amended, 15 U.S.C. 18.</P>
                    <HD SOURCE="HD1">II. Definitions</HD>
                    <P>As used in this Final Judgment:</P>
                    <P>A. “Nexstar” means defendant Nexstar Broadcasting Group, Inc., a Delaware corporation with its headquarters in Irving, Texas, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>B. “Mission” means defendant Mission Broadcasting, Inc. a Delaware corporation with its headquarters in Westlake, Ohio, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>C. “CCA” means Communications Corporation of America, a Delaware corporation headquartered in Lafayette, Louisiana, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>D. “Silver Point” means Silver Point Capital Fund, L.P., a Delaware limited partnership headquartered in Greenwich, Connecticut, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>E. “Acquirer” means BCBE, or another entity to which the defendants divest the Divestiture Assets.</P>
                    <P>F. “BCBE” means Bayou City Broadcasting Evansville, Inc., a Delaware corporation headquartered in Boston, Massachusetts, its successors and assigns, and its subsidiaries, divisions, groups, affiliates, partnerships and joint ventures, and their directors, officers, managers, agents, and employees.</P>
                    <P>G. “WEVV-TV” means the broadcast television station located in the Evansville, Indiana DMA owned by defendant CCA operating on virtual Channel 44.</P>
                    <P>H. “Divestiture Assets” means all of the assets, tangible or intangible, used in the operation of WEVV-TV, including, but not limited to, all real property (owned or leased) used in the operation of the station, all broadcast equipment, office equipment, office furniture, fixtures, materials, supplies, and other tangible property used in the operation of the station; all licenses, permits, authorizations, and applications therefore issued by the Federal Communications Commission (“FCC”) and other government agencies related to that station; all contracts (including programming contracts and rights), agreements, network affiliation agreements, leases and commitments and understandings of defendant CCA relating to the operation of WEVV-TV; all trademarks, service marks, trade names, copyrights, patents, slogans, programming materials, and promotional materials relating to WEVV-TV; all customer lists, contracts, accounts, and credit records; and all logs and other records maintained by defendant CCA in connection with WEVV-TV.</P>
                    <P>
                        I. “DMA” means designated market area as defined by A.C. Nielsen Company based upon viewing patterns and used by the 
                        <E T="03">Investing In Television BIA Market Report 2014</E>
                         (1st ed.). DMAs are ranked according to the number of households therein and are used by broadcasters, advertisers and advertising agencies to aid in evaluating television audience size and composition.
                    </P>
                    <HD SOURCE="HD1">III. Applicability</HD>
                    <P>A. This Final Judgment applies to Nexstar, Mission, CCA, and Silver Point as defined above, and all other persons in active concert or participation with any of them who receive actual notice of this Final Judgment by personal service or otherwise.</P>
                    <P>B. If, prior to complying with Sections IV and V of this Final Judgment, defendants sell or otherwise dispose of all or substantially all of their assets or of lesser business units that include the defendants' Divestiture Assets, they shall require the purchaser to be bound by the provisions of this Final Judgment. Defendants need not obtain such an agreement from the Acquirer of the assets divested pursuant to the Final Judgment.</P>
                    <HD SOURCE="HD1">IV. Divestitures</HD>
                    <P>A. Defendants are ordered and directed to divest the Divestiture Assets to an Acquirer acceptable to the United States in its sole discretion, in a manner consistent with this Final Judgment and the Hold Separate Stipulation and Order in this case. The divestiture pursuant to this Section shall take place within ninety (90) calendar days after the filing of the Complaint in this matter or five (5) days after notice of entry of this Final Judgment by the Court, whichever is later. The United States, in its sole discretion, may agree to an extension of this time period not to exceed thirty (30) calendar days, and shall notify the Court in such circumstances. Defendants shall use their best efforts to accomplish the divestiture ordered by this Final Judgment as expeditiously as possible, including using their best efforts to obtain all necessary FCC approvals as expeditiously as possible.</P>
                    <P>B. In the event that defendants are attempting to divest the assets to an Acquirer other than BCBE, in accomplishing the divestiture ordered by this Final Judgment,</P>
                    <P>(1) Defendants promptly shall make known, by usual and customary means, the availability of the Divestiture Assets;</P>
                    <P>(2) Defendants shall inform any person making inquiry regarding a possible purchase of the Divestiture Assets that they are being divested pursuant to this Final Judgment and provide that person with a copy of this Final Judgment;</P>
                    <P>(3) Defendants shall offer to furnish to all prospective Acquirers, subject to customary confidentiality assurances, all information and documents relating to the Divestiture Assets customarily provided in a due diligence process except such information or documents subject to the attorney-client privileges or work-product doctrine; and</P>
                    <P>(4) Defendants shall make available such information to the United States at the same time that such information is made available to any other person.</P>
                    <P>C. Defendants shall provide the Acquirer and the United States information relating to the personnel involved in the operation and management of the Divestiture Assets to enable the Acquirer to make offers of employment. Defendants shall not interfere with any negotiations by the Acquirer to employ or contract with any employee of any defendant whose primary responsibility is the operation or management of the Divestiture Assets.</P>
                    <P>D. Defendants shall permit the Acquirer of the Divestiture Assets to have reasonable access to personnel and to make inspections of the physical facilities of WEVV-TV; access to any and all environmental, zoning, and other permit documents and information; and access to any and all financial, operational, or other documents and information customarily provided as part of a due diligence process.</P>
                    <P>E. Defendants shall warrant to the Acquirer that each asset will be operational on the date of sale.</P>
                    <P>F. Defendants shall not take any action that will impede in any way the permitting, operation, or divestiture of the Divestiture Assets.</P>
                    <P>
                        G. Defendants shall warrant to the Acquirer that there are no material defects in the environmental, zoning, or other permits pertaining to the operation of each asset, and 
                        <PRTPAGE P="72211"/>
                        that following the sale of the Divestiture Assets, defendants will not undertake, directly or indirectly, any challenges to the environmental, zoning, or other permits relating to the operation of the Divestiture Assets.
                    </P>
                    <P>H. Unless the United States otherwise consents in writing, the divestiture pursuant to Section IV, or by trustee appointed pursuant to Section V of this Final Judgment, shall include the entire Divestiture Assets, and be accomplished in such a way as to satisfy the United States, in its sole discretion, that the Divestiture Assets can and will be used by the Acquirer as part of a viable, ongoing commercial television broadcasting business and the divestiture of such assets will achieve the purposes of this Final Judgment and remedy the competitive harm alleged in the Complaint. The divestiture, whether pursuant to Section IV or Section V of this Final Judgment:</P>
                    <P>(1) shall be made to an Acquirer that, in the United States' sole judgment, has the intent and capability (including the necessary managerial, operational, technical, and financial capability) of competing effectively in the television broadcasting business in the Evansville, Indiana DMA; and</P>
                    <P>(2) shall be accomplished so as to satisfy the United States, in its sole discretion, that none of the terms of any agreement between the Acquirer and defendants gives defendants the ability unreasonably to raise the Acquirer's costs, to lower the Acquirer's efficiency, or otherwise to interfere in the ability of the Acquirer to compete effectively.</P>
                    <HD SOURCE="HD1">V. Appointment of Trustee</HD>
                    <P>A. If either (a) the defendants have not divested the Divestiture Assets within the time period specified in Paragraph IV(A), or (b) the defendants have reason to believe that BCBE may be unable to complete the purchase of the Divestiture Assets, defendants shall notify the United States of that fact in writing.</P>
                    <P>B. If (a) the defendants have not divested the Divestiture Assets within the time period specified in Paragraph IV(A), or (b) the United States decides in its sole discretion that BCBE is likely to be unable to complete the purchase of the Divestiture Assets, upon application of the United States in its sole discretion, the Court shall appoint a trustee selected by the United States and approved by the Court to effect the divestiture of the Divestiture Assets.</P>
                    <P>C. After the appointment of a trustee becomes effective, only the trustee shall have the right to sell the Divestiture Assets. The trustee shall have the power and authority to accomplish the divestiture to an Acquirer, and in a manner, acceptable to the United States in its sole discretion at such price and on such terms as are then obtainable upon reasonable effort by the trustee, subject to the provisions of Sections IV, V, and VI of this Final Judgment, and shall have such other powers as this Court deems appropriate. Subject to Paragraph V(D) of this Final Judgment, the trustee may hire at the cost and expense of defendants any investment bankers, attorneys, or other agents, who shall be solely accountable to the trustee, reasonably necessary in the trustee's judgment to assist in the divestiture. Defendants shall inform any person making an inquiry regarding a possible purchase of the Divestiture Assets that they are being divested pursuant to this Final Judgment and provide that person with a copy of this Final Judgment and contact information for the trustee.</P>
                    <P>D. Defendants shall not object to a sale by the trustee on any ground other than the trustee's malfeasance. Any such objection by defendants must be conveyed in writing to the United States and the trustee within ten (10) calendar days after the trustee has provided the notice required under Section VI.</P>
                    <P>E. The trustee shall serve at the cost and expense of defendants, on such terms and conditions as the United States approves, including confidentiality requirements and conflict of interest certifications. The trustee shall account for all monies derived from the sale of the assets sold by the trustee and all costs and expenses so incurred. After approval by the Court of the trustee's accounting, including fees for its services yet unpaid and those of any professionals and agents retained by the trustee, all remaining money shall be paid to defendants and the trust shall then be terminated. The compensation of the trustee and any professionals and agents retained by the trustee shall be reasonable in light of the value of the Divestiture Assets and based on a fee arrangement providing the trustee with an incentive based on the price and terms of the divestiture and the speed with which it is accomplished, but timeliness is paramount. If the trustee and Defendants are unable to reach agreement on the trustee's compensation or other terms and conditions within fourteen (14) calendar days of appointment of the trustee, the United States may, in its sole discretion, take appropriate action, including making a recommendation to the Court.</P>
                    <P>F. Defendants shall use their best efforts to assist the trustee in accomplishing the required divestiture. The trustee and any consultants, accountants, attorneys, and other persons retained by the trustee shall have full and complete access to the personnel, books, records, and facilities of the business to be divested, and defendants shall develop financial and other information relevant to such business as the trustee may reasonably request, subject to reasonable protection for trade secret or other confidential research, development, or commercial information. Defendants shall take no action to interfere with or to impede the trustee's accomplishment of the divestiture.</P>
                    <P>G. After his or her appointment, the trustee shall file monthly reports with the United States and, as appropriate, the Court setting forth the trustee's efforts to accomplish the divestiture ordered under this Final Judgment. To the extent such reports contain information that the trustee deems confidential, such reports shall not be filed in the public docket of the Court. Such reports shall include the name, address, and telephone number of each person who, during the preceding month, made an offer to acquire, expressed an interest in acquiring, entered into negotiations to acquire, or was contacted or made an inquiry about acquiring, any interest in the Divestiture Assets, and shall describe in detail each contact with any such person. The trustee shall maintain full records of all efforts made to divest the Divestiture Assets.</P>
                    <P>H. If the trustee has not accomplished the divestiture ordered under this Final Judgment within six (6) months after its appointment, the trustee shall promptly file with the Court a report setting forth: (1) The trustee's efforts to accomplish the required divestiture, (2) the reasons, in the trustee's judgment, why the required divestiture have not been accomplished, and (3) the trustee's recommendations. To the extent that such report contains information that the trustee deems confidential, such report shall not be filed in the public docket of the Court. The trustee shall at the same time furnish such report to the United States, which shall have the right to make additional recommendations consistent with the purpose of the trust. The Court thereafter shall enter such orders as it shall deem appropriate to carry out the purpose of the Final Judgment, which may, if necessary, include extending the trust and the term of the trustee's appointment by a period requested by the United States.</P>
                    <P>I. If the United States determines that the trustee has ceased to act or failed to act diligently or in a reasonably cost-effective manner, it may recommend the Court appoint a substitute trustee.</P>
                    <HD SOURCE="HD1">VI. Notice of Proposed Divestiture</HD>
                    <P>A. Within two (2) business days following execution of a definitive divestiture agreement, defendants or the trustee, whichever is then responsible for effecting the divestiture required herein, shall notify the United States of any proposed divestiture required by Section IV or V of this Final Judgment. If the trustee is responsible, it shall similarly notify defendants. The notice shall set forth the details of the proposed divestiture and list the name, address, and telephone number of each person not previously identified who offered or expressed an interest in or desire to acquire any ownership interest in the Divestiture Assets, together with full details of the same.</P>
                    <P>B. Within fifteen (15) calendar days of receipt by the United States of such notice, the United States may request from defendants, the proposed Acquirer, any other third party, or the trustee if applicable, additional information concerning the proposed divestiture, the proposed Acquirer, and any other potential Acquirer. Defendants and the trustee shall furnish any additional information requested within fifteen (15) calendar days of the receipt of the request, unless the parties shall otherwise agree.</P>
                    <P>
                        C. Within thirty (30) calendar days after receipt of the notice or within twenty (20) calendar days after the United States has been provided the additional information requested from defendants, the proposed Acquirer, any third party, and the trustee, whichever is later, the United States, in its sole discretion, shall provide written notice to defendants and the trustee, if there is one, stating whether or not it objects to the 
                        <PRTPAGE P="72212"/>
                        proposed divestiture. If the United States provides written notice that it does not object, the divestiture may be consummated, subject only to defendants' limited right to object to the sale under Paragraph V(D) of this Final Judgment. Absent written notice that the United States does not object to the proposed Acquirer or upon objection by the United States, a divestiture proposed under Section IV or Section V shall not be consummated. Upon objection by defendants under Paragraph V(D), a divestiture proposed under Section V shall not be consummated unless approved by the Court.
                    </P>
                    <HD SOURCE="HD1">VII. Financing</HD>
                    <P>Defendants shall not finance all or any part of any purchase made pursuant to Section IV or V of this Final Judgment.</P>
                    <HD SOURCE="HD1">VIII. Hold Separate</HD>
                    <P>Until the divestiture required by this Final Judgment has been accomplished, defendants shall take all steps necessary to comply with the Hold Separate Stipulation and Order entered by this Court. Defendants shall take no action that would jeopardize the divestiture ordered by this Court.</P>
                    <HD SOURCE="HD1">IX. Affidavits</HD>
                    <P>A. Within twenty (20) calendar days of the filing of the Complaint in this matter, and every thirty (30) calendar days thereafter until the divestiture has been completed under Section IV or V, defendants shall deliver to the United States an affidavit as to the fact and manner of their compliance with Section IV or V of this Final Judgment. Each such affidavit shall include the name, address, and telephone number of each person who, during the preceding thirty (30) days, made an offer to acquire, expressed an interest in acquiring, entered into negotiations to acquire, or was contacted or made an inquiry about acquiring, any interest in the Divestiture Assets, and shall describe in detail each contact with any such person during that period.</P>
                    <P>B. Each such affidavit shall also include a description of the efforts defendants have taken to complete the sale of the Divestiture Assets—including efforts to secure regulatory approvals—and to provide required information to prospective Acquirers, including the limitations, if any, on such information. Assuming the information set forth in the affidavit is true and complete, any objection by the United States to information provided by defendants, including limitation on information, shall be made within fourteen (14) days of receipt of such affidavit.</P>
                    <P>C. Within twenty (20) calendar days of the filing of the Complaint in this matter, each defendant shall deliver to the United States an affidavit that describes in reasonable detail all actions defendants have taken and all steps defendants have implemented on an ongoing basis to comply with Section VIII of this Final Judgment. Each such affidavit shall also include a description of the efforts defendants have taken to complete the sale of the Divestiture Assets, including efforts to secure FCC or other regulatory approvals. Defendants shall deliver to the United States an affidavit describing any changes to the efforts and actions outlined in defendants' earlier affidavits filed pursuant to this section within fifteen (15) calendar days after the change is implemented.</P>
                    <P>D. Defendants shall keep all records of all efforts made to preserve and divest the Divestiture Assets until one year after such divestiture has been completed.</P>
                    <HD SOURCE="HD1">X. Compliance Inspection</HD>
                    <P>A. For the purposes of determining or securing compliance with this Final Judgment, or of any related orders such as any Hold Separate Order, or of determining whether the Final Judgment should be modified or vacated, and subject to any legally recognized privilege, from time to time duly authorized representatives of the United States Department of Justice, including consultants and other persons retained by the United States, shall, upon written request of an authorized representative of the Assistant Attorney General in charge of the Antitrust Division, and on reasonable notice to defendants, be permitted:</P>
                    <P>(1) access during defendants' office hours to inspect and copy, or at the option of the United States, to require defendants to provide hard copies or electronic copies of, all books, ledgers, accounts, records, data and documents in the possession, custody or control of defendants, relating to any matters contained in this Final Judgment; and</P>
                    <P>(2) to interview, either informally or on the record, defendants' officers, employees, or agents, who may have their individual counsel present, regarding such matters. The interviews shall be subject to the reasonable convenience of the interviewee and without restraint or interference by defendants.</P>
                    <P>B. Upon the written request of an authorized representative the Assistant Attorney General in charge of the Antitrust Division, defendants shall submit such written reports or responses to written interrogatories, under oath if requested, relating to any of the matters contained in this Final Judgment as may be requested.</P>
                    <P>C. No information or documents obtained by the means provided in this section shall be divulged by the United States to any person other than an authorized representative of the executive branch of the United States, except in the course of legal proceedings to which the United States is a party (including grand jury proceedings), or for the purpose of securing compliance with this Final Judgment, or as otherwise required by law.</P>
                    <P>D. If at the time information or documents are furnished by defendants to the United States, defendants represent and identify in writing the material in any such information or documents to which a claim of protection may be asserted under Rule 26(c)(1)(G) of the Federal Rules of Civil Procedure, and defendants mark each pertinent page of such material, “Subject to claim of protection under Rule 26(c)(1)(G) of the Federal Rules of Civil Procedure,” then the United States shall give defendants ten (10) calendar days notice prior to divulging such material in any legal proceeding (other than a grand jury proceeding).</P>
                    <HD SOURCE="HD1">XI. No Reacquisition</HD>
                    <P>A. Defendants may not (1) reacquire any part of the Divestiture Assets, (2) acquire any option to reacquire any part of the Divestiture Assets or to assign the Divestiture Assets to any other person, (3) enter into any local marketing agreement, joint sales agreement, other cooperative selling arrangement, or shared services agreement, or conduct other business negotiations jointly with the Acquirer with respect to the Divestiture Assets, or (4) provide financing or guarantees of financing with respect to the Divestiture Assets, during the term of this Final Judgment. The shared services prohibition does not preclude Defendants from continuing or entering into agreements in a form customarily used in the industry to (1) share news helicopters or (2) pool generic video footage that does not include recording a reporter or other on-air talent, and does not preclude defendants from entering into any non-sales-related shared services agreement that is approved in advance by the United States in its sole discretion.</P>
                    <P>B. Notwithstanding any prohibition in this section, Defendants may acquire an affiliation with the FOX or CBS broadcast networks serving the Evansville, Indiana DMA during the period of this Final Judgment only if all of the following conditions are met:</P>
                    <P>(1) at least one year has elapsed from the date of the filing of the Complaint in this matter;</P>
                    <P>(2) Defendants notify the Department of Justice in writing of their intention to acquire the FOX or CBS affiliation in Evansville; and</P>
                    <P>(3) the Department of Justice acting in its sole discretion gives its approval for the Defendants to acquire the FOX or CBS affiliation in Evansville.</P>
                    <P>Within ten (10) business days of receiving notice from the Defendants, the Department will respond in writing giving its approval or requesting additional information from the Defendants. Within fifteen (15) business days of receiving the requested additional information, the Department will respond in writing either giving or withholding its approval.</P>
                    <HD SOURCE="HD1">XII. Retention of Jurisdiction</HD>
                    <P>This Court retains jurisdiction to enable any party to this Final Judgment to apply to this Court at any time for further orders and directions as may be necessary or appropriate to carry out or construe this Final Judgment, to modify any of its provisions, to enforce compliance, and to punish violations of its provisions.</P>
                    <HD SOURCE="HD1">XIII. Expiration of Final Judgment</HD>
                    <P>Unless this Court grants an extension, this Final Judgment shall expire ten (10) years from the date of its entry.</P>
                    <HD SOURCE="HD1">XV. Public Interest Determination</HD>
                    <P>
                        Entry of this Final Judgment is in the public interest. The parties have complied with the requirements of the Antitrust Procedures and Penalties Act, 15 U.S.C. 16, including making copies available to the public of this Final Judgment, the Competitive Impact Statement, and any comments thereon, and the United States' 
                        <PRTPAGE P="72213"/>
                        responses to comments. Based upon the record before the Court, which includes the Competitive Impact Statement and any comments and responses to comments filed with the Court, entry of this Final Judgment is in the public interest.
                    </P>
                    <FP SOURCE="FP-DASH">Date: </FP>
                    <P>Court approval subject to procedures of Antitrust Procedures and Penalties Act, 15 U.S.C. 16.</P>
                    <FP SOURCE="FP-DASH"/>
                    <FP SOURCE="FP-2">
                        <E T="03">United States District Judge</E>
                    </FP>
                </EXTRACT>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28585 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Foreign Claims Settlement Commission</SUBAGY>
                <DEPDOC>[F.C.S.C. Meeting and Hearing Notice No. 11-14]</DEPDOC>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <P>The Foreign Claims Settlement Commission, pursuant to its regulations (45 CFR part 503.25) and the Government in the Sunshine Act (5 U.S.C. 552b), hereby gives notice in regard to the scheduling of open meetings as follows:</P>
                <P>Tuesday, December 16, 2014: 10:00 a.m.—Oral hearings on Objection to Commission's Proposed Decisions in Claim Nos. IRQ-I-023 and IRQ-I-024.</P>
                <P>
                    <E T="03">Status:</E>
                     Open.
                </P>
                <P>All meetings are held at the Foreign Claims Settlement Commission, 600 E Street NW., Washington, DC. Requests for information, or advance notices of intention to observe an open meeting, may be directed to: Patricia M. Hall, Foreign Claims Settlement Commission, 600 E Street NW., Suite 6002, Washington, DC 20579. Telephone: (202) 616-6975.</P>
                <SIG>
                    <NAME>Brian M. Simkin,</NAME>
                    <TITLE>Chief Counsel.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28663 Filed 12-3-14; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-BA-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request; Focus Groups for Evaluating the Effectiveness of Employee Retirement Income Security Act Section 408(b)(2) Disclosure Requirements</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Labor (DOL) is submitting the Employee Benefits Security Administration (EBSA) sponsored information collection request (ICR) proposal titled, “Focus Groups for Evaluating the Effectiveness of Employee Retirement Income Security Act Section 408(b)(2) Disclosure Requirements,” to the Office of Management and Budget (OMB) for review and approval for use in accordance with the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ). Public comments on the ICR are invited.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The OMB will consider all written comments that agency receives on or before January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free of charge from the RegInfo.gov Web site at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=201408-1210-004</E>
                         (this link will only become active on the day following publication of this notice) or by contacting Michel Smyth by telephone at 202-693-4129 (this is not a toll-free number) or by email at 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov</E>
                        .
                    </P>
                    <P>
                        Submit comments about this request by mail or courier to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for DOL-EBSA, Office of Management and Budget, Room 10235, 725 17th Street NW., Washington, DC 20503; by Fax: 202-395-5806 (this is not a toll-free number); or by email: 
                        <E T="03">OIRA_submission@omb.eop.gov</E>
                        . Commenters are encouraged, but not required, to send a courtesy copy of any comments by mail or courier to the U.S. Department of Labor-OASAM, Office of the Chief Information Officer, Attn: Departmental Information Compliance Management Program, Room N1301, 200 Constitution Avenue NW., Washington, DC 20210; or by email: 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION:</HD>
                    <P>
                        Contact Michel Smyth by telephone at 202-693-4129 (this is not a toll-free number) or by email at 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov</E>
                        .
                    </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>44 U.S.C. 3507(a)(1)(D).</P>
                    </AUTH>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This ICR seeks PRA authority for focus groups to be used for evaluating the effectiveness of Employee Retirement Income Security Act (ERISA) section 408(b)(2) disclosure requirements. The ERISA requires a plan fiduciary, when selecting and monitoring service providers and plan investments, to act prudently and solely in the interest of plan participants and beneficiaries. A responsible plan fiduciary must also ensure that any arrangement with a service provider is reasonable and that only reasonable compensation is paid for services. Fundamental to the ability of fiduciaries to discharge these obligations is obtaining information sufficient to enable them to make informed decisions about an employee benefit plan's services, the costs of such services, and the service providers. This ICR is designed to explore current practices and effects of a final regulation published in the 
                    <E T="04">Federal Register</E>
                     on February 3, 2012, to implement section 408(b)(2) and to gather information about the need for a guide, summary, or similar tool to help a responsible plan fiduciary navigate through and understand the disclosures. 
                    <E T="03">See</E>
                     77 FR 5632. The EBSA intends to use information collected from the focus groups: (1) To assess responsible plan fiduciaries' experience in receiving the disclosures the 408(b)(2) regulations require; (2) to assess the effectiveness of the disclosures in helping plan fiduciaries make decisions; (3) to determine how well plan fiduciaries understand the disclosures, especially in the small plan marketplace (100 participants or less); and (4) to evaluate whether, and how, a guide, summary, or similar tool would help a fiduciary understand the disclosures. The focus group results will be used to inform and support a notice of final rulemaking for the guide requirement.
                </P>
                <P>
                    This proposed information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information if the collection of information does not display a valid Control Number. 
                    <E T="03">See</E>
                     5 CFR 1320.5(a) and 1320.6. For additional information, see the related notice published in the 
                    <E T="04">Federal Register</E>
                     on March 12, 2014 (79 FR 14085).
                </P>
                <P>
                    Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the 
                    <E T="02">ADDRESSES</E>
                     section within thirty (30) days of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . In order to help ensure appropriate consideration, comments should mention OMB ICR Reference Number 201408-1210-004. The OMB is particularly interested in comments that:
                    <PRTPAGE P="72214"/>
                </P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     DOL-EBSA.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Focus Groups for Evaluating the Effectiveness of Employee Retirement Income Security Act Section 408(b)(2) Disclosure Requirements.
                </P>
                <P>
                    <E T="03">OMB ICR Reference Number:</E>
                     201408-1210-004.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Private Sector—businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Respondents:</E>
                     85.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Responses:</E>
                     85.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Time Burden:</E>
                     128 hours.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Other Costs Burden:</E>
                     $0.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Michel Smyth,</NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28592 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-29-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Workforce Investment Act; Native American Employment and Training Council, Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration, U.S. Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to Section 10(a)(2) of the Federal Advisory Committee Act (FACA) (Public Law 92-463), as amended, and Section 166(h)(4) of the Workforce Investment Act (WIA) [29 U.S.C. 2911(h)(4)], notice is hereby given of the next meeting of the Native American Employment and Training Council (Council), as constituted under WIA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will begin at 9:00 a.m. (Eastern Standard Time) on Wednesday, December 17, 2014, and continue until 5:00 p.m., that day. The meeting will reconvene at 9:00 a.m. on Thursday, December 18, 2014, and adjourn at 5:00 p.m., that day. The period from 3:30 p.m. to 5:30 p.m., on December 17, 2014, will be reserved for participation and comment by members of the public.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the Bureau of Labor Statistics, Postal Square Building, 2 Massachusetts Ave. NE., Washington DC 20212, in the conference center, Rooms 7 and 8.</P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The meeting will be open to the public. Members of the public not present may submit a written statement on or before December 10, 2014, to be included in the record of the meeting. Statements are to be submitted to Ms. Athena R. Brown, Designated Federal Officer (DFO), U.S. Department of Labor, 200 Constitution Avenue NW., Room S-4209, Washington, DC 20210. Persons who need special accommodations should contact Mr. Craig Lewis at (202) 693-3384, at least two business days before the meeting. The formal agenda will focus on the following topics: (1) U.S. Department of Labor, Employment and Training Administration Update and the Workforce Innovation and Opportunity Act of 2014; (2) Training and Technical Assistance; (3) Council and Workgroup Updates and Recommendations; (4) New Business and Next Steps; and (5) Public Comment.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Athena R. Brown, DFO, Division of Indian and Native American Programs, Employment and Training Administration, U.S. Department of Labor, Room S-4209, 200 Constitution Avenue NW., Washington, DC 20210. Telephone number (202) 693-3737 (VOICE) (this is not a toll-free number).</P>
                    <SIG>
                        <NAME>Portia Wu,</NAME>
                        <TITLE>Assistant Secretary, Employment and Training Administration.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28566 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4501-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL FOUNDATION FOR THE ARTS AND THE HUMANITIES</AGENCY>
                <SUBJECT>Notice of Proposed Information Collection Requests: Let's Move Museums, Let's Move Gardens</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Institute of Museum and Library Services, National Foundation for the Arts and the Humanities.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comments, collection of information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Institute of Museum and Library Services (IMLS), as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. By this notice, IMLS is soliciting comments concerning a survey to gather information to identify museums that are currently or have plans to provide interactive experiences (exhibitions); afterschool, summer and other targeted programs, and food service operations that help fight childhood obesity. The data collection will help to identify best practices and collect information about the capacity of museums to reach the public with important public health messages.</P>
                    <P>
                        A copy of the proposed information collection request can be obtained by contacting the individual listed below in the 
                        <E T="02">ADDRESSES</E>
                         section of this notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments must be submitted to the office listed in the 
                        <E T="02">ADDRESSES</E>
                         section below on or before February 5, 2015.
                    </P>
                    <P>IMLS is particularly interested in comments that help the agency to:</P>
                    <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                    <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information including the validity of the methodology and assumptions used;</P>
                    <P>
                        • Enhance the quality, utility, and clarity of the information to be collected; and
                        <PRTPAGE P="72215"/>
                    </P>
                    <P>
                        • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated electronic, mechanical, or other technological collection techniques, or other forms of information technology, 
                        <E T="03">e.g.,</E>
                         permitting electronic submissions of responses.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send comments to: Claudia French, Institute of Museum and Library Services, 1800 M Street NW., 9th Floor, Washington, DC 20036. 
                        <E T="03">Telephone:</E>
                         (202) 653-4717. 
                        <E T="03">Email: cfrench@imls.gov</E>
                         or by 
                        <E T="03">teletype</E>
                         (TTY/TDD) for persons with hearing difficulty at (202) 653-4614.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Institute of Museum and Library Services is the primary source of federal support for the Nation's 123,000 libraries and 35,000 museums. The Institute's mission is to inspire libraries and museums to advance innovation, learning and civic engagement. The Institute works at the national level and in coordination with state and local organizations to sustain heritage, culture, and knowledge; enhance learning and innovation; and support professional development. IMLS is responsible for identifying national needs for and trends in museum, library, and information services; measuring and reporting on the impact and effectiveness of museum, library and information services throughout the United States, including programs conducted with funds made available by IMLS; identifying, and disseminating information on, the best practices of such programs; and developing plans to improve museum, library and information services of the United States and strengthen national, State, local, regional, and international communications and cooperative networks (20 U.S.C. Chapter 72, 20 U.S.C. 9108).</P>
                <HD SOURCE="HD1">II. Current Actions</HD>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated electronic, mechanical, or other technological collection techniques, or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submissions of responses.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Institute of Museum and Library Services.
                </P>
                <P>
                    <E T="03">Title: Let's Move</E>
                     Museums, 
                    <E T="03">Let's Move</E>
                     Gardens.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3137-0084.
                </P>
                <P>
                    <E T="03">Agency Number:</E>
                     3137.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Museums, state, local, tribal government and not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     50.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     .17.
                </P>
                <P>
                    <E T="03">Total Annual Costs to Respondents:</E>
                     $164.
                </P>
                <P>
                    <E T="03">Total Annualized to Federal Government:</E>
                     $4,615
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Claudia French, Institute of Museum and Library Services, 1800 M Street NW., 9th Floor, Washington, DC 20036. 
                        <E T="03">Telephone:</E>
                         (202) 653-4717. 
                        <E T="03">Email: cfrench@imls.gov</E>
                         or by 
                        <E T="03">teletype</E>
                         (TTY/TDD) for persons with hearing difficulty at (202) 653-4614.
                    </P>
                    <SIG>
                        <DATED> Dated: December 2, 2014.</DATED>
                        <NAME>Kim Miller,</NAME>
                        <TITLE>Management Analyst.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28572 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Notice of Permits Issued Under the Antarctic Conservation Act of 1978</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Science Foundation</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of permits issued under the Antarctic Conservation of 1978, Public Law 95-541.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Science Foundation (NSF) is required to publish notice of permits issued under the Antarctic Conservation Act of 1978. This is the required notice.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Li Ling Hamady, ACA Permit Officer, Division of Polar Programs, Rm. 755, National Science Foundation, 4201 Wilson Boulevard, Arlington, VA 22230. Or by email: 
                        <E T="03">ACApermits@nsf.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On October 30, 2014 the National Science Foundation published a notice in the 
                    <E T="04">Federal Register</E>
                     of a permit application received. The permit was issued on December 1, 2014 to:
                </P>
                <FP SOURCE="FP-1">Dr. Diana H. Wall Permit No. 2015-012</FP>
                <SIG>
                    <NAME>Nadene G. Kennedy,</NAME>
                    <TITLE>Polar Coordination Specialist, Division of Polar Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28578 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Astronomy and Astrophysics Advisory Committee; Notice of Meeting</SUBJECT>
                <P>In accordance with the Federal Advisory Committee Act (Pub., L. 92-463, as amended), the National Science Foundation announces the following meeting:</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name and Committee Code:</E>
                         Astronomy and Astrophysics Advisory Committee #13883.
                    </P>
                    <P>
                        <E T="03">Date and Time:</E>
                    </P>
                    <FP SOURCE="FP-1">January 28, 2015 9:00 a.m.-5:00 p.m.</FP>
                    <FP SOURCE="FP-1">January 29, 2015 9:00 a.m.-12:00 p.m.</FP>
                    <P>
                        <E T="03">Place:</E>
                         National Science Foundation, Room 1235, Stafford I Building, 4201 Wilson Blvd., Arlington, VA 22230.
                    </P>
                    <P>
                        <E T="03">Type of Meeting:</E>
                         Open.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Dr. Jim Ulvestad, Division Director, Division of Astronomical Sciences, Suite 1045, National Science Foundation, 4201 Wilson Blvd., Arlington, VA 22230. Telephone: 703-292-7165.
                    </P>
                    <P>
                        <E T="03">Purpose of Meeting:</E>
                         To provide advice and recommendations to the National Science Foundation (NSF), the National Aeronautics and Space Administration (NASA) and the U.S. Department of Energy (DOE) on issues within the field of astronomy and astrophysics that are of mutual interest and concern to the agencies.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To hear presentations of current programming by representatives from NSF, NASA, DOE and other agencies relevant to astronomy and astrophysics; to discuss current and potential areas of cooperation between the agencies; to formulate recommendations for continued and new areas of cooperation and mechanisms for achieving them.
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Suzanne Plimpton,</NAME>
                    <TITLE>Acting Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28573 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. M-52-033-COL; NRC-2008-0566]</DEPDOC>
                <SUBJECT>In the Matter of DTE Electric Company, Combined License for Enrico Fermi Unit 3; Notice of Hearing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of hearing.</P>
                </ACT>
                <SUM>
                    <PRTPAGE P="72216"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) will convene an evidentiary session to receive testimony and exhibits in the uncontested portion of this proceeding regarding the application of DTE Electric Company for a combined license (COL) to construct and operate a new nuclear power generation facility at the Enrico Fermi Nuclear Plant Unit 3 (Fermi 3). This mandatory hearing will concern safety and environmental matters relating to the requested COL.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The hearing will be held on February 4, 2015, beginning at 8:30 a.m. Eastern Time. For the schedule for submitting pre-filed documents and deadlines affecting Interested Government Participants, see Section VI of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please refer to Docket ID M-52-033-COL when contacting the NRC about the availability of information regarding this document. You may obtain publicly-available information related to this document using any of the following methods:</P>
                    <P>
                        • NRC's Electronic Hearing Docket: You may obtain publicly available documents related to this hearing on line at 
                        <E T="03">http://www.nrc.gov/about-nrc/regulatory/adjudicatory.html</E>
                        .
                    </P>
                    <P>
                        • NRC's Agencywide Documents Access and Management System (ADAMS): You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                         To begin the search, select “
                        <E T="03">ADAMS Public Documents”</E>
                         and then select “
                        <E T="03">Begin Web-based ADAMS Search.”</E>
                         For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to 
                        <E T="03">pdr.resource@nrc.gov.</E>
                         The ADAMS accession number for each document referenced in this document (if that document is available in ADAMS) is provided the first time that a document is referenced.
                    </P>
                    <P>• NRC's PDR: You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland, 20852.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Glenn Ellmers, Office of the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, telephone: 301-415-0442; email: 
                        <E T="03">Glenn.Ellmers@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Commission hereby gives notice that, pursuant to Section 189a of the Atomic Energy Act of 1954, as amended (the Act), it will convene an evidentiary session to receive testimony and exhibits in the uncontested portion of this proceeding regarding DTE Electric Company's September 18, 2008, application for a COL under part 52 of Title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR) to construct and operate a new nuclear power generation facility at the Enrico Fermi Nuclear Plant Unit 3 site in Monroe County, Michigan (ADAMS Accession No. ML082630034). This mandatory hearing will concern safety and environmental matters relating to the requested COL, as more fully described below. Participants in the hearing are not to address any contested issues in their written filings or oral presentations.
                </P>
                <HD SOURCE="HD1">II. Evidentiary Uncontested Hearing</HD>
                <P>The Commission will conduct this hearing beginning at 8:30 a.m., Eastern Time on February 4, 2015, at the Commission's headquarters in Rockville, Maryland. The hearing will continue on subsequent days, if necessary.</P>
                <HD SOURCE="HD1">III. Presiding Officer</HD>
                <P>The Commission is the presiding officer for this proceeding.</P>
                <HD SOURCE="HD1">IV. Matters To Be Considered</HD>
                <P>The matter at issue in this proceeding is whether the review of the application by the Commission's staff has been adequate to support the findings found in 10 CFR 52.97 and 10 CFR 51.107. Those findings are as follows:</P>
                <HD SOURCE="HD2">Issues Pursuant to the Atomic Energy Act of 1954, as Amended</HD>
                <P>With respect to the COL: (1) Whether the applicable standards and requirements of the Act and the Commission's regulations have been met; (2) whether any required notifications to other agencies or bodies have been duly made; (3) whether there is reasonable assurance that the facility will be constructed and will operate in conformity with the license, the provisions of the Act, and the Commission's regulations; (4) whether the applicant is technically and financially qualified to engage in the activities authorized; and (5) whether issuance of the license will not be inimical to the common defense and security or the health and safety of the public.</P>
                <HD SOURCE="HD2">Issues Pursuant to the National Environmental Policy Act (NEPA) of 1969</HD>
                <P>With respect to the COL: (1) Determine whether the requirements of Sections 102(2) (A), (C), and (E) of NEPA and the applicable regulations in 10 CFR part 51 have been met; (2) independently consider the final balance among conflicting factors contained in the record of the proceeding with a view to determining the appropriate action to be taken; (3) determine, after weighing the environmental, economic, technical, and other benefits against environmental and other costs, and considering reasonable alternatives, whether the combined license should be issued, denied, or appropriately conditioned to protect environmental values; and (4) determine whether the NEPA review conducted by the NRC staff has been adequate.</P>
                <HD SOURCE="HD1">V. Schedule for Submittal of Pre-Filed Documents</HD>
                <P>No later than January 14, 2015, unless the Commission directs otherwise, the staff and the applicant shall submit a list of its anticipated witnesses for the hearing.</P>
                <P>No later than January 14, 2015, unless the Commission directs otherwise, the applicant shall submit its pre-filed written testimony. The staff submitted its testimony on November 20, 2014.</P>
                <P>The Commission may issue written questions to the applicant or the staff before the hearing. If such questions are issued, an order containing such questions will be issued no later than December 30, 2014. Responses to such questions are due January 14, 2015, unless the Commission directs otherwise.</P>
                <HD SOURCE="HD1">VI. Interested Government Participants</HD>
                <P>
                    No later than December 19, 2014, any interested U.S. State, local government body, federally-recognized Indian tribe, Canadian Province, local government body, or First Nation 
                    <SU>1</SU>
                    <FTREF/>
                     may file with the Commission a statement of any issues or questions that the U.S. State, local government body, Indian tribe, Canadian Province, local government body, or First Nation wishes the Commission to give particular attention to as part of the uncontested hearing process. Such statement may be accompanied by any supporting documentation that the U.S. State, local government body, Indian tribe, Canadian Province, local government body, or First Nation sees fit to provide. Any statements and supporting documentation (if any) received by the Commission using the agency's E-filing 
                    <PRTPAGE P="72217"/>
                    system 
                    <SU>2</SU>
                    <FTREF/>
                     by the deadline indicated above will be made part of the record of the proceeding. The Commission will use such statements and documents as appropriate to inform its pre-hearing questions to the staff and applicant, its inquiries at the oral hearing, and its decision following the hearing. The Commission may also request, on or about January 7, 2015, that one or more particular U.S. States, local government bodies, Indian tribes, Canadian Provinces, local government bodies, or First Nations send one representative each to the evidentiary hearing to answer Commission questions and/or make a statement for the purpose of assisting the Commission's exploration of one or more of the issues raised by the U.S. State, local government body, Indian tribe, Canadian Province, local government body, or First Nation in the pre-hearing filings described above. The decision whether to request the presence of a representative of a U.S. State, local government body, Indian tribe, Canadian Province, local government body, or First Nation at the evidentiary hearing to make a statement and/or answer Commission questions is solely at the Commission's discretion. The Commission's request will specify the issue or issues that each representative should be prepared to address.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Due to the proximity of the Fermi 3 site to the Canadian border, the Commission is expanding the list of interested government participants to include Canadian Provinces, local governments, and First Nations in this proceeding.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The process for accessing and using the agency's E-filing system is described in the March 17, 2009, notice of hearing that was issued by the Commission for this proceeding. See Notice of Hearing 74 FR 836. Participants who are unable to use the electronic information exchange (EIE), or who will have difficulty complying with EIE requirements in the time frame provided for submission of written statements, may provide their statements by electronic mail to 
                        <E T="03">hearingdocket@nrc.gov.</E>
                    </P>
                </FTNT>
                <P>
                    U.S. States, local governments, Indian tribes, Canadian Provinces, local governments, and First Nations should be aware that this evidentiary hearing is separate and distinct from the NRC's contested hearing process. Issues within the scope of contentions that have been admitted or contested issues pending before the Atomic Safety and Licensing Board or the Commission in a contested proceeding for a COL application are outside the scope of the uncontested proceeding for that COL application. In addition, although U.S. States, local governments, Indian tribes, Canadian Provinces, local governments, or First Nations participating as described above may take any position they wish, or no position at all, with respect to issues regarding the COL application or the NRC staff's associated environmental review that do fall within the scope of the uncontested proceeding (
                    <E T="03">i.e.,</E>
                     issues that are not within the scope of admitted contentions or pending contested issues), they should be aware that many of the procedures and rights applicable to the NRC's contested hearing process due to the inherently adversarial nature of such proceedings are not available in the uncontested hearing. Participation in the NRC's contested hearing process is governed by 10 CFR 2.309 (for persons or entities, including U.S. States, local governments, Indian tribes, Canadian Provinces, local governments, or First Nations, seeking to file contentions of their own) and 10 CFR 2.315(c) (for interested U.S. States, local governments, Indian tribes, Canadian Provinces, local governments, or First Nations seeking to participate with respect to contentions filed by others). Participation in this uncontested hearing does not affect a U.S. State's, local government's, Indian tribe's, Canadian Province's, local government's, or First Nation's right to participate in the separate contested hearing process.
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 1st day of December, 2014.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Annette L. Vietti-Cook,</NAME>
                    <TITLE>Secretary of the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28610 Filed 12-5-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P  </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF SCIENCE AND TECHNOLOGY POLICY</AGENCY>
                <SUBAGY>National Science and Technology Council</SUBAGY>
                <SUBJECT>Notice of Public Meetings: Public Meetings of the National Science and Technology Council; Committee on Technology; Nanoscale Science, Engineering, and Technology Subcommittee; National Nanotechnology Coordination Office</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Nanotechnology Coordination Office (NNCO), on behalf of the Nanoscale Science, Engineering, and Technology (NSET) Subcommittee of the Committee on Technology, National Science and Technology Council (NSTC) and in collaboration with the European Commission, will hold the 2015 “EU-U.S.: Bridging NanoEHS Research Efforts” joint workshop on March 12-13, 2015, in Venice, Italy. The workshop will bring together the U.S.-EU Communities of Research (CORs), which serve as a platform for U.S. and EU scientists to share information on nanoEHS research. The six Communities were established in 2012 and are listed below. This workshop—the 4th since 2011—is intended to further develop and support the CORs' activities.</P>
                    <P>• Exposure through the Life Cycle, with Material Characterization.</P>
                    <P>• Ecotoxicity Testing and Predictive Models, with Material Characterization.</P>
                    <P>• Predictive Modeling for Human Health, with Material Characterization.</P>
                    <P>• Databases and Ontologies.</P>
                    <P>• Risk Assessment.</P>
                    <P>• Risk Management and Control.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Thursday, March 12, 2015, from 8:30 a.m. until 6:00 p.m. and Friday, March 13, 2015, from 8:30 a.m. until 3:30 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The workshop will be held at Ca' Foscari University of Venice at Dorsoduro 3689—30123 in Venice, Italy.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information regarding this Notice, please contact Stacey Standridge at National Nanotechnology Coordination Office, by telephone (703-292-8103) or email (
                        <E T="03">sstandridge@nnco.nano.gov</E>
                        ). Additional information about the workshop, including the agenda, is posted at 
                        <E T="03">http://us-eu.org/2015workshop/.</E>
                    </P>
                    <P>
                        <E T="03">Registration:</E>
                         Due to space limitations, pre-registration for the workshop is required. Registration is on a first-come, first-served basis and will be capped at approximately 100 participants. Registration will open on Thursday, December 4, 2014. Individuals planning to attend the workshop should register online at 
                        <E T="03">http://www.sun-fp7.eu/events/upcoming-events/eu-us-bridging-nanoehs-research-efforts-a-joint-workshop-2015/.</E>
                         Written notices of participation by email should be sent to 
                        <E T="03">sstandridge@nnco.nano.gov</E>
                         or mailed to Stacey Standridge, 4201 Wilson Blvd., Stafford II, Suite 405, Arlington, VA 22230. Written notices must be received by February 15, 2015, to be considered.
                    </P>
                    <P>
                        <E T="03">Meeting Accomodations:</E>
                         Individuals requiring special accommodation to access this public meeting should contact Stacey Standridge (telephone 703-292-8103) at least ten business days prior to the meeting so that appropriate arrangements can be made.
                    </P>
                    <SIG>
                        <NAME>Ted Wackler,</NAME>
                        <TITLE>Deputy Chief of Staff and Assistant Director.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28570 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3270-F5-P  </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="72218"/>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[SEC File No. 270-146, OMB Control No.3235-0134]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     U.S. Securities and Exchange Commission, Office of FOIA Services, Washington, DC 20549-2736.
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Rule 15c1-7.</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“Commission”) has submitted to the Office of Management and Budget (“OMB”) a request for approval of extension of the existing collection of information provided for in Rule 15c1-7 (17 CFR 240.15c1-7) under the Securities Exchange Act of 1934 (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ) (“Exchange Act”).
                </P>
                <P>Rule 15c1-7 states that any act of a broker-dealer designed to effect securities transactions with or for a customer account over which the broker-dealer (directly or through an agent or employee) has discretion will be considered a fraudulent, manipulative, or deceptive practice under the federal securities laws, unless a record is made of the transaction immediately by the broker-dealer. The record must include (a) the name of the customer, (b) the name, amount, and price of the security, and (c) the date and time when such transaction took place. The Commission estimates that 446 respondents collect information related to approximately 400,000 transactions annually under Rule 15c1-7 and that each respondent would spend approximately 5 minutes on the collection of information for each transaction, for approximately 33,333 aggregate hours per year (approximately 74.7 hours per respondent).</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.</P>
                <P>
                    The public may view the background documentation for this information collection at the following Web site: 
                    <E T="03">www.reginfo.gov.</E>
                     Comments should be directed to: (i) Desk Officer for the Securities and Exchange Commission, Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington, DC 20503 or by sending an email to: 
                    <E T="03">Shagufta_Ahmed@omb.eop.gov;</E>
                     and (ii) Pamela Dyson, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Remi Pavlik-Simon, 100 F Street NE., Washington, DC 20549, or by sending an email to 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                     Comments must be submitted within 30 days of this notice.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28550 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[SEC File No. 270-418, OMB Control No. 3235-0485]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     Securities and Exchange Commission, Office of FOIA Services, 100 F Street NE., Washington, DC 20549-2736.
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">Extension: </FP>
                    <FP SOURCE="FP1-2">Rule 15c2-1.</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“Commission”) has submitted to the Office of Management and Budget (“OMB”) a request for approval of extension of the previously approved collection of information provided for in Rule 15c2-1, (17 CFR 240.15c2-1), under the Securities Exchange Act of 1934 (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>Rule 15c2-1 (17 CFR 240.15c2-1) prohibits the commingling under the same lien of securities of margin customers (a) with other customers without their written consent and (b) with the broker or dealer. The rule also prohibits the re-hypothecation of customers' margin securities for a sum in excess of the customer's aggregate indebtedness. Pursuant to Rule 15c2-1, respondents must collect information necessary to prevent the re-hypothecation of customer securities in contravention of the rule, issue and retain copies of notices of hypothecation of customer securities in accordance with the rule, and collect written consents from customers in accordance with the rule. The information is necessary to ensure compliance with the rule and to advise customers of the rule's protections.</P>
                <P>
                    There are approximately 61 respondents (
                    <E T="03">i.e.,</E>
                     broker-dealers that conducted business with the public, filed Part II or Part IICSE of the FOCUS Report, did not claim an exemption from the Rule 15c3-3 reserve formula computation, and reported that they had a bank loan during at least one quarter of the current year) that require an aggregate total of 1,373 hours to comply with the rule. Each of these approximately 61 registered broker-dealers makes an estimated 45 annual responses. Each response takes approximately 0.5 hours to complete. Thus, the total compliance burden per year is 1,373 burden hours.
                </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.</P>
                <P>
                    The public may view background documentation for this information collection at the following Web site: 
                    <E T="03">www.reginfo.gov.</E>
                     Comments should be directed to: (i) Desk Officer for the Securities and Exchange Commission, Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington, DC 20503, or by sending an email to: 
                    <E T="03">Shagufta_Ahmed@omb.eop.gov;</E>
                     and (ii) Pamela Dyson, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Remi Pavlik-Simon, 100 F Street NE., Washington, DC 20549, or by sending an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                     Comments must be submitted to OMB within 30 days of this notice.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28551 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[SEC File No. 270-423, OMB Control No.3235-0472]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     U.S. Securities and Exchange Commission, Office of FOIA Services, Washington, DC 20549-2736.
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Rule 15c1-6.</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“Commission”) has submitted to the Office of Management and Budget (“OMB”) a request for approval of extension of the existing collection of information provided for in Rule 15c1-
                    <PRTPAGE P="72219"/>
                    6 (17 CFR 240.15c1-6) under the Securities Exchange Act of 1934 (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ) (Exchange Act).
                </P>
                <P>Rule 15c1-6 states that any broker-dealer trying to sell to or buy from a customer a security in a primary or secondary distribution in which the broker-dealer is participating or is otherwise financially interested must give the customer written notification of the broker-dealer's participation or interest at or before completion of the transaction. The Commission estimates that 446 respondents collect information annually under Rule 15c1-6 and that each respondent would spend approximately 10 hours annually complying with the collection of information requirement (approximately 4,460 hours in aggregate).</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.</P>
                <P>
                    Background documentation for this information collection may be viewed at the following Web site: 
                    <E T="03">www.reginfo.gov.</E>
                     Comments should be directed to: (i) Desk Officer for the Securities and Exchange Commission, Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington, DC 20503 or by sending an email to: 
                    <E T="03">Shagufta_Ahmed@omb.eop.gov;</E>
                     and (ii) Pamela Dyson, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Remi Pavlik-Simon, 100 F Street NE., Washington, DC 20549, or by sending an email to 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                     Comments must be submitted within 30 days of this notice.
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2014.</DATED>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28549 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P  </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73712; File No. SR-OPRA-2014-03]</DEPDOC>
                <SUBJECT>Options Price Reporting Authority; Order Approving an Amendment to the Plan for Reporting of Consolidated Options Last Sale Reports and Quotation Information To Amend OPRA's Definition of the term “Nonprofessional”</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On March 11, 2014, the Options Price Reporting Authority (“OPRA”) submitted to the Securities and Exchange Commission (“Commission”), pursuant to Section 11A of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 608 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     an amendment to the Plan for Reporting of Consolidated Options Last Sale Reports and Quotation Information (“OPRA Plan”).
                    <SU>3</SU>
                    <FTREF/>
                     The proposed OPRA Plan amendment would revise the definition of the term “Nonprofessional.” The proposed OPRA Plan amendment was published for comment in the 
                    <E T="04">Federal Register</E>
                     on August 18, 2014.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission received no comment letters in response to the Notice.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The OPRA Plan is a national market system plan approved by the Commission pursuant to Section 11A of the Act and Rule 608 thereunder. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 17638 (March 18, 1981), 22 SE.C. Docket 484 (March 31, 1981). The full text of the OPRA Plan is available at 
                        <E T="03">http://www.opradata.com.</E>
                         The OPRA Plan provides for the collection and dissemination of last sale and quotation information on options that are traded on the participant exchanges. The twelve participants to the OPRA Plan are BATS Exchange, Inc., BOX Options Exchange, LLC, Chicago Board Options Exchange, Incorporated, C2 Options Exchange, Incorporated, International Securities Exchange, LLC, Miami International Securities Exchange, LLC, NASDAQ OMX BX, Inc., NASDAQ OMX PHLX LLC, NASDAQ Stock Market LLC, NYSE MKT LLC, NYSE Arca, Inc., and Topaz Exchange, LLC (d/b/a ISE Gemini).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 72824 (August 12, 2014), 79 FR 48780 (“Notice”).
                    </P>
                </FTNT>
                <P>This order approves the proposed OPRA Plan amendment.</P>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    The purpose of the proposed amendment is to revise the definition of the term “Nonprofessional” as that term is used in the “Addendum for Nonprofessionals” that is attached to OPRA's Electronic Form of Subscriber Agreement and its Hardcopy Form of Subscriber Agreement.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         These two forms are Attachments B-1 and B-2 to OPRA's Form of Vendor Agreement and they are available on OPRA's Web site at 
                        <E T="03">www.opradata.com.</E>
                    </P>
                </FTNT>
                <P>Paragraph (c) of OPRA's current definition of the term “Nonprofessional” specifies that to qualify as a “Nonprofessional” a person must not be: “(i) registered or qualified with the Securities and Exchange Commission, the Commodities Futures Trading Commission, any state securities agency, any securities exchange/association, or any commodities/futures contract market/association, (ii) engaged as an “investment adviser,” as that term is defined in the Investment Advisers Act of 1940 (whether or not registered or qualified under that Act); or (iii) employed by a bank or other organization exempt from registration under Federal and/or state securities laws to perform functions that would require you to be so registered or qualified if you were to perform such functions for an organization not so exempt.” According to OPRA, a literal reading of this language could lead to the conclusion that a person who works outside of the United States as (for example) a securities broker could qualify as a “Nonprofessional,” because the person is not covered by clauses (i), (ii) or (iii) of Paragraph (c).</P>
                <P>
                    OPRA is not aware of any instances in which an OPRA Vendor has determined that Subscribers who work outside the United States qualify to be Nonprofessional Subscribers on the basis of reading the definition of the term “Nonprofessional” in this manner.
                    <SU>6</SU>
                    <FTREF/>
                     However, OPRA believes that it is appropriate to modify the language to prevent such a reading. Accordingly, OPRA proposes to modify the current definition by adding a phrase at the beginning of paragraph (c) to clarify that the current language applies to persons who work in the United States and adding a sentence to paragraph (c) to say that “For a natural person who works outside of the United States, a `Professional' is a natural person who performs the same functions as someone who would be considered a `Professional' in the United States.”
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         According to OPRA, the definition of the term “Nonprofessional Subscriber” used by the Consolidated Tape Association (“CTA”), which is substantively similar to OPRA's definition in almost all respects, prevents a similar reading of its definition.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion</HD>
                <P>
                    After careful review, the Commission finds that the proposed OPRA Plan amendment is consistent with the requirements of the Act and the rules and regulations thereunder.
                    <SU>7</SU>
                    <FTREF/>
                      
                    <PRTPAGE P="72220"/>
                    Specifically, the Commission finds that the proposed OPRA Plan amendment is consistent with Section 11A of the Act 
                    <SU>8</SU>
                    <FTREF/>
                     and Rule 608 thereunder 
                    <SU>9</SU>
                    <FTREF/>
                     in that it is appropriate in the public interest, for the protection of investors and the maintenance of fair and orderly markets, and to remove impediments to, and perfect the mechanisms of, a national market system. The proposed change to the definition of the term Nonprofessional is designed to clarify that the term is meant to apply to persons engaged in the same type of business whether they are located in the United States or elsewhere. The Commission believes that OPRA's proposal is consistent with Section 11A of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and Rule 608 thereunder 
                    <SU>11</SU>
                    <FTREF/>
                     because the proposal is designed to add clarity to OPRA's existing term and should therefore help to avoid investor confusion. In addition, the Commission notes that the proposed revisions to the term “Nonprofessional” will make the term used by OPRA consistent with the similar term used by CTA.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         In approving this proposed OPRA Plan Amendment, the Commission has considered its 
                        <PRTPAGE/>
                        impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 11A of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     and Rule 608 thereunder,
                    <SU>13</SU>
                    <FTREF/>
                     that the proposed OPRA Plan amendment (SR-OPRA-2014-03) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             17 CFR 200.30-3(a)(29).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28546 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73711; File No. SR-OPRA-2013-03]</DEPDOC>
                <SUBJECT>Options Price Reporting Authority; Order Approving an Amendment to the Plan for Reporting of Consolidated Options Last Sale Reports and Quotation Information To Amend Sections 5.4 and 7.1 of the OPRA Plan</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On October 21, 2013, the Options Price Reporting Authority (“OPRA”) submitted to the Securities and Exchange Commission (“Commission”), pursuant to Section 11A of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 608 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     an amendment to the Plan for Reporting of Consolidated Options Last Sale Reports and Quotation Information (“OPRA Plan”).
                    <SU>3</SU>
                    <FTREF/>
                     The proposed OPRA Plan amendment would modify Sections 5.4 and 7.1 of the OPRA Plan as they relate to operations of OPRA outside of OPRA's regular hours of operations.
                    <SU>4</SU>
                    <FTREF/>
                     The proposed OPRA Plan amendment was published for comment in the 
                    <E T="04">Federal Register</E>
                     on August 18, 2014.
                    <SU>5</SU>
                    <FTREF/>
                     The Commission received no comment letters in response to the Notice.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The OPRA Plan is a national market system plan approved by the Commission pursuant to Section 11A of the Act and Rule 608 thereunder. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 17638 (March 18, 1981), 22 SE.C. Docket 484 (March 31, 1981). The full text of the OPRA Plan is available at 
                        <E T="03">http://www.opradata.com.</E>
                         The OPRA Plan provides for the collection and dissemination of last sale and quotation information on options that are traded on the participant exchanges. The twelve participants to the OPRA Plan are BATS Exchange, Inc., BOX Options Exchange, LLC, Chicago Board Options Exchange, Incorporated, C2 Options Exchange, Incorporated, International Securities Exchange, LLC, Miami International Securities Exchange, LLC, NASDAQ OMX BX, Inc., NASDAQ OMX PHLX LLC, NASDAQ Stock Market LLC, NYSE MKT LLC, NYSE Arca, Inc., and Topaz Exchange, LLC (d/b/a ISE Gemini).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         OPRA's regular hours of operations are from 7:30 a.m. to 6:00 p.m. Eastern time. 
                        <E T="03">See</E>
                         Section 5.3 of the OPRA Plan.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 72820 (August 12, 2014), 79 FR 48779 (“Notice”).
                    </P>
                </FTNT>
                <P>This order approves the proposed OPRA Plan amendment.</P>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    The purpose of the proposed amendment is to (1) amend the OPRA Plan so that it provides for the aggregation of costs for operations of OPRA outside of its regular hours of operations (“after-hours operations”) with costs for operations of OPRA during its regular hours of operations (“regular-hours operations”); and (2) state expressly that OPRA may establish separate fees for access to OPRA data during periods of after-hours operations.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         OPRA does not currently operate outside of its regular hours of operations. However, according to OPRA, one of its member exchanges has indicated that it is planning to initiate after-hours trading and requested that OPRA operate during the after-hours period when its market will be open for trading. The current OPRA Plan provides that the OPRA System will operate outside of its regular hours of operation at the request of any one or more of its member exchanges. 
                        <E T="03">See</E>
                         Section 5.3 of the OPRA Plan. OPRA is not proposing any changes to Section 5.3 of the OPRA Plan.
                    </P>
                </FTNT>
                <P>
                    Currently, the OPRA Plan provides that the costs of OPRA's after-hour operations are to be allocated separately from the costs of OPRA's regular-hour operations and in a somewhat different manner. The OPRA Plan currently provides that the costs of OPRA's regular-hour operations below a specified ceiling 
                    <SU>7</SU>
                    <FTREF/>
                     and OPRA's revenues from regular-hour operations are both to be allocated among the OPRA member exchanges on the basis of the relative number of compared trades in options contracts traded on each of the OPRA member exchanges.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Clause 7.1(a)(iii)(2) of the OPRA Plan provides that costs above a “specified ceiling” are to be allocated in accordance with OPRA's Capacity Guidelines. The “ceiling” is described in Guideline 7 of the Capacity Guidelines. OPRA is not proposing any changes in the allocation of costs as described in the Capacity Guidelines.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Section 7.1 of the OPRA Plan.
                    </P>
                </FTNT>
                <P>The current provisions of the OPRA Plan state that, if the OPRA System operates outside of OPRA's regular hours, any costs attributable to such operation will be allocated to the exchange or exchanges that are actually operating during the after-hours period. The OPRA Plan does not make any special provision for the allocation of revenues derived from fees for access to OPRA data generated in the course of after-hours operations, and the OPRA Plan therefore provides that these revenues will be allocated among the OPRA member exchanges in the same way that revenues derived from regular-hours operations are allocated. The result is that the OPRA Plan currently provides for the allocation of costs of after-hours trading only to the exchange or exchanges that are actually operating during the after-hours period, but for the allocation of revenues resulting from fees for access to quotation and last sale information generated in the course of after-hours operations to all of the OPRA member exchanges on the basis of the relative number of compared trades in options contracts traded on each of the OPRA member exchanges in trading during both regular hours and outside of regular hours.</P>
                <P>OPRA is therefore proposing to revise the OPRA Plan to provide that the costs of after-hours operations will be aggregated with the costs of operating the OPRA System during regular hours of operation. As a result of the proposed change, the aggregated costs of operating the System during all hours of operation would be allocated among all of OPRA's member exchanges, regardless of whether any particular exchange operates its market outside of regular hours.</P>
                <P>
                    In addition, OPRA's Fee Schedule does not currently provide specific fees for access to OPRA data during periods 
                    <PRTPAGE P="72221"/>
                    of after-hours operations. Therefore, OPRA is proposing to add a sentence to Section 5.4(d) of the OPRA Plan to state expressly that it may establish such fees.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         OPRA is also proposing to make a non-substantive change to Section 5.4(d) of the OPRA Plan to reflect that the OPRA Fee Schedule is no longer identified as “Exhibit B” to the OPRA Plan but is publicly available on the OPRA Web site under the “Fees” tab.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion</HD>
                <P>
                    After careful review, the Commission finds that the proposed OPRA Plan amendment is consistent with the requirements of the Act and the rules and regulations thereunder.
                    <SU>10</SU>
                    <FTREF/>
                     Specifically, the Commission finds that the proposed OPRA Plan amendment is consistent with Section 11A of the Act 
                    <SU>11</SU>
                    <FTREF/>
                     and Rule 608 thereunder 
                    <SU>12</SU>
                    <FTREF/>
                     in that it is appropriate in the public interest, for the protection of investors and the maintenance of fair and orderly markets, and to remove impediments to, and perfect the mechanisms of, a national market system. OPRA believes that the proposed amendment will better align the provisions of the OPRA Plan relating to the allocation of costs of after-hours operations with the provisions of the OPRA Plan relating to the allocation of revenues derived from after-hours trading. The Commission believes that OPRA's proposal is consistent with Section 11A of the Act 
                    <SU>13</SU>
                    <FTREF/>
                     and Rule 608 thereunder.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         In approving this proposed OPRA Plan Amendment, the Commission has considered its impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 11A of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     and Rule 608 thereunder,
                    <SU>16</SU>
                    <FTREF/>
                     that the proposed OPRA Plan amendment (SR-OPRA-2013-03) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78k-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 242.608.
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             17 CFR 200.30-3(a)(29).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28545 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73705; File No. SR-NASDAQ-2014-118]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; The NASDAQ Stock Market LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Modify NASDAQ Rule 7001(c)</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on November 26, 2014, The NASDAQ Stock Market LLC (“NASDAQ” or the “Exchange”) filed with the Securities and Exchange Commission (“Commission”) a proposed rule change as described in Items I, II and III below, which Items have been prepared by the Exchange. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of the Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to modify NASDAQ Rule 7001(c) concerning market maker participant identifier 
                    <SU>3</SU>
                    <FTREF/>
                     (“MPID”) fees. The Exchange proposes to implement the proposed rule change on December 1, 2014.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         When applied to a market maker, sometimes referred to as a “maker participant identifier.”
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is available at 
                    <E T="03">nasdaq.cchwallstreet.com,</E>
                     at NASDAQ's principal office, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, NASDAQ included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>NASDAQ is proposing to amend the fees assessed under Rule 7001(c) for MPIDs. MPIDs are special numerical identifiers assigned to certain broker-dealers to identify the firms' transaction and quoting activity. NASDAQ administers the assignment of MPIDs, which may be requested by a broker-dealer for use on NASDAQ systems, reporting to Financial Industry Regulatory Authority (“FINRA”), or a combination of the two. NASDAQ member firms are provided with a Primary MPID upon gaining NASDAQ membership, but may also request additional MPIDs. These additional MPIDs are called Supplemental MPIDs and may be used by member firms to separate orders or quotes entered into the NASDAQ system for affiliates, segregated business units or trading desks, or sponsored access firms. Member firms also may use Supplemental MPIDs exclusively for reporting information to facilities of the FINRA, such as the FINRA/NASDAQ Trade Reporting Facility.</P>
                <P>
                    Under Rule 7001(c), NASDAQ provides a Primary MPID at no cost, and Supplemental MPIDs for a fee of $1,000 per month, per additional identifier. The Exchange also provides Supplemental MPIDs at no cost if they are used exclusively for reporting information to facilities of FINRA. The Exchange has not modified the fees assessed for MPIDs since adopting Rule 7001(c) in July 2010.
                    <SU>4</SU>
                    <FTREF/>
                     NASDAQ is proposing to eliminate the distinction between Primary and Supplemental MPIDs and assess a fee of $500 per month, per identifier. As is currently the case, NASDAQ will not assess a fee for MPIDs used exclusively for reporting to the facilities of FINRA. A consequence of the proposed change is that some member firms will experience an overall fee increase. Specifically, a member firm that currently has only one MPID (a “Primary MPID” under the current rule) would now have to pay $500 per month for the MPID under the proposed change, whereas that member firm pays nothing under the current rule. A member firm that has two MPIDs currently, none of which are [sic] used exclusively for reporting to the facilities of FINRA, would experience no change in the total monthly fee assessed for its 
                    <PRTPAGE P="72222"/>
                    MPIDs.
                    <SU>5</SU>
                    <FTREF/>
                     A member firm that has three or more MPIDs, none of which are [sic] used exclusively for reporting to the facilities of FINRA, would experience a fee reduction. The Exchange notes that its membership fees will continue to remain lower than the analogous fees assessed by the New York Stock Exchange for membership.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 62564 (July 23, 2010), 75 FR 44830 (July 29, 2010) (SR-NASDAQ-2010-089).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Such a member firm currently receives the Primary MPID at no cost and the Supplemental MPID at $1,000 per month. Under the proposed change, such a member firm would pay $500 per month for each of the MPIDs, totaling $1,000 per month.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange believes that the New York Stock Exchange (“NYSE”) Trading License Fee is analogous to membership fees of NASDAQ as they both provide access to the trading facilities of their respective exchanges. In this regard, NYSE assesses an annual fee of $40,000 for the first two licenses held by a member organization, and $25,000 for each additional license. 
                        <E T="03">See https://www.nyse.com/publicdocs/nyse/markets/nyse/NYSE_Price_List.pdf.</E>
                         By contrast, NASDAQ would assess the proposed monthly fee of $500 per MPID, an annual membership fee of $3,000, and a trading rights fee of $1,000 per month ($12,000 annually). 
                        <E T="03">See</E>
                         NASDAQ Rule 7001(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    NASDAQ believes that the proposed rule change is consistent with the provisions of Section 6 of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     in general, and with Sections 6(b)(4) and 6(b)(5) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     in particular, in that it provides for the equitable allocation of reasonable dues, fees and other charges among members and issuers and other persons using any facility or system which NASDAQ operates or controls, and is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b)(4) and (5).
                    </P>
                </FTNT>
                <P>
                    NASDAQ believes that the proposed simplification and uniform application of the fee assessed for MPIDs is an equitable allocation of a reasonable fee because it removes a distinction from the rule based on the number of MPIDs held and allocates a lower per MPID fee based strictly on the number of MPIDs subscribed. Although the proposed rule change reduces the per MPID fee assessed, it will result in a higher fee for some member firms that subscribe only to a Primary MPID currently. The Exchange believes that applying the proposed fee to all MPIDs subscribed that are used for Exchange trading activity allocates the fee more precisely with the benefit received. NASDAQ notes that it incurs the same cost in administering all MPIDs, including what is currently known as a Primary MPID. The Exchange believes that the proposed fee is reasonable because it lowers the fee to a level that more closely aligns the costs NASDAQ incurs in administering an individual MPID with the fee received. NASDAQ currently provides a Primary MPID at no cost, while Supplemental MPIDs not used exclusively for reporting to the facilities of FINRA are assessed a fee. NASDAQ had adopted the Supplemental MPID fees in an effort to help cover the costs of administering MPIDs and to also bring efficiency to their use by member firms.
                    <SU>9</SU>
                    <FTREF/>
                     When it adopted the Supplemental MPID fees, NASDAQ noted that it had observed that many member firms subscribed to multiple MPIDs through which very little activity occurred.
                    <SU>10</SU>
                    <FTREF/>
                     NASDAQ notes that the current fee structure has had the desired effect. Accordingly, NASDAQ now believes that reducing the per MPID fee, yet applying it to all MPIDs, is reasonable as it better aligns the fees assessed for MPIDs with the costs incurred by NASDAQ while also retaining an incentive to use MPIDs efficiently. NASDAQ anticipates that the proposed change will result in an overall increase in income received from MPID subscription fees. The Exchange believes that it is reasonable to adjust fees from time to time so that it can continue to make a profit on the products and services it offers. Ensuring that its products and services provide the Exchange with a profit allows it continue to offer and enhance such products and services, such as MPIDs. As noted above, the Exchange believes it is more equitable to allocate the fees on a per MPID basis because it better aligns the fees assessed with the costs incurred in offering MPIDs.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Supra</E>
                         note 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>NASDAQ also believes that the proposed rule change is not designed to permit unfair discrimination between member firms because the proposed fee will be assessed based on the number of MPIDs subscribed. The Exchange notes that all member firms will be assessed a fee for what is now considered a Primary MPID. As a consequence, member firms that currently subscribe only to a Primary MPID and have no Supplemental MPIDs or only Supplemental MPIDs used exclusively for reporting to the facilities of FINRA, will experience a fee increase. Other member firms, however, will either see no increase in fee [sic] or experience a fee reduction under the proposed change. NASDAQ believes that the proposed change is not unfairly discriminatory because all subscribing member firms will be assessed a fee for what is currently known as a Primary MPID. As noted above, all member firms derive benefit from each MPID used in transacting on NASDAQ, and NASDAQ is adjusting the fee to ensure that each subscribing member firm pays for the benefit received.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    NASDAQ does not believe that the proposed rule changes will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act, as amended.
                    <SU>11</SU>
                    <FTREF/>
                     NASDAQ does not believe that the proposed rule change places an unnecessary burden on competition because it more equitably applies the fee among subscribers. Specifically, the proposed change ties the fee directly to the number of MPIDs subscribed and eliminates the free Primary MPID. NASDAQ notes that, although all member firms will have to pay a fee for what is currently known as a Primary MPID and some member firms will experience a fee increase as a result of the proposed change, such a change is appropriate because it more closely aligns the subscription fee assessed for an MPID with the cost incurred by NASDAQ in administering it and ensures that offering the service is profitable to the Exchange. As discussed above, NASDAQ's membership fees remain lower than the analogous fees of the NYSE, and membership fees are subject to competition from other exchanges. Accordingly, if the changes proposed herein are unattractive to market participants, it is likely that NASDAQ will experience a decline in membership and/or order flow as a result.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>Written comments were neither solicited nor received.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing change has become effective pursuant to Section 19(b)(3)(A) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     and paragraph (f) 
                    <SU>13</SU>
                    <FTREF/>
                     of Rule 19b-4, thereunder. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 240.19b-4(f)
                    </P>
                </FTNT>
                <PRTPAGE P="72223"/>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov</E>
                    . Please include File Number SR-NASDAQ-2014-118 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Brent J. Fields, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-NASDAQ-2014-118. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549 on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of such filing also will be available for inspection and copying at the principal offices of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NASDAQ-2014-118, and should be submitted on or before December 26, 2014.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O' Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28534 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73706; File No. SR-NYSEArca-2014-89]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Order Instituting Proceedings To Determine Whether To Approve or Disapprove Proposed Rule Change Relating To Listing and Trading of Shares of Eight PIMCO Exchange-Traded Funds</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On August 15, 2014, NYSE Arca, Inc. (“NYSEArca” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act” or “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to list and trade shares of the following eight PIMCO exchange-traded funds, pursuant to NYSE Arca Equities Rule 8.600: PIMCO StocksPLUS® Absolute Return Exchange-Traded Fund (“StocksPLUS AR Fund”), PIMCO Small Cap StocksPLUS® AR Strategy Exchange-Traded Fund (“Small Cap StocksPLUS AR Fund”), PIMCO Fundamental IndexPLUS® AR Exchange-Traded Fund (“Fundamental IndexPLUS Fund”), PIMCO Small Company Fundamental IndexPLUS® AR Strategy Exchange-Traded Fund (“Small Company Fundamental IndexPLUS Fund”), PIMCO EM Fundamental IndexPLUS® AR Strategy Exchange-Traded Fund (“EM Fundamental IndexPLUS Fund”), PIMCO International Fundamental IndexPLUS® AR Strategy Exchange-Traded Fund (“International Fundamental IndexPLUS Fund”), PIMCO EM StocksPLUS® AR Strategy Exchange-Traded Fund (“EM StocksPLUS Fund”), and PIMCO International StocksPLUS® AR Strategy Exchange-Traded Fund (Unhedged) (“International StocksPLUS Fund”) (each a “Fund” and collectively the “Funds.”). The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on September 3, 2014.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. On October 15, 2014, pursuant to Section 19(b)(2) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to either approve the proposed rule change, disapprove the proposed rule change, or institute proceedings to determine whether to disapprove the proposed rule change.
                    <SU>5</SU>
                    <FTREF/>
                     This order institutes proceedings under Section 19(b)(2)(B) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     to determine whether to approve or disapprove the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 72937 (Aug. 27, 2014), 79 FR 52385 (“Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 73364, 79 FR 62988 (Oct. 21, 2014). The Commission determined that it was appropriate to designate a longer period within which to take action on the proposed rule change so that it has sufficient time to consider the proposed rule change. Accordingly, the Commission designated December 2, 2014 as the date by which it should approve, disapprove, or institute proceedings to determine whether to disapprove the proposed rule change.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    The Exchange proposes to list and trade shares (“Shares”) of the Funds under NYSE Arca Equities Rule 8.600, which governs the listing and trading of Managed Fund Shares.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         A Managed Fund Share is a security that represents an interest in an investment company registered under the Investment Company Act of 1940 (15 U.S.C. 80a-1) (“1940 Act”) organized as an open-end investment company or similar entity that invests in a portfolio of securities selected by its investment adviser consistent with its investment objectives and policies. In contrast, an open-end investment company that issues Investment Company Units, listed and traded on the Exchange under NYSE Arca Equities Rule 5.2(j)(3), seeks to provide investment results that correspond generally to the price and yield performance of a specific foreign or domestic stock index, fixed income securities index or combination thereof.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">
                    A. Characteristics and Holdings of the Funds 
                    <SU>8</SU>
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Additional information regarding the Shares and the Funds, including investment strategy, risks, creation and redemption procedures, portfolio holdings, and investment restrictions, is included in the Notice, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. Investment Objective and Principal Holdings</HD>
                <P>
                    Each Fund would seek total return that exceeds the total return of its equity securities index benchmark, and under normal circumstances would seek to achieve its investment objective by investing in derivatives overlying its benchmark and a portfolio of Fixed Income Instruments (defined below), which would be managed using an absolute return approach. Typically, the Funds would use derivative instruments as a substitute for taking a position in 
                    <PRTPAGE P="72224"/>
                    the underlying asset 
                    <SU>9</SU>
                    <FTREF/>
                     or as part of a strategy designed to reduce exposure to other risks. The Funds may also use derivative instruments to enhance returns.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The Exchange states that derivatives may be purchased with a small fraction of the assets that would be needed to purchase the benchmark index securities directly, so that the remainder of the Funds' assets may be invested in Fixed Income Instruments. Accordingly, the Funds generally would not invest directly in benchmark index component stocks, but the Exchange states that the Funds may invest in stocks and exchange-traded funds.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that “Fixed Income Instruments” may include: Securities issued or guaranteed by the U.S. Government, its agencies, or government-sponsored enterprises (“U.S. Government Securities”); corporate debt securities of U.S. and non-U.S. issuers, including convertible securities and corporate commercial paper; mortgage-backed and other asset-backed securities; inflation-indexed bonds issued both by governments and corporations; structured notes, including hybrid or “indexed” securities, and event-linked bonds; 
                    <SU>10</SU>
                    <FTREF/>
                     bank capital and trust preferred securities; loan participations and assignments; 
                    <SU>11</SU>
                    <FTREF/>
                     delayed funding loans and revolving credit facilities; bank certificates of deposit, fixed time deposits and bankers' acceptances; repurchase agreements on Fixed Income Instruments and reverse repurchase agreements on Fixed Income Instruments; debt securities issued by states or local governments and their agencies, authorities and other government-sponsored enterprises; obligations of non-U.S. governments or their subdivisions, agencies, and government-sponsored enterprises; and obligations of international agencies or supranational entities. The Exchange also states that derivative instruments may include the following: Forwards; exchange-traded and over-the-counter (“OTC”) options contracts; exchange-traded futures contracts; exchange-traded and OTC swap agreements; exchange-traded and OTC options on futures contracts; and OTC options on swap agreements.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The Exchange states that such investments will constitute only up to 20% of a Fund's total assets.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The Exchange states that such investments will constitute only up to 20% of a Fund's total assets.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         According to the Exchange, all investment guidelines and limitations will apply to a Fund's aggregate investment exposure to a particular type of investment that is the subject of the guideline or limitation, whether such exposure is obtained through direct holdings or through derivative instruments. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, at 52387.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Other Investments</HD>
                <P>The Funds may invest in securities and instruments that are economically tied to foreign (non-U.S.) countries. The Funds may invest in securities denominated in foreign (non-U.S.) currencies and in U.S. dollar-denominated securities of foreign (non-U.S.) issuers, subject to applicable limitations set forth in the Notice. With respect to the Funds' absolute return investments, each Fund will normally limit its foreign currency exposure (from non-U.S. dollar-denominated securities or currencies) to 20% of its total assets. With respect to the Funds' absolute return investments, each Fund may invest up to 25% of its total assets in securities and instruments that are economically tied to emerging market countries.</P>
                <P>The Funds may engage in foreign currency transactions on a spot (cash) basis or forward basis, and they may invest in foreign currency futures contracts and options contracts. The Funds may enter into these contracts to hedge against foreign exchange risk, to increase exposure to a foreign currency, or to shift exposure to foreign currency fluctuations from one currency to another. Suitable hedging transactions may not be available in all circumstances and there can be no assurance that the Funds will engage in such transactions at any given time or from time to time.</P>
                <P>The Funds may, without limitation, seek to obtain market exposure to the securities in which they primarily invest by entering into a series of purchase and sale contracts. The Funds may purchase or sell securities on a when-issued, delayed delivery or forward commitment basis and may engage in short sales.</P>
                <HD SOURCE="HD3">3. Additional Investment Limits</HD>
                <P>According to the Exchange, each of the Funds may invest up to 10% of its total assets in preferred stocks, convertible securities, and other equity-related securities. Each Fund may invest up to 20% of its total assets in: (i) Variable and floating rate securities that are not Fixed Income Instruments; (ii) floaters and inverse floaters that are not Fixed Income Instruments; (iii) trade claims, privately placed and unregistered securities, exchange-traded and OTC-traded structured products, including credit-linked securities and commodity-linked notes; (iv) Brady Bonds; and (v) bank loans.</P>
                <P>Each Fund may, with up to 20% of its total assets, enter into repurchase agreements on instruments other than Fixed Income Instruments. Each Fund may also, with up to 20% of its total assets, enter into reverse repurchase agreements on instruments other than Fixed Income Instruments, subject to the Fund's limitations on borrowings.</P>
                <P>Each Fund may invest up to 20% of its total assets in “high yield securities” or unrated securities determined by PIMCO to be of comparable quality (except that within such limitation, the Fund may invest in mortgage-related securities rated below B).</P>
                <P>Each Fund may invest up to 20% of its assets in mortgage-related and other asset-backed securities, although this 20% limitation does not apply to securities issued or guaranteed by Federal agencies and/or U.S. government sponsored instrumentalities.</P>
                <HD SOURCE="HD1">III. Proceedings To Determine Whether To Approve or Disapprove the Proposed Rule Change and Grounds for Disapproval Under Consideration</HD>
                <P>
                    The Commission is instituting proceedings pursuant to Section 19(b)(2)(B) of the Act 
                    <SU>13</SU>
                    <FTREF/>
                     to determine whether the proposed rule change should be approved or disapproved. Institution of such proceedings is appropriate at this time in view of the legal and policy issues raised by the proposed rule change, as discussed below. Institution of proceedings does not indicate that the Commission has reached any conclusions with respect to any of the issues involved. Rather, as described below, the Commission seeks and encourages interested persons to provide comment on the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <P>
                    Pursuant to Section 19(b)(2)(B) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     the Commission is providing notice of the grounds for disapproval under consideration. The Commission is instituting proceedings to allow for additional analysis of, and input from commenters with respect to, the proposed rule change's consistency with Section 6(b)(5) of the Exchange Act, which requires, among other things, that the rules of a national securities exchange be “designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade,” and “to protect investors and the public interest.” 
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Procedure: Request for Written Comments</HD>
                <P>
                    The Commission requests that interested persons provide written submissions of their views, data, and arguments with respect to the concerns identified above, as well as any other concerns they may have with the proposal. In particular, the Commission 
                    <PRTPAGE P="72225"/>
                    invites the written views of interested persons concerning (1) the transparency and liquidity of the markets for the assets in which each Fund would be permitted to invest a substantial portion of its portfolio and (2) the expected effectiveness and efficiency of arbitrage with respect to the market price of the Funds' shares and the value of the underlying portfolio assets, given the transparency and liquidity of the markets for those underlying assets.
                </P>
                <P>
                    Although there do not appear to be any issues relevant to approval or disapproval which would be facilitated by an oral presentation of views, data, and arguments, the Commission will consider, pursuant to Rule 19b-4, any request for an opportunity to make an oral presentation.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Section 19(b)(2) of the Act, as amended by the Securities Act Amendments of 1975, Pub. L. 94-29 (June 4, 1975), grants the Commission flexibility to determine what type of proceeding—either oral or notice and opportunity for written comments—is appropriate for consideration of a particular proposal by a self-regulatory organization. 
                        <E T="03">See</E>
                         Securities Act Amendments of 1975, Senate Comm. on Banking, Housing &amp; Urban Affairs, S. Rep. No. 75, 94th Cong., 1st Sess. 30 (1975).
                    </P>
                </FTNT>
                <P>Interested persons are invited to submit written data, views, and arguments regarding whether the proposal should be approved or disapproved by December 26, 2014. Any person who wishes to file a rebuttal to any other person's submission must file that rebuttal by January 9, 2015.</P>
                <P>Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NYSEArca-2014-89 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Numbers SR-NYSEArca-2014-89. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of such filings also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NYSEArca-2014-89 and should be submitted on or before December 26, 2014. Rebuttal comments should be submitted by January 9, 2015.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             17 CFR 200.30-3(a)(57).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28547 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73710; File No. SR-OCC-2014-805]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; The Options Clearing Corporation; Notice of Withdrawal of an Advance Notice Concerning Enhancements to the Risk Management Framework Applied to the Clearance of Confirmed Trades Executed in Extended and Overnight Trading Sessions</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>
                    On September 17, 2014, The Options Clearing Corporation (“OCC”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 806(e)(1) of the Payment, Clearing, and Settlement Supervision Act of 2010 (“Clearing Supervision Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4(n)(1)(i),
                    <SU>2</SU>
                    <FTREF/>
                     an advance notice concerning enhancements to the risk management framework applied to the clearance of confirmed trades executed in extended and overnight trading sessions. Notice of the advance notice was published in the 
                    <E T="04">Federal Register</E>
                     on October 20, 2014.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission did not receive any comments in response to the advance notice.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         12 U.S.C. 5465(e)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4(n)(1)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 73343 (October 14, 2014), 79 FR 62684 (October 20, 2014) (SR-OCC-2014-805).
                    </P>
                </FTNT>
                <P>On October 28, 2014, OCC filed a withdrawal of its advance notice (SR-OCC-2014-805) from consideration by the Commission. The Commission is hereby publishing notice of the withdrawal.</P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28544 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73708; File No. SR-MSRB-2014-08]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Municipal Securities Rulemaking Board; Notice of Filing of a Proposed Rule Change Consisting of Proposed Amendments to MSRB Rules G-1, on Separately Identifiable Department or Division of a Bank; G-2, on Standards of Professional Qualification; G-3, on Professional Qualification Requirements; and D-13, on Municipal Advisory Activities</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on November 18, 2014, the Municipal Securities Rulemaking Board (the “MSRB” or “Board”) filed with the Securities and Exchange Commission (the “SEC” or “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the MSRB. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The MSRB filed with the Commission a proposed rule change consisting of proposed amendments to MSRB Rules G-1, on separately identifiable department or division of a bank; G-2, on standards of professional qualification; G-3, on professional qualification requirements; and D-13, on municipal advisory activities (the “proposed rule change”). The MSRB is 
                    <PRTPAGE P="72226"/>
                    proposing that these amendments become effective 60 days following the date of SEC approval.
                </P>
                <P>
                    The text of the proposed rule change is available on the MSRB's Web site at 
                    <E T="03">www.msrb.org/Rules-and-Interpretations/SEC-Filings/2014-Filings.aspx,</E>
                     at the MSRB's principal office, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the MSRB included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The MSRB has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <HD SOURCE="HD3">Description of the Proposed Rule Change</HD>
                <P>
                    The purpose of the proposed rule change is to establish professional qualification requirements for municipal advisors and their associated persons and to make related changes to select MSRB rules. The MSRB is charged with setting professional standards and continuing education requirements for municipal advisors. Specifically, the Act requires associated persons of brokers, dealers and municipal securities dealers (“dealers”) and municipal advisors to pass examinations as the MSRB may establish to demonstrate that such individuals meet the standards of competence as the MSRB finds necessary or appropriate in the public interest or for the protection of investors and municipal entities or obligated persons.
                    <SU>3</SU>
                    <FTREF/>
                     A professional qualification examination is intended to determine whether an individual meets the MSRB's basic qualification standards for a particular registration category. The examination measures a candidate's knowledge of the business activities, as well as the regulatory requirements, including MSRB rules, rule interpretations and federal law applicable to a particular registration category.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(A) of the Act, 15 U.S.C. 78o-4(b)(2)(A).
                    </P>
                </FTNT>
                <P>
                    MSRB Rule G-3 establishes classifications and qualification requirements for associated persons of dealers. The proposed rule change would add the following two new registration classifications for municipal advisors under Rule G-3: (a) Municipal advisor representatives—those individuals who engage in municipal advisory activities; and (b) municipal advisor principals—those individuals who engage in the management, direction or supervision of the municipal advisory activities of the municipal advisor and its associated persons.
                    <SU>4</SU>
                    <FTREF/>
                     The proposed amendments also would require each prospective municipal advisor representative to take and pass the municipal advisor representative qualification examination being developed by the MSRB prior to being qualified as a municipal advisor representative. Qualification as a municipal advisor representative would be a prerequisite to qualification as a municipal advisor principal. Each municipal advisor would be required to designate at least one individual as a municipal advisor principal who would be responsible for supervising the municipal advisory activities of the municipal advisor, and each municipal advisor principal would be required to pass the municipal advisor representative qualification examination to perform the supervisory activities of a principal.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The definition of municipal advisor representative would be substantially identical to the category of individuals for whom a Form MA-I is required to be completed as part of a municipal advisor's registration with the SEC—natural persons associated with the municipal advisor engaged in municipal advisory activities on behalf of the firm.
                    </P>
                </FTNT>
                <P>To provide prospective municipal advisor representatives with sufficient time to prepare for and take the examination, the MSRB proposes a one-year grace period for test takers to pass the examination. In addition, given the general view of industry participants that the 90-day apprenticeship requirement for municipal securities representatives in Rule G-3 does not provide any additional benefit, the MSRB proposes to eliminate the requirement for municipal securities representatives and, similarly, does not propose an apprenticeship requirement for municipal advisor representatives.</P>
                <P>MSRB Rule G-2 establishes the standards of professional qualification for dealers and currently provides that no dealer shall engage in municipal securities activities unless such dealer and every natural person associated with such dealer is qualified in accordance with MSRB rules. The proposed rule change amends Rule G-2 to add a basic requirement that no municipal advisor shall engage in municipal advisory activities unless such municipal advisor and every natural person associated with such municipal advisor is qualified in accordance with MSRB rules.</P>
                <P>
                    The proposed rule change would also amend Rule D-13, on municipal advisory activities, to incorporate SEC rules by providing that the term “municipal advisory activities” means, except as otherwise specifically provided by rule of the Board, the activities described in Section 15B(e)(4)(A)(i) and (ii) of the Act 
                    <SU>5</SU>
                    <FTREF/>
                     and the rules and regulations promulgated thereunder. In recognition of the new regulatory scheme for municipal advisors, the proposed rule change would amend Rules G-1 and G-3 to provide that dealers and their municipal securities representatives may continue to perform financial advisory or consultative services for issuers in connection with the issuance of municipal securities, except to the extent the municipal securities representatives engaged in the activities must be qualified as municipal advisor representatives to perform such services. Finally, Rule G-1 also would be amended to provide that, for purposes of its municipal advisory activities, the term “separately identifiable department or division of a bank” would have the same meaning as in Securities Exchange Act Rule 15Ba1-1(d)(4).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Section 15B(e)(4)(A)(i) and (ii) of the Act, 15 U.S.C. 78o-4(e)(4)(A)(i) and (ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         17 CFR 240.15Ba1-1(d)(4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">New Registration Classifications</HD>
                <P>
                    The proposed amendments to Rule G-3 would create two new registration classifications: (a) Municipal advisor representative and (b) municipal advisor principal. These classifications are consistent with other regulatory schemes, including those for broker-dealers.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Examples of these other schemes include the following classifications: Series 7 (General Securities Representative) and Series 24 (General Securities Principal); Series 42 (Registered Options Representative) and Series 4 (Registered Options Principal); Series 22 (Direct Participation Programs Limited Representative) and Series 39 (Direct Participation Programs Limited Principal).
                    </P>
                </FTNT>
                <P>
                    The new classifications would distinguish between municipal advisor representatives who would be qualified to engage in municipal advisory activities and municipal advisor principals who would be qualified to engage in and supervise the municipal advisory activities of the municipal 
                    <PRTPAGE P="72227"/>
                    advisor and its associated persons. The proposed amendments to Rule G-3 would define a municipal advisor representative as a natural person associated with a municipal advisor, other than a person performing only clerical, administrative, support or similar functions.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Rule D-13 defines municipal advisory activities as the activities described in Section 15B(e)(4)(A)(i) and (ii) of the Act. Rule D-13 would be amended to reflect the SEC's interpretation of the statutory definition of municipal advisor. Hence, “municipal advisory activities” would mean the activities described in Section 15B(e)(4)(A)(i) and (ii) of the Act and the rules and regulations promulgated thereunder.
                    </P>
                </FTNT>
                <P>
                    The proposed amendments would define a municipal advisor principal as a natural person associated with a municipal advisor who is directly engaged in the management, direction or supervision of the municipal advisory activities, as defined in Rule D-13, of the municipal advisor. In addition, the proposed amendments to Rule G-3 would require each municipal advisor to designate at least one municipal advisor principal to be responsible for the municipal advisory activities of the municipal advisor.
                    <SU>9</SU>
                    <FTREF/>
                     Further, the proposed rule change would require each municipal advisor representative and municipal advisor principal to take and pass the municipal advisor representative qualification examination prior to being qualified as a municipal advisor representative or municipal advisor principal, respectively. The examination is discussed in more detail below.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         MSRB Rule G-44 sets forth the obligation of municipal advisors to supervise the municipal advisory activities of the municipal advisor and its associated persons to ensure compliance with applicable MSRB and SEC rules. Exchange Act Release No. 73415 (Oct. 23, 2014), 79 FR 64423 (Oct. 29, 2014), File No. SR-MSRB-2014-06, available at 
                        <E T="03">http://www.sec.gov/rules/sro/msrb/2014/34-73415.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Grace Period</HD>
                <P>
                    To provide for an orderly transition to the new professional qualification requirements for municipal advisors, the MSRB proposes that prospective municipal advisor representatives have one year from the effective date of the examination to pass it.
                    <SU>10</SU>
                    <FTREF/>
                     During this grace period, municipal advisor professionals could continue to engage in municipal advisory activities. The grace period is intended to provide municipal advisor representatives with sufficient time to study and take (and, if necessary retake) the examination without causing undue disruption to the business of the municipal advisor. As is the case for all MSRB qualification examinations, individuals who do not pass the examination would be permitted to retake the examination after 30 days. However, any person who fails the examination three or more times in succession would be prohibited from taking the examination for six months.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The MSRB will announce the effective date of the municipal advisor representative qualification examination at a later date.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         MSRB Rule G-3(f), proposed MSRB Rule G-3(g) in Exhibit 5.
                    </P>
                </FTNT>
                <P>Prior to the effective date of the examination and prior to the commencement of the one-year grace period, the MSRB will file a study outline describing the topics on the examination, the percentage of the examination devoted to the topic areas, and the number of questions on the examination. The study outline will also contain reference material and sample examination questions to assist examination takers. The MSRB expects that it will provide more information about the study outline through a webinar or other means, subsequent to the filing of the study outline with the SEC. A pilot examination is expected to be delivered in 2015. The MSRB will use the results of the pilot examination to set the passing grade, which will be added to the study outline.</P>
                <HD SOURCE="HD3">Uniform Requirement—Grandfathering</HD>
                <P>The proposed rule change would require that all persons deemed municipal advisor representatives under Rule G-3 pass the qualification examination, regardless of whether such persons have passed other MSRB or MSRB-recognized examinations (such as the Series 52 or 7 examinations), or previously have been engaged in municipal advisory activities. While commenters requested, as discussed below, that the MSRB waive the requirement or “grandfather” those individuals who have passed certain other professional qualifications examinations or have experience in providing municipal advisory services, the MSRB believes that the significant changes that accompany the new regulatory regime for municipal advisors dictate that each individual engaged in municipal advisory activities demonstrate a minimum level of knowledge of the job responsibilities and regulatory requirements by passing a general qualification examination.</P>
                <P>
                    The MSRB has considered this issue carefully and has determined that the practice of grandfathering will not effectively ensure a minimum level of competency by those individuals acting as municipal advisor representatives. For example, the MSRB has no practical means to determine whether an individual is competent based on experience. The MSRB believes that Congress, through the Act, requires more than reliance on a representation of competence.
                    <SU>12</SU>
                    <FTREF/>
                     As for those who suggest they have demonstrated a basic competence by passing another qualification examination, the MSRB believes the job responsibilities of a municipal advisor professional and the regulations governing such individuals are sufficiently distinct in application as to require that they pass a separate examination.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release No. 70462 at 6 (Sept. 20, 2013), 78 FR 67467 at 67469 (Nov. 12, 2013) (“SEC Final Registration Rule”) and Section 15B(b)(2)(A) of the Act, 15 U.S.C. 78o-4(b)(2)(A).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Waivers</HD>
                <P>The Board will consider waiving the requirement that a municipal advisor representative or municipal advisor principal pass the municipal advisor representative qualification examination in extraordinary cases: (1) Where the applicant participated in the development of the municipal advisor representative qualification examination as a member of the Board's Professional Qualifications Advisory Committee (PQAC); or (2) where good cause is shown by an applicant who previously qualified as a municipal advisor representative by passing the municipal advisor representative qualification examination and such qualification lapsed. The Board will review each waiver request on its individual merits, taking into consideration relevant facts presented by the applicant. For example, the Board may consider granting a waiver for an individual whose municipal advisor representative qualification lapsed but who demonstrated subsequent investment industry or related professional experience.</P>
                <HD SOURCE="HD3">Apprenticeship</HD>
                <P>
                    MSRB Rule G-3 currently requires a municipal securities representative to serve an apprenticeship period of 90 days before transacting business with any member of the public or receiving compensation for such activities. The intent of the provision was to ensure that persons with no prior experience in the securities industry would learn from an experienced professional before conducting business with the public. Regulated entities have provided feedback that the requirement does not provide any additional benefit because the 90-day training period is short and the rule provides no specific training requirements. Moreover, the SEC approved a similar rule change by Financial Industry Regulatory Authority 
                    <PRTPAGE P="72228"/>
                    (FINRA) in eliminating the apprenticeship requirement established under prior New York Stock Exchange (NYSE) Rule 345 for certain registered persons, noting that the change would permit its member firms to determine, consistent with their supervisory obligations, the extent and duration of the initial training of such registered persons.
                    <SU>13</SU>
                    <FTREF/>
                     The MSRB believes that dealers and municipal advisors should determine the length and nature of the initial training for newly registered persons, consistent with the approach taken by FINRA. Consequently, the MSRB proposes to eliminate the apprenticeship requirement for municipal securities representatives and proposes no such requirement for municipal advisor representatives.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         FINRA Regulatory Notice 08-64 (Oct. 2008). Exchange Act Release No. 58103 (Jul. 3, 2008), 73 FR 40403 (Jul. 14, 2008), File No. SR-FINRA-2008-036.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Technical Amendments</HD>
                <P>The MSRB is amending Rule G-3(a)(ii) to correctly re-letter G-3(a)(ii)(D) as G-3(a)(ii)(C).</P>
                <HD SOURCE="HD3">Effective Date</HD>
                <P>The MSRB is proposing that these amendments become effective 60 days following the date of SEC approval. The effective date and the compliance date of the municipal advisor representative qualification examination will be announced by the MSRB with at least 30 days notice. The one-year grace period will extend from the effective date to the compliance date.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The MSRB believes that the proposed rule change is consistent with Section 15B(b)(2)(A) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     which provides that the MSRB's rules shall:
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(A) of the Act, 15 U.S.C. 78o-4(b)(2)(A).
                    </P>
                </FTNT>
                <EXTRACT>
                    <FP>provide that no municipal securities broker or municipal securities dealer shall effect any transaction in, or induce or attempt to induce the purchase or sale of, any municipal security, and no broker, dealer, municipal securities dealer, or municipal advisor shall provide advice to or on behalf of a municipal entity or obligated person with respect to municipal financial products or the issuance of municipal securities, unless . . . such municipal securities broker or municipal securities dealer and every natural person associated with such municipal securities broker or municipal securities dealer meet such standards of training, experience, competence, and such other qualifications as the Board finds necessary or appropriate in the public interest or for the protection of investors and municipal entities or obligated persons.</FP>
                </EXTRACT>
                <P>This provision provides the MSRB with authority to establish standards of competence as the MSRB finds necessary to carry out its regulatory duties. It also provides that, in connection with the definition and application of such standards, the MSRB may appropriately classify municipal advisors and their associated persons, specify that all or any portion of such standards shall be applicable to any such class, and require persons in any such class to pass an examination regarding such standards of competence.</P>
                <P>Professional qualification examinations are an established means for determining the basic competency of individuals in a particular class. The proposed rule change would require individuals who engage in or supervise municipal advisory activities to pass such an examination. The MSRB believes that requiring prospective municipal advisor representatives to pass a basic qualification examination will protect investors, municipal entities and obligated persons by ensuring such representatives have a basic understanding of the role of a municipal advisor representative and the rules and regulations governing such individuals.</P>
                <P>
                    In its final rule on the permanent registration of municipal advisors, the SEC noted that “[t]he new registration requirements and regulatory standards are intended to mitigate some of the problems observed with the conduct of some municipal advisors, including . . . advice rendered by financial advisors without adequate training or qualifications. ” 
                    <SU>15</SU>
                    <FTREF/>
                     The municipal advisor representative qualification examination is consistent with the intent to mitigate problems associated with advice provided by those individuals without adequate training or qualifications.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         78 FR 67467 at 67469 (Nov. 12, 2013).
                    </P>
                </FTNT>
                <P>
                    Additionally, the MSRB believes that the proposed rule change is consistent with Section 15B(b)(2)(L)(iii) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     which provides that the MSRB's rules shall, with respect to municipal advisors, provide professional standards. The proposed rule change would establish professional standards for those individuals engaged in or supervising municipal advisory activities by requiring such individuals to demonstrate a basic competency regarding the role of municipal advisor representatives and the rules and regulations governing the conduct of such persons.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(L)(iii) of the Act, 15 U.S.C. 78o-4(b)(2)(L)(iii).
                    </P>
                </FTNT>
                <P>
                    Section 15B(b)(2)(L)(iv) of the Act 
                    <SU>17</SU>
                    <FTREF/>
                     requires that rules adopted by the Board not impose a regulatory burden on small municipal advisors that is not necessary or appropriate in the public interest and for the protection of investors, municipal entities, and obligated persons, provided that there is robust protection of investors against fraud. The MSRB believes that the proposed rule change is consistent with this provision. While the proposed rule change would affect all municipal advisors, including small municipal advisors, it would be a necessary and appropriate regulatory burden in order to establish the baseline competence of those individuals engaged in municipal advisory activities, and it also would promote compliance with MSRB rules. While there will be one-time costs associated with preparing for and taking the municipal advisor representative qualification examination, the MSRB does not believe that such costs will impose a regulatory burden on small municipal advisors that is not necessary or appropriate to protect investors, municipal entities and obligated persons. A discussion of the economic analysis of the proposed rule change and its impact on small municipal advisors is provided below.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(L)(iv) of the Act, 15 U.S.C. 78o-4(b)(2)(L)(iv).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    Section 15B(b)(2)(C) of the Act 
                    <SU>18</SU>
                    <FTREF/>
                     requires that MSRB rules not be designed to impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act. In determining whether this standard has been met, the MSRB has been guided by the Board's recently-adopted policy to more formally integrate economic analysis into the rulemaking process. In accordance with this policy the Board has evaluated the potential impacts of the proposed rule change, including in comparison to reasonable alternative regulatory approaches.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(C) of the Act, 15 U.S.C. 78o-4(b)(2)(C).
                    </P>
                </FTNT>
                <P>
                    The MSRB does not believe that the proposed rule change would impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act, in so far as the proposed rule change merely establishes baseline professional qualification standards for all municipal advisors. The baseline standard would provide the MSRB assurance that individuals 
                    <PRTPAGE P="72229"/>
                    who take and pass the municipal advisor representative qualification examination demonstrate a basic knowledge of the role of a municipal advisor representative and the rules and regulations governing the conduct of individuals engaging in municipal advisory activities. The MSRB has considered whether it is possible that the costs associated with preparing for and taking the municipal advisor representative qualification examination, relative to the baseline of no professional qualification examination, may affect the competitive landscape by leading some municipal advisors to exit the market, curtail their activities or consolidate with other firms. For example, some municipal advisors may determine to consolidate with other municipal advisors in order to benefit from economies of scale (
                    <E T="03">e.g.,</E>
                     by leveraging existing resources of a larger firm to prepare candidates to take the qualification examination) rather than to incur separately the costs associated with the proposed rule change. Others may exit the market, rather than incurring the cost of preparing for and taking a qualification examination.
                </P>
                <P>
                    In the SEC Final Registration Rule, the SEC recognized that municipal advisors would incur programmatic costs, including “costs to meet standards of training, experience, competence, and other qualifications, as well as continuing education requirements, that the MSRB may establish in the future.” 
                    <SU>19</SU>
                    <FTREF/>
                     Such exits from the market may lead to a reduced pool of municipal advisors. However, the SEC also noted that the market for municipal advisory services is likely to remain competitive despite the potential exit of some municipal advisors (including small entity municipal advisors), consolidation of municipal advisors, or lack of new entrants into the market.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         78 FR 67467 at 67611 (Nov. 12, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         78 FR 67467 at 67630 (Nov. 12, 2013).
                    </P>
                </FTNT>
                <P>It is also possible that competition for municipal advisory services can be affected by whether incremental costs associated with the municipal advisor representative qualification examination are passed on to advisory clients. The amount of costs passed on may be influenced by the size of the municipal advisory firm. For smaller municipal advisors with fewer clients, the incremental costs associated with the qualification examination may represent a greater percentage of annual revenues, and, thus, such advisors may be more likely to pass those costs along to their advisory clients. As noted above, however, the costs of preparing for and taking the examination would be incurred only once for each municipal advisor representative, assuming the representative passed the examination on the first occasion.</P>
                <P>
                    The Act provides that MSRB rules may not impose a regulatory burden on small municipal advisors that is not necessary or appropriate in the public interest and for the protection of investors, municipal entities, and obligated persons provided that there is robust protection of investors against fraud.
                    <SU>21</SU>
                    <FTREF/>
                     The MSRB is sensitive to the potential impact of the requirements contained in the proposed rule change on small municipal advisors. The MSRB understands that some small municipal advisors and sole proprietors, unlike larger municipal advisory firms, may not employ full-time staff to train individuals to take and pass professional qualification examinations and that the cost of complying with the requirements of the proposed rule change may be proportionally higher for these smaller firms. To minimize potential disruption to firms' business activities and to allow sufficient time for municipal advisor professionals to study for the examination, the proposed rule change would provide covered registered persons with a one-year grace period to pass the examination. The MSRB recognizes that requiring all individuals engaged in municipal advisory activities to take the examination means that many individuals with ongoing business obligations would be required to prepare for and take the examination in addition to fulfilling their business commitments. The MSRB believes that the one-year grace period would provide such individuals with sufficient flexibility to plan their examination preparation time around their existing and ongoing business obligations. Going forward, new municipal advisor professionals entering the market would be able to study for and take the examination before incurring municipal advisory business commitments. The MSRB believes that the proposed rule change is consistent with the Act's provision with respect to burdens imposed on small municipal advisors because the financial burden of preparing for and taking the qualification examination is offset by the need to ensure that municipal advisor professionals have a basic level of competency.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(L)(iv) of the Act, 15 U.S.C. 78o-4(b)(2)(L)(iv).
                    </P>
                </FTNT>
                <P>
                    On March 17, 2014, the MSRB published a request for public comment on a draft of the proposed rule change.
                    <SU>22</SU>
                    <FTREF/>
                     In response, the MSRB received thirty-five comment letters.
                    <SU>23</SU>
                    <FTREF/>
                     The comments, which are summarized in Section 5 below, focused principally on the qualification examination.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         MSRB Notice 2014-08 (Mar. 17, 2014) (March Notice).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Letters were received from Arrow Partners (“Arrow”), Association of Registration Management (“ARM”), Bond Dealers of America (“BDA”), Cedar Partners, Ltd (“Cedar”), Central States Capital Markets (“Central States”), CFA Institute (“CFA”), Compass Securities Corporation (“Compass”), Dixworks LLC (“Dixworks”), Fitzgibbon Toigo Associates (“Fitzgibbon”), Fortress Group, Inc. (“Fortress”), Frank Taylor, George K. Baum &amp; Company (“George K. Baum”), Government Credit Corporation (“GCC”), Hamersley Partners, LLC (“Hamersley”), IMMS LLC (“IMMS”), Investment Company Institute (“ICI”), Jorge Rosso, Monahan &amp; Roth, LLC (“Monahan”), MVision Private Equity Advisers USA LLC (“MVision”), National Association of Independent Public Finance Advisors (“NAIPFA”), New Albany Capital Partners, LLC (“New Albany”), Oyster River Capital LP (“Oyster River”), Perkins Fund Marketing LLC (“Perkins”), Raftelis Financial Consultants, Inc. (“Raftelis”), Securities Industry and Financial Markets Association (“SIFMA”), Sonja Sullivan, Stacy Havener, Stonehaven, Tessera Capital Partners (“Tessera”), Third Party Marketers Association (“3PM”), Tibor Partners Inc. (“Tibor”), Timothy D. Wasson, Yuba Group (“Yuba”), Zions First National Bank, by W. David Hemingway (“Zions Bank I”), Zions First National Bank, by James G. Livingston (“Zions Bank II”).
                    </P>
                </FTNT>
                <P>The qualification examination is intended to determine whether a municipal advisor representative meets a minimum level of competency and, in general, commenters acknowledged that municipal advisor representatives should meet or exceed a minimum level of competency. However, several commenters expressed concerns about implementation costs associated with the proposed examination. These commenters suggested that the MSRB consider alternatives for determining a municipal advisor representative's competency. Although the suggested alternatives vary, they fall into two main categories. First, several commenters asked the MSRB to reconsider the scope of the proposed qualification examination, suggesting the examination should be administered separately or as part of an existing qualification examination. Second, commenters suggested that municipal advisor professionals be grandfathered based on either their experience or their existing professional qualifications. These options are discussed in Section 5 below.</P>
                <P>
                    Commenters expressed concerns about the costs of preparing for and taking a qualification examination. SIFMA offered estimates of the costs to firms and individuals associated with taking the examination. These costs included fees per examination, study materials, the value of time used to 
                    <PRTPAGE P="72230"/>
                    study for the exam, recordkeeping costs, and compliance costs. Although many of these costs are unknown, SIFMA estimates that the known likely costs to individuals and firms will be at least $5,000 per individual taking the examination. In addition, SIFMA noted that costs also would be incurred by the MSRB to support development of questions for the new examination and by FINRA to administer the examination. SIFMA argued that these costs would “multiply exponentially” as potentially thousands of people who are or will be dually registered as municipal securities representatives and municipal advisory representatives—or will be moving from one classification to another—will need to take an additional qualification examination and incur additional expenses. SIFMA suggested that costs could be reduced by broadening the scope of the Series 52 examination to include questions related to competency as a municipal advisor representative.
                </P>
                <P>
                    BDA estimated costs of up to $100,000 per individual to meet the requirements as a municipal securities representative and as a municipal advisor representative. BDA did not explain how it arrived at this estimate, although it indicated that the figure includes the lost time of municipal advisor representatives that could have been used serving clients. BDA assumes that 75,000 individuals (33,000 individuals from non-dealer municipal advisors and 42,000 from dealer-municipal advisors) would need to take the new examination.
                    <SU>24</SU>
                    <FTREF/>
                     The product of BDA's estimated cost per individual and their estimated number of test takers yields a total estimated cost in the billions of dollars. Although BDA admits that it performed a “back of the envelope” assessment of the costs, the MSRB does not believe this cost estimate has adequate foundation.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         BDA also expressed concern about the administration of the qualification examination, positing that the number of individuals taking the examination would create congestion at examination centers and may result in professionals unable to complete their required testing. The MSRB is confident that FINRA—assuming it is designated as the administrator of the municipal advisor representative qualification examination under Section 15B(c)(7)(A)(iii) of the Act—and the examination centers employed by FINRA have the capacity to accommodate all individuals who will be required to take the qualification examination during the one-year grace period and thereafter.
                    </P>
                </FTNT>
                <P>SIFMA's estimates of cost per individual are better supported. Although cost estimates will vary, the SIFMA estimates appear to be more credible and useful and were considered by the MSRB. SIFMA notes that there will be unknown costs, so their estimate should be regarded as a minimum amount. The costs to the MSRB and FINRA in creating and administering the examination are relevant. However, a portion of those costs will likely be covered by examination fees. Given that these fees have been considered as part of the costs borne by individuals and firms, the relevant costs to the MSRB and FINRA would be those costs not covered by examination fees.</P>
                <P>
                    The BDA estimate of 75,000 test takers appears high and inconsistent with the permanent municipal advisor registration information received by the SEC to date. A more accurate figure has been provided by the SEC, which estimates in the SEC Final Registration Rule that municipal advisors will need to submit a new Form MA-I for approximately 950 individuals annually.
                    <SU>25</SU>
                    <FTREF/>
                     Using SIFMA's cost estimate, the total cost to the industry per year, excluding unknown recordkeeping and compliance costs, yields an estimate of approximately $4,750,000 in annual costs. Of course, in the first year the costs would be higher because those individuals currently engaged in municipal advisory activities will take the examination. Based on the initial analysis, the Board expects approximately 3,000 initial examination takers. This could result in a total cost of $15 million, using SIFMA's cost estimate of $5,000 per person. Most of this cost will be borne by large dealer-municipal advisors that elect to qualify a large number of their associated persons as municipal advisor representatives. The MSRB expects that many of these firms will leverage their training resources to lower the cost per examination candidate. The MSRB also believes that the total cost to municipal advisors to prepare individuals to take the qualification examination will drop significantly after the one-year grace period, as the number of examination takers decreases and then levels off.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         78 FR 67467 at 67589 (Nov. 12, 2013).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <HD SOURCE="HD3">Scope of the Qualification Examination</HD>
                <P>Commenters expressed varying views about the proper scope of a qualification examination. BDA offered three alternatives for the Board to consider: (a) Qualifying municipal advisor professionals using the Series 52 examination; (b) creating a single, new, comprehensive examination for all municipal securities and advisor professionals; and (c) creating a supplemental examination for previously registered municipal securities professionals that would cover the new municipal advisor material.</P>
                <P>SIFMA recommended that the Board consider adding questions to the existing Series 52 qualification examination. SIFMA stated that this alternative would be less burdensome to the industry, and would ensure that there was no delay in developing examination material and administering the examination. SIFMA also stated that examining municipal securities and advisory competency in one examination would aid small dealers, many of whom perform both functions and are very sensitive to compliance costs. Further, SIFMA stated that there are potentially thousands of individuals who are dually registered and would benefit from having a single examination. This is essentially the same approach as the universal examination recommended by BDA.</P>
                <P>Consistent with SIFMA's recommendation for a single qualification examination, ARM also suggested that if the MSRB feels that the duties of municipal advisor representatives require additional expertise that additional questions be added to existing examinations rather than creating entirely new examinations.</P>
                <P>
                    The Board maintains there is a need for separate qualification examinations because the content of such an examination will be designed to meet the MSRB's goal of determining whether a prospective municipal advisor representative meets the minimum level of competency required of a municipal advisor professional. The examination, while covering a variety of municipal advisory activities, will be more targeted than a combined examination that attempts to evaluate the competence of individuals engaged in varied municipal securities and municipal advisory activities. As discussed below, certain commenters take issue with the breadth of the proposed municipal advisor representative examination because of the more limited nature of their functions. These concerns could be exacerbated by combining the municipal advisor and securities representative examinations. Although a combined examination may be less costly to create and administer, and may place a smaller cost burden on dealers, such an examination may place a larger cost burden on non-dealer municipal advisors and their associated persons who have no need for or interest in demonstrating competency as a municipal securities representative but 
                    <PRTPAGE P="72231"/>
                    would be required to prepare for and pass an examination that included significant content relating to the role and regulation of municipal securities representatives.
                </P>
                <P>BDA suggests, alternatively, that the MSRB develop a supplemental examination for municipal securities representatives. Under this approach, municipal advisor professionals not qualified as municipal securities representatives could take the municipal securities representative qualification examination and municipal advisor supplement or a new municipal advisor representative qualification examination developed by the MSRB. The net effect of this alternative is a separate examination for municipal advisory activities. While a supplemental examination might require fewer questions than a stand-alone examination, the practicalities of maintaining many different examinations should not be underestimated. Moreover, to maintain consistency, the MSRB would then need to develop a supplemental examination for municipal advisors seeking to register as municipal securities representatives, which would necessitate a total of four examinations, adding further and unnecessary complexity to the registration process. Lastly, the MSRB believes that existing municipal securities representatives should be proficient on those portions of a municipal advisor representative examination that overlap with the municipal securities representative examination.</P>
                <P>
                    In contrast to other commenters, ICI argued against a single general qualification exam. ICI recommended that the MSRB create a separate qualification examination for those who provide advice regarding municipal fund securities. ICI cites the MSRB's policy on economic analysis that allows for consideration of different rule specifications or differing requirements for different market participants. Alternatively, ICI recommends grandfathering those individuals who have passed the Series 6 examination.
                    <SU>26</SU>
                    <FTREF/>
                     The Board believes that passing the Series 6 examination would demonstrate only a basic competency in servicing retail customers who purchase mutual funds, interests in 529 college savings plans and variable annuities and, hence, would not establish an individual's competency as a municipal advisor representative. The Board appreciates ICI's contention that the activities of municipal advisors who provide advice to municipal entities regarding municipal fund securities are different than the municipal advisory activities of traditional municipal advisors. The MSRB also acknowledges that some of the content on the examination will not be directly related to municipal fund securities. Nevertheless, the Board believes that individuals who engage in municipal advisory activities regarding municipal fund securities should demonstrate knowledge of the rules and regulations governing municipal advisors by taking the municipal advisor representative qualification examination.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The Investment Company and Variable Contracts Products Representative Qualifications Examination, (Series 6) authorizes individuals to sell a limited set of securities products including, mutual funds and variable annuities.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Grandfathering</HD>
                <P>ARM suggested that the MSRB consider grandfathering individuals who have corresponding registrations as a municipal securities representative or municipal securities principal on the grounds that these individuals have completed more encompassing examinations and that they are experienced municipal securities professionals whose expertise should be sufficient to engage in municipal advisory activities. SIFMA, BDA and 3PM also recommended that individuals who are currently qualified to perform municipal securities activities be grandfathered.</P>
                <P>
                    Yuba commented that the Board should make the supervisor examination available before, or simultaneously with, the representative examination and eliminate the need for a supervisor to take both examinations. The Board believes it is important that the representative examination be introduced prior to any principal examination because the examination will determine the basic competency of those individuals who are engaged in municipal advisory activity and have the most direct impact on municipal entities and investors. While the supervisory activities of municipal advisor principals are important, the MSRB will consider an examination for principals at a later date, and should not delay the introduction of an examination that has been in preparation for nearly four years. And in any event, a principal is customarily required to pass the representative examination.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         MSRB Rule G-3(b)(ii)(B).
                    </P>
                </FTNT>
                <P>A focused examination for municipal advisor professionals will likely be more effective in meeting the MSRB's goal of determining whether a municipal advisor representative meets a minimum level of competency than recognizing a professional qualification examination for municipal securities representatives or accepting the self-reported experience of an individual who worked in a previously unregulated environment. While it is self-evident that relying on existing qualifications (such as having passed the Series 52 examination) or general experience would place a smaller cost burden on firms and individuals than requiring all individuals engaged in municipal advisory activities to take and pass a new qualification examination, the MSRB believes such an examination is necessary to establish a baseline of competency for municipal advisors.</P>
                <P>The Board determined that grandfathering would not be consistent with the intent of Congress and the SEC in creating a new municipal advisor regulatory regime. The new regulation was created in response to problems that Congress and the SEC observed regarding the activities of municipal advisors. Requiring municipal advisor professionals to take and pass a basic qualification examination ensures that such individuals demonstrate a minimum level of understanding of the role and responsibilities of municipal advisors and applicable rules and regulations.</P>
                <P>
                    By contrast, grandfathering presumes that each municipal advisor representative has a basic competency in the subject matter. Congress explicitly called for the development of professional standards for municipal advisors.
                    <SU>28</SU>
                    <FTREF/>
                     Given the MSRB's statutory obligation to protect investors, municipal entities and obligated persons that interact with and/or rely on municipal advisor professionals, there should be a compelling reason to rely on their prior experience as evidence of their competence. Even if an individual passed the Series 7 or 52 examinations, the content was not specifically related to municipal advisory activities or the regulation of such activities. While examinations such as the Series 52 may have some overlapping content, the examination questions being developed for municipal advisor professionals by PQAC are being drafted based on the particular job responsibilities of municipal advisor professionals and the rules and regulations governing such responsibilities. In this regard, the Series 7 and 52 examinations do not adequately test the specific job responsibilities of municipal advisor professionals.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         Section 15B(b)(2)(L) of the Act, 15 U.S.C. 78o-4(b)(2)(L).
                    </P>
                </FTNT>
                <P>
                    The focus of the Series 52 examination is on underwriting, trading, 
                    <PRTPAGE P="72232"/>
                    research and sales, not municipal advisory activities. Approximately one-quarter of the examination covers rules and regulations applicable to these activities and over half of the examination covers municipal securities features and principles relevant to municipal securities activities. There are few questions directly related to the job responsibilities of municipal advisor professionals, and those that exist are generally written from the perspective as municipal securities representative. Without significant content related to the job responsibilities of municipal advisor professionals, the Board believes that passing the Series 52 examination does not establish an individual's basic competency to perform municipal advisory activities.
                    <SU>29</SU>
                    <FTREF/>
                     Moreover, the municipal advisor regulatory regime is still being developed by the Board, and individuals who have passed the Series 52 examination would not have demonstrated knowledge of the new core municipal advisor regulations.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         While the Series 52 examination covers concepts related to the activities of a traditional financial advisor, those concepts are discrete and do not extend to the broader set of municipal advisory activities that will be covered on the municipal advisor representative qualification examination.
                    </P>
                </FTNT>
                <P>
                    Certain commenters urged the Board to adopt the approach taken by FINRA when implementing the investment banking representative qualification examination (Series 79).
                    <SU>30</SU>
                    <FTREF/>
                     FINRA grandfathered general securities representatives (Series 7 or Series 7 equivalent) if they opted-in within six months of the effective date of the rule.
                    <SU>31</SU>
                    <FTREF/>
                     FINRA explained that the new examination would provide a more targeted assessment (than the Series 7 examination) of the competency of investment banking professionals. Some commenters further suggested that, if grandfathering is permitted, the MSRB could ensure that relevant municipal advisor content is delivered through the continuing education program. While continuing education is important, it should not serve as a substitute for a basic competency examination unless other alternatives are not feasible. The Board believes the approach taken by FINRA (then National Association of Securities Dealers, “NASD”) in implementing the research analyst qualification examination (Series 86/87) is a more appropriate analogue. In that instance, no grandfathering was permitted due to the FINRA's desire that all research analysts demonstrate the same level of analytical competency and knowledge of the law.
                    <SU>32</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         The following commenters suggested using FINRA's approach to grandfathering: BDA, George K. Baum, SIFMA, and 3PM.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         FINRA Regulatory Notice 09-41 (Jul. 2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         NASD Notice to Members 04-25 (Mar. 2004).
                    </P>
                </FTNT>
                <P>The argument for grandfathering individuals based on experience is not persuasive because the MSRB has no way of determining the competence of individuals who have been acting as municipal advisors but have been unregulated at the federal level. While it is likely that many municipal advisor professionals are experienced and knowledgeable and have more than a basic level of competency, the MSRB is not in a position to review the background and experience of each professional to determine whether such individual is qualified. Qualifying all individuals as municipal advisor representatives based solely on their experience would likely result in the qualification of some individuals who could not demonstrate a basic competency regarding the responsibilities of municipal advisors and the regulations governing municipal advisory activities.</P>
                <P>Given the new regulatory regime for municipal advisors, the differences in size and type of municipal advisors, as well as the varied experience and background of municipal advisor professionals, it is important that each individual demonstrate a basic competency.</P>
                <HD SOURCE="HD2">Apprenticeship, Grace Period, and Classifications</HD>
                <P>
                    Commenters broadly supported the elimination of the apprenticeship requirement for municipal securities representatives and not establishing one for municipal advisor representatives.
                    <SU>33</SU>
                    <FTREF/>
                     There also was broad support for establishing a one-year grace period to provide municipal advisor representatives with sufficient time to study and take the examination without causing undue disruption to the business of the municipal advisor.
                    <SU>34</SU>
                    <FTREF/>
                     3PM, however, suggested that more time was necessary, and NAIPFA said it could not opine as to whether the one-year grace period would be sufficient because it was unsure if the study guide would be available before the grace period commenced. As noted above, prior to the commencement of the grace period, the MSRB will file with the SEC a study outline for the examination and then conduct a pilot examination. The pilot examination will likely be administered in 2015 and will enable the Board to establish a passing score for the examination. After a passing score is established, the MSRB will issue a regulatory notice establishing an effective date and compliance date for the examination. The grace period will commence on the effective date and conclude on the compliance date.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         The following commenters were supportive of eliminating the apprenticeship requirement: George K. Baum, SIFMA, Zions Bank II, Yuba and 3PM.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         The following commenters were supportive of the one-year grace period: BDA, New Albany, ICI, SIFMA, Zions Bank II and 3PM.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Municipal Advisor Representative Examination Delivery and Administration</HD>
                <P>
                    Several commenters raised questions regarding the administration and delivery of the examination, specifically about retention of the registration information for non-dealer municipal advisors that are not included in FINRA's central registration depository.
                    <SU>35</SU>
                    <FTREF/>
                     Commenters want to ensure a similar process is in place for non-dealer municipal advisors. Similarly, commenters asked that the MSRB utilize the existing securities industry registration forms (
                    <E T="03">e.g.,</E>
                     Form U4). These issues are beyond the scope of the proposed rule change. The MSRB will address the administration of the examination at a later date.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         The following commenters raised issues regarding the administration and delivery of the examination: ARM, BDA and George K. Baum.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Comment on the Implication of Revising Rule G-1</HD>
                <P>In response to the proposed revisions to MSRB Rule G-1, Zions Bank (Zions Bank I) commented that the proposed amendments should not be interpreted or applied in any way that would preclude a bank, or a separately identifiable department or division of a bank (“SID”), or a bank affiliate, from engaging in municipal securities and municipal advisory activities. It is not the intent of the amendments to preclude banks, SIDS, or bank affiliates from engaging in a broad range of municipal securities and/or municipal advisory activities, so long as they are properly registered under MSRB rules and the federal securities laws and otherwise comply with any limitations therein.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Within 45 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period of up to 90 days (i) as the Commission may designate if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the self-regulatory organization consents, the Commission will:
                    <PRTPAGE P="72233"/>
                </P>
                <P>(A) By order approve or disapprove such proposed rule change, or</P>
                <P>(B) institute proceedings to determine whether the proposed rule change should be disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov</E>
                    . Please include File Number SR-MSRB-2014-08 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549.</P>
                <FP>
                    All submissions should refer to File Number SR-MSRB-2014-08. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549 on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the MSRB. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-MSRB-2014-08 and should be submitted on or before December 26, 2014.
                </FP>
                <SIG>
                    <P>
                        For the Commission, pursuant to delegated authority.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28543 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-73707; File No. SR-MSRB-2014-09]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Municipal Securities Rulemaking Board; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Consisting of Amendments to MSRB's Electronic Municipal Market Access (EMMA) System To Add Disclosures Related to Municipal Asset-Backed Securities</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on November 25, 2014, the Municipal Securities Rulemaking Board (the “MSRB” or “Board”) filed with the Securities and Exchange Commission (the “SEC” or “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by the MSRB. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The MSRB is filing with the Commission a proposed rule change consisting of amendments to the MSRB's Electronic Municipal Market Access (“EMMA”) system to add disclosures related to municipal asset-backed securities (“ABS”) required under Exchange Act Rule 15Ga-1 
                    <SU>3</SU>
                    <FTREF/>
                     to be filed on Form ABS-15G to the list of categories of continuing disclosures that EMMA will accept and disseminate publicly (the “proposed rule change”). The proposed rule change also makes minor changes of a technical nature, including removing outdated language, updating the naming convention used for published submitter and subscriber specification documents and updating information concerning how users can access submitter and subscriber specification documents (“technical amendments”). The MSRB filed the proposed rule change under Section 19(b)(3)(A)(iii) of the Exchange Act 
                    <SU>4</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>5</SU>
                    <FTREF/>
                     thereunder as a noncontroversial rule change that renders the proposal effective upon filing. The proposed rule change will be made operative no earlier than January 9, 2015 and no later than January 31, 2015, with the precise effective date in that range to be announced by the MSRB in a notice published on the MSRB Web site.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is available on the MSRB's Web site at 
                    <E T="03">www.msrb.org/Rules-and-Interpretations/SEC-Filings/2014-Filings.aspx,</E>
                     at the MSRB's principal office, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the MSRB included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The MSRB has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    Pursuant to Section 943 of the Dodd-Frank Wall Street Reform and Consumer Protection Act,
                    <SU>6</SU>
                    <FTREF/>
                     the SEC adopted new rules related to representations and warranties in ABS. One of these rules, Exchange Act Rule 15Ga-1,
                    <SU>7</SU>
                    <FTREF/>
                     requires, among other things, certain disclosures related to municipal ABS to be filed on Form ABS-15G. Pursuant to Rule 314 of Regulation S-T,
                    <SU>8</SU>
                    <FTREF/>
                     the SEC identified EMMA, in addition to the Electronic Data Gathering, Analysis, and Retrieval system (“EDGAR”), as a venue that a municipal securitizer may use to make submissions of Form ABS-15G in compliance with Exchange Act Rule 15Ga-1.
                    <SU>9</SU>
                    <FTREF/>
                     Accordingly, the proposed rule change consists of amendments to the EMMA system to add disclosures related to municipal ABS required 
                    <PRTPAGE P="72234"/>
                    under Exchange Act Rule 15Ga-1 
                    <SU>10</SU>
                    <FTREF/>
                     on Form ABS-15G to the list of categories of continuing disclosures that EMMA will accept and disseminate publicly.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Pub. L. 111-203, 124 Stat. 1376 (2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         17 CFR 232.314.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The proposed rule change also consists of technical amendments to the EMMA service.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The MSRB has adopted the proposed rule change pursuant to Section 15B(b)(2)(C) of the Exchange Act,
                    <SU>12</SU>
                    <FTREF/>
                     which provides that the MSRB's rules shall
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78o-4(b)(2)(C).
                    </P>
                </FTNT>
                <EXTRACT>
                    <FP>be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in municipal securities, to remove impediments to and perfect the mechanism of a free and open market in municipal securities, and, in general, to protect investors and the public interest.</FP>
                </EXTRACT>
                <FP>
                    The MSRB believes that the proposed rule change is consistent with the Exchange Act because it facilitates the implementation of Exchange Act Rule 15Ga-1.
                    <SU>13</SU>
                    <FTREF/>
                     In addition, the proposed rule change serves to remove impediments to and help perfect the mechanism of a free and open market in municipal securities and promotes the statutory mandate of the MSRB to protect investors and the public interest. The proposed rule change would aid in making additional information for making investment decisions more easily accessible to all participants in the municipal securities market on an equal basis throughout the life of the securities without barriers to obtaining such information. Broad access to the disclosures related to municipal ABS required under Exchange Act Rule 15Ga-1 
                    <SU>14</SU>
                    <FTREF/>
                     on Form ABS-15G through the continuing disclosure service of EMMA should assist in preventing fraudulent and manipulative acts and practices by improving the opportunity for public investors to access material information about issuers and their securities.
                </FP>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    The MSRB does not believe that the proposed rule change would impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Exchange Act. The SEC identified EMMA as a venue that a municipal securitizer may use to make submissions of Form ABS-15G in compliance with Exchange Act Rule 15Ga-1.
                    <SU>15</SU>
                    <FTREF/>
                     In identifying EMMA, in addition to EDGAR, as a venue for the disclosures on Form ABS-15G the SEC stated that “filing on EMMA will facilitate use by investors, since the demand, repurchase and replacement disclosures will generally be available in the same repository where investors are most likely to look for other municipal ABS disclosures.” 
                    <SU>16</SU>
                    <FTREF/>
                     The proposed rule change would facilitate a requirement that already has been adopted by the SEC and carries the benefits articulated by the SEC as a result of permitting submissions of Form ABS-15G in compliance with Exchange Act Rule 15Ga-1 
                    <SU>17</SU>
                    <FTREF/>
                     and Rule 314 of Regulation S-T 
                    <SU>18</SU>
                    <FTREF/>
                     to be provided to investors on EMMA with other municipal ABS disclosures. While the SEC's adoption of Exchange Act Rule 15Ga-1 
                    <SU>19</SU>
                    <FTREF/>
                     and Rule 314 of Regulation S-T 
                    <SU>20</SU>
                    <FTREF/>
                     are themselves significant, the proposed rule change to accommodate the intended alternative disclosure venue of EMMA and to make technical amendments to the EMMA service would not significantly affect the protection of investors or the public interest and would not impose any significant burden on competition.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release Nos. 33-9175 and 34-63741 (January 20, 2011), 76 FR 4489, 4509 (January 26, 2011).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         17 CFR 232.314.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 240.15Ga-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         17 CFR 232.314.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>Written comments were neither solicited nor received on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>Because the foregoing proposed rule change does not:</P>
                <P>(i) Significantly affect the protection of investors or the public interest;</P>
                <P>(ii) impose any significant burden on competition; and</P>
                <P>(iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, </P>
                <FP>
                    it has become effective pursuant to Section 19(3)(A) of the Exchange Act 
                    <SU>21</SU>
                    <FTREF/>
                     and Rule 19(b)-4(f)(6) 
                    <SU>22</SU>
                    <FTREF/>
                     thereunder.
                </FP>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Exchange Act.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Exchange Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form 
                    <E T="03">http://www.sec.gov/rules/sro.shtml;</E>
                     or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-MSRB-2014-09 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549.</P>
                <FP>
                    All submissions should refer to File Number SR-MSRB-2014-09. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549 on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the MSRB. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-MSRB-2014-09 and should be submitted on or before December 26, 2014.
                </FP>
                <SIG>
                    <PRTPAGE P="72235"/>
                    <P>
                        For the Commission, pursuant to delegated authority.
                        <SU>23</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28548 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-73713; File No. SR-NASDAQ-2014-113]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; The NASDAQ Stock Market LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Relating to an Amendment To Conform Rule Text</SUBJECT>
                <DATE>December 1, 2014.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on November 18, 2014, The NASDAQ Stock Market LLC (“NASDAQ” or “Exchange”) filed with the Securities and Exchange Commission (“SEC” or “Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by NASDAQ. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>NASDAQ proposes to modify Chapter XV, entitled “Options Pricing,” at Section 2 governing pricing for NASDAQ members using the NASDAQ Options Market (“NOM”), NASDAQ's facility for executing and routing standardized equity and index options.</P>
                <P>
                    Specifically, NOM proposes to conform certain language related to Penny Pilot Options
                    <SU>3</SU>
                    <FTREF/>
                     rebates currently applicable to Customers,
                    <SU>4</SU>
                    <FTREF/>
                     Professionals
                    <SU>5</SU>
                    <FTREF/>
                     and NOM Market Makers.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Penny Pilot was established in March 2008 and in October 2009 was expanded and extended through December 31, 2014. 
                        <E T="03">See</E>
                         Securities Exchange Act Release Nos. 57579 (March 28, 2008), 73 FR 18587 (April 4, 2008) (SR-NASDAQ-2008-026) (notice of filing and immediate effectiveness establishing Penny Pilot); 60874 (October 23, 2009), 74 FR 56682 (November 2, 2009) (SR-NASDAQ-2009-091) (notice of filing and immediate effectiveness expanding and extending Penny Pilot); 60965 (November 9, 2009), 74 FR 59292 (November 17, 2009) (SR-NASDAQ-2009-097) (notice of filing and immediate effectiveness adding seventy-five classes to Penny Pilot); 61455 (February 1, 2010), 75 FR 6239 (February 8, 2010) (SR-NASDAQ-2010-013) (notice of filing and immediate effectiveness adding seventy-five classes to Penny Pilot); 62029 (May 4, 2010), 75 FR 25895 (May 10, 2010) (SR-NASDAQ-2010-053) (notice of filing and immediate effectiveness adding seventy-five classes to Penny Pilot); 65969 (December 15, 2011), 76 FR 79268 (December 21, 2011) (SR-NASDAQ-2011-169) (notice of filing and immediate effectiveness extension and replacement of Penny Pilot); 67325 (June 29, 2012), 77 FR 40127 (July 6, 2012) (SR-NASDAQ-2012-075) (notice of filing and immediate effectiveness and extension and replacement of Penny Pilot through December 31, 2012); 68519 (December 21, 2012), 78 FR 136 (January 2, 2013) (SR-NASDAQ-2012-143) (notice of filing and immediate effectiveness and extension and replacement of Penny Pilot through June 30, 2013); 69787 (June 18, 2013), 78 FR 37858 (June 24, 2013) (SR-NASDAQ-2013-082) (notice of filing and immediate effectiveness and extension and replacement of Penny Pilot through December 31, 2013); 71105 (December 17, 2013), 78 FR 77530 (December 23, 2013) (SR-NASDAQ-2013-154) (notice of filing and immediate effectiveness and extension and replacement of Penny Pilot through June 30, 2014); and 79 FR 31151 (May 23, 2014), 79 FR 31151 (May 30, 2014) (SR-NASDAQ-2014-056) ((notice of filing and immediate effectiveness and extension and replacement of Penny Pilot through December 31, 2014). 
                        <E T="03">See also</E>
                         NOM Rules, Chapter VI, Section 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The term “Customer” applies to any transaction that is identified by a Participant for clearing in the Customer range at The Options Clearing Corporation (“OCC”) which is not for the account of broker or dealer or for the account of a “Professional” (as that term is defined in Chapter I, Section 1(a)(48)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The term “Professional” means any person or entity that (i) is not a broker or dealer in securities, and (ii) places more than 390 orders in listed options per day on average during a calendar month for its own beneficial account(s) pursuant to Chapter I, Section 1(a)(48). All Professional orders shall be appropriately marked by Participants.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The term “NOM Market Maker” means a Participant that has registered as a Market Maker on NOM pursuant to Chapter VII, Section 2, and must also remain in good standing pursuant to Chapter VII, Section 4. In order to receive NOM Market Maker pricing in all securities, the Participant must be registered as a NOM Market Maker in at least one security.
                    </P>
                </FTNT>
                <P>
                    The text of the proposed rule change is available on the Exchange's Web site at 
                    <E T="03">http://www.nasdaq.cchwallstreet.com,</E>
                     at the principal office of the Exchange, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The purpose of the proposed rule change is to conform rule text in Chapter XV, entitled “Options Pricing,” at Section 2(1) governing the rebates and fees assessed for options orders entered into NOM. Specifically, the Exchange proposes to amend rule text describing the volume required to qualify for certain Customer and Professional Penny Pilot Options Rebate to Add Liquidity tiers and also certain NOM Market Maker Penny Pilot Options Rebate to Add Liquidity tiers.</P>
                <P>
                    With respect to the Customer and Professional Tier 8 Penny Pilot Options Rebate to Add Liquidity, the NOM Market Maker Tier 6 Penny Pilot Options Rebate to Add Liquidity and the $0.02 per contract Tier 8 incentive for the Customer and Professional Penny Pilot Options Rebate to Add Liquidity,
                    <SU>7</SU>
                    <FTREF/>
                     the Exchange proposes to amend the language which describes the required national customer volume in multiply-listed equity and ETF options classes in a month in these sections. The Exchange is proposing to conform this language with current rule text which describes total industry customer equity and ETF option average daily volume (“ADV”) contracts per day in a month. This proposed amendment is non-substantive as the two concepts are not different. The Exchange is proposing to conform the language to avoid confusion. This amendment will not amend the manner in which those rebates are paid today.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Participants that add Customer, Professional, Firm, Non-NOM Market Maker and/or Broker-Dealer liquidity in Penny Pilot Options and/or Non- Penny Pilot Options of 1.25% or more of national customer volume in multiply-listed equity and ETF options classes in a month will receive an additional $0.02 per contract Penny Pilot Options Customer Rebate to Add Liquidity for each transaction which adds liquidity in Penny Pilot Options in that month.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that its proposal is consistent with Section 6(b) of the Act 
                    <SU>8</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act 
                    <SU>9</SU>
                    <FTREF/>
                     in particular, in that it is designed to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general to protect investors and the public interest, in that 
                    <PRTPAGE P="72236"/>
                    the amendments will provide greater clarity to the pricing of these options.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Exchange believes that the amendments provide greater specificity and conform word usage with respect to rebates and incentives offered by NOM. The Exchange is not proposing to amend the pricing, rather the Exchange believes the amendments make clear that the terms national customer volume and total industry volume are equivalent.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The amendments to the options pricing are non-substantive and merely seek to conform rule text to make clear that the same standard of measure is being applied to determine the qualifications for the volume tiers and incentives.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments were either solicited or received.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Because the foregoing proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A)(ii) of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and subparagraph (f)(6) of Rule 19b-4 thereunder.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(3)(a)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is: (i) Necessary or appropriate in the public interest; (ii) for the protection of investors; or (iii) otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved. The Exchange has provided the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NASDAQ-2014-113 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-NASDAQ-2014-113. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml).</E>
                     Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NASDAQ-2014-113, and should be submitted on or before December 26, 2014.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28584 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Data Collection Available for Public Comments</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Small Business Administration (SBA) intends to request approval, from the Office of Management and Budget (OMB) for the collection of information described below. The Paperwork Reduction Act (PRA) of 1995, 44 U.S.C. Chapter 35 requires federal agencies to publish a notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information before submission to OMB, and to allow 60 days for public comment in response to the notice. This notice complies with that requirement.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send all comments to Craig Heilman, Director of Veteran Programs, Office of Veteran Business Development, Small Business Administration, 409 3rd Street, 5th Floor, Washington, DC 20416.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Tyrenna Tolbert, Program Support Specialist, Office of Veteran Business Development, 
                        <E T="03">tyrenna.tolbert@sba.gov,</E>
                         202-205-7526, or Curtis B. Rich, Management Analyst, 202-205-7030, 
                        <E T="03">curtis.rich@sba.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Boots to Business is an entrepreneurial education initiative offered by the U.S. Small Business Administration (SBA) as a career track within the Department of Defense's revised Training Assistance Program called Transition Goals, Plans, Success (Transition GPS). The curriculum provides valuable assistance to transitioning service members exploring self-employment opportunities by leading them through the key steps for evaluating business concepts and the foundational knowledge required for developing a business plan. Participants are also introduced to SBA resources available to help access startup capital and additional technical assistance.</P>
                <P>
                    This form facilitates online registration for the Boots to Business 
                    <PRTPAGE P="72237"/>
                    course for eligible service members and their spouses. The information collected provides pertinent data to the management and participation of the course in addition to assisting instructors to better tailor the individual classes based on the experience and interests of the participants.
                </P>
                <P>
                    <E T="03">Solicitation of Public Comments:</E>
                </P>
                <P>SBA is requesting comments on (a) Whether the collection of information is necessary for the agency to properly perform its functions; (b) whether the burden estimates are accurate; (c) whether there are ways to minimize the burden, including through the use of automated techniques or other forms of information technology; and (d) whether there are ways to enhance the quality, utility, and clarity of the information.</P>
                <P>
                    <E T="03">Summary of Information Collection:</E>
                </P>
                <P>
                    <E T="03">Title:</E>
                     Boots to Business Registration.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Transitioning service members and spouses.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Responses:</E>
                     10,000.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Hour Burden:</E>
                     1,667 hours.
                </P>
                <SIG>
                    <NAME>Curtis B. Rich,</NAME>
                    <TITLE>Management Analyst. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28512 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #13985]</DEPDOC>
                <SUBJECT>Colorado Disaster #CO-00068 Declaration of Economic Injury</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 1.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Economic Injury Disaster Loan (EIDL) declaration for the State of COLORADO, dated 05/14/2014.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Red Mountain Pass Rockslide.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         01/13/2014 and continuing through 06/12/2014.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         11/26/2014.
                    </P>
                    <P>
                        <E T="03">EIDL Loan Application Deadline Date:</E>
                         02/16/2015.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of the Administrative EIDL disaster declaration for the State of Colorado, dated 05/14/2014 is hereby amended to establish the incident period for this disaster as beginning 01/13/2014 and continuing through 06/12/2014.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59002)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: November 26, 2014.</DATED>
                    <NAME>Maria Contreras-Sweet,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28514 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SOCIAL SECURITY ADMINISTRATION</AGENCY>
                <DEPDOC>[Docket No. SSA-2014-0074]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Request and Comment Request</SUBJECT>
                <P>The Social Security Administration (SSA) publishes a list of information collection packages requiring clearance by the Office of Management and Budget (OMB) in compliance with Public Law 104-13, the Paperwork Reduction Act of 1995, effective October 1, 1995. This notice includes revisions and an extension of OMB-approved information collections.</P>
                <P>SSA is soliciting comments on the accuracy of the agency's burden estimate; the need for the information; its practical utility; ways to enhance its quality, utility, and clarity; and ways to minimize burden on respondents, including the use of automated collection techniques or other forms of information technology. Mail, email, or fax your comments and recommendations on the information collection(s) to the OMB Desk Officer and SSA Reports Clearance Officer at the following addresses or fax numbers.</P>
                <FP SOURCE="FP-1">
                    (OMB), Office of Management and Budget, Attn: Desk Officer for SSA, Fax: 202-395-6974, Email address: 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </FP>
                <FP SOURCE="FP-1">
                    (SSA), Social Security Administration, OLCA, Attn: Reports Clearance Director, 3100 West High Rise, 6401 Security Blvd., Baltimore, MD 21235, Fax: 410-966-2830, Email address: 
                    <E T="03">OR.Reports.Clearance@ssa.gov.</E>
                </FP>
                <P>
                    Or you may submit your comments online through 
                    <E T="03">www.regulations.gov,</E>
                     referencing Docket ID Number [SSA-2014-0074].
                </P>
                <P>I. The information collection below is pending at SSA. SSA will submit it to OMB within 60 days from the date of this notice. To be sure we consider your comments, we must receive them no later than February 3, 2015. Individuals can obtain copies of the collection instruments by writing to the above email address.</P>
                <P>
                    <E T="03">Application for Mother's or Father's Insurance Benefits—20 CFR 404.339-404.342, 20 CFR 404.601-404.603—0960-0003.</E>
                     Section 202(g) of the Social Security Act provides for the payment of monthly benefits to the widow or widower of an insured individual if the surviving spouse is caring for the deceased worker's child (who is entitled to Social Security benefits). SSA uses the information on Form SSA-5-BK to determine an individual's eligibility for mother's or father's insurance benefits. The respondents are individuals caring for a child of the deceased worker who is applying for mother's or father's insurance benefits under the Old Age, Survivors, and Disability Insurance program (OASDI).
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Frequency of 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Total 
                            <LI>estimated </LI>
                            <LI>annual </LI>
                            <LI>burden </LI>
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-5-F6 (paper)</ENT>
                        <ENT>1,611</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>403</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCS</ENT>
                        <ENT>26,045</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>6,511</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">MCS/Signature Proxy</ENT>
                        <ENT>26,044</ENT>
                        <ENT>1</ENT>
                        <ENT>14</ENT>
                        <ENT>6077</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>53,700</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>12,991</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="72238"/>
                <P>
                    II. SSA submitted the information collections below to OMB for clearance. Your comments regarding the information collections would be most useful if OMB and SSA receive them 30 days from the date of this publication. To be sure we consider your comments, we must receive them no later than January 5, 2015. Individuals can obtain copies of the OMB clearance package by writing to 
                    <E T="03">OR.Reports.Clearance@ssa.gov.</E>
                </P>
                <P>
                    1. 
                    <E T="03">Letter to Employer Requesting Information About Wages Earned by Beneficiary—20 CFR 416.703, 404.801 &amp; 404.820—0960-0034.</E>
                     Social Security disability recipients receive payments based on their inability to engage in substantial gainful activity (SGA) because of a physical or mental condition. If the recipients work, SSA must evaluate and determine if they continue to meet the disability requirements of the law. Therefore, we use Form SSA-L725 to request monthly earnings information from the recipient's employer. We then use the earnings data to determine whether the recipient is engaging in SGA, since work after a recipient becomes entitled to benefits can cause a cessation of disability. The respondents are businesses that employ Social Security disability recipients.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Frequency of 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated 
                            <LI>total </LI>
                            <LI>annual </LI>
                            <LI>burden </LI>
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-L725</ENT>
                        <ENT>150,000</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>100,000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    2. 
                    <E T="03">Letter to Employer Requesting Wage Information—0960-0138.</E>
                     SSA must establish and verify wage information for Supplemental Security Income (SSI) applicants and recipients when determining SSI eligibility and payment amounts. SSA uses Form SSA-L4201 to collect wage data from employers. SSA uses the information to determine eligibility and proper payment amounts for SSI applicants and recipients. The respondents are employers of SSI applicants and recipients.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Frequency of 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated 
                            <LI>total </LI>
                            <LI>annual </LI>
                            <LI>burden </LI>
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-L4201</ENT>
                        <ENT>133,000</ENT>
                        <ENT>1</ENT>
                        <ENT>30</ENT>
                        <ENT>66,500</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    3. 
                    <E T="03">Statement of Living Arrangements, In-Kind Support, and Maintenance—20 CFR 416.1130-416.1148—0960-0174.</E>
                     SSA determines SSI payment amounts based on applicants' and recipients' needs. We measure individuals' needs, in part, by the amount of income they receive, including in-kind support and maintenance in the form of food and shelter provided by other persons. SSA uses Form SSA-8006-F4 to determine if in-kind support and maintenance exists for SSI applicants and recipients. This information also assists SSA in determining the income value of in-kind support and maintenance SSI applicants and recipients receive. The respondents are individuals who apply for SSI payments, or who complete an SSI eligibility redetermination.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Frequency of 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated 
                            <LI>total </LI>
                            <LI>annual </LI>
                            <LI>burden </LI>
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-8006-F4</ENT>
                        <ENT>173,380</ENT>
                        <ENT>1</ENT>
                        <ENT>7</ENT>
                        <ENT>20,228</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    4. 
                    <E T="03">Claimant's Recent Medical Treatment—20 CFR 404.1512 and 416.912—0960-0292.</E>
                     When Disability Determinations Services (DDS) deny a claim at the reconsideration level, the claimant has a right to request a hearing before an administrative law judge (ALJ). For the hearing, SSA asks the claimant to complete and return the HA-4631 if the claimant's file does not reflect a current, complete medical history as the claimant proceeds through the appeals process. ALJs must obtain the information to update and complete the record and to verify the accuracy of the information. Through this process, ALJs can ascertain whether the claimant's situation has changed. The ALJs and hearing office staff use the response to make arrangements for consultative examination(s) and the attendance of an expert witness(es), if appropriate. During the hearing, the ALJ offers any completed questionnaires as exhibits and may use them to: (1) Refresh the claimant's memory, and (2) shape their questions. The respondents are claimant's requesting hearings on entitlement to OASDI benefits or SSI payments.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                    <PRTPAGE P="72239"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated total annual burden 
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">HA-4631</ENT>
                        <ENT>200,000</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>33,333</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    5. 
                    <E T="03">Certification of Low Birth Weight for SSI Eligibility of Funds You Provided to Another and Statement of Funds You Received—20 CFR 416.931, 416.926a(m), and 416.924—0960-0720.</E>
                     Hospitals and claimants use Form SSA-3380 to provide medical information to local field offices (FO) and the DDS on behalf of infants with low birth weight. FOs use the form as a protective filing statement and the medical information to make presumptive disability findings, which allow expedited payment to eligible claimants. DDSs use the medical information to determine disability and continuing disability. The respondents are hospitals and claimants who have information identifying low birth weight babies and their medical conditions.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated total annual burden 
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SSA-3380</ENT>
                        <ENT>28,125</ENT>
                        <ENT>1</ENT>
                        <ENT>15</ENT>
                        <ENT>7,031</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    6. 
                    <E T="03">Request to Show Cause for Failure to Appear—20 CFR 404.938, 20 CFR 416.1438, and 20 CFR 404.957(a)(ii)—0960-0794.</E>
                     When claimants who requested a hearing before an ALJ fail to appear at their scheduled hearing, the ALJ may reschedule the hearing if the claimants establish good cause for missing the hearings. To establish good cause, claimants must show one of the following: (1) SSA did not properly notify the claimant of the hearing, or (2) an unexpected event occurred without sufficient time for the claimant to request a postponement. The claimants can use paper Form HA-L90 to provide their reason for not appearing at their scheduled hearings; or the claimants' representatives can use Electronic Records Express to submit the HA-L90 online. If the ALJ determines the claimants established good cause for failure to appear at the hearing, the ALJ will schedule a supplemental hearing; if not, the ALJ will make a claims eligibility determination based on the claimants' evidence of record. Respondents are claimants, or their representatives, seeking to establish good cause for failure to appear at a scheduled hearing before an ALJ.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of an OMB-approved information collection.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Modality of completion</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Frequency of response</CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden per </LI>
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">
                            Estimated total annual burden 
                            <LI>(hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">HA-L90 (paper or Electronic Records Express)</ENT>
                        <ENT>40,000</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>6,667</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Faye Lipsky,</NAME>
                    <TITLE>Reports Clearance Officer, Social Security Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28562 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4191-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Notice of Intent To Rule on Request To Release Airport Property at Eufaula Municipal Airport, Eufaula, Arkansas</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Request to Release Airport Property.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to rule and invites public comment on the release of land at Eufaula Municipal Airport under the provisions of Section 125 of the Wendell H. Ford Aviation Investment Reform Act for the 21st Century (AIR 21).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on this application may be mailed or delivered to the FAA at the following address: Mr. Glenn A Boles, Manager, Federal Aviation Administration, Southwest Region, Airports Division, AR/OK Airports Development Office, ASW-630, Fort Worth, Texas 76137.</P>
                    <P>In addition, one copy of any comments submitted to the FAA must be mailed or delivered to The Honorable Selina Jayne-Dornan, Mayor of Eufaula at the following address: City of Eufaula, Oklahoma, 64 Memorial Drive, Eufaula, OK 74432.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mrs Kathy Franklin, Program Manager, Federal Aviation Administration, AR/OK Airports Development Office, ASW-630, 2601 Meacham Blvd., Fort Worth, Texas 76137.</P>
                    <P>The request to release property may be reviewed in person at this same location.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FAA invites public comment on the request to release property at the Eufaula Municipal Airport under the provisions of the AIR 21.</P>
                <P>On November 18, 2014, the FAA determined that the request to release property at Eufaula Municipal Airport submitted by the City of Eufaula met the procedural requirements of the Federal aviation Regulations, Part 155. The FAA may approve the request, in whole or in part, no later than January, 2015.</P>
                <P>
                    The following is a brief overview of the request: The City of Eufaula requests the release of 14.68 acres of airport property valued at $29,360.00. The release of property will allow for the sale of the property to the Oklahoma Department of Transportation for the development of an industrial facility for maintenance activities. The City of Eufaula will use the $29,360.00 
                    <PRTPAGE P="72240"/>
                    resulting from the sale to fund construction of a pilots lounge and restrooms which are not presently available at the airport.
                </P>
                <P>
                    Any person may inspect the request in person at the FAA office listed above under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <P>In addition, any person may, upon request, inspect the application, notice and other documents germane to the application in person at the Eufaula Municipal Airport.</P>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on November 18, 2014.</DATED>
                    <NAME>Byron K. Huffman,</NAME>
                    <TITLE>Acting Manager, Airports Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28611 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Office of Commercial Space Transportation; Amended Waiver for Launch and Mission Risk</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of amended waiver.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                         This notice concerns an amendment to a waiver related to the launch and reentry of an Orion Multi-Purpose Crew Vehicle. On March 10, 2014, the FAA issued United Launch Alliance (ULA) and Lockheed Martin (Lockheed) waivers to certain risk requirements of the FAA's regulations. Since that time, changes to the mission's flight plan have increased its risk profile. After analyzing this updated risk profile, the FAA finds that the analysis underlying the original waiver decisions still applies. The FAA, therefore, amends its original waiver to permit launch risk from debris of 217 × 10
                        <E T="51">−6</E>
                         and total mission risk from debris of up to 218 × 10
                        <E T="51">−6</E>
                        .
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         For technical questions concerning this waiver, contact Charles P. Brinkman, Aerospace Engineer, AST-200, Office of Commercial Space Transportation (AST), Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-7715; email: 
                        <E T="03">phil.brinkman@faa.gov.</E>
                         For legal questions concerning this waiver, contact Benjamin Jacobs, Attorney-Advisor, Regulations Division (AGC-210), Office of the Chief Counsel, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-7240; email: 
                        <E T="03">benjamin.jacobs@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>Lockheed and ULA are private commercial space flight companies. Lockheed entered into a contract with the National Aeronautics and Space Administration (NASA) to provide the first orbital flight test for NASA's Orion Multi-Purpose Crew Vehicle (Orion) Program. Lockheed has contracted with ULA to provide launch services for the mission.</P>
                <P>The FAA is responsible for licensing, among other things, the launch of a launch vehicle and the reentry of a reentry vehicle, under authority granted to the Secretary of Transportation by 51 U.S.C. Subtitle V, chapter 509 (Chapter 509), and delegated to the FAA's Administrator and Associate Administrator for Commercial Space Transportation.</P>
                <P>
                    The mission at issue in this notice is Orion Exploration Flight Test 1, which is scheduled to launch from Cape Canaveral Air Force Station in Florida in early December. The mission tests the Orion Multi-Purpose Crew Vehicle in an un-crewed, limited-capability configuration, and serves as a stepping stone towards a crew-capable vehicle that would enable human exploration missions beyond Earth orbit. The mission is comprised of a launch, which is conducted by ULA, and a reentry, which is conducted by Lockheed. The launch vehicle is ULA's Delta IV Heavy launch vehicle, which consists of a Common Booster Core (CBC) as the first stage with two additional strap-on CBCs and a Delta IV Cryogenic Second Stage (DCSS). The first burn of the DCSS places the Orion and the DCSS in orbit, and a second DCSS burn places the Orion into a highly elliptical, negative-perigee trajectory, to simulate the thermal conditions and high reentry speeds the module would experience returning from missions beyond Earth orbit. After separating from the DCSS, the Orion module reenters over the eastern Pacific Ocean, splashing down 231 nautical miles west of Baja California, Mexico.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         We note that, due to the unique characteristics of this mission, FAA regulations require us to account for risks that are typically not included in our § 417.107 analysis—namely, the uncontrolled reentry of an upper stage after orbital insertion.
                    </P>
                </FTNT>
                <P>
                    Section 417.107(b)(1) of Title 14 of the Code of Federal Regulations (14 CFR) prohibits, in relevant part, the launch of a launch vehicle if the expected casualty (E
                    <E T="52">c</E>
                    ) rate for the flight exceeds 30 × 10
                    <E T="51">−6</E>
                     for impacting inert and explosive debris (debris). Section 435.35 establishes acceptable risk for reentry vehicles, and requires operators to comply with §§ 431.35(a) and 431.35(b)(1)(i),
                    <SU>2</SU>
                    <FTREF/>
                     which in turn prohibit an E
                    <E T="52">c</E>
                     for debris in excess of 30 × 10
                    <E T="51">−6</E>
                     for both launch and reentry combined.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Although the module is a reentry vehicle and not a reusable launch vehicle, 14 CFR 435.33 incorporates and applies § 431.43 to all reentry vehicles.
                    </P>
                </FTNT>
                <P>
                    On February 27, 2014, ULA petitioned the FAA for waivers of these provisions because the projected risk from debris during launch was 164 × 10
                    <E T="51">− 6</E>
                    , and the projected risk from debris during reentry was less than 1 × 10
                    <E T="51">−6</E>
                    —for a total-mission debris risk of approximately 165 × 10
                    <E T="51">−6</E>
                    . The FAA issued a waiver and, on March 10, 2014, gave notice in the 
                    <E T="04">Federal Register</E>
                    . 
                    <E T="03">Notice of Waiver</E>
                    , Mar. 10, 2014 (79 FR 13375). This initial waiver allowed a maximum-allowable E
                    <E T="52">c</E>
                     value for ULA and Lockheed's proposed mission of 165 × 10
                    <E T="51">−6</E>
                    ,
                    <SU>3</SU>
                    <FTREF/>
                     based on the risk increase the launch operators requested.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Our March 2014 Notice correctly identified the total mission debris risk as 165 × 10
                        <E T="51">−6</E>
                        , but when breaking down the sources of that risk, we listed four risk factors adding up to a total of only 164 × 10
                        <E T="51">−6</E>
                        . 79 FR at 13376. This breakdown mistakenly omitted the debris risk related from controlled disposal of the upper stage, with an E
                        <E T="52">c</E>
                         of &lt; 1 × 10
                        <E T="51">−6</E>
                        .
                    </P>
                </FTNT>
                <P>
                    On November 3, 2014, ULA and Lockheed transmitted to the FAA the mission's final trajectory and an updated risk analysis. Since that time, ULA and Lockheed have continued to submit updated risk information, as it becomes available, to the FAA. According to these documents, it is necessary for ULA and Lockheed to modify the mission's launch trajectory, for two reasons: To lower the mission's maximum heating temperature constraint, and to adjust the flight azimuth to be the same as what was flown in previous missions. On November 20, 2014, in light of the changed mission trajectory, ULA petitioned for an amendment to its waiver to allow an E
                    <E T="52">c</E>
                     of 207 × 10
                    <E T="51">−6</E>
                     for debris from launch. On November 21, 2014, Lockheed petitioned for an amendment to its waiver to allow total mission risk of 208 × 10
                    <E T="51">−6</E>
                    .
                </P>
                <P>
                    Using ULA's updated trajectory, the FAA calculates the debris-related E
                    <E T="52">c</E>
                     for failure during the de-orbit burn, after the first 120 seconds, increases to 76 × 10
                    <E T="51">−6</E>
                     from 53 × 10
                    <E T="51">−6</E>
                    . In addition, calculations by the FAA and the United States Air Force indicate an increased debris risk, from launch to orbital insertion, of approximately 30 × 10
                    <E T="51">−6</E>
                     above original estimates. As a result, the FAA calculates that overall launch risk increases from 164 × 10
                    <E T="51">−6</E>
                     to 217 × 10
                    <E T="51">−6</E>
                    , and total mission risk increases from 165 × 10
                    <E T="51">−6</E>
                     to 218 × 10
                    <E T="51">−6</E>
                    . The FAA believes these risk figures best 
                    <PRTPAGE P="72241"/>
                    capture the uncertainties due to weather and the inability to perform significant mitigation at the launch site on the day of launch.
                </P>
                <HD SOURCE="HD1">A. Analysis of the Updated Risk Assessment</HD>
                <P>
                    The FAA's original waiver analyzed ULA and Lockheed's proposals using the waiver criteria established by our statutory and regulatory framework. Section 50905(b)(3) allows the FAA to waive a license requirement if the waiver (1) will not jeopardize public health and safety, and safety of property; (2) is in the public interest; and (3) will not jeopardize national security and foreign policy interests of the United States. 
                    <E T="03">See also</E>
                     49 CFR 404.5(b). We reapply those same criteria here.
                </P>
                <HD SOURCE="HD2">1. Public Health and Safety, and Safety of Property</HD>
                <P>
                    The FAA's initial waiver examined ULA and Lockheed's proposal in comparison with the historically acceptable launch risk levels at other Federal agencies to determine whether the mission would fall within those parameters. The rationale for our approval of ULA and Lockheed's prior waiver requests applies equally to their revised risk assessment. Although the FAA's regulations prohibit debris risk in excess of 30 × 10
                    <E T="51">−6</E>
                    , a waiver is warranted in this case because the United States Government's experience conducting other space missions with risk in excess of 100 × 10
                    <E T="51">−6</E>
                     demonstrates that the risks of this mission are consistent with the public health and safety, and the safety of property. As we stated in our March 10, 2014, 
                    <E T="03">Notice of Waiver,</E>
                     the United States Government has repeatedly accepted risk for government launches in excess of the FAA's 30 × 10
                    <E T="51">−6</E>
                    , without negative consequences for safety. 79 FR at 13376. The Space Shuttle, for example, used a debris risk criterion of 200 × 10
                    <E T="51">−6</E>
                     for launch risk to the public. 
                    <E T="03">See</E>
                     NASA's Implementation Plan for Space Shuttle Return to Flight and Beyond, Vol. 1 Final Edition, at 2-39 (May 15, 2007). In addition, in 2005, the U.S. Air Force accepted risk levels in a government launch ranging from 145 to 317 × 10
                    <E T="51">−6</E>
                    . Dept. of the Air Force Memorandum, Overflight Risk Exceedance Waiver for Titan IV B-30, Mission (Apr. 4, 2005).
                </P>
                <P>
                    ULA's updated launch risk of 217 × 10
                    <E T="51">−6</E>
                     is still less than the risk levels previously approved for a government launch. Accordingly, granting a waiver of §§ 417.107(b)(1) and 431.35(b)(1)(i) in this case does not jeopardize the public health and safety, or the safety of property.
                </P>
                <HD SOURCE="HD2">2. Public Interest</HD>
                <P>The FAA looks to its enabling statute to determine how Congress has defined the public interest. The FAA implements the agency's statutory mandate to encourage the development of commercial space capabilities and the continuous improvement of the safety of launch vehicles designed to carry passengers. 51 U.S.C. 50901(b).</P>
                <P>As with their initial petition, ULA and Lockheed's petition for an amended waiver are consistent with the public interest because the test flight is necessary to the development of NASA's human-missions capability beyond Earth orbit.</P>
                <HD SOURCE="HD1">D. National Security and Foreign Policy Interests</HD>
                <P>The FAA has not identified any national security or foreign policy implications associated with amending this waiver.</P>
                <HD SOURCE="HD1">Summary and Conclusion</HD>
                <P>
                    The FAA determines that amending the waivers associated with this mission will not jeopardize public health and safety or safety of property. In addition, amending the waivers is in the public interest because it accomplishes the goals of Chapter 509 and does not unduly increase risk to the public. Finally, amending the waivers will not jeopardize national security and foreign policy interests of the United States. The FAA therefore amends its prior waivers of the requirements of 14 CFR 417.107(b)(1) and 431.35(b)(1)(i) for launch and mission risk, respectively, to allow launch risk of an E
                    <E T="52">c</E>
                     of 217 × 10
                    <E T="51">−6</E>
                     and total mission risk of 218 × 10
                    <E T="51">−6</E>
                    .
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on November 26, 2014.</DATED>
                    <NAME>Kenneth Wong,</NAME>
                    <TITLE>Licensing and Evaluation Division Manager.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28614 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Railroad Administration</SUBAGY>
                <DEPDOC>[Docket No. FRA-2014-0011-N-22]</DEPDOC>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Railroad Administration (FRA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the Paperwork Reduction Act of 1995, this notice announces that the renewal Information Collection Requests (ICR) abstracted below are being forwarded to the Office of Management and Budget (OMB) for review and comment. The ICR describes the nature of the information collection and its expected burden. The 
                        <E T="04">Federal Register</E>
                         notice with a 60-day comment period soliciting comments on the following collection of information was published on September 5, 2014 (79 FR 56616).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before January 5, 2015.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Robert Brogan, Office of Planning and Evaluation Division, RRS-21, Federal Railroad Administration, 1200 New Jersey Ave. SE., Mail Stop 25, Washington, DC 20590 (Telephone: (202) 493-6292), or Ms. Kimberly Toone, Office of Information Technology, RAD-20, Federal Railroad Administration, 1200 New Jersey Ave. SE., Mail Stop 35, Washington, DC 20590 (Telephone: (202) 493-6132). (These telephone numbers are not toll-free.)</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Paperwork Reduction Act of 1995 (PRA), Public Law 104-13, sec. 2, 109 Stat. 163 (1995) (codified as revised at 44 U.S.C. 3501-3520), and its implementing regulations, 5 CFR part 1320, require Federal agencies to issue two notices seeking public comment on information collection activities before OMB may approve paperwork packages. 44 U.S.C. 3506, 3507; 5 CFR 1320.5, 1320.8(d)(1), 1320.12. On September 5, 2014, FRA published a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     soliciting comment on ICR that the agency is seeking OMB approval. 
                    <E T="03">See</E>
                     79 FR 56616. FRA received no comments in response to this notice.
                </P>
                <P>
                    Before OMB decides whether to approve these proposed collections of information, it must provide 30 days for public comment. 44 U.S.C. 3507(b); 5 CFR 1320.12(d). Federal law requires OMB to approve or disapprove paperwork packages between 30 and 60 days after the 30 day notice is published. 44 U.S.C. 3507 (b)-(c); 5 CFR 1320.12(d); 
                    <E T="03">see also</E>
                     60 FR 44978, 44983, Aug. 29, 1995. OMB believes that the 30 day notice informs the regulated community to file relevant comments and affords the agency adequate time to digest public comments before it renders a decision. 60 FR 44983, Aug. 29, 1995. Therefore, respondents should submit their respective comments to OMB within 30 days of publication to best ensure having their full effect. 5 
                    <PRTPAGE P="72242"/>
                    CFR 1320.12(c); 
                    <E T="03">see also</E>
                     60 FR 44983, Aug. 29, 1995.
                </P>
                <P>The summary below describes the nature of the information collection request (ICR) and the expected burden. The revised request is being submitted for clearance by OMB as required by the PRA.</P>
                <P>
                    <E T="03">Title:</E>
                     Identification of Cars Moved in Accordance with Order 13528.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2130-0506.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This collection of information identifies a freight car being moved within the scope of Order 13528 (now codified at under 49 CFR 232.3). Otherwise, an exception will be taken, and the car will be set out of the train and not delivered. The information that must be recorded is specified at 49 CFR 232.3(d)(3), which requires that a car be properly identified by a card attached to each side of the car and signed stating that such movement is being made under authority of the Order. Section 232.2(d)(3) does not require retaining cards or tags. When a car bearing a tag for movement under this provision arrives at its destination, the tags are simply removed. This requirement/record comes into play only when a railroad finds it necessary to move equipment as specified above. FRA estimates that approximately 400 cars per year are moved under this Order. 
                </P>
                <P>
                    <E T="03">Request:</E>
                     Extension without change of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses (Railroads).
                </P>
                <P>
                    <E T="03">Form(s):</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Annual Estimated Burden:</E>
                     67 hours.
                </P>
                <P>
                    <E T="03">Title:</E>
                     U.S. Locational Requirement for Dispatching U.S. Rail Operations.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2130-0556.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Part 241 requires, in the absence of a waiver, that all dispatching of railroad Operations that occurs in the United States be performed in this country, with a minor exception. A railroad is allowed to conduct extraterritorial dispatching from Mexico or Canada in emergency situations, but only for the duration of the emergency. A railroad relying on the exception must provide written notification of its action to the FRA Regional Administrator of each FRA region in which the railroad operation occurs; such notification is not required before addressing the emergency situation. The information collected under this rule will be used as part of FRA's oversight function to ensure that extraterritorial dispatchers comply with applicable safety regulations.
                </P>
                <P>
                    <E T="03">Request:</E>
                     Extension without change of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses (Railroads).
                </P>
                <P>
                    <E T="03">Form(s):</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Annual Estimated Burden:</E>
                     8 hours.
                </P>
                <P>
                    <E T="03">Addressee:</E>
                     Send comments regarding this information collections to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 Seventeenth Street NW., Washington, DC 20503, Attention: FRA Desk Officer. Comments may also be sent via email to OMB at the following address: 
                    <E T="03">oira_submissions@omb.eop.gov.</E>
                </P>
                <P>
                    <E T="03">Comments are invited on the following:</E>
                     Whether the proposed collections of information are necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; the accuracy of the Department's estimates of the burden of the proposed information collections; ways to enhance the quality, utility, and clarity of the information to be collected; and ways to minimize the burden of the collections of information on respondents, including the use of automated collection techniques or other forms of information technology.
                </P>
                <P>
                    A comment to OMB is best assured of having its full effect if OMB receives it within 30 days of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 44 U.S.C. 3501-3520.</P>
                </AUTH>
                <SIG>
                    <DATED>Issued in Washington, DC, on December 1, 2014.</DATED>
                    <NAME>Rebecca Pennington,</NAME>
                    <TITLE>Chief Financial Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28506 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Railroad Administration</SUBAGY>
                <DEPDOC>[Docket Number FRA-2009-0074]</DEPDOC>
                <SUBJECT>Petition for Waiver of Compliance</SUBJECT>
                <P>In accordance with Part 211 of Title 49 Code of Federal Regulations, this document provides the public notice that by a document dated October 14, 2014, the Canadian National Railway Company (CN), Brotherhood of Locomotive Engineers and Trainmen (BLET), and International Association of Sheet Metal, Air, Rail and Transportation  Workers (SMART), have jointly petitioned the Federal Railroad Administration (FRA) for an extension of their waiver of compliance from certain provisions of the Federal hours of service laws contained at 49 U.S.C. 21103(a)(4). FRA assigned the petition Docket Number FRA-2009-0074.</P>
                <P>In their petition, CN, BLET, and SMART seek relief from 49 U.S.C. 21103(a)(4), which, in part, requires a train employee to receive 48 hours off duty after initiating an on-duty period for 6 consecutive days. Specifically, CN, BLET, and SMART seek a waiver to allow a train employee to initiate an on-duty period, each day, for 6 consecutive days followed by 24 hours off duty. In support of the request, CN, BLET, and SMART explained that CN has operated these schedules of 6 consecutive on-duty periods followed by 24 hours off duty successfully since 2002. CN, BLET, and SMART indicate that these schedules have not had an adverse impact on safety.</P>
                <P>CN provided work schedules for the employees covered by the waiver, which shows them reporting for work within pre-set 4-hour calling spreads with a regular rest day. CN also provided an analysis of the most current 12-month period of train-employee on-duty human factor-related accidents and injuries. CN indicates that its analyses revealed that of the 22 human factor-related accidents involving CN employees in the preceding 12 months, none involved employees covered under the waiver working 6 consecutive days followed by 24 hours off duty. Finally, CN said that all employees covered by the waiver were provided information about the waiver extension petition, and that there were no objections to the waiver extension by these employees.</P>
                <P>
                    A copy of the petition, as well as any written communications concerning the petition, is available for review online at 
                    <E T="03">www.regulations.gov</E>
                     and in person at the U.S. Department of Transportation's (DOT) Docket Operations Facility, 1200 New Jersey Avenue SE., W12-140, Washington, DC 20590. The Docket Operations Facility is open from 9 a.m. to 5 p.m., Monday through Friday, except Federal Holidays.
                </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request.</P>
                <P>All communications concerning these proceedings should identify the appropriate docket number and may be submitted by any of the following methods:</P>
                <P>
                    • 
                    <E T="03">Web site:</E>
                      
                    <E T="03">http://www.regulations.gov.</E>
                     Follow the online instructions for submitting comments.
                </P>
                <P>
                    • 
                    <E T="03">Fax:</E>
                     202-493-2251.
                    <PRTPAGE P="72243"/>
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Docket Operations Facility, U.S. Department of Transportation, 1200 New Jersey Avenue SE., W12-140, Washington, DC 20590.
                </P>
                <P>
                    • 
                    <E T="03">Hand Delivery:</E>
                     1200 New Jersey Avenue SE., Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal Holidays.
                </P>
                <P>Communications received by January 20, 2015 will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable.</P>
                <P>
                    Anyone is able to search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the document, if submitted on behalf of an association, business, labor union, etc.). In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its processes. DOT posts these comments, without edit, including any personal information the commenter provides, to 
                    <E T="03">www.regulations.gov,</E>
                     as described in the system of records notice (DOT/ALL-14 FDMS), which can be viewed at 
                    <E T="03">www.dot.gov/privacy.</E>
                     See also 
                    <E T="03">http://www.regulations.gov/#!privacyNotice</E>
                     for the privacy notice of regulations.gov.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on December 1, 2014.</DATED>
                    <NAME>Ron Hynes,</NAME>
                    <TITLE>Director, Office of Technical Oversight.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28518 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. DOT-NHTSA-2014-0122]</DEPDOC>
                <SUBJECT>Notice and Request for Comments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Transportation (DOT) invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. Before a Federal agency can collect certain information from the public, it must receive approval from the Office of Management and Budget (OMB). Under procedures established by the Paperwork Reduction Act of 1995, before seeking OMB approval, Federal agencies must solicit public comment on proposed collections of information, including extensions and reinstatement of previously approved collections.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments [identified by Docket No. DOT-OST-200X-XXXX] through one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         1-202-493-2251
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Docket Management Facility, U.S. Department of Transportation, 1200 New Jersey Avenue SE., West Building, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except on Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Walter Culbreath, 202-366-1566, Office of the Chief Information Officer, U.S. Department of Transportation, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2127-0682
                </P>
                <P>
                    <E T="03">Title:</E>
                     Generic Clearance for the Collection of Qualitative Feedback on Agency Service Delivery
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The proposed information collection activity provides a means to garner qualitative customer and stakeholder feedback in an efficient, timely manner, in accordance with the Administration's commitment to improving service delivery.
                </P>
                <P>This feedback will provide insights into customer or stakeholder perceptions, experiences and expectations, provide an early warning of issues with service, or focus attention on areas where communication, training or changes in operations might improve delivery of products or services. These collections will allow for ongoing, collaborative and actionable communications between the Agency and its customers and stakeholders. It will also allow feedback to contribute directly to the improvement of program management.</P>
                <P>The solicitation of feedback will target areas such as: Timeliness, appropriateness, accuracy of information, courtesy, efficiency of service delivery, and resolution of issues with service delivery. Responses will be assessed to plan and inform efforts to improve or maintain the quality of service offered to the public. If this information is not collected, vital feedback from customers and stakeholders on the Agency's services will be unavailable.</P>
                <P>The Agency will only submit a collection for approval under this generic clearance if it meets the following conditions:</P>
                <P>• The collections are voluntary;</P>
                <P>• The collections are low-burden for respondents (based on considerations of total burden hours, total number of respondents, or burden-hours per respondent) and are low-cost for both the respondents and the Federal Government;</P>
                <P>• The collections are non-controversial and do not raise issues of concern to other Federal agencies;</P>
                <P>• Any collection is targeted to the solicitation of opinions from respondents who have experience with the program or may have experience with the program in the near future;</P>
                <P>• Personally identifiable information (PII) is collected only to the extent necessary and is not retained;</P>
                <P>• Information gathered is intended to be used only internally for general service improvement and program management purposes and is not intended for release outside of the agency (if released, the agency must indicate the qualitative nature of the information);</P>
                <P>• Information gathered will not be used for the purpose of substantially informing influential policy decisions; and</P>
                <P>• Information gathered will yield qualitative information; the collections will not be designed or expected to yield statistically reliable results or used as though the results are generalizable to the population of study.</P>
                <P>
                    Feedback collected under this generic clearance provides useful information, but it does not yield data that can be generalized to the overall population. This type of generic clearance for qualitative information will not be used for quantitative information collections that are designed to yield reliably actionable results, such as monitoring trends over time or documenting program performance. Such data uses require more rigorous designs that address: The target population to which generalizations will be made, the sampling frame, the sample design (including stratification and clustering), the precision requirements or power calculations that justify the proposed sample size, the expected response rate, methods for assessing potential non-response bias, the protocols for data collection, and any testing procedures that were or will be undertaken prior to fielding the study. Depending on the degree of influence the results are likely to have, such collections may still be 
                    <PRTPAGE P="72244"/>
                    eligible for submission for other generic mechanisms that are designed to yield quantitative results.
                </P>
                <P>As a general matter, information collections will not result in any new system of records containing privacy information and will not ask questions of a sensitive nature, such as sexual behavior and attitudes, religious beliefs, and other matters that are commonly considered private.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals and Households, Businesses and Organizations, State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Estimated number of Respondents:</E>
                     162,350.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Once per request.
                </P>
                <P>
                    <E T="03">Number of Responses:</E>
                     162,350.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     83,191.
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for the Department's performance; (b) the accuracy of the estimated burden; (c) ways for the Department to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized without reducing the quality of the collected information. The agency will summarize and/or include your comments in the request for OMB's clearance of this information collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; and 49 CFR 1:48.</P>
                </AUTH>
                <SIG>
                    <NAME>Kevin Mahoney,</NAME>
                    <TITLE>Director, Office of Corporate Customer Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28542 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Surface Transportation Board</SUBAGY>
                <DEPDOC>[Docket No. FD 35877]</DEPDOC>
                <SUBJECT>Genesee &amp; Wyoming Inc.—Acquisition of Control Exemption (Including Existing Interchange Commitment)—Arkansas Midland Railroad Company, Inc., The Prescott and Northwestern Railroad Company, and Warren &amp; Saline River Railroad Company </SUBJECT>
                <P>
                    Genesee &amp; Wyoming Inc. (GWI),
                    <SU>1</SU>
                    <FTREF/>
                     a publicly traded non-carrier holding company, has filed a verified notice of exemption pursuant to 49 CFR 1180.2(d)(2), to acquire control of the following Class III rail carriers: Arkansas Midland Railroad Company, Inc. (AKMD), The Prescott and Northwestern Railroad Company (PNW), and Warren &amp; Saline Railroad Company (WSR) (collectively, the Acquired Railroads).
                    <SU>2</SU>
                    <FTREF/>
                     The Acquired Railroads are currently owned and under the common control of Pinsly Railroad Company (Pinsly).
                    <SU>3</SU>
                    <FTREF/>
                     GWI has submitted to the Board a redacted, public version of its Stock Purchase Agreement with Pinsly.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Most recently, GWI was authorized to control Rapid City, Pierre &amp; Eastern Railroad, Inc. (RCP&amp;E), in common control with other carriers in GWI's corporate family, upon RCP&amp;E's becoming a Class II carrier. 
                        <E T="03">See Genesee &amp; Wyo. Inc.—Continuance in Control Exemption—Rapid City, Pierre &amp; E. R.R.,</E>
                         FD 35800 (STB served Mar. 27, 2014). GWI provides with its verified notice of exemption a map showing the locations of the GWI-controlled railroads.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         AKMD connects with WSR at Warren, Ark. 
                        <E T="03">See Pinsly R.R.—Control Exemption—Warren &amp; Saline River R.R.,</E>
                         FD 35293 (STB served Nov. 3, 2009). The Board has previously issued notices of exemption under 49 CFR 1180.2(d)(2) where some of the railroads to be acquired connect with each other. 
                        <E T="03">See, e.g.,</E>
                          
                        <E T="03">SteelRiver Infrastructure Partners—Control Exemption—Patriot Rail</E>
                         (
                        <E T="03">SteelRiver</E>
                        ), FD 35622 (STB served May 23, 2012); 
                        <E T="03">Patriot Woods R.R.—Acquis. &amp; Operation Exemption—Weyerhaeuser NR Co., Weyerhaeuser Woods R.R. Operating Div.,</E>
                         FD 35431 (STB served Nov. 5, 2010) (authorizing two of the railroads later involved in 
                        <E T="03">SteelRiver</E>
                         to connect with each other).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Acquired Railroads own and operate rail lines solely within the State of Arkansas.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         With its verified notice of exemption, GWI filed under seal an unredacted version of its Stock Purchase Agreement and a motion for protective order to allow limited access to that agreement and other materials GWI has filed under seal. That motion is being addressed separately.
                    </P>
                </FTNT>
                <P>
                    GWI states that: (1) The Acquired Railroads do not connect with any of GWI's subsidiary railroads; 
                    <SU>5</SU>
                    <FTREF/>
                     (2) the proposed transaction is not part of a series of anticipated transactions to connect the Acquired Railroads and any of GWI's subsidiary railroads; and (3) the proposed transaction does not involve a Class I rail carrier. The proposed transaction is therefore exempt from the prior approval requirements of 49 U.S.C. 11323 pursuant to 49 CFR 1180.2(d)(2).
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         According to GWI, AKMD and one of GWI's existing subsidiaries, Little Rock &amp; Western Railway, L.P. (LRWN) both interchange with Union Pacific Railroad Company (UP) in the same yard in Little Rock, Ark. GWI states, however, that neither AKMD nor LRWN have the right to use any UP facilities to connect with each other.
                    </P>
                </FTNT>
                <P>Through its verified notice of exemption, GWI seeks to acquire all of the issued and outstanding stock of the Acquired Railroads from Pinsly. GWI states that the proposed transaction would allow the Acquired Railroads to take advantage of the administrative, financial, marketing, and operational support that GWI could provide, which would, in turn, promote the ability of the Acquired Railroads to provide safe and efficient service to their shippers. GWI claims that, although the Acquired Railroads do not connect with any of the railroads already controlled by GWI, the newly acquired railroads will expand the presence of GWI's affiliates in Arkansas.</P>
                <P>
                    GWI states that no interchange commitment is being imposed as part of this transaction but that one of the Acquired Railroads, AKMD, has an existing lease agreement with UP that includes an interchange commitment.
                    <SU>6</SU>
                    <FTREF/>
                     GWI notes that this existing commitment is part of AKMD's lease of several lines from UP 
                    <SU>7</SU>
                    <FTREF/>
                     and was negotiated as part of the overall economic package in the original lease transactions. Because GWI is acquiring control of AKMD through a stock purchase, GWI states that there will be no effect on AKMD's operating rights under the UP Lease.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         GWI states that it does not believe that the Board's interchange commitment disclosure requirements are intended to apply to equity control transactions in which no new interchange commitment is being imposed as part of the transaction. Without waiving that argument, GWI provides, in its verified notice and a confidential appendix, information about the interchange commitment that GWI notes “would be required” under 49 CFR 1180.4(g)(4)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Under this lease, as supplemented (UP Lease), AKMD operates the North Little Rock Branch in North Little Rock, the Warren Branch between Dermott and Warren, and the Cypress Bend Branch between McGehee and Cypress Bend. 
                        <E T="03">See also Ark. Midland R.R.—Lease &amp; Operation Exemption—Union Pac. R.R.,</E>
                         FD 33908 (STB served Aug. 23, 2000); 
                        <E T="03">Ark. Midland R.R.—Change in Operators Exemption—Line of Union Pac. R.R.,</E>
                         FD 34567 (STB served Nov. 17, 2004); and 
                        <E T="03">Ark. Midland R.R.—Lease &amp; Operation Exemption—Union Pac. R.R.,</E>
                         FD 34714 (STB served Aug. 30, 2005).
                    </P>
                </FTNT>
                <P>The earliest the transaction could be consummated is December 20, 2014, the effective date of the exemption (30 days after the exemption was filed). The parties expect to consummate the transaction shortly after the exemption becomes effective, assuming all other conditions to closing have been satisfied by that time.</P>
                <P>
                    Under 49 U.S.C. 10502(g), the Board may not use its exemption authority to relieve a rail carrier of its statutory obligation to protect the interests of its employees. Because the transaction involves the control of one or more Class III rail carriers and two Class II rail carriers, the transaction is subject to the labor protective requirements of 49 U.S.C. 11326(a) and 
                    <E T="03">New York Dock Railway—Control—Brooklyn Eastern District Terminal,</E>
                     360 I.C.C. 60 (1979).
                </P>
                <P>
                    If the verified notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                     Petitions to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the effectiveness of the exemption. Petitions to stay must be filed by December 12, 2014 (at least 
                    <PRTPAGE P="72245"/>
                    seven days before the exemption becomes effective).
                </P>
                <P>An original and ten copies of all pleadings, referring to Docket No. FD 35877, must be filed with the Surface Transportation Board, 395 E Street SW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on: Eric M. Hocky, Clark Hill PLC, One Commerce Square, 2005 Market Street, Suite 1000, Philadelphia, PA 19103.</P>
                <P>
                    Board decisions and notices are available on our Web site at 
                    <E T="03">WWW.STB.DOT.GOV.</E>
                </P>
                <SIG>
                    <DATED>Decided: December 2, 2014.</DATED>
                    <P>By the Board, Rachel D. Campbell, Director, Office of Proceedings.</P>
                    <NAME>Raina S. White,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2014-28571 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Revision of an Approved Information Collection; Comment Request; Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions With Total Consolidated Assets of $50 Billion or More Under the Dodd-Frank Wall Street Reform and Consumer Protection Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency, Treasury (OCC). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P> The OCC, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to comment on a revision to this information collection, as required by the Paperwork Reduction Act of 1995. An agency may not conduct or sponsor, and a respondent is not required to respond to, an information collection unless it displays a currently valid Office of Management and Budget (OMB) control number. Currently, the OCC is soliciting comment concerning a revision to a regulatory reporting requirement for national banks and Federal savings associations titled, “Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions with Total Consolidated Assets of $50 Billion or More under the Dodd-Frank Wall Street Reform and Consumer Protection Act.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2015. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                         Communications Division, Office of the Comptroller of the Currency, Mailstop 2-3, Attention: 1557-0319, 400 7th St. SW., Washington, DC 20219. In addition, comments may be sent by fax to (571) 465-4326 or by electronic mail to 
                        <E T="03">regs.comments@occ.treas.gov.</E>
                         You may personally inspect and photocopy comments at the OCC, 400 7th St. SW., Washington, DC 20219. For security reasons, the OCC requires that visitors make an appointment to inspect comments. You may do so by calling (202) 649-6700. Upon arrival, visitors will be required to present valid government-issued photo identification and to submit to security screening in order to inspect and photocopy comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        You can request additional information from Johnny Vilela or Mary H. Gottlieb, OCC Clearance Officers, (202) 649-5490, for persons who are deaf or hard of hearing, TTY, (202) 649-5597, Legislative and Regulatory Activities Division, Office of the Comptroller of the Currency, 400 7th St. SW., Washington, DC 20219. In addition, copies of the templates referenced in this notice can be found on the OCC's Web site under News and Issuances (
                        <E T="03">http://www.occ.treas.gov/tools-forms/forms/bank-operations/stress-test-reporting.html</E>
                        ).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The OCC is requesting comment on the following revision to an approved information collection:</P>
                <P>
                    <E T="03">Title:</E>
                     Company-Run Annual Stress Test Reporting Template and Documentation for Covered Institutions with Total Consolidated Assets of $50 Billion or More under the Dodd-Frank Wall Street Reform and Consumer Protection Act.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1557-0319.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Section 165(i)(2) of the Dodd-Frank Wall Street Reform and Consumer Protection Act 
                    <SU>1</SU>
                    <FTREF/>
                     (Dodd-Frank Act) requires certain financial companies, including national banks and Federal savings associations, to conduct annual stress tests 
                    <SU>2</SU>
                    <FTREF/>
                     and requires the primary financial regulatory agency 
                    <SU>3</SU>
                    <FTREF/>
                     of those financial companies to issue regulations implementing the stress test requirements.
                    <SU>4</SU>
                    <FTREF/>
                     A national bank or Federal savings association is a “covered institution” and therefore subject to the stress test requirements if its total consolidated assets are more than $10 billion. Under section 165(i)(2), a covered institution is required to submit to the Board of Governors of the Federal Reserve System (Board) and to its primary financial regulatory agency a report at such time, in such form, and containing such information as the primary financial regulatory agency may require.
                    <SU>5</SU>
                    <FTREF/>
                     On October 9, 2012, the OCC published in the 
                    <E T="04">Federal Register</E>
                     a final rule implementing the section 165(i)(2) annual stress test requirement.
                    <SU>6</SU>
                    <FTREF/>
                     This rule describes the reports and information collections required to meet the reporting requirements under section 165(i)(2). These information collections will be given confidential treatment (5 U.S.C. 552(b)(4)).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Pub. L. 111-203, 124 Stat. 1376, July 2010.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         12 U.S.C. 5365(i)(2)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         12 U.S.C. 5301(12).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         12 U.S.C. 5365(i)(2)(C).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         12 U.S.C. 5365(i)(2)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         77 FR 61238 (October 9, 2012).
                    </P>
                </FTNT>
                <P>
                    In 2012, the OCC first implemented the reporting templates referenced in the final rule. 
                    <E T="03">See</E>
                     77 FR 49485 (August 16, 2012) and 77 FR 66663 (November 6, 2012). The OCC is now revising them as described below. The OCC proposed these revisions on September 10, 2014.
                    <SU>7</SU>
                    <FTREF/>
                     The OCC received one comment and is adopting the revisions as final, with some adjustments described below.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         79 FR 53835.
                    </P>
                </FTNT>
                <P>The OCC intends to use the data collected to assess the reasonableness of the stress test results of covered institutions and to analyze forward-looking regarding a covered institution's capital adequacy. The OCC also may use the results of the stress tests to determine whether additional analytical techniques and exercises could be appropriate to identify, measure, and monitor risks at the covered institution. The stress test results are expected to support ongoing improvement in a covered institution's stress testing practices with respect to its internal assessments of capital adequacy and overall capital planning.</P>
                <P>
                    The OCC recognizes that many covered institutions with total consolidated assets of $50 billion or more are required to submit reports using the Comprehensive Capital Analysis and Review (CCAR) reporting form FR Y-14A.
                    <SU>8</SU>
                    <FTREF/>
                     The OCC also recognizes the Board has modified the FR Y-14A reporting form, and to the extent practical the OCC will keep its reporting requirements consistent with the Board's FR Y-14A in order to minimize burden on covered institutions.
                    <SU>9</SU>
                    <FTREF/>
                     Therefore, the OCC is revising its reporting requirements to remain consistent with the Board's FR Y-14A for covered institutions with total consolidated assets of $50 billion 
                    <PRTPAGE P="72246"/>
                    or more. Furthermore, the OCC is revising the Scenario schedule, which collects information on scenario variables beyond those provided by regulators. The purpose of this revision is to require further clarity on the definitions of the additional scenario variables as well as information on how the additional scenario variables are used by covered institutions.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">http://www.federalreserve.gov/reportforms.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         79 FR 64026 (Oct. 27, 2014).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Revisions To Reporting Templates for Institutions With $50 Billion or More in Assets</HD>
                <P>The revisions to the DFAST-14A reporting templates consist of adding data items, deleting data items, redefining existing data items, and renumbering data items. These changes would provide additional information to enhance the ability of the OCC to analyze the validity and integrity of firms' projections and increase consistency between the FR Y-14A reporting templates and DFAST-14A reporting templates. The OCC has conducted a thorough review of the changes and believes that the incremental burden of these changes is justified given the need for this data to properly conduct the OCC's supervisory responsibilities related to the stress testing.</P>
                <HD SOURCE="HD1">Summary Schedule</HD>
                <P>
                    The OCC is making a number of changes to the Summary schedule to better assess covered institutions' calculation of risk-weighted assets (RWA) and certain other items detailed below. Please note that all line item numbers referenced in this Notice refer to the existing reporting schedules, not the revised reporting schedules. Because the changes add and delete some data items, line-item numbering between the existing and templates may be different (
                    <E T="03">e.g.,</E>
                     Income Statement item 125, Total Other Losses, in the existing reporting template is now item 124 in the template).
                </P>
                <HD SOURCE="HD2">
                    <E T="03">Revisions to Income Statement Worksheet</E>
                </HD>
                <P>In order to accurately collect information for the Income Statement, the OCC is changing items 127 and 128 (Realized Gains/Losses on available-for-sale securities and held-to-maturity securities, including OTTI) to be reported items instead of being equal to the total amounts on the Securities OTTI by Portfolio worksheet. Additionally, for consistency with changes to the Counterparty Risk Worksheet described below, items 59 and 62 (Trading Incremental Default Losses and Other CCR Losses) would be modified to be Trading Issuer Default Losses and CCR Losses, and line item 61 (Counterparty Incremental Default Losses) is being removed.</P>
                <HD SOURCE="HD2">Revisions to RWA and Capital Worksheets</HD>
                <P>
                    To better align the collection of regulatory capital components with the Board's FR Y-14A, the OCC is modifying the definitions of the items on the Capital—DFAST worksheet to refer to or mirror the definitions that appear on revisions to the FR Y-14A. Respondents are required to apply the appropriate transition provisions to all transition-affected items of the Capital—DFAST schedule consistent with revisions to regulatory capital rules. With regard to the RWA worksheets, the standardized approach RWA and market RWA items of the General RWA worksheet have been changed in accordance with proposed modifications to Schedule RC-R of the Call Report 
                    <SU>10</SU>
                    <FTREF/>
                     and modifications to the FR Y-14A that are currently being considered, and moved to a separate worksheet (Standardized RWA). These changes include both the modification and addition of items, for an overall addition of 12 items. Additionally, the computed items one through five of the current Advanced RWA worksheet are being removed.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         70 FR 35634 (June 23, 2014).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Revisions to Retail Repurchase Worksheet</HD>
                <P>Due to recent activity by respondents involving settlements related to their representation and warranty (R&amp;W) liabilities related to residential mortgages, the OCC will collect additional detail about the R&amp;W liabilities. Specifically, line items are being added that collect the unpaid principal balance (UPB) of loans covered by completed settlements for which liability remains and for which no liability remains by vintage beginning with 2004, as well as total settlement across vintages, for the following categories of loans: Loans sold to Fannie Mae, loans sold to Freddie Mac, loans insured by the U.S. government, loans securitized with monoline insurance, loans secured without monoline insurance, and whole loans sold.</P>
                <HD SOURCE="HD2">Revisions to Securities Worksheets</HD>
                <P>Because covered bonds have unique characteristics relative to other asset categories currently on this worksheet, the OCC is adding a separate covered bond category to the Securities worksheets to evaluate respondents' projections of these assets. Additionally, two columns would be added to collect information for the Securities AFS OCI by Portfolio worksheet that would allow changes in market value to be distinguished from changes in portfolio allocation for each projected quarter: Beginning Fair Market Value and Fair Value Rate of Change, which is the weighted average percent change in fair value over the quarter. Finally, to reduce reporting burden and increase efficiency in reporting, the nine sub-asset categories of Domestic Non-Agency Residential Mortgage-Backed Securities (RMBS) are being removed from the same worksheet, and the available-for-sale and held-to-maturity portions of the Securities OTTI by Portfolio worksheet are being combined with the addition of a column to identify AFS amounts versus HTM amounts.</P>
                <HD SOURCE="HD2">Revisions to Trading Worksheet</HD>
                <P>Because credit valuation adjustment (CVA) losses are modeled separately from trading portfolio losses, the OCC is requiring that the profit (loss) amount related to CVA hedges be reported separately from other trading activity.</P>
                <HD SOURCE="HD2">Revisions to Counterparty Risk Worksheet</HD>
                <P>To allow respondents to use alternative methodologies for estimating losses related to the default of issuers and counterparties, the requirement of using the incremental default risk (IDR) methodology are being removed. Accordingly, line items 1, 1a and 1b (Trading Incremental Default Losses, Trading Incremental Default Losses from securitized products, and Trading Incremental Default Losses from other credit sensitive instruments) are modified to be Issuer Default Losses. Additionally, line items 3 (Counterparty Incremental Default Losses) and 3a (Impact of CCR IDR Hedges) are being removed, line item 4 (Other CCR Losses) are modified to be CCR Losses, and the line item Effect of CCR Hedges is being added.</P>
                <HD SOURCE="HD1">Regulatory Capital Instruments Schedule</HD>
                <P>
                    Changes to the Regulatory Capital Instruments schedule are consistent with changes to the FR Y-14A. Specifically, the OCC is (1) adding an item that collects employee stock compensation to the four quarterly redemption/repurchase and issuance activity sub-sections; (2) adding 18 items to the general risk-based capital rules section and 28 items to the revised regulatory capital section; and (3) changing the capital balance items in the general risk-based capital rules 
                    <PRTPAGE P="72247"/>
                    section and the revised regulatory capital section from reported items to formulas to permit the capital balance items to be automatically computed using the new items.
                </P>
                <HD SOURCE="HD1">Regulatory Capital Transitions Schedule</HD>
                <P>Similar to the changes being made to the RWA and Capital worksheets of the Summary schedule, changes to the Regulatory Capital Transitions schedule will better align the collection of regulatory capital components with revisions to the FR Y-14A and proposed revisions to Schedule RC-R of the Call Report. The OCC is (1) aligning the definitions of the items on the Capital Composition worksheet to be consistent with the FR Y-14A; (2) modifying the RWA General worksheet to align with revisions to the FR Y-14A, including changing the name to Standardized RWA and modifying, removing and adding items for a net increase of 15 items; (3) modifying, adding and removing items on the Advanced RWA worksheet to align with the Advanced RWA worksheet on the Summary schedule, for a net increase of 21 items; and (4) revising the Leverage Exposure worksheet in accordance with changes to the supplementary leverage requirement, for a net increase of ten items.</P>
                <HD SOURCE="HD1">Counterparty Credit Risk Schedule</HD>
                <P>Significant additions are being made to the CCR schedule to more adequately and accurately capture exposure information related to derivatives and securities financing transactions (SFTs) used in supervisory loss estimates and supervisory activities. These additions would remediate deficiencies discovered in the current collection related to exposure, including a lack of information regarding collateral, asset types, and total exposure to a given counterparty.</P>
                <P>The OCC is (1) adding a worksheet that collects the derivative exposures at a legal-entity netting-agreement level for the top 25 non-central clearing counterparties (non-CCP) and non-G-7 counterparties, as well as all CCPs and the G-7 counterparties that includes a breakout of collateral into cash and non-cash, and exposures into 14 asset categories; (2) changing the current SFT sub-schedule to collect exposures and collateral separately at a counterparty legal-entity netting-agreement level for the top 25 non-CCP and non-G-7 counterparties as well as all CCPs and the G-7 counterparties and adding asset sub-categories for a total of 30 specific asset types; (3) removing all columns with the bank specification of margin period of risk (MPOR) under the global market shocks from worksheets 1(a)-1(e); (4) removing the column LGD Derived from Unstressed PD on the EE profile by CP worksheet; and (5) adding columns to worksheet 1(e) to collect both gross and net stressed and unstressed current exposure to CCPs.</P>
                <HD SOURCE="HD1">Scenario Schedule</HD>
                <P>Additional scenario variables, which are collected on this schedule, are key drivers in projection methodologies. The OCC is revising the Scenario schedule to further clarify the definitions of the additional scenario variables as well as to gather further information on how the additional scenario variables are used by covered institutions. It is expected that this additional clarity and information will assist in comparing information in this schedule across covered institutions.</P>
                <P>
                    The OCC is (1) providing additional guidance on the syntax for naming additional scenario variables to increase the comparability of additional scenario variables across covered institutions; (2) adding a column to explicitly capture the “unit of measure” of the additional scenario variables, 
                    <E T="03">e.g.,</E>
                     basis points, percentages, dollars; (3) adding a column to explicitly capture the frequency of the variable, 
                    <E T="03">e.g.,</E>
                     monthly or 3-month average; and (4) adding multiple columns to understand where the additional scenario variables are used in modeling. These last additional columns align with the methodology documentation framework described in Appendix A of the instructions.
                </P>
                <HD SOURCE="HD1">Supporting Documentation</HD>
                <P>The instructions provide that banks must provide a comprehensive inventory of models used in the projection of losses, revenues, expenses, balances, and RWAs. Additionally, the instructions provide that covered institutions must submit written procedures or other documentation that outlines internal controls and processes used to ensure the accuracy of the submissions</P>
                <HD SOURCE="HD1">Technical Changes</HD>
                <P>The OCC received one comment letter. The commenter expressed concerns about certain differences between the DFAST-14A reporting templates and the FR Y-14A reporting form used by the Board, particularly the additional information on the DFAST-14A Scenario schedule. While the OCC has attempted to keep the DFAST-14A reporting templates very similar to the FR Y-14A, the OCC supervises different legal entities than the Board and is required to administer different statutory and regulatory requirements. </P>
                <P>Therefore, some differences exist between the final DFAST-14A reporting templates and FR Y-14A. The revised templates include changes to some line items in order to match the FR Y-14A as much as possible. With respect to the additional information required on the DFAST-14A Scenario schedule, the OCC believes that additional scenario variables are key model inputs that are critical to assessing the reasonableness of a covered institution's model-based estimates. Accordingly, the final revised templates require submission of this additional information. The revised templates also contain various technical, syntax, and reference changes.</P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     23. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     16,466 hours.
                </P>
                <P>The OCC recognizes that the Board has estimated 67,848 hours for bank holding companies to prepare the reporting schedules submitted for the FR Y-14A. The OCC believes that the systems the covered institutions use to prepare the FR Y-14A reporting schedules will also be used to prepare the reporting schedules described in this notice. Comments submitted in response to this notice will be summarized and included in the request for OMB approval. All comments will become a matter of public record. Comments continue to be invited on: </P>
                <P>(a) Whether the collection of information is necessary for the proper performance of the functions of the OCC, including whether the information has practical utility; </P>
                <P>(b) The accuracy of the OCC's estimate of the burden of the collection of information; </P>
                <P>(c) Ways to enhance the quality, utility, and clarity of the information to be collected; </P>
                <P>(d) Ways to minimize the burden of the collection on respondents, including through the use of automated collection techniques or other forms of information technology; and </P>
                <P>(e) Estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <NAME>Stuart Feldstein, </NAME>
                    <TITLE>Director, Legislative and Regulatory Activities Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28575 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="72248"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of Foreign Assets Control</SUBAGY>
                <SUBJECT>Unblocking of a Specially Designated Global Terrorist Pursuant to Executive Order 13224</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Foreign Assets Control, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Treasury Department's Office of Foreign Assets Control (OFAC) is removing from the List of Specially Designated Nationals and Blocked Persons (SDN List) the name of one individual whose property and interests in property have been unblocked pursuant to Executive Order 13224 of September 23, 2001, “Blocking Property and Prohibiting Transactions With Persons Who Commit, Threaten To Commit, or Support Terrorism.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>OFAC's actions described in this notice are effective November 26, 2014.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Associate Director for Global Targeting, tel.: 202/622-2420, Assistant Director for Sanctions Compliance &amp; Evaluation, tel.: 202/622-2490, Assistant Director for Licensing, tel.: 202/622-2480, Office of Foreign Assets Control, or Chief Counsel (Foreign Assets Control), tel.: 202/622-2410, Office of the General Counsel, Department of the Treasury (not toll free numbers).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Electronic and Facsimile Availability</HD>
                <P>
                    The SDN List and additional information concerning OFAC sanctions programs are available from OFAC's Web site (
                    <E T="03">www.treasury.gov/ofac</E>
                    ). Certain general information pertaining to OFAC's sanctions programs is also available via facsimile through a 24-hour fax-on-demand service, tel.: 202/622-0077.
                </P>
                <HD SOURCE="HD1">Notice of OFAC Action</HD>
                <P>On September 11, 2014, OFAC unblocked the property and interests in property of the following individual pursuant to E.O. 13224, “Blocking Property and Prohibiting Transactions With Persons Who Commit, Threaten To Commit, or Support Terrorism.” All property and interests in property of the individual that are in or hereafter come within the United States or the possession or control of United States persons are now unblocked.</P>
                <HD SOURCE="HD2">Individual</HD>
                <P>1. AL-QADI, Yasin Abdullah Ezzedine (a.k.a. KADI, Shaykh Yassin Abdullah; a.k.a. KAHDI, Yasin), Jeddah, Saudi Arabia; DOB 23 Feb 1955; POB Cairo, Egypt; nationality Saudi Arabia; Passport B 751550; alt. Passport E 976177 issued 06 Mar 2004 expires 11 Jan 2009; alt. Passport A 848526 (Saudi Arabia) expires 29 Mar 2001 (individual) [SDGT].</P>
                <SIG>
                    <DATED>Dated: November 26, 2014.</DATED>
                    <NAME>John E. Smith,</NAME>
                    <TITLE>Acting Director, Office of Foreign Assets Control.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28598 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AL-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[OMB Control No. 2900-0013]</DEPDOC>
                <SUBJECT>Agency Information Collection (Application for United States Flag for Burial Purposes): Activity Under OMB Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans Benefits Administration, Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3521), this notice announces that the Veterans Benefits Administration (VBA), Department of Veterans Affairs, will submit the collection of information abstracted below to the Office of Management and Budget (OMB) for review and comment. The PRA submission describes the nature of the information collection and its expected cost and burden; it includes the actual data collection instrument.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before January 5, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the collection of information through 
                        <E T="03">www.Regulations.gov,</E>
                         or to Office of Information and Regulatory Affairs, Office of Management and Budget, Attn: VA Desk Officer; 725 17th St. NW., Washington, DC 20503 or sent through electronic mail to 
                        <E T="03">oira_submission@omb.eop.gov.</E>
                         Please refer to “OMB Control No. 2900-0013” in any correspondence.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Crystal Rennie, Enterprise Records Service (005R1B), Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420, (202) 632-7492 or email 
                        <E T="03">crystal.rennie@va.gov.</E>
                         Please refer to “OMB Control No. 2900-0013.”
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Application for United States Flag for Burial Purposes, VA Form 27-2008.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2900-0013.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     VA Form 27-2008 is used for the sole purpose of gathering the necessary information to determine eligibility for issuance of a burial flag to the next-of-kin or friend of a deceased Veteran.
                </P>
                <P>
                    An agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number. The 
                    <E T="04">Federal Register</E>
                     Notice with a 60-day comment period soliciting comments on this collection of information was published on August 26, 2014, at page 50987.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     162,500 hours.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Respondent:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     One-time.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     650,000.
                </P>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <P>By direction of the Secretary.</P>
                    <NAME>Crystal Rennie,</NAME>
                    <TITLE>Department Clearance Officer, Department of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28558 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[OMB Control No. 2900—NEW (10-10139)]</DEPDOC>
                <SUBJECT>Proposed Information Collection (PACT Evaluating Peer Notifications To Improve Statin Medication Adherence Among Patients With Coronary Artery Disease); Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans Health Administration, Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Veterans Health Administration (VHA), Department of Veterans Affairs (VA), is announcing an opportunity for public comment on the proposed collection of certain information by the agency. Under the Paperwork Reduction Act (PRA) of 1995, Federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each new collection, and allow 60 days for public comment in response to the notice. This notice solicits comments on the information needed to evaluate the project aims to enhance PACT implementation by evaluating the effects of the VA PACT initiative and by 
                        <PRTPAGE P="72249"/>
                        test new, innovative strategies for patient care that can be spread if proven effective.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments and recommendations on the proposed collection of information should be received on or before February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the collection of information through Federal Docket Management System (FDMS) at 
                        <E T="03">www.Regulations.gov;</E>
                         or Audrey Revere, Office of Regulatory and Administrative Affairs, Veterans Health Administration (10B4), Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420 or email: 
                        <E T="03">Audrey.revere@va.gov.</E>
                         Please refer to “OMB Control No. 2900—NEW (PACT Evaluating Peer Notifications to Improve Statin Medication Adherence among Patients with Coronary Artery Disease)” in any correspondence. During the comment period, comments may be viewed online through the FDMS.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Audrey Revere at (202) 461-5694.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Under the PRA of 1995 (Public Law 104-13; 44 U.S.C. 3501-3521), Federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. This request for comment is being made pursuant to Section 3506(c)(2)(A) of the PRA.</P>
                <P>With respect to the following collection of information, VHA invites comments on:  (1) Whether the proposed collection of information is necessary for the proper performance of VHA's functions, including whether the information will have practical utility; (2) the accuracy of VHA's estimate of the burden of the proposed collection of information; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or the use of other forms of information technology.</P>
                <P>
                    <E T="03">Titles:</E>
                     PACT Evaluating Peer Notifications to Improve Statin Medication Adherence among Patients with Coronary Artery Disease, VA Form 10-10139.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2900—NEW.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     New data collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Despite the importance of medication adherence, we have few effective tools to help patients improve taking their medications. One strategy to improve medication adherence is using newer technology to make engagement with patients significantly easier and more immediate. These studies evaluating how best to use these technologies and engage different support providers (family/friends/or peers) to improve medication adherence.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     336 burden hours.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Respondent:</E>
                     90 minutes.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Once annually.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     224.
                </P>
                <SIG>
                    <P>By direction of the Secretary.</P>
                    <NAME>Crystal Rennie,</NAME>
                    <TITLE>Department Clearance Officer, Department of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28556 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[OMB Control No. 2900—NEW (10-10138)]</DEPDOC>
                <SUBJECT>Proposed Information Collection (Using Peer Mentors To Support PACT Team Efforts To Improve Diabetes); Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans Health Administration, Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Veterans Health Administration (VHA), Department of Veterans Affairs (VA), is announcing an opportunity for public comment on the proposed collection of certain information by the agency. Under the Paperwork Reduction Act (PRA) of 1995, Federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including each new collection, and allow 60 days for public comment in response to the notice. This notice solicits comments on the information collection needed to evaluate the project aims to enhance PACT implementation by evaluating the effects of the VA PACT initiative and by test new, innovative strategies for patient care that can be spread if proven effective.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments and recommendations on the proposed collection of information should be received on or before February 3, 2015.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the collection of information through Federal Docket Management System (FDMS) at 
                        <E T="03">www.Regulations.gov;</E>
                         or Audrey Revere, Office of Regulatory and Administrative Affairs, Veterans Health Administration (10B4), Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420 or email: 
                        <E T="03">Audrey.revere@va.gov.</E>
                         Please refer to “OMB Control No. 2900—NEW (Using Peer Mentors to Support PACT Team Efforts to Improve Diabetes)” in any correspondence. During the comment period, comments may be viewed online through the FDMS.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Audrey Revere at (202) 461-5694.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Under the PRA of 1995 (Public Law 104-13; 44 U.S.C. 3501-3521), Federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. This request for comment is being made pursuant to Section 3506(c)(2)(A) of the PRA.</P>
                <P>With respect to the following collection of information, VHA invites comments on:  (1) Whether the proposed collection of information is necessary for the proper performance of VHA's functions, including whether the information will have practical utility; (2) the accuracy of VHA's estimate of the burden of the proposed collection of information; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or the use of other forms of information technology.</P>
                <P>
                    <E T="03">Titles:</E>
                     Using Peer Mentors to Support PACT Team Efforts to Improve Diabetes, VA Form 10-10138.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2900—NEW.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     New data collection.
                </P>
                <P>
                    <E T="03">Abstract</E>
                     This project is being conducted under the auspices of the VISN 4 Demonstration Lab, which was funded by Patient Care Services to assess the Patient Aligned Care Team (PACT) model of care for Veterans. There is considerable interest in and urgency to implement the PACT model—reflecting both a desire to improve health care for Veterans and to sustain the VA's leadership in health care quality. CEPACT aims to contribute to these goals by evaluating the effects of the VA PACT initiative and by test new, innovative strategies for patient care that can be spread if proven effective.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     1,473 burden hours.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Respondent:</E>
                     147 minutes.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Once annually.
                    <PRTPAGE P="72250"/>
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     600.
                </P>
                <SIG>
                    <DATED>Dated: December 2, 2014.</DATED>
                    <P>By direction of the Secretary.</P>
                    <NAME>Crystal Rennie,</NAME>
                    <TITLE>Department Clearance Officer, Department of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2014-28557 Filed 12-4-14; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="72251"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Securities and Exchange Commission</AGENCY>
            <CFR>17 CFR Parts 240, 242, and 249</CFR>
            <TITLE>Regulation Systems Compliance and Integrity; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="72252"/>
                    <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                    <CFR>17 CFR Parts 240, 242, and 249</CFR>
                    <DEPDOC>[Release No. 34-73639; File No. S7-01-13]</DEPDOC>
                    <RIN>RIN 3235-AL43</RIN>
                    <SUBJECT>Regulation Systems Compliance and Integrity</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Securities and Exchange Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule and form; final rule amendment; technical amendment.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Securities and Exchange Commission (“Commission”) is adopting new Regulation Systems Compliance and Integrity (“Regulation SCI”) under the Securities Exchange Act of 1934 (“Exchange Act”) and conforming amendments to Regulation ATS under the Exchange Act. Regulation SCI will apply to certain self-regulatory organizations (including registered clearing agencies), alternative trading systems (“ATSs”), plan processors, and exempt clearing agencies (collectively, “SCI entities”), and will require these SCI entities to comply with requirements with respect to the automated systems central to the performance of their regulated activities.</P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            <E T="03">Effective date:</E>
                             February 3, 2015.
                        </P>
                        <P>
                            <E T="03">Compliance date:</E>
                             The applicable compliance dates are discussed in Section IV.F of this release.
                        </P>
                    </DATES>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>David Liu, Senior Special Counsel, Office of Market Supervision, at (312) 353-6265, Heidi Pilpel, Senior Special Counsel, Office of Market Supervision, at (202) 551-5666, Sara Hawkins, Special Counsel, Office of Market Supervision, at (202) 551-5523, Yue Ding, Special Counsel, Office of Market Supervision, at (202) 551-5842, David Garcia, Special Counsel, Office of Market Supervision, at (202) 551-5681, and Elizabeth C. Badawy, Senior Accountant, Office of Market Supervision, at (202) 551-5612, Division of Trading and Markets, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-7010.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        Regulation SCI will, with regard to SCI entities, supersede and replace the Commission's current Automation Review Policy (“ARP”), established by the Commission's two policy statements, each titled “Automated Systems of Self-Regulatory Organizations,” issued in 1989 and 1991.
                        <SU>1</SU>
                        <FTREF/>
                         Regulation SCI also will supersede and replace aspects of those policy statements codified in Rule 301(b)(6) under the Exchange Act, applicable to significant-volume ATSs that trade NMS stocks and non-NMS stocks.
                        <SU>2</SU>
                        <FTREF/>
                         Regulation SCI will require SCI entities to establish written policies and procedures reasonably designed to ensure that their systems have levels of capacity, integrity, resiliency, availability, and security adequate to maintain their operational capability and promote the maintenance of fair and orderly markets, and that they operate in a manner that complies with the Exchange Act. It will also require SCI entities to mandate participation by designated members or participants in scheduled testing of the operation of their business continuity and disaster recovery plans, including backup systems, and to coordinate such testing on an industry- or sector-wide basis with other SCI entities. In addition, Regulation SCI will require SCI entities to take corrective action with respect to SCI events (defined to include systems disruptions, systems compliance issues, and systems intrusions), and notify the Commission of such events. Regulation SCI will further require SCI entities to disseminate information about certain SCI events to affected members or participants and, for certain major SCI events, to all members or participants of the SCI entity. In addition, Regulation SCI will require SCI entities to conduct a review of their systems by objective, qualified personnel at least annually, submit quarterly reports regarding completed, ongoing, and planned material changes to their SCI systems to the Commission, and maintain certain books and records. Finally, the Commission also is adopting modifications to the volume thresholds in Regulation ATS 
                        <SU>3</SU>
                        <FTREF/>
                         for significant-volume ATSs that trade NMS stocks and non-NMS stocks, applying them to SCI ATSs (as defined below), and moving this standard from Regulation ATS to adopted Regulation SCI for these asset classes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release Nos. 27445 (November 16, 1989), 54 FR 48703 (November 24, 1989) (“ARP I Release” or “ARP I”) and 29185 (May 9, 1991), 56 FR 22490 (May 15, 1991) (“ARP II Release” or “ARP II” and, together with ARP I, the “ARP Policy Statements”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6). 
                            <E T="03">See also</E>
                             Securities Exchange Act Release No. 40760 (December 8, 1998), 63 FR 70844 (December 22, 1998) (“ATS Release”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             17 CFR 242.300-303 (“Regulation ATS”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">Table of Contents</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. Introduction</FP>
                        <FP SOURCE="FP-2">II. Background</FP>
                        <FP SOURCE="FP1-2">A. Automation Review Policy Inspection Program</FP>
                        <FP SOURCE="FP1-2">B. Recent Events</FP>
                        <FP SOURCE="FP-2">III. Overview</FP>
                        <FP SOURCE="FP-2">IV. Description of Adopted Regulation SCI and Form SCI</FP>
                        <FP SOURCE="FP1-2">A. Definitions Establishing the Scope of Regulation SCI—Rule 1000</FP>
                        <FP SOURCE="FP1-2">1. SCI Entities</FP>
                        <FP SOURCE="FP1-2">a. SCI Self-Regulatory Organization or SCI SRO</FP>
                        <FP SOURCE="FP1-2">b. SCI Alternative Trading System</FP>
                        <FP SOURCE="FP1-2">c. Plan Processor</FP>
                        <FP SOURCE="FP1-2">d. Exempt Clearing Agency Subject to ARP</FP>
                        <FP SOURCE="FP1-2">2. SCI Systems, Critical SCI Systems, and Indirect SCI Systems</FP>
                        <FP SOURCE="FP1-2">a. Overview</FP>
                        <FP SOURCE="FP1-2">b. SCI Systems</FP>
                        <FP SOURCE="FP1-2">c. Critical SCI Systems</FP>
                        <FP SOURCE="FP1-2">d. Indirect SCI Systems (Proposed as “SCI Security Systems”)</FP>
                        <FP SOURCE="FP1-2">3. SCI Events</FP>
                        <FP SOURCE="FP1-2">a. Systems Disruption</FP>
                        <FP SOURCE="FP1-2">b. Systems Compliance Issue</FP>
                        <FP SOURCE="FP1-2">c. Systems Intrusion</FP>
                        <FP SOURCE="FP1-2">B. Obligations of SCI Entities—Rules 1001-1004</FP>
                        <FP SOURCE="FP1-2">1. Policies and Procedures to Achieve Capacity, Integrity, Resiliency, Availability and Security—Rule 1001(a)</FP>
                        <FP SOURCE="FP1-2">2. Policies and Procedures to Achieve Systems Compliance—Rule 1001(b)</FP>
                        <FP SOURCE="FP1-2">3. SCI Events: Corrective Action; Commission Notification; Dissemination of Information—Rule 1002</FP>
                        <FP SOURCE="FP1-2">a. Triggering Standard</FP>
                        <FP SOURCE="FP1-2">b. Corrective Action—Rule 1002(a)</FP>
                        <FP SOURCE="FP1-2">c. Commission Notification—Rule 1002(b)</FP>
                        <FP SOURCE="FP1-2">d. Dissemination of Information—Rule 1002(c)</FP>
                        <FP SOURCE="FP1-2">4. Notification of Systems Changes—Rule 1003(a)</FP>
                        <FP SOURCE="FP1-2">5. SCI Review—Rule 1003(b)</FP>
                        <FP SOURCE="FP1-2">6. SCI Entity Business Continuity and Disaster Recovery Plans Testing Requirements for Members or Participants—Rule 1004</FP>
                        <FP SOURCE="FP1-2">C. Recordkeeping, Electronic Filing on Form SCI, and Access—Rules 1005-1007</FP>
                        <FP SOURCE="FP1-2">1. Recordkeeping—Rules 1005-1007</FP>
                        <FP SOURCE="FP1-2">2. Electronic Filing and Submission of Reports, Notifications, and Other Communications—Rule 1006</FP>
                        <FP SOURCE="FP1-2">3. Access to the Systems of an SCI Entity</FP>
                        <FP SOURCE="FP1-2">D. Form SCI</FP>
                        <FP SOURCE="FP1-2">E. Other Comments Received</FP>
                        <FP SOURCE="FP1-2">F. Effective Date and Compliance Dates</FP>
                        <FP SOURCE="FP-2">V. Paperwork Reduction Act</FP>
                        <FP SOURCE="FP-2">VI. Economic Analysis</FP>
                        <FP SOURCE="FP-2">VII. Regulatory Flexibility Act Certification</FP>
                        <FP SOURCE="FP-2">VIII. Statutory Authority and Text of Amendments</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Introduction</HD>
                    <P>
                        The U.S. securities markets attract a wide variety of issuers and broad investor participation, and are essential for capital formation, job creation, and economic growth, both domestically and across the globe. The U.S. securities markets have been transformed by regulatory and related technological developments in recent years. They have, among other things, substantially enhanced the speed, capacity, efficiency, and sophistication of the trading functions that are available to 
                        <PRTPAGE P="72253"/>
                        market participants.
                        <SU>4</SU>
                        <FTREF/>
                         At the same time, these technological advances have generated an increasing risk of operational problems with automated systems, including failures, disruptions, delays, and intrusions. Given the speed and interconnected nature of the U.S. securities markets, a seemingly minor systems problem at a single entity can quickly create losses and liability for market participants, and spread rapidly across the national market system, potentially creating widespread damage and harm to market participants, including investors.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 61358 (January 14, 2010), 75 FR 3594, 3598 (January 21, 2010) (Concept Release on Equity Market Structure).
                        </P>
                    </FTNT>
                    <P>
                        This transformation of the U.S. securities markets has occurred in the absence of a formal regulatory structure governing the automated systems of key market participants. Instead, for over two decades, Commission oversight of the technology of the U.S. securities markets has been conducted primarily pursuant to a voluntary set of principles articulated in the Commission's ARP Policy Statements,
                        <SU>5</SU>
                        <FTREF/>
                         applied through the Commission's Automation Review Policy inspection program (“ARP Inspection Program”).
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             While participation in the ARP Inspection Program is voluntary, the underpinnings of ARP I and ARP II are rooted in Exchange Act requirements. 
                            <E T="03">See infra</E>
                             notes 7-12 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             
                            <E T="03">See infra</E>
                             Section II.A (discussing the ARP Inspection Program). 
                            <E T="03">See also supra</E>
                             note 1. The ARP Inspection Program has historically been administered by the Commission's Division of Trading and Markets. In February 2014, to consolidate the inspection function of the group with the Commission's Office of Compliance Inspections and Examinations (“OCIE”), the ARP Inspection Program was transitioned to OCIE and has been renamed the Technology Controls Program (“TCP”). However, for ease of reference to the historical ARP Inspection Program, relevant portions of the SCI Proposal, and references in comment letters, this Release will continue to use the terms ARP, ARP Inspection Program, and ARP staff, unless the context otherwise requires.
                        </P>
                    </FTNT>
                    <P>
                        Section 11A(a)(2) of the Exchange Act,
                        <SU>7</SU>
                        <FTREF/>
                         enacted as part of the Securities Acts Amendments of 1975 (“1975 Amendments”),
                        <SU>8</SU>
                        <FTREF/>
                         directs the Commission, having due regard for the public interest, the protection of investors, and the maintenance of fair and orderly markets, to use its authority under the Exchange Act to facilitate the establishment of a national market system for securities in accordance with the Congressional findings and objectives set forth in Section 11A(a)(1) of the Exchange Act.
                        <SU>9</SU>
                        <FTREF/>
                         Among the findings and objectives in Section 11A(a)(1) is that “[n]ew data processing and communications techniques create the opportunity for more efficient and effective market operations” 
                        <SU>10</SU>
                        <FTREF/>
                         and “[i]t is in the public interest and appropriate for the protection of investors and the maintenance of fair and orderly markets to assure . . . the economically efficient execution of securities transactions.” 
                        <SU>11</SU>
                        <FTREF/>
                         In addition, Sections 6(b), 15A, and 17A(b)(3) of the Exchange Act impose obligations on national securities exchanges, national securities associations, and clearing agencies, respectively, to be “so organized” and “[have] the capacity to . . . carry out the purposes of [the Exchange Act].” 
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             15 U.S.C. 78k-1(a)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Pub. L. 94-29, 89 Stat. 97 (1975).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             15 U.S.C. 78k-1(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             Section 11A(a)(1)(B) of the Exchange Act, 15 U.S.C. 78k-1(a)(1)(B).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             Section 11A(a)(1)(C)(i) of the Exchange Act, 15 U.S.C. 78k-1(a)(1)(C)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">See</E>
                             Sections 6(b)(1), 15A(b)(2), and 17A(b)(3) of the Exchange Act, 15 U.S.C. 78f(b)(1), 78
                            <E T="03">o</E>
                            -3(b)(2), 78q-1(b)(3), respectively. 
                            <E T="03">See also</E>
                             Section 2 of the Exchange Act, 15 U.S.C. 78b, and Section 19 of the Exchange Act, 15 U.S.C. 78s.
                        </P>
                    </FTNT>
                    <P>
                        In March 2013, the Commission proposed Regulation Systems Compliance and Integrity (“Regulation SCI”) 
                        <SU>13</SU>
                        <FTREF/>
                         to require certain key market participants to, among other things: (1) Have comprehensive policies and procedures in place to help ensure the robustness and resiliency of their technological systems, and also that their technological systems operate in compliance with the federal securities laws and with their own rules; and (2) provide certain notices and reports to the Commission to improve Commission oversight of securities market infrastructure. As discussed in further detail below and in the SCI Proposal, Regulation SCI was proposed to update, formalize, and expand the Commission's ARP Inspection Program, and, with respect to SCI entities, to supersede and replace the Commission's ARP Policy Statements and rules regarding systems capacity, integrity and security in Rule 301(b)(6) of Regulation ATS.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             Securities Exchange Act Release No. 69077 (March 8, 2013), 78 FR 18083 (March 25, 2013) (“Proposing Release” or “SCI Proposal”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6) and ATS Release, 
                            <E T="03">supra</E>
                             note 2.
                        </P>
                    </FTNT>
                    <P>
                        A confluence of factors contributed to the Commission's proposal of Regulation SCI and to the Commission's current determination that it is necessary and appropriate at this time to address the technological vulnerabilities, and improve Commission oversight, of the core technology of key U.S. securities markets entities, including national securities exchanges and associations, significant alternative trading systems, clearing agencies, and plan processors. These considerations include: the evolution of the markets to become significantly more dependent upon sophisticated, complex and interconnected technology; the current successes and limitations of the ARP Inspection Program; a significant number of, and lessons learned from, recent systems issues at exchanges and other trading venues,
                        <SU>15</SU>
                        <FTREF/>
                         increased concerns over “single points of failure” in the securities markets; 
                        <SU>16</SU>
                        <FTREF/>
                         and the views of a wide variety of commenters received in response to the SCI Proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18085-91 for a further discussion of these developments and 
                            <E T="03">infra</E>
                             Section II.B (discussing recent events related to technology issues). In addition, prior to issuing the Proposing Release, in October 2012 the Commission convened a roundtable entitled “Technology and Trading: Promoting Stability in Today's Markets” (“Technology Roundtable”). The Technology Roundtable examined the relationship between the operational stability and integrity of the securities market and the ways in which market participants design, implement, and manage complex and interconnected trading technologies. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 67802 (September 7, 2012), 77 FR 56697 (September 13, 2012) (File No. 4-652) and Technology Roundtable Transcript, available at: 
                            <E T="03">http://www.sec.gov/news/otherwebcasts/2012/ttr100212-transcript.pdf.</E>
                             A webcast of the Roundtable is available at: 
                            <E T="03">www.sec.gov/news/otherwebcasts/2012/ttr100212.shtml.</E>
                             As noted in the Proposing Release, the Commission believes that the information presented at the Technology Roundtable further highlighted that quality standards, testing, and improved response mechanisms are among the issues needing very thoughtful and focused attention in today's securities markets. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18090-91 for further discussion of the Technology Roundtable.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.A.2.c (discussing single points of failure in the securities markets in conjunction with the adopted term “critical SCI system”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission received 60 comment letters on the proposal from national securities exchanges, registered securities associations, registered clearing agencies, ATSs, broker-dealers, institutional and individual investors, industry trade groups, software and technology vendors, and academics.
                        <SU>17</SU>
                        <FTREF/>
                         Commenters generally supported the goals of the proposal, but as further discussed below, some expressed concern about various specific elements of the proposal, and recommended certain modifications or clarifications.
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             Comments received on the proposal are available on the Commission's Web site, available at: 
                            <E T="03">http://www.sec.gov/comments/s7-01-13/s70113.shtml. See</E>
                             Exhibit A for a citation key to the comment letters cited in this release.
                        </P>
                        <P>
                             Upon request from some commenters, the Commission extended the comment period for an additional 45 days in order to give the public additional time to comment on the matters addressed by the SCI Proposal. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 69606 (May 20, 2013), 78 FR 30803 (May 23, 2013).
                        </P>
                    </FTNT>
                    <P>
                        After careful review and consideration of the comment letters, 
                        <PRTPAGE P="72254"/>
                        the Commission is adopting Regulation SCI (“Rule”) and Form SCI (“Form”) with certain modifications from the SCI Proposal, as discussed below, to respond to concerns expressed by commenters and upon further consideration by the Commission of the more appropriate approach to further the goals of the national market system by strengthening the technology infrastructure of the U.S. securities markets.
                    </P>
                    <HD SOURCE="HD1">II. Background</HD>
                    <HD SOURCE="HD2">A. Automation Review Policy Inspection Program</HD>
                    <P>
                        For over two decades, the Commission's ARP Inspection Program has helped the Commission oversee the technology infrastructure of the U.S. securities markets. This voluntary information technology review program was developed by staff of the Commission to implement the Commission's ARP Policy Statements issued in 1989 and 1991.
                        <SU>18</SU>
                        <FTREF/>
                         Through these Policy Statements, the Commission articulated its views on the steps that SROs should take with regard to their automated systems, set forth recommendations for how SROs should conduct independent reviews, and provided that SROs should notify the Commission of material systems changes and significant systems problems.
                        <SU>19</SU>
                        <FTREF/>
                         In 1998, the Commission adopted Regulation ATS which, among other things, imposed by rule certain aspects of the ARP Policy Statements on significant-volume ATSs.
                        <SU>20</SU>
                        <FTREF/>
                         Further, Commission staff subsequently provided additional guidance regarding various aspects of the ARP Inspection Program through letters to ARP entities, including recommendations regarding reporting planned systems changes and systems issues to the Commission.
                        <SU>21</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">See</E>
                             ARP Policy Statements, 
                            <E T="03">supra</E>
                             note 1. For a detailed discussion of the ARP Policy Statements, 
                            <E T="03">see</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18085-86.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             
                            <E T="03">See</E>
                             ARP Policy Statements, 
                            <E T="03">supra</E>
                             note 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6) and ATS Release, 
                            <E T="03">supra</E>
                             note 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             In June 2001, staff from the Division of Market Regulation sent a letter to the SROs and other participants in the ARP Inspection Program regarding Guidance for Systems Outage and System Change Notifications (“2001 Staff ARP Interpretive Letter”). 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18087, n. 35. The 2001 Staff ARP Interpretive Letter is available at: 
                            <E T="03">http://www.sec.gov/divisions/marketreg/sroautomation.shtml.</E>
                        </P>
                    </FTNT>
                    <P>
                        Under the ARP Inspection Program, Commission staff (“ARP staff”) conducts inspections of the trading and related systems of national securities exchanges and associations, certain ATSs, clearing agencies, and plan processors (collectively “ARP entities”), attends periodic technology briefings by ARP entities, monitors planned significant system changes, and responds to reports of system failures, disruptions, and other systems problems of ARP entities. The goal of the ARP inspections is to evaluate whether an ARP entity's controls over its information technology resources in nine general areas, or information technology “domains,” 
                        <SU>22</SU>
                        <FTREF/>
                         is consistent with ARP and industry guidelines. Such guidelines are identified by ARP staff from a variety of information technology publications that ARP staff believes reflects industry standards for securities market participants.
                        <SU>23</SU>
                        <FTREF/>
                         At the conclusion of an ARP inspection, ARP staff typically issues a report to the ARP entity with an assessment of the ARP entity's information technology program for its key systems, including any recommendations for improvement.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             These information technology “domains” include: application controls; capacity planning; computer operations and production environment controls; contingency planning; information security and networking; audit; outsourcing; physical security; and systems development methodology. Each domain itself contains subcategories. For example, “contingency planning” includes business continuity, disaster recovery, and pandemic planning, among other things. 
                            <E T="03">See id.</E>
                             at 18086.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             
                            <E T="03">See id.</E>
                             at 18086-87.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             In addition, Commission staff conducts inspections of SROs, as part of the Commission's oversight of them. Unlike ARP inspections, however, which focus on information technology controls, such Commission staff primarily conducts risk-based examinations of securities exchanges, FINRA, and other SROs to evaluate whether they and their member firms are complying with the Exchange Act, the rules thereunder, and SRO rules, as applicable. As part of the Commission's oversight of the SROs, Commission staff also reviews systems compliance issues reported to Commission staff. The information gained from the Commission staff review of reported systems compliance issues helps to inform its examination risk-assessments for SROs. 
                            <E T="03">See id.</E>
                             at 18087.
                        </P>
                    </FTNT>
                    <P>
                        Because the ARP Inspection Program was established pursuant to Commission policy statements rather than Commission rules, participation in and compliance with the ARP Inspection Program by ARP entities is voluntary. As such, despite its general success in working with SROs to improve their automated systems, there are certain limitations with the ARP Inspection Program. In particular, because of the voluntary nature of the ARP Inspection Program, the Commission is constrained in its ability to assure compliance with ARP standards. The Government Accountability Office (“GAO”) has identified the voluntary nature of the ARP Inspection Program as a limitation and recommended that the Commission make compliance with ARP guidelines mandatory.
                        <SU>25</SU>
                        <FTREF/>
                         In addition, as more fully discussed in the SCI Proposal, the evolution of the U.S. securities markets in recent years to become almost entirely electronic and highly dependent on sophisticated trading and other technology, including complex and interconnected routing, market data, regulatory, surveillance and other systems, has posed challenges for the ARP Inspection Program.
                        <SU>26</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             
                            <E T="03">See</E>
                             GAO, Financial Market Preparedness: Improvements Made, but More Action Needed to Prepare for Wide-Scale Disasters, Report No. GAO-04-984 (September 27, 2004). GAO cited instances in which the GAO believed that entities participating in the ARP Inspection Program failed to adequately address or implement ARP staff recommendations as the reasoning behind its recommendation to make compliance with ARP guidelines mandatory.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18087-89.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Recent Events</HD>
                    <P>
                        A series of high-profile recent events involving systems-related issues further highlights the need for market participants to bolster the operational integrity of their automated systems in this area. In the SCI Proposal, the Commission identified several systems problems experienced by SROs and ATSs that garnered significant public attention and illustrated the types and risks of systems issues affecting today's markets.
                        <SU>27</SU>
                        <FTREF/>
                         Since Regulation SCI's proposal in March 2013, additional systems problems among market participants have occurred, further underscoring the importance of bolstering the robustness of U.S. market infrastructure to help ensure its stability, integrity, and resiliency.
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             
                            <E T="03">See id.</E>
                             at 18089-90. The Proposing Release also discussed the effects of Superstorm Sandy on the U.S. securities exchanges, noting certain weaknesses in business continuity and disaster recovery planning that were highlighted by the event. 
                            <E T="03">See id.</E>
                             at 18091.
                        </P>
                    </FTNT>
                    <P>
                        In particular, since Regulation SCI's proposal, disruptions have continued to occur across a variety of market participants. For example, with respect to the options markets, some exchanges have delayed the opening of trading,
                        <SU>28</SU>
                        <FTREF/>
                          
                        <PRTPAGE P="72255"/>
                        halted trading,
                        <SU>29</SU>
                        <FTREF/>
                         or experienced other errors as a result of systems issues,
                        <SU>30</SU>
                        <FTREF/>
                         and trading in options was halted due to a systems issue with the securities information processor for options market information.
                        <SU>31</SU>
                        <FTREF/>
                         Systems issues have also impacted consolidated market data in the equities markets, including one incident that led to a trading halt in all securities listed on a particular exchange.
                        <SU>32</SU>
                        <FTREF/>
                         Systems issues have also affected trading off of national securities exchanges, including an incident where FINRA halted trading in all OTC equity securities due to a lack of availability of quotation information resulting from a connectivity issue experienced by an ATS.
                        <SU>33</SU>
                        <FTREF/>
                         Systems issues during this time have not been limited to systems disruptions, but have also included allegations of systems compliance issues.
                        <SU>34</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             On April 25, 2013, the Chicago Board Options Exchange, Inc. (“CBOE”) delayed the opening of trading on its exchange for over three hours due to what CBOE described as an internal “software bug.” 
                            <E T="03">See</E>
                             CBOE Information Circular IC13-036, April 29, 2013, available at: 
                            <E T="03">http://www.cboe.com/publish/InfoCir/IC13-036.pdf.</E>
                             During this time, while trading in many products was able to continue on the other options exchanges, trading was completely halted for those products that are singly-listed on CBOE, including options on the S&amp;P 500 Index and the CBOE Volatility Index (“VIX”). Trading was able to resume by approximately 1:00 p.m. ET, though some residual systems problems continued. Specifically, certain auction mechanisms were unavailable for the remainder of the day and some of the trade data from April 25 was erroneously re-transmitted to OCC on April 26. 
                            <E T="03">See id.</E>
                             and CBOE System Status notifications for 
                            <PRTPAGE/>
                            April 25, 2013, available at: 
                            <E T="03">http://www.cboe.com/aboutcboe/systemstatus/search.aspx.</E>
                             CBOE subsequently reported that preliminary staging work related to a planned reconfiguration of CBOE's systems in preparation for extended trading hours on the CBOE Futures Exchange and CBOE options exchange “exposed and triggered a design flaw in the existing messaging infrastructure configuration.” 
                            <E T="03">See</E>
                             CBOE Information Circular IC13-036, April 29, 2013, available at: 
                            <E T="03">http://www.cboe.com/publish/InfoCir/IC13-036.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             On November 1, 2013, Nasdaq halted trading on the Nasdaq Options Market (“NOM”) for more than five hours through the close of the trading day. Nasdaq stated that the halt was a result of “a significant increase in order entries which inhibited the system's ability to accept orders and disseminate quotes on a subset of symbols.” As Nasdaq stated, Nasdaq determined that it was in the best interest of market participants and investors to cancel all orders on the NOM book and continue the market halt through the close. 
                            <E T="03">See</E>
                             Nasdaq Market System Status Updates for November 1, 2013, available at: 
                            <E T="03">https://www.nasdaqtrader.com/Trader.aspx?id=MarketSystemStatusSearch.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             On April 29, 2014, NYSE Arca and NYSE Amex Options experienced a systems issue that resulted in numerous complex orders booking at incorrect prices. In some cases, this resulted in erroneous fill reports, all of which were subsequently nullified. 
                            <E T="03">See</E>
                             Trader Update to All NYSE Amex Options and NYSE Arca Options Participants, “Erroneous Complex Order Executions,” dated April 29, 2014, available at: 
                            <E T="03">http://www1.nyse.com/pdfs/2014_04_29_NYSE_Amex_and_Arca_Options_Erroneous_Complex_Order_Executions.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             On September 16, 2013, options market trading was halted for approximately 20 minutes due to a systems issue with the Options Price Reporting Authority (“OPRA”), the securities information processor for options market information that disseminates option quotation and last sale information to market data vendors. OPRA reported that it experienced problems processing quotes as a result of a software issue originating from a limited rollout of certain software upgrades. 
                            <E T="03">See</E>
                             Notice to All OPRA Market Data Recipients from OPRA, LLC, dated September 18, 2013, available at: 
                            <E T="03">http://www.opradata.com/specs/16-sept-2013-opra-outage.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             On August 22, 2013, the NASDAQ Stock Market LLC (“Nasdaq”) halted trading in all Nasdaq-listed securities for more than three hours after the Nasdaq UTP Securities Information Processor (“SIP”), the single source of consolidated market data for Nasdaq-listed securities, was unable to process quotes from exchanges for dissemination to the public. According to Nasdaq, a sequence of events created a spike in message traffic volume into the SIP exceeding the SIP's capacity and causing the system to fail. Nasdaq cited “more than 20 connect and disconnect sequences from NYSE Arca” and a “stream of quotes for inaccurate symbols from NYSE Arca” as events contributing to the systems problem. Nasdaq noted that the stream of messages, which was 26 times greater than usual activity, degraded the system and exceeded its capacity, ultimately resulting in the failure. Nasdaq stated that these events exposed a flaw in the SIP's software code which prevented a successful failover to the backup system. 
                            <E T="03">See</E>
                             “NASDAQ OMX Provides Updates on Events of August 22, 2013,” by NASDAQ OMX (August 29, 2013), available at: 
                            <E T="03">http://www.nasdaqomx.com/newsroom/pressreleases/pressrelease?messageId=1204807&amp;displayLanguage=en;</E>
                             and Nasdaq Market System Status notifications for August 22, 2013, available at: 
                            <E T="03">https://www.nasdaqtrader.com/Trader.aspx?id=MarketSystemStatusSearch.</E>
                        </P>
                        <P>
                            Nasdaq experienced another outage related to the SIP on September 4, 2013. This incident lasted only several minutes and affected only a subset of Nasdaq-listed securities. 
                            <E T="03">See</E>
                             “NASDAQ OMX Issues Statement on the Securities Information Processor,” by NASDAQ OMX (September 4, 2013), available at: 
                            <E T="03">http://ir.nasdaqomx.com/releasedetail.cfm?ReleaseID=788700.</E>
                        </P>
                        <P>
                            The SIP consolidates quotation information and transaction reports from market centers and disseminates such consolidated information to market participants pursuant to the Commission-approved Joint Self-Regulatory Organization Plan Governing the Collection, Consolidation and Dissemination of Quotation and Transaction Information for Nasdaq-Listed Securities Traded on Exchanges on an Unlisted Trading Privilege Basis, available at: 
                            <E T="03">http://www.utpplan.com/. See generally</E>
                             Rule 608 of Regulation NMS, 17 CFR 242.608 (“Filing and amendment of national market system plans”). 
                        </P>
                        <P>
                             More recently, on October 30, 2014, according to the NYSE, a network hardware failure impacted the Consolidated Tape System, Consolidated Quote System, and Options Price Reporting Authority data feeds at the primary data center. Exchanges experienced issues publishing and receiving trades and quotes as a result. After investigation of the issue, the Securities Industry Automation Corporation (“SIAC”) (the processor for the affected data feeds) switched over to the secondary data center for these data feeds and normal processing subsequently resumed. The exchanges then connected to the secondary data center as provided for in SIAC's business continuity plan. 
                            <E T="03">See</E>
                             “Service Advisory—CTA Update,” by NYSE (October 30, 2014), available at: 
                            <E T="03">https://markets.nyx.com/nyse/market-status/view/13467</E>
                             and “NMS SIP market wide issue,” by NYSE (October 30, 2014), available at: 
                            <E T="03">https://markets.nyx.com/nyse/market-status/view/13465.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             On November 7, 2013, FINRA halted trading for over 3
                            <FR>1/2</FR>
                             hours in all OTC equity securities due to a lack of availability of quotation information resulting from a connectivity issue experienced by OTC Markets Group Inc.'s OTC Link ATS. 
                            <E T="03">See</E>
                             “Market-Wide Quotation and Trading Halt for all OTC Equity Securities,” FINRA Uniform Practice Advisory, UPC #47-13, November 7, 2013, available at: 
                            <E T="03">http://www.finra.org/web/groups/industry/@ip/@comp/@mt/documents/upcnotices/p381590.pdf;</E>
                             “Quotation and Trading Halt for OTC Equity Securities,” FINRA Uniform Practice Advisory, UPC #48-13, November 7, 2013, available at: 
                            <E T="03">http://www.finra.org/web/groups/industry/@ip/@comp/@mt/documents/upcnotices/p381593.pdf;</E>
                             “OTC Markets Group Issues Statement on OTC Link® ATS Trading on November 7, 2013,” OTC Disclosure &amp; News Service, November 7, 2013, available at: 
                            <E T="03">http://www.otcmarkets.com/stock/OTCM/news/OTC-Markets-Group-Issues-Statement-on-OTC-Linkreg-ATS-Trading-on-November-7-2013?id=71144.</E>
                             OTC Markets Group subsequently reported that a network outage at one of its core network providers caused the lack of connectivity to its primary data center in New Jersey. 
                            <E T="03">See</E>
                             “OTC Markets Group Issues Statement on OTC Link® ATS Trading on November 7, 2013,” OTC Disclosure &amp; News Service, November 7, 2013, available at: 
                            <E T="03">http://www.otcmarkets.com/stock/OTCM/news/OTC-Markets-Group-Issues-Statement-on-OTC-Linkreg-ATS-Trading-on-November-7-2013?id=71144.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             For example, in June 2013, the Commission charged CBOE and its affiliate (C2 Options Exchange, Incorporated (“C2”)) for various systemic breakdowns in their regulatory and compliance responsibilities as self-regulatory organizations, including failure to enforce the federal securities laws and Commission rules. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 69726, In the Matter of Chicago Board Options Exchange, Incorporated and C2 Options Exchange, Incorporated (settled action: June 11, 2013), available at: 
                            <E T="03">http://www.sec.gov/litigation/admin/2013/34-69726.pdf</E>
                             (“CBOE Order”). CBOE and C2 consented to an Order Instituting Administrative and Cease-and-Desist Proceedings Pursuant to Sections 19(h) and 21C of the Securities Exchange Act of 1934, Making Findings, and Imposing Sanctions and a Cease-and-Desist Order. In the CBOE Order, among other charges, the Commission stated that “CBOE's automated surveillance programs for manually handled trades were ineffective” and that “CBOE failed to maintain a reliable or accurate audit trail of orders” on its trading facility. 
                            <E T="03">See id.</E>
                             at 11, 13.
                        </P>
                        <P>
                            In addition, in May 2014, the Commission sanctioned the New York Stock Exchange LLC (“NYSE”) and two of its affiliated exchanges (NYSE Arca, Inc. (“NYSE Arca”), NYSE MKT LLC (“NYSE MKT”)) for alleged failure to comply with their responsibilities as self-regulatory organizations to conduct their business operations in accordance with Commission-approved exchange rules and the federal securities laws. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 72065, In the Matter of New York Stock Exchange LLC, NYSE Arca, Inc., NYSE MKT LLC, and Archipelago Securities, L.L.C. (settled action: May 1, 2014), available at: 
                            <E T="03">http://www.sec.gov/litigation/admin/2014/34-72065.pdf</E>
                             (“NYSE Order”). NYSE, NYSE Arca, NYSE MKT, and Archipelago Securities consented to an Order Instituting Administrative and Cease-and-Desist Proceedings Pursuant to Sections 19(h) and 21C of the Securities Exchange Act of 1934, Making Findings, and Imposing Sanctions and a Cease-and-Desist Order. In the NYSE Order, the Commission cited various instances of NYSE systems not operating in compliance with their effective rules, such as NYSE's block trading facility not functioning in accordance with applicable rules; NYSE distributing an automated feed of closing order imbalance information to its floor brokers at an earlier time than specified in NYSE rules; and NYSE failing to execute certain orders in locked markets contrary to exchange rules. 
                            <E T="03">See id.</E>
                             In the NYSE Order, the Commission stated that the exchanges “lacked comprehensive and consistently-applied policies and procedures for . . . evaluating whether business operations were being conducted fully in accordance with existing exchange rules and the federal securities laws.” 
                            <E T="03">Id.</E>
                             at 3.
                        </P>
                    </FTNT>
                    <P>
                        Systems issues are not unique to the U.S. securities markets, with similar incidents occurring in the U.S. commodities markets as well as foreign markets.
                        <SU>35</SU>
                        <FTREF/>
                         However, the Commission 
                        <PRTPAGE P="72256"/>
                        believes that it is critical that key U.S. securities market participants bolster their operational integrity to prevent, to the extent reasonably possible, these types of events, which can not only lead to tangible monetary losses,
                        <SU>36</SU>
                        <FTREF/>
                         but which commenters believe to have the potential to reduce investor confidence in the U.S. markets.
                        <SU>37</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Jacob Bunge, Bradley Hope, and Leslie Josephs, “Technical Glitch Hits CME Trading,” Wall St. J., April 8, 2014; Jeremy Grant, “Glitch Delays Singapore Derivative Trade,” Fin. Times, April 9, 2013; Tamsyn Parker, “NZX Trading 
                            <PRTPAGE/>
                            Resumes After Technical Glitch,” The New Zealand Herald, July 1, 2013; Matt Clinch, “Flash Crash: Israel Stocks Hit by Typo,” CNBC.com, available at: 
                            <E T="03">http://www.cnbc.com/id/100986999;</E>
                             and Ksenia Galouchko, “Moscow Exchange Halts Derivatives Trading for Almost an Hour,” Bloomberg, November 13, 2013.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13 (discussing systems issues affecting the initial public offerings (“IPO”) of BATS Global Markets, Inc. and Facebook, Inc.). In a rule change approved by the Commission in March 2013, Nasdaq implemented a $62 million accommodation program to compensate certain members for their losses in connection with the Facebook IPO. Securities Exchange Act Release No. 69216 (March 22, 2013), 78 FR 19040 (March 28, 2013). In its quarterly earnings announcement for the second quarter of 2013, UBS reported a $356 million loss tied to Facebook's IPO, while The Knight Capital Group and Citadel Investment Group claimed losses of $30 million to $35 million and Citigroup cited losses close to $20 million. 
                            <E T="03">See</E>
                             Michael J. De La Merced, “Behind the Huge Facebook Loss at UBS,” N.Y. Times, July 21, 2012. 
                            <E T="03">See also</E>
                             Angel Letter at 15 (stating that catastrophic failures in exchange systems are extremely costly in terms of direct losses to participants and result in reduced investor confidence in markets); and Better Markets Letter at 2 (citing to the systems related problems at Knight Capital, Direct Edge, BATS, and during the Facebook IPO that resulted in investor or company losses).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel2 Letter at 2; Sungard Letter at 2; Better Markets Letter at 2; Leuchtkafer Letter at 3; FSI Letter at 3; and Angel Letter at 10, 15.
                        </P>
                    </FTNT>
                    <P>
                        The SCI Proposal also noted that the risks associated with cybersecurity, and how to protect against systems intrusions, are increasingly of concern to all types of entities.
                        <SU>38</SU>
                        <FTREF/>
                         On March 27, 2014, the Commission conducted a Cybersecurity Roundtable (“Cybersecurity Roundtable”).
                        <SU>39</SU>
                        <FTREF/>
                         The Cybersecurity Roundtable addressed the cybersecurity landscape and cybersecurity issues faced by participants in the financial markets today, including exchanges, broker-dealers, investment advisers, transfer agents and public companies.
                        <SU>40</SU>
                        <FTREF/>
                         Panelists discussed, among other topics, the scope and nature of cybersecurity threats to the financial industry; how market participants can effectively manage cybersecurity threats, including public and private sector coordination efforts and information sharing; the role that government should play to promote cybersecurity in the financial markets and market infrastructure; cybersecurity disclosure issues faced by public companies; and the identification of appropriate best practices and standards with regard to cybersecurity. Although the views of panelists varied, many emphasized the significant risk that cybersecurity attacks pose to the financial markets and market infrastructure today and the need to effectively manage that risk through measures such as testing, risk assessments, adoption of consistent best practices and standards, and information sharing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18089-90.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 71742 (March 19, 2014), 79 FR 16071 (March 24, 2014) (File No. 4-673). A webcast of the Cybersecurity Roundtable is available at: 
                            <E T="03">http://www.sec.gov/news/otherwebcasts/2014/cybersecurity-roundtable-032614.shtml.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             The first panel discussed the cybersecurity landscape, and panelists included: Cyrus Amir-Mokri, Assistant Secretary for Financial Institutions, Department of the Treasury; Mary E. Galligan, Director, Cyber Risk Services, Deloitte and Touche LLP; Craig Mundie, Member, President's Council of Advisors on Science and Technology; Senior Advisor to the Chief Executive Officer, Microsoft Corporation; Javier Ortiz, Vice President, Strategy and Global Head of Government Affairs, TaaSera, Inc.; Andy Roth, Partner and Co-Chair, Global Privacy and Security Group, Dentons US LLP; Ari Schwartz, Acting Senior Director for Cybersecurity Programs, National Security Council, The White House; Adam Sedgewick, Senior Information Technology Policy Advisor, national Institute of Standards and Technology; and Larry Zelvin, Director, National Cybersecurity and Communications Integration Center, U.S. Department of Homeland Security.
                        </P>
                        <P> The second panel discussed public company disclosure of cybersecurity risks and incidents, and panelists included: Peter Beshar, Executive Vice President and General Counsel, Marsh &amp; McLennan Companies, Inc.; David Burg, Global and U.S. Advisor Cyber Security Leader, PricewaterhouseCoopers LLP; Roberta Karmel, Centennial Professor of Law, Brooklyn Law School; Jonas Kron, Senior Vice President, Director of Shareholder Advocacy, Trillum Asset Management LLC; Douglas Meal, Partner, Ropes &amp; Gray LLP; and Leslie T. Thornton, Vice President and General Counsel, WGL Holdings, Inc. and Washington Gas Light Company.</P>
                        <P> The third panel addressed cybersecurity issues faced by the securities markets, and panelists included: Mark G. Clancy, Managing Director and Corporate Information Security Officer, The Depository Trust and Clearing Corporation; Mark Graff, Chief Information Security Officer, Nasdaq OMX; Todd Furney, Vice President, Systems Security, Chicago Board Options Exchange; Katheryn Rosen, Deputy Assistant Secretary, Office of Financial Institutions Policy, Department of the Treasury; Thomas Sinnott, Managing Director, Global Information Security, CME Group; and Aaron Weissenfluh, Chief Information Security Officer, BATS Global Markets, Inc.</P>
                        <P> The final panel discussed how broker-dealers, investment advisers, and transfer agents address cybersecurity issues, and panelists included: John Denning, Senior Vice President, Operational Policy Integration, Development and Strategy, Bank of America/Merrill Lynch; Jimmie H. Lenz, Senior Vice President, Chief Risk and Credit Officer, Wells Fargo Advisors LLC; Mark R. Manley, Senior Vice President, Deputy General Counsel and Chief Compliance Officer, AllianceBernstein L.P.; Marcus Prendergast, Director and Corporate Information Security Officer, ITG; Karl Schimmeck, Managing Director, Financial Services Operations, Securities Industry and Financial Markets Association; Daniel M. Sibears, Executive Vice President, Regulatory Operations/Shared Services, FINRA; John Reed Stark, Managing Director, Stroz Friedberg; Craig Thomas, Chief Information Security Officer, Computershare; and David G. Tittsworth, Executive Director and Executive Vice President, Investment Adviser Association.</P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Overview</HD>
                    <P>
                        The Commission acknowledges that the nature of technology and the level of sophistication and automation of current market systems prevent any measure, regulatory or otherwise, from completely eliminating all systems disruptions, intrusions, or other systems issues.
                        <SU>41</SU>
                        <FTREF/>
                         However, given the issues outlined above, the Commission believes that the adoption of, and compliance by SCI entities with Regulation SCI, with the modifications from the SCI Proposal as discussed below, will advance the goals of the national market system by enhancing the capacity, integrity, resiliency, availability, and security of the automated systems of entities important to the functioning of the U.S. securities markets, as well as reinforce the requirement that such systems operate in compliance with the Exchange Act and rules and regulations thereunder, thus strengthening the infrastructure of the U.S. securities markets and improving its resilience when technological issues arise. In this respect, Regulation SCI establishes an updated and formalized regulatory framework, thereby helping to ensure more effective Commission oversight of such systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             
                            <E T="03">See, e.g.,</E>
                             October 2, 2012 remarks by Dr. Nancy Leveson, Professor of Aeronautics and Astronautics and Professor of Engineering Systems, MIT, Technology Roundtable (stating, for example, that “it is impossible to build totally secure software systems” and “we've learned that we cannot build an unsinkable ship and cannot build unfailable software”), available at: 
                            <E T="03">http://www.sec.gov/news/otherwebcasts/2012/ttr100212-transcript.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        As proposed, Regulation SCI would have applied to “SCI entities” (estimated in the SCI Proposal to be 44 entities), a term which would have included all self-regulatory organizations (excluding security futures exchanges), ATSs that exceed specified volume thresholds, plan processors for market data NMS plans, and certain exempt clearing agencies. The most significant elements of the SCI Proposal 
                        <SU>42</SU>
                        <FTREF/>
                         would have required each SCI entity to:
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             Each provision of the SCI Proposal is described in further detail below in Section IV. 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.
                        </P>
                    </FTNT>
                    <P>
                        • Implement policies and procedures reasonably designed to ensure that its “SCI systems” and “SCI security systems” have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and 
                        <PRTPAGE P="72257"/>
                        promote the maintenance of fair and orderly markets, with deemed compliance for policies and procedures that are consistent with current SCI industry standards, including identified information technology publications listed on proposed Table A;
                    </P>
                    <P>• Implement policies and procedures reasonably designed to ensure that its systems operate in the manner intended, including in compliance with the federal securities laws and rules, and the entity's rules and governing documents, with safe harbors from liability for SCI entities and individuals;</P>
                    <P>• Upon any “responsible SCI personnel” becoming aware of the occurrence of an “SCI event” (defined to include systems disruptions, systems compliance issues, and systems intrusions), begin to take appropriate corrective action, including mitigating potential harm to investors and market integrity and devoting adequate resources to remedy the SCI event as soon as practicable;</P>
                    <P>• Report to the Commission the occurrence of any SCI event; and notify its members or participants of certain types of SCI events;</P>
                    <P>• Notify the Commission 30 days in advance of “material systems changes” (subject to an exception for exigent circumstances) and provide semi-annual summary progress reports on such material systems changes;</P>
                    <P>• Conduct an annual review, to be performed by objective, qualified personnel, of its compliance with Regulation SCI and submit a report of such annual review to its senior management and to the Commission;</P>
                    <P>• Designate those of its members or participants that would be required to participate in the testing (to occur at least annually) of its business continuity and disaster recovery plans, and coordinate such testing with other SCI entities on an industry- or sector-wide basis; and</P>
                    <P>• Meet certain other requirements, including maintaining records related to compliance with Regulation SCI and providing Commission representatives reasonable access to its systems to assess compliance with the rule.</P>
                    <P>
                        The Commission received substantial comment on the SCI Proposal from a wide range of entities. Commenters generally expressed support for the goals of the rule, but many suggested that the SCI Proposal's scope was unnecessarily broad and could be more tailored to lower compliance costs and still achieve the goal of reducing significant technology risk in the markets. Broadly speaking, the areas of concern garnering the greatest comment included the: (i) Breadth of certain key proposed definitions; (ii) costs associated with the scope of the proposed rule, including its reporting obligations; (iii) publications designated on Table A as proposed examples of “current SCI industry standards;” (iv) proposed entity safe harbor for systems compliance policies and procedures; (v) breadth of the proposed mandatory testing requirements; and (vi) proposed access provision.
                        <SU>43</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             A more detailed discussion of commenters' views can be found below in Section IV.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered the views of commenters in crafting Regulation SCI to meet its goals to strengthen the technology infrastructure of the securities markets and improve its resilience when technology falls short. Many of these modifications are intended to further focus the scope of the requirements from the proposal and to lessen the costs and burdens on SCI entities, while still allowing the Commission to achieve its goals. While Section IV below provides a detailed discussion of the changes the Commission has made to the SCI Proposal in adopting Regulation SCI today,
                        <SU>44</SU>
                        <FTREF/>
                         broadly speaking, the key changes include:
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             The Economic Analysis, 
                            <E T="03">infra</E>
                             Section VI, discusses the economic effects, including the costs and benefits, of the provisions of Regulation SCI, as adopted.
                        </P>
                    </FTNT>
                    <P>• Refining the scope of the proposal by, among other things, revising certain key definitions (including the definition of SCI systems and the definition of SCI ATS to exclude ATSs that trade only municipal securities or corporate debt securities (together, “fixed-income ATSs”)), refining the reporting framework for SCI events, and replacing the proposed 30-day advanced reporting requirement for material systems changes with a quarterly reporting requirement;</P>
                    <P>• Modifying the proposal to differentiate certain obligations and requirements, including tailoring certain obligations based on the criticality of a system (by, for example, adopting a new defined term “critical SCI system” for which heightened requirements will apply), and based on the significance of an event (such as adopting a new defined term “major SCI event” for purposes of the dissemination requirements, and establishing differing reporting obligations for SCI events that have had no or a de minimis impact on the SCI entity's operations or on market participants);</P>
                    <P>• Modifying the proposed policies and procedures requirements relating to both operational capability and the maintenance of fair and orderly markets, as well as systems compliance;</P>
                    <P>• Refining the scope of SCI entity members and participants that would be required to participate in mandatory business continuity/disaster recovery plan testing; and</P>
                    <P>• Eliminating the proposed requirement that SCI entities provide Commission representatives reasonable access to their systems because the Commission can adequately assess an SCI entity's compliance with Regulation SCI through existing recordkeeping requirements and examination authority, as well as through the new recordkeeping requirement in Rule 1005 of Regulation SCI.</P>
                    <P>In addition, the Commission notes that proposed Regulation SCI consisted of a single rule (Rule 1000) that included subparagraphs ((a) through (f)) addressing the various obligations of the rule. However, for clarity and simplification, adopted Regulation SCI is renumbered as Rules 1000 through 1007, as follows:</P>
                    <P>• Adopted Rule 1000 (which corresponds to proposed Rule 1000(a)) contains definitions for terms used in Regulation SCI;</P>
                    <P>• Adopted Rule 1001 (proposed Rules 1000(b)(1)-(2)) contains the policies and procedures requirements for SCI entities relating to both operational capability and the maintenance of fair and orderly markets, as well as systems compliance;</P>
                    <P>• Adopted Rule 1002 (proposed Rules 1000(b)(3)-(5)) contains the obligations of SCI entities with respect to SCI events, which include corrective action, Commission notification, and information dissemination;</P>
                    <P>• Adopted Rule 1003 (proposed Rules 1000(b)(6)-(8)) contains requirements relating to material systems changes and SCI reviews;</P>
                    <P>• Adopted Rule 1004 (proposed Rule 1000(b)(9)) contains requirements relating to business continuity and disaster recovery testing;</P>
                    <P>• Adopted Rule 1005 (proposed Rule 1000(c)) contains requirements relating to recordkeeping;</P>
                    <P>• Adopted Rule 1006 (proposed Rule 1000(d)) contains requirements relating to electronic filing and submission;</P>
                    <P>• Adopted Rule 1007 (proposed Rule 1000(e)) contains requirements for service bureaus.</P>
                    <HD SOURCE="HD1">IV. Description of Adopted Regulation SCI and Form SCI</HD>
                    <HD SOURCE="HD2">A. Definitions Establishing the Scope of Regulation SCI—Rule 1000</HD>
                    <P>
                        A series of definitions set forth in Rule 1000 relate to the scope of Regulation SCI. These include the definitions for “SCI entity” (as well as the types of entities that are SCI entities, 
                        <PRTPAGE P="72258"/>
                        namely “SCI SRO,” SCI ATS,” “plan processor,” and “exempt clearing agency subject to ARP”), “SCI systems” (and related definitions for “indirect SCI systems” and “critical SCI systems”), and “SCI event” (as well as the types of events that constitute SCI events, namely “systems disruption,” “systems compliance issue,” and “systems intrusion”).
                        <SU>45</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             Rule 1000 contains additional defined terms that are discussed in subsequent sections below. 
                            <E T="03">See infra</E>
                             Section IV.B.3 (discussing the definition of “responsible SCI personnel”), Section IV.B.3.d (discussing “major SCI event” and deletion of the proposed definition of “dissemination SCI event”), Section IV.B.4 (discussing deletion of the proposed definition for “material systems change”), Section IV.B.5 (discussing “SCI review” and “senior management”), and Section IV.C.2 (discussing “electronic signature”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. SCI Entities</HD>
                    <P>
                        Regulation SCI imposes requirements on entities meeting the definition of “SCI entity” under the rule. Proposed Rule 1000(a) defined “SCI entity” as an “SCI self-regulatory organization, SCI alternative trading system, plan processor, or exempt clearing agency subject to ARP.” 
                        <SU>46</SU>
                        <FTREF/>
                         The Commission is adopting the definition of “SCI entity” in Rule 1000 as proposed.
                        <SU>47</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release 
                            <E T="03">supra</E>
                             note 13, at Section III.B.1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             Proposed Rule 1000(a) also defined each of the terms within the definition of SCI entity for the purpose of designating specifically the entities that would be subject to Regulation SCI. As described in the Sections IV.A.1.a-d below, the Commission is also adopting these terms as proposed and without modification, with the exception of the definition of “SCI ATS,” which is being revised to exclude ATSs that trade only municipal securities or corporate debt securities.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters discussed the definition of SCI entity generally and advocated for an expansion of the proposed definition, asserting that additional categories of market participants may have the potential to impact the market in the event of a systems issue.
                        <SU>48</SU>
                        <FTREF/>
                         For example, one commenter suggested that the definition of “SCI entity” be extended to include the ATS and broker-dealer entities covered by the Regulation NMS definition of a “trading center.” 
                        <SU>49</SU>
                        <FTREF/>
                         Another commenter stated that the Commission should potentially expand the definition of SCI entity to also include dark pools if they met the volume thresholds of ATSs.
                        <SU>50</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 8-9 and Liquidnet Letter at 2-3. 
                            <E T="03">See also</E>
                             BlackRock Letter at 4 (stating, among other things, that Regulation SCI should extend to any trading platforms that transact significant volume because these venues have a meaningful role and impact on the equity market). 
                            <E T="03">See also infra</E>
                             Section IV.E (discussing comments regarding the potential inclusion of other types of entities, such as broker-dealers generally, within the scope of Regulation SCI).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             Specifically, Section 600(b)(78) of Regulation NMS includes within the definition of a “trading center” “an ATS, an exchange market maker, an OTC market maker, or any other broker or dealer that executes orders internally by trading as principal or crossing orders as agent.” 17 CFR 242.600(b)(68). 
                            <E T="03">See</E>
                             NYSE Letter at 8-9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             
                            <E T="03">See</E>
                             CoreOne Letter at 7-9. CoreOne recommended that the Commission require dark pools to publicly disclose their aggregate volume in a manner similar to disclosures made by exchanges and ATSs. CoreOne stated that, once dark pools publicly disclose their volumes, it would be easier to evaluate whether dark pools should be included as SCI entities. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Other commenters believed that the scope of the definition should be more limited.
                        <SU>51</SU>
                        <FTREF/>
                         For example, one commenter suggested that the definition should only include those entities that are systemically important to the functioning of the U.S. securities markets and should utilize volume thresholds for exchanges and ATSs to make this determination.
                        <SU>52</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             
                            <E T="03">See, e.g.,</E>
                             KCG Letter at 6-8; ITG Letter at 2-4; and CME Letter at 2-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 2-4, 7. This commenter argued that, alternatively, the Commission could impose a lower set of obligations on “lesser” SCI entities. 
                            <E T="03">See id.,</E>
                             at 9-11. 
                            <E T="03">See also infra</E>
                             notes 81-82 (discussing this commenter's suggested thresholds for exchanges) and note 131 (discussing this commenter's recommended thresholds for ATSs). 
                            <E T="03">See</E>
                             discussion in Sections IV.A.1.a and IV.A.1.b (relating to SCI SROs and SCI ATSs, respectively).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters advocated the adoption of a “risk-based” approach, which would entail categorizing market participants based on the criticality of the functions performed rather than applying Regulation SCI to all “SCI entities” equally.
                        <SU>53</SU>
                        <FTREF/>
                         Some commenters suggested replacing the term “SCI entity” with categories of participants based on potential market impact or including in the definition only those participants that are essential to continuous market-wide operation or that are the sole providers of a service in the securities markets.
                        <SU>54</SU>
                        <FTREF/>
                         Other commenters agreed with the proposed scope of the term “SCI entity,” but believed that the various requirements under the rule should be tiered based on risk profiles.
                        <SU>55</SU>
                        <FTREF/>
                         Several commenters identified various factors that should be considered in conducting a risk-assessment such as whether an entity is a primary listing market, is the sole market where the security is traded, or performs a monopoly or utility type role where there is no redundancy built into the marketplace, among others.
                        <SU>56</SU>
                        <FTREF/>
                         Some commenters identified specific functions that they believed to be highly critical to the functioning of the securities markets and thus pose the greatest risk to the markets in the event of a systems issue, including securities information processing, clearance and settlement systems, and trading of exclusively listed securities, among others.
                        <SU>57</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 5-6; SIFMA Letter at 4-5; KCG Letter at 2-3, 6-8; Fidelity Letter at 2-4; UBS Letter at 2-4; and LiquidPoint Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 3-6; Direct Edge Letter at 1-2; and KCG Letter at 2-3, 6-8. Specifically, Direct Edge stated that SCI entities should include Commission-registered exchanges, securities information processors under approved NMS plans for market data, and clearance and settlement systems.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 4 and Fidelity Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 4 and Fidelity Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 4; Direct Edge Letter at 1-2; and KCG Letter at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of the comments, the Commission has determined to adopt the overall scope of entities covered by Regulation SCI as proposed.
                        <SU>58</SU>
                        <FTREF/>
                         As discussed below, the Commission continues to believe that it is appropriate and would further the goals of the national market system to subject all SROs (excluding securities futures exchanges), ATSs meeting certain volume thresholds with respect to NMS stocks and non-NMS stocks (discussed further below), plan processors, and certain exempt clearing agencies to the requirements of Regulation SCI. The Commission believes that this definition appropriately includes those entities that play a significant role in the U.S. securities markets and/or have the potential to impact investors, the overall market, or the trading of individual securities.
                        <SU>59</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             
                            <E T="03">But see infra</E>
                             Section IV.A.1.b (discussing revisions to the definition of “SCI ATS”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             
                            <E T="03">See infra</E>
                             Sections IV.A.1.a-d (discussing more specifically each category of entity included within the definition of “SCI entity”).
                        </P>
                    </FTNT>
                    <P>
                        While some commenters supported expanding the definition of SCI entity to encompass various other types of entities, the Commission has determined not to expand the scope of entities subject to Regulation SCI at this time. As noted in the SCI Proposal, Regulation SCI is based, in part, on the ARP Inspection Program, which has included the voluntary participation of all active registered clearing agencies, all registered national securities exchanges, the only registered national securities association—Financial Industry Regulatory Authority (“FINRA”), one exempt clearing agency, and one ATS.
                        <SU>60</SU>
                        <FTREF/>
                         The ARP Inspection Program has also included the systems of entities that process and disseminate quotation and transaction data on behalf of the Consolidated Tape Association System (“CTA Plan”), Consolidated Quotation System (“CQS Plan”), Joint Self-Regulatory Organization Plan 
                        <PRTPAGE P="72259"/>
                        Governing the Collection, Consolidation, and Dissemination of Quotation and Transaction Information for Nasdaq-Listed Securities Traded on Exchanges on an Unlisted Trading Privileges Basis (“Nasdaq UTP Plan”), and Options Price Reporting Authority (“OPRA Plan”).
                        <SU>61</SU>
                        <FTREF/>
                         Significant-volume ATSs have also been subject to certain aspects of the ARP Policy Statements pursuant to Regulation ATS.
                        <SU>62</SU>
                        <FTREF/>
                         In addition, one entity that has been granted an exemption from registration as a clearing agency has been subject to the ARP Inspection Program pursuant to the conditions of the exemption order issued by the Commission.
                        <SU>63</SU>
                        <FTREF/>
                         The scope of the definition of SCI entity is intended to largely reflect the historical reach of the ARP Inspection Program and existing Rule 301 of Regulation ATS, while also expanding the coverage to certain additional entities that the Commission believes play a significant role in the U.S. securities markets and/or have the potential to impact investors, the overall market, or the trading of individual securities. The Commission acknowledged in the SCI Proposal that there may be other categories of entities not included within the definition of SCI entity that, given their increasing size and importance, could pose risks to the market should an SCI event occur.
                        <SU>64</SU>
                        <FTREF/>
                         However, as discussed in further detail below,
                        <SU>65</SU>
                        <FTREF/>
                         the Commission believes that, at this time, the entities included within the definition of SCI entity, because of their current role in the U.S. securities markets and/or their level of trading activity, have the potential to pose the most significant risk in the event of a systems issue. Although some commenters suggested that Regulation SCI should cover a greater range of market participants,
                        <SU>66</SU>
                        <FTREF/>
                         the Commission believes that it is important to move forward now on rules that will meaningfully enhance the technology standards and oversight of key markets and market infrastructure. Further, the Commission believes that a measured approach that takes an incremental expansion from the entities covered under the ARP Inspection Program is an appropriate method for imposing the mandatory requirements of Regulation SCI at this time given the potential costs of compliance. This approach will enable the Commission to monitor and evaluate the implementation of Regulation SCI, the risks posed by the systems of other market participants, and the continued evolution of the securities markets, such that it may consider, in the future, extending the types of requirements in Regulation SCI to additional categories of market participants, such as non-ATS broker-dealers, security-based swap dealers, investment advisers, investment companies, transfer agents, and other key market participants. As noted in the SCI Proposal, should the Commission decide to propose to apply some or all of the requirements of Regulation SCI to additional types of entities, the Commission will issue a separate release discussing such a proposal and seeking public comment.
                        <SU>67</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18086.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             
                            <E T="03">See infra</E>
                             note 196 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             
                            <E T="03">See</E>
                             Rule 301(b)(6) of Regulation ATS, 17 CFR 242.301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18096-97. 
                            <E T="03">See also infra</E>
                             Section IV.A.1.d (discussing the inclusion in Regulation SCI of exempt clearing agencies subject to ARP).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18138-39.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             
                            <E T="03">See infra</E>
                             Sections IV.A.1.a-d (discussing more specifically each category of entity included within the definition of “SCI entity”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             
                            <E T="03">See supra</E>
                             notes 48-50 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18138.
                        </P>
                    </FTNT>
                    <P>
                        With respect to another commenter's recommendation regarding dark pools, to the extent that this commenter intended its comment to refer to ATSs, ATSs would be included within the scope of Regulation SCI if they met the applicable volume thresholds discussed below.
                        <SU>68</SU>
                        <FTREF/>
                         To the extent that this commenter intended its comment to refer to other types of non-ATS dark venues where broker-dealers internalize order flow, the Commission notes that it has determined not to extend the scope of Regulation SCI to other types of broker-dealers at this time for the reasons discussed below.
                        <SU>69</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.A.1.b (discussing definition of “SCI ATS”). This commenter also recommended that the Commission require dark pools to publicly disclose their aggregate volume to make it easier to evaluate whether dark pools should be included as SCI entities, and supported FINRA's plans to require such trading volume disclosures. The Commission notes that FINRA recently adopted new Rule 4552, which requires each ATS to report to FINRA weekly volume information regarding transactions in NMS stocks and OTC equity securities, and FINRA makes such information publicly available on its Web site. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 71341 (January 17, 2014), 79 FR 4213 (January 24, 2014) (approving FINRA Rule 4552 requiring each ATS to report to FINRA weekly volume information and number of securities transactions). The Commission also notes that all ATSs (including dark pool ATSs) are required under Regulation ATS to provide the Commission with quarterly trading volume information. 
                            <E T="03">See</E>
                             Rule 301(b)(9) of Regulation ATS, 17 CFR 242.301(b)(9).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             
                            <E T="03">See infra</E>
                             text accompanying notes 121-125.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has also determined not to further limit the scope of entities subject to Regulation SCI as suggested by some commenters. As discussed in more detail below, the Commission continues to believe that each of the identified categories of entities plays a significant role in the U.S. securities markets and/or has the potential to impact investors, the overall market, or the trading of individual securities, and thus should be subject to the requirements of Regulation SCI. Accordingly, the Commission does not agree that it should adopt a “risk-based” approach to 
                        <E T="03">further limit</E>
                         the categories of market participants subject to Regulation SCI. The Commission believes that limiting the applicability of Regulation SCI to only the most systemically important entities posing the highest risk to the markets is too limited of a category of market participants, as it would exclude certain entities that, in the Commission's view, have the potential to pose significant risks to the securities markets should an SCI event occur. However, the Commission believes it is appropriate to incorporate risk-based considerations in various other aspects of Regulation SCI. Consistent with the views of some commenters advocating that the requirements of Regulation SCI should be tailored to the specific risk-profile of a particular entity or particular system,
                        <SU>70</SU>
                        <FTREF/>
                         the Commission notes that Regulation SCI, as proposed, was intended to incorporate a consideration of risk within its requirements and believes it is appropriate to more explicitly incorporate risk considerations in various provisions of adopted Regulation SCI. For example, as discussed in further detail below, the requirement to have reasonably designed policies and procedures relating to operational capability was designed to permit SCI entities to take a risk-based approach in developing their policies and procedures based on the criticality of a particular system.
                        <SU>71</SU>
                        <FTREF/>
                         In addition, the Commission believes that it is appropriate to further incorporate a risk-based approach into other aspects of the regulation, and thus, as discussed below, is adopting a new term—“critical SCI systems”—to identify systems that the Commission believes should be subject to heightened requirements in certain areas.
                        <SU>72</SU>
                        <FTREF/>
                         Further, the Commission has determined that certain other definitions (such as the definition of “SCI systems”), and certain requirements of the rule (such as Commission notification for SCI events and material systems changes), should be scaled back and refined consistent with a risk-based approach, as discussed 
                        <PRTPAGE P="72260"/>
                        below. The Commission believes that these modifications, further incorporating risk-based considerations in the requirements and scaling back certain requirements, provide the proper balance between requiring that the appropriate entities are subject to baseline standards for systems capacity, integrity, resiliency, availability, security, and compliance, while reducing the overall burden of the rule for all SCI entities, which is consistent with, and responsive to, the views of those commenters that the Commission take a more risk-based approach to SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             
                            <E T="03">See supra</E>
                             note 55 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.1 (discussing the policies and procedures requirement under adopted Rule 1001(a)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.A.2.c (discussing the definition of “critical SCI systems”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">a. SCI Self-Regulatory Organization or SCI SRO</HD>
                    <P>
                        Proposed Rule 1000(a) defined “SCI self-regulatory organization,” or “SCI SRO,” to be consistent with the definition of “self-regulatory organization” set forth in Section 3(a)(26) of the Exchange Act.
                        <SU>73</SU>
                        <FTREF/>
                         This definition covered all national securities exchanges registered under Section 6(b) of the Exchange Act,
                        <SU>74</SU>
                        <FTREF/>
                         registered securities associations,
                        <SU>75</SU>
                        <FTREF/>
                         registered clearing agencies,
                        <SU>76</SU>
                        <FTREF/>
                         and the Municipal Securities Rulemaking Board (“MSRB”).
                        <SU>77</SU>
                        <FTREF/>
                         The definition, however, excluded an exchange that lists or trades security futures products that is notice-registered with the Commission as a national securities exchange pursuant to Section 6(g) of the Exchange Act, as well as any limited purpose national securities association registered with the Commission pursuant to Exchange Act Section 15A(k).
                        <SU>78</SU>
                        <FTREF/>
                         Accordingly, the proposed definition of SCI SRO in Rule 1000(a) included all national securities exchanges registered under Section 6(b) of the Exchange Act, all registered securities associations, all registered clearing agencies, and the MSRB.
                        <SU>79</SU>
                        <FTREF/>
                         The definition of “SCI self-regulatory organization” or “SCI SRO” is being adopted in Rule 1000 as proposed.
                        <SU>80</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 78c(a)(26): “The term `self-regulatory organization' means any national securities exchange, registered securities association, or registered clearing agency, or (solely for purposes of sections 19(b), 19(c), and 23(b) of this title) the Municipal Securities Rulemaking Board established by section 15B of this title.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             Currently, these registered national securities exchanges are: (1) BATS Exchange, Inc. (“BATS”); (2) BATS Y-Exchange, Inc. (“BATS-Y”); (3) Boston Options Exchange LLC (“BOX”); (4) CBOE; (5) C2; (6) Chicago Stock Exchange, Inc. (“CHX”); (7) EDGA Exchange, Inc. (“EDGA”); (8) EDGX Exchange, Inc. (“EDGX”); (9) International Securities Exchange, LLC (“ISE”); (10) Miami International Securities Exchange, LLC (“MIAX”); (11) NASDAQ OMX BX, Inc. (“Nasdaq OMX BX”); (12) NASDAQ OMX PHLX LLC (“Nasdaq OMX Phlx”); (13) Nasdaq; (14) National Stock Exchange, Inc. (“NSX”); (15) NYSE; (16) NYSE MKT; (17) NYSE Arca; and (18) ISE Gemini, LLC (“ISE Gemini”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             FINRA is the only registered national securities association.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             Currently, there are seven clearing agencies (Depository Trust Company (“DTC”); Fixed Income Clearing Corporation (“FICC”); National Securities Clearing Corporation (“NSCC”); Options Clearing Corporation (“OCC”); ICE Clear Credit; ICE Clear Europe; and CME) with active operations that are registered with the Commission. The Commission notes that in 2012 it adopted Rule 17Ad-22, which requires registered clearing agencies to have effective risk management policies and procedures in place. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 68080 (October 22, 2012), 77 FR 66220 (November 2, 2012) (“Clearing Agency Standards Release”). The Commission believes that Regulation SCI, to the extent it addresses areas of risk management similar to those addressed by Rule 17Ad-22(d)(4), complements Rule 17Ad-22(d)(4). 
                        </P>
                        <P>
                             Additionally, on March 12, 2014, the Commission proposed rules that would apply to SEC-registered clearing agencies that have been designated as systemically important by the Financial Stability Oversight Council or that are involved in activities with a more complex risk profile, such as clearing security-based swaps. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 71699 (Mar. 12, 2014), 79 FR 16865 (March 26, 2014) (“Covered Clearing Agencies Proposal”). Regulation SCI and proposed Rule 17Ad-22(e)(17) are intended to be consistent and complementary. 
                            <E T="03">See also</E>
                             Covered Clearing Agencies Proposal, 79 FR at 16866, n.1 and accompanying text (discussing the Commission's consideration of the relevant international standards).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             15 U.S.C. 78c(a)(26). As noted in the Proposing Release, historically, the ARP Inspection Program did not include the MSRB, but instead focused on entities having trading, quotation and transaction reporting, and clearance and settlement systems more closely connected to the equities and options markets. The Commission believes that it is appropriate to apply Regulation SCI to the MSRB, particularly given the fact that the MSRB is the only SRO relating to municipal securities and is a key provider of consolidated market data for the municipal securities market. Accordingly, as proposed, the term “SCI SRO” included the MSRB. In 2008, the Commission amended Rule 15c2-12 to designate the MSRB as the single centralized disclosure repository for continuing municipal securities disclosure. In 2009, the MSRB established the Electronic Municipal Market Access system (“EMMA”). EMMA now serves as the official repository of municipal securities disclosure, providing the public with free access to relevant municipal securities data, and is the central database for information about municipal securities offerings, issuers, and obligors. Additionally, the MSRB's Real-Time Transaction Reporting System (“RTRS”), with limited exceptions, requires municipal bond dealers to submit transaction data to the MSRB within 15 minutes of trade execution, and such near real-time post-trade transaction data can be accessed through the MSRB's EMMA Web site. While pre-trade price information is not as readily available in the municipal securities market, the Commission's Report on the Municipal Securities Market also recommended that the Commission and MSRB explore the feasibility of enhancing EMMA to collect best bids and offers from material ATSs and make them publicly available on fair and reasonable terms. 
                            <E T="03">See</E>
                             Report on the Municipal Securities Market (July 31, 2012), available at: 
                            <E T="03">http://www.sec.gov/news/studies/2012/munireport073112.pdf.</E>
                             The Commission believes that the MSRB's SCI systems currently are limited to those operated by or on behalf of the MSRB that directly support market data (
                            <E T="03">i.e.,</E>
                             currently limited to the EMMA, RTRS, and SHORT systems). As discussed more fully below, the EMMA, RTRS, and SHORT systems referenced by the MSRB in its comment letter would be market data systems within the definition of SCI systems because they provide or directly support price transparency. 
                            <E T="03">See infra</E>
                             note 253 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 78f(g); 15 U.S.C. 78
                            <E T="03">o</E>
                            -3(k). These entities are security futures exchanges and the National Futures Association, for which the CFTC serves as their primary regulator. 
                            <E T="03">See generally</E>
                             CFTC Concept Release on Risk Controls and System Safeguards for Automated Trading Environments, 78 FR 56542 (September 12, 2013) (“CFTC Concept Release”) (describing the CFTC's regulatory scheme for addressing risk controls relating to automated systems).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             For any SCI SRO that is a national securities exchange, any facility of such national securities exchange, as defined in Section 3(a)(2) of the Exchange Act, 15 U.S.C. 78c(a)(2), also is covered because such facilities are included within the definition of “exchange” in Section 3(a)(1) of the Exchange Act, 15 U.S.C. 78c(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             The Commission notes that NSX ceased trading as of the close of business on May 30, 2014. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 72107 (May 2, 2014), 79 FR 27017 (May 12, 2014) (Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Cease Trading on Its Trading System) (“NSX Trading Cessation Notice”). In the NSX Trading Cessation Notice, NSX stated: “[T]he Exchange will continue to be registered as a national securities exchange and will continue to retain its status as a self-regulatory organization[;]” and further, that it “shall file a proposed rule change pursuant to Rule 19b-4 of the Exchange Act prior to any resumption of trading on the Exchange pursuant to Chapter XI (Trading Rules).” Because NSX remains a national securities exchange registered under Section 6(b) of the Exchange Act, it continues to meet the definition of SCI entity, and is counted as an SCI entity for purposes of this release.
                        </P>
                    </FTNT>
                    <P>
                        One commenter suggested that the rule should include volume thresholds for exchanges.
                        <SU>81</SU>
                        <FTREF/>
                         Specifically, this commenter recommended that, with regard to exchanges, the definition should include only those exchanges that have five percent or more of average daily dollar volume in at least five NMS stocks for four of the previous six months.
                        <SU>82</SU>
                        <FTREF/>
                         Another commenter asked the Commission to adopt certain specific exceptions to the definition of SCI SRO and SCI entity for entities that are dually registered with the CFTC and Commission where the CFTC is the entity's “primary regulator” and for any entity that does not play a “significant role” in the markets subject to the Commission's jurisdiction and that cannot have a “significant impact” on the markets subject to the Commission's jurisdiction.
                        <SU>83</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 10. This commenter also suggested similar revised thresholds for SCI ATSs. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             note 131 and accompanying text. Although only one commenter specifically commented on the proposed inclusion of SCI SROs within the scope of Regulation SCI, as discussed above, some commenters believed that Regulation SCI should generally take a more risk-based or tiered approach generally which, in some cases, would affect which entities (including SCI SROs) would be subject to Regulation SCI. 
                            <E T="03">See supra</E>
                             notes 53-56 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 2.
                        </P>
                    </FTNT>
                    <P>
                        The Commission does not believe that a trading volume threshold is 
                        <PRTPAGE P="72261"/>
                        appropriate for SCI SROs that are exchanges, but instead believes that Regulation SCI should apply to all SCI SROs. The threshold suggested by the commenter would exclude from Regulation SCI those exchanges with volumes below the suggested threshold; however, the Commission believes that all exchanges play a significant role in our securities markets. For example, all stock exchanges are subject to a variety of specific public obligations under the Exchange Act, including the requirements of Regulation NMS which, among other things, designates the best bid or offer of such exchanges to be protected quotations.
                        <SU>84</SU>
                        <FTREF/>
                         Accordingly, every exchange may have a protected quotation that can obligate market participants to send orders to that exchange. Among other reasons, given that market participants may be required to send orders to any one of the exchanges at any given time if such exchange is displaying the best bid or offer, the Commission believes that it is important that the safeguards of Regulation SCI apply equally to all exchanges irrespective of trading volume.
                    </P>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             
                            <E T="03">See generally</E>
                             17 CFR 242.600-612. In addition, as the commenter's suggested thresholds would apply only with respect to exchanges that trade NMS stocks, national securities exchanges that do not trade NMS stocks (
                            <E T="03">i.e.,</E>
                             options exchanges) would also be excluded from Regulation SCI under the commenter's suggestion. The Commission believes that it would be inappropriate to exclude options exchanges from the requirements of Regulation SCI, because technology risks are equally applicable to such exchanges, as evidenced by recent significant technology incidents affecting the options markets. 
                            <E T="03">See supra</E>
                             notes 28-31 and accompanying text. As such, systems issues at options exchanges can pose significant risks to the markets, and the Commission believes that the inclusion of options exchanges within the scope of Regulation SCI is necessary to achieve the goals of Regulation SCI.
                        </P>
                    </FTNT>
                    <P>
                        With regard to one commenter's suggestion to except from the definition of SCI SRO those entities dually registered with the CFTC and Commission where the CFTC is the entity's “primary regulator,”
                        <SU>85</SU>
                        <FTREF/>
                         the Commission disagrees that such entities should be relieved from the requirements of Regulation SCI solely because they are dually registered.
                        <SU>86</SU>
                        <FTREF/>
                         While the CFTC is responsible for overseeing such an entity with regard to its futures activities, it does not have oversight responsibility for the entity's securities-related activities and systems. While the commenter stated that it (as a dual registrant) is already subject to similar requirements to adopt controls and procedures with regard to operational risk and reliability, security, and capacity of its systems pursuant to CFTC regulations, the Commission again notes that such requirements do not apply to such an entity's securities-related systems as such systems are outside of the CFTC's jurisdiction and, as such, such systems would not be subject to inspection and examination by the CFTC for compliance with such requirements.
                        <SU>87</SU>
                        <FTREF/>
                         Further, Regulation SCI imposes a notification framework to inform the Commission of SCI events and material systems changes, as well as other requirements unique to Regulation SCI. Accordingly, the Commission believes that such entities should be subject to the requirements of Regulation SCI. In addition, as noted above, this commenter also asked the Commission to create an exception for any entity that does not play a “significant role” in the markets subject to the Commission's jurisdiction and that cannot have a “significant impact” on the markets subject to the Commission's jurisdiction.
                        <SU>88</SU>
                        <FTREF/>
                         While the Commission disagrees with excluding SROs from coverage as discussed above, the Commission notes that it is revising the proposed definition of SCI systems to clarify that the term SCI systems encompasses only those systems that, 
                        <E T="03">with respect to securities,</E>
                         directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance, as discussed below.
                        <SU>89</SU>
                        <FTREF/>
                         Accordingly, the Commission believes this change should address the commenter's concerns about the requirements applying to entities whose systems cannot affect the markets subject to the Commission's jurisdiction, 
                        <E T="03">i.e.,</E>
                         the U.S. securities markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             
                            <E T="03">See supra</E>
                             note 83 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             The commenter notes that the Commission has proposed to exclude from the definition of SCI SRO those exchanges that list or trade security futures products that are notice-registered with the Commission pursuant to Section 6(g), as well as limited purpose national securities associations registered with the Commission pursuant to Exchange Act Section 15A(k). 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18093, n. 97 and accompanying text. The Commission notes that such entities are subject to the joint jurisdiction of the Commission and the CFTC. To avoid duplicative regulation, however, the CFMA established a system of notice registration under which trading facilities and intermediaries that are already registered with either the Commission or the CFTC may register with the other agency on an expedited basis for the limited purpose of trading security futures products. A “notice registrant” is then subject to primary oversight by one agency, and is exempted under the CFMA from all but certain specified provisions of the laws administered by the other agency. 
                            <E T="03">See</E>
                             Section 6(g)(4) and Section 15A(k)(3)-(4) (enumerating the provisions of the Exchange Act from which a notice-registered exchange and limited purpose national securities association, respectively, are exempted). Given this, the Commission believes that it is appropriate to defer to the CFTC regarding the systems integrity of these entities). 
                            <E T="03">See also generally</E>
                             CFTC Concept Release, 
                            <E T="03">supra</E>
                             note 78. This regulatory scheme does not apply outside of the specific contexts of security futures exchanges and associations. In contrast, entities that are registered with both the Commission and the CFTC in other capacities, such as clearing agencies, are subject to a full set of regulations by each regulator. The Exchange Act and Commodity Exchange Act do not exempt these entities, due to any dual regulatory scheme, from any provisions of the laws administered by the Commission and, as discussed further below, the Commission believes they should not be afforded an exclusion from Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             The Commission notes that, to the extent that such an entity's systems for its functions that fall in the purview of the Commission (relating to securities and securities-based swaps) and that fall in the purview of the CFTC (relating to futures and swaps) are integrated, it believes that the focus of the CFTC's exams and inspections of such systems would be on such systems' functionality related to non-securities-related activities, such as swaps or futures, and not those related to securities activities. Thus, the Commission believes that the potential examination and inspection of such integrated systems by both the CFTC and SEC does not support the exclusion of the SCI entities operating such systems, or the systems themselves, from the scope of Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             
                            <E T="03">See supra</E>
                             note 83 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (emphasis added). 
                            <E T="03">See also infra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. SCI Alternative Trading System</HD>
                    <P>
                        Proposed Rule 1000(a) defined the term “SCI alternative trading system,” or “SCI ATS,” as an alternative trading system, as defined in § 242.300(a), which during at least four of the preceding six calendar months, had: (1) With respect to NMS stocks—(i) five percent or more in any single NMS stock, and 0.25 percent or more in all NMS stocks, of the average daily dollar volume reported by an effective transaction reporting plan, or (ii) one percent or more, in all NMS stocks, of the average daily dollar volume reported by an effective transaction reporting plan; (2) with respect to equity securities that are not NMS stocks and for which transactions are reported to a self-regulatory organization, five percent or more of the average daily dollar volume as calculated by the self-regulatory organization to which such transactions are reported; or (3) with respect to municipal securities or corporate debt securities, five percent or more of either—(i) the average daily dollar volume traded in the United States, or (ii) the average daily transaction volume traded in the United States.
                        <SU>90</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.1.
                        </P>
                    </FTNT>
                    <P>
                        The proposed definition would have modified the thresholds currently appearing in Rule 301(b)(6) of Regulation ATS that apply to significant-volume ATSs.
                        <SU>91</SU>
                        <FTREF/>
                         Specifically, 
                        <PRTPAGE P="72262"/>
                        the proposed definition would have: Used average daily dollar volume thresholds, instead of an average daily share volume threshold, for ATSs that trade NMS stocks or equity securities that are not NMS stocks (“non-NMS stocks”); used alternative average daily dollar and transaction volume-based tests for ATSs that trade municipal securities or corporate debt securities; lowered the volume thresholds applicable to ATSs for each category of asset class; and moved the proposed thresholds to Regulation SCI. In particular, with respect to NMS stocks, the Commission proposed to change the volume threshold from 20 percent of average daily volume in any NMS stock such that an ATS that traded NMS stocks that met either of the following two alternative threshold tests would be subject to the requirements of proposed Regulation SCI: (i) Five percent or more in any NMS stock, and 0.25 percent or more in all NMS stocks, of the average daily dollar volume reported by an effective transaction reporting plan; or (ii) one percent or more, in all NMS stocks, of the average daily dollar volume reported by an effective transaction reporting plan. With respect to non-NMS stocks, municipal securities, and corporate debt securities, the Commission proposed to reduce the standard from 20 percent to five percent for these types of securities,
                        <SU>92</SU>
                        <FTREF/>
                         the same percentage threshold for such types of securities that triggers the fair access provisions of Rule 301(b)(5) of Regulation ATS.
                        <SU>93</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             17 CFR 242.301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             
                            <E T="03">See</E>
                             Rule 301(b)(5) of Regulation ATS under the Exchange Act. 17 CFR 242.301(b)(5). In addition, as noted above, the proposed rule used alternative average daily dollar and transaction volume-based tests for ATSs that trade municipal securities or corporate debt securities.
                        </P>
                    </FTNT>
                    <P>The proposed definition of “SCI ATS” is being adopted substantially as proposed with regard to ATSs trading NMS stocks and ATSs trading non-NMS stocks, with the addition of a six-month compliance period for entities satisfying the thresholds in the definition for the first time, as discussed in more detail below. However, for the reasons discussed below, the Commission has determined to exclude from the definition of “SCI ATS” ATSs that trade only municipal securities or corporate debt securities and accordingly, such ATSs will not be subject to the requirements of Regulation SCI.</P>
                    <HD SOURCE="HD3">Inclusion of ATSs Generally</HD>
                    <P>
                        Many commenters provided comment on the inclusion of ATSs within the scope of Regulation SCI. Some commenters believed that more ATSs should be covered by Regulation SCI.
                        <SU>94</SU>
                        <FTREF/>
                         For example, some commenters suggested that the term “SCI ATS” should include all ATSs, because these commenters believed that they have the potential to negatively impact the market in the event of a systems issue.
                        <SU>95</SU>
                        <FTREF/>
                         Moreover, one commenter stated that the Commission should not distinguish between ATSs based on calculated thresholds because an ATS might limit trading on its system so as to avoid being subject to the requirements of Regulation SCI.
                        <SU>96</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 9-10; Lauer Letter at 4; and CoreOne Letter at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 9-10; and Lauer Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 9-10.
                        </P>
                    </FTNT>
                    <P>
                        Conversely, other commenters stated that fewer, or even no, ATSs should be covered.
                        <SU>97</SU>
                        <FTREF/>
                         Such commenters generally argued that there are key differences between ATSs and exchanges, and thus, ATSs should be regulated differently from exchanges and not be included in Regulation SCI with exchanges.
                        <SU>98</SU>
                        <FTREF/>
                         The differences identified by commenters included: ATSs' relative market shares and sizes; the fact that ATSs are already subject to various regulations as broker-dealers (including Rule 15c3-5 under the Exchange Act, various FINRA rules, and Regulation ATS); and certain fundamental economic differences between the two types of entities (including that exchanges can gain revenue from listing and market data, have self-clearing, and have a protected quote).
                        <SU>99</SU>
                        <FTREF/>
                         One commenter argued that, if the Commission were to include ATSs in Regulation SCI, it should treat ATSs and SROs equally by allowing ATSs to have the same benefits of SROs, including allowing ATSs to derive an income stream from contributions to the SIP, have access to clearing, and have immunity from lawsuits.
                        <SU>100</SU>
                        <FTREF/>
                         Other commenters also noted that, although ATSs have an increasingly large, collective market share, ATSs have not contributed to any of the recent major systems issues that have impacted the market.
                        <SU>101</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 3; ITG Letter at 3; KCG Letter at 8; and OTC Markets Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 3; ITG Letter at 3; KCG Letter at 9, 14-17; TMC Letter at 2; and OTC Markets Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 4; and BIDS Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter stated that the SCI Proposal unfairly discriminated against ATSs by including them within the definition of SCI entity.
                        <SU>102</SU>
                        <FTREF/>
                         Specifically, although this commenter did not believe that Regulation SCI should be expanded to include more entities, it stated that the SCI Proposal's failure to capture certain entities (such as clearing firms, market makers, block positioners, and order routing firms) that it believed could have a greater impact on market stability in the event of a systems issue, while including ATSs, demonstrates that the proposal is arbitrary, capricious, and unfairly discriminatory in nature.
                        <SU>103</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of the comment letters, the Commission continues to believe that the inclusion of ATSs that trade NMS stocks and non-NMS stocks in Regulation SCI is appropriate.
                        <SU>104</SU>
                        <FTREF/>
                         The Commission believes that certain of those ATSs play an important role in today's securities markets, and thus should be subject to the safeguards and obligations of Regulation SCI. As noted in the SCI Proposal, the equity markets have evolved significantly over recent years, resulting in an increase in the number of trading centers and a reduction in the concentration of trading activity.
                        <SU>105</SU>
                        <FTREF/>
                         As such, even smaller trading centers, such as certain higher-volume ATSs, now collectively represent a significant source of liquidity for NMS stocks and some ATSs have similar and, in some cases, greater trading volume than some national securities exchanges, with no single national securities exchange executing more than approximately 19 percent of volume in NMS stocks in today's securities markets.
                        <SU>106</SU>
                        <FTREF/>
                         Accordingly, the Commission believes that ATSs meeting certain volume thresholds can play a significant role in the securities markets and, given their heavy reliance on automated systems, have the potential to significantly impact investors, the overall market, 
                        <PRTPAGE P="72263"/>
                        and the trading of individual securities should an SCI event occur.
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             Given the inclusion of ATSs that trade NMS stocks and non-NMS stocks within the scope of Regulation SCI, Regulation ATS is also being amended to remove paragraphs (b)(6)(i)(A) and (b)(6)(i)(B) of Rule 301 so that Rule 301(b)(6) will no longer apply to ATSs trading NMS stocks and non-NMS stocks. However, as described below, the Commission has determined to exclude ATSs that trade only municipal securities or corporate debt securities from the scope of Regulation SCI, and such ATSs will remain subject to the requirements of Rule 301(b)(6) if they meet the volume thresholds therein. 17 CFR 242.301(b)(6). 
                            <E T="03">See supra</E>
                             notes 14 and 20 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18094.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             
                            <E T="03">See</E>
                             market volume statistics reported by BATS, available at: 
                            <E T="03">http://www.batstrading.com/market_summary/</E>
                             (no single stock exchange executed more than approximately 19 percent during the second quarter of 2014, with Nasdaq having the highest market share of 18.6 percent). In comparison, according to data from Form ATS-R for the second quarter of 2014, approximately 18 percent of consolidated NMS stocks dollar volume took place on ATSs.
                        </P>
                    </FTNT>
                    <P>
                        Commenters identified certain differences between exchanges and ATSs, which commenters argued justified different treatment under Regulation SCI for ATSs or exclusion of ATSs from the regulation completely.
                        <SU>107</SU>
                        <FTREF/>
                         While the Commission recognizes that there are some fundamental differences between ATSs and exchanges, including certain of those identified by commenters, the Commission does not agree that all ATSs should be excluded from Regulation SCI because, as discussed above, it believes that there are certain significant-volume ATSs that have the potential to significantly impact investors, the overall market, or the trading of individual securities should an SCI event occur. At the same time, the risk-based considerations permitted in adopted Regulation SCI may result in the systems of those ATSs that are subject to Regulation SCI (
                        <E T="03">i.e.,</E>
                         SCI ATSs) being subject to less stringent requirements than the systems of SROs or other SCI entities in certain areas. For example, as discussed in further detail below, the Commission is adopting a definition of “critical SCI systems,” which are a subset of SCI systems that are subject to certain heightened requirements under Regulation SCI. This definition is intended to capture those systems that are core to the functioning of the securities markets or that represent “single points of failure” and thus, pose the greatest risk to the markets. The Commission believes that, as currently constituted, relative to the systems of SCI SROs, the systems of SCI ATSs generally would not fall within this category of critical SCI systems, and thus such SCI ATSs would not be subject to the more stringent requirements that would be applicable to the critical SCI systems of other SCI entities. The Commission also notes that other requirements under Regulation SCI are designed to be consistent with a risk-based approach. The Commission believes that this approach recognizes the different roles played by different SCI systems at various SCI entities and, where permitted, allows each SCI entity, including SCI ATSs, to tailor the applicable requirements accordingly.
                    </P>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             
                            <E T="03">See supra</E>
                             notes 98-99 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        While some commenters noted that ATSs have not contributed to any of the recent high-profile systems issues,
                        <SU>108</SU>
                        <FTREF/>
                         the Commission does not believe that the relative lack of high-profile systems issues at ATSs to date is an indication that ATSs do not have the potential to have a significant impact on the market in the event of a future systems issue.
                        <SU>109</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             
                            <E T="03">See supra</E>
                             note 101 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             The Commission also notes that, as discussed above, in November 2013, a systems issue at OTC Link ATS led FINRA to halt trading in all OTC securities for over three hours. 
                            <E T="03">See supra</E>
                             note 33 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters noted the competitive environment of ATSs and argued that, if one ATS experiences a systems issue and becomes temporarily unavailable, trading can be easily rerouted to other venues.
                        <SU>110</SU>
                        <FTREF/>
                         The Commission acknowledges that a temporary outage at an ATS (or at a SCI SRO, for that matter) may not lead to a widespread systemic disruption. However, the Commission notes that Regulation SCI is not designed to solely address system issues that cause widespread systemic disruption, but also to address more limited systems malfunctions and other issues that can harm market participants or create compliance issues.
                        <SU>111</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 3; and KCG Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             The Commission notes that each ATS provides different services in terms of, among other things, pricing, latency, and order fills to meet investors' specific needs. Thus, for example, an ATS outage could interfere with the supply of certain services that investors demand and, thus, could impose costs on investors.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters also stated that inclusion of ATSs is not necessary because ATSs are already subject to sufficient regulations as broker-dealers, citing Rule 15c3-5 under the Exchange Act, various FINRA rules, and Regulation ATS.
                        <SU>112</SU>
                        <FTREF/>
                         While the Commission acknowledges that these rules similarly impose requirements related to the capacity, integrity and/or security of a broker-dealer's systems and are designed to address some of the same concerns that Regulation SCI is intended to address, the Commission notes that these rules generally take a different approach than Regulation SCI. For example, the obligations of an ATS under Rule 15c3-5 address vulnerability in the national market system that relate specifically to market access,
                        <SU>113</SU>
                        <FTREF/>
                         whereas Regulation SCI is designed to further the goals of the national market system more broadly by helping to ensure the capacity, integrity, resiliency, availability, and security of the automated systems of entities important to the functioning of the U.S. securities markets.
                        <SU>114</SU>
                        <FTREF/>
                         Thus, the Commission has determined to include ATSs within the scope of Regulation SCI because of their role as markets and a potential significant source of liquidity. With regard to the FINRA rules identified by commenters, the Commission does not believe that these rules, even when considered in combination with Rule 15c3-5, are an appropriate substitute for the comprehensive approach in Regulation SCI for ATSs in their role as markets.
                        <SU>115</SU>
                        <FTREF/>
                         Finally, as noted above, 
                        <PRTPAGE P="72264"/>
                        Rule 301(b)(6) of Regulation ATS imposed by rule certain aspects of the ARP Policy Statements on significant-volume ATSs. As described in detail herein, Regulation SCI seeks to expand upon, update, and modernize the requirements of the ARP Policy Statements and Rule 301(b)(6), by, for example, expanding the requirements to a broader set of systems, imposing new requirements for information dissemination regarding SCI events, and requiring Commission notification for additional types of events, among others. Accordingly, the Commission believes that, for SCI ATSs, the existing broker-dealer rules and regulations identified by commenters are complemented by the requirements of Regulation SCI (other than Rule 301(b)(6), which will no longer apply to ATSs that trade NMS stocks and non-NMS stocks), and do not serve as substitutes for the regulatory framework being adopted today.
                    </P>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             
                            <E T="03">See supra</E>
                             notes 98-99 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 63241 (November 3, 2010), 75 FR 69792 (November 15, 2010) (“Market Access Release”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             The Commission notes that Rule 15c3-5 focuses on addressing the particular risks that arise when broker-dealers provide electronic access to exchanges or ATSs and therefore does not address the same range of technology-related issues as Regulation SCI is designed to address. Both Rule 15c3-5 and Regulation SCI are policies and procedures-based rules that are designed to address the risks presented by the pervasive use of technology in today's markets.The policies and procedures required by Regulation SCI apply broadly to technology that supports trading, clearance and settlement, order routing, market data, market regulation, and market surveillance and, among other things, address their overall capacity, integrity, resilience, availability, and security. Rule 15c3-5, by contrast, is more narrowly focused on those technology and other errors that can create some of the more significant risks to broker-dealers and the markets, namely those that arise when a broker-dealer enters orders into an exchange or ATS, including when it provides sponsored or direct market access to customers or other persons, where the consequences of such an error can rapidly magnify and spread throughout the markets. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             note 115 (discussing FINRA rules applicable to broker-dealers). The Commission will continue to monitor and evaluate the risks posed by broker-dealer systems to the market and the implementation of the Market Access Rule, and may consider extending the types of requirements in Regulation SCI to additional market participants in the future.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             For example, NASD Rule 3010(b)(1) requires a member to establish, maintain, and enforce written procedures to supervise the types of business in which it engages and to supervise the activities of registered representatives, registered principals, and other associated persons that are reasonably designed to achieve compliance with applicable securities laws and regulations. This rule relates to policies and procedures to achieve compliance with applicable securities laws and regulations, and thus the Commission believes that this requirement is broadly related to adopted Rule 1001(b) regarding policies and procedures to ensure systems compliance. However, the Commission notes that, unlike adopted Rule 1001(b), which focuses on ensuring that an entity's systems operate in compliance with the Exchange Act, the rules and regulations thereunder and the entity's rules and governing documents, this NASD rule does not specifically address compliance of the systems of FINRA members. Further, the Commission does not believe this provision covers more broadly policies and procedures akin to those in adopted Rule 1001(a) that are designed to ensure that SCI systems have levels of capacity, integrity, resiliency, availability, and security adequate to maintain the SCI entity's operation capability and promote fair and orderly markets. Similarly, while FINRA Rule 3130 relates to adopted Rule 1001(b) regarding policies and procedures to ensure systems compliance in that it requires a member's chief compliance officer to certify that the member has in place written policies and procedures reasonably designed to achieve compliance with applicable FINRA rules, MSRB rules, and federal securities laws and regulations, it does not specifically address compliance of the 
                            <E T="03">systems</E>
                             of FINRA members, and does not require similar policies and procedures to those in adopted Rule 1001(a) regarding operational capability of SCI entities. Further, while FINRA Rule 4530 imposes a reporting regime for, among other things, 
                            <PRTPAGE/>
                            compliance issues and other events where a member has concluded or should have reasonably concluded that a violation of securities or other enumerated law, rule, or regulation of any domestic or foreign regulatory body or SRO has occurred, the Commission notes that these reporting requirements are different in several respects from the Commission notification requirements relating to systems compliance issues (
                            <E T="03">e.g.,</E>
                             scope, timing, content, the recipient of the reports) and, importantly, would not cover reporting of systems disruptions or systems intrusions that did not also involve a violation of a securities law, rule, or regulation. In addition, FINRA Rule 4370 generally requires that a member maintain a written continuity plan identifying procedures relating to an emergency or significant business disruption, which is akin to adopted Rule 1001(a)(2)(v) requiring policies and procedures for business continuity and disaster recovery plans. Unlike Regulation SCI, however, the FINRA rule does not include the requirement that the business continuity and disaster recovery plans be reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption, nor does it require the functional and performance testing and coordination of industry or sector-testing of such plans, which the Commission believes to be instrumental in achieving the goals of Regulation SCI with respect to SCI entities.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also believes that, unlike with respect to exchanges, it is appropriate that Regulation SCI not apply to all ATSs. Exchanges, as self-regulatory organizations, play a special role in the U.S. securities markets, and as such, are subject to certain requirements under the Exchange Act and are able to enjoy certain unique benefits.
                        <SU>116</SU>
                        <FTREF/>
                         Accordingly, as discussed above, the Commission believes it is appropriate to subject all national securities exchanges to the requirements of Regulation SCI regardless of trading volume.
                        <SU>117</SU>
                        <FTREF/>
                         In contrast, in recognition of the more limited role that certain ATSs may play in the securities markets and the costs that will result from compliance with the requirements of the regulation, the Commission believes that it is appropriate to adopt volume thresholds, as discussed below, to identify those ATSs that have the potential to significantly impact the market should an SCI event occur, therefore warranting inclusion within the scope of the regulation. One commenter, in advocating for the application of the regulation to all ATSs, stated that the Commission should not adopt volume thresholds because ATSs may limit trading so as to avoid being subject to the requirements of Regulation SCI.
                        <SU>118</SU>
                        <FTREF/>
                         The Commission does not believe that the possibility of some ATSs structuring their business to fall below the thresholds of the rule is a sufficient justification for applying the rule to all ATSs. The Commission notes that, to the extent that an ATS limits its trading so as not to reach the volume thresholds for SCI ATSs, it would have less potential to impact investors and the market and may appropriately not be subject to the requirements of the rules. As discussed further below, the Commission believes that the dual dollar volume threshold for NMS stocks being adopted today is appropriately designed to ensure that ATSs that have either the potential to significantly impact the market as a whole or the potential to significantly impact the market for a single NMS stock (and have some impact on the market as a whole at the same time) will be subject to the requirements of Regulation SCI. Thus, only those ATSs that limit their trading so as to fall below both the single NMS stock threshold and the broad NMS stocks threshold will not be subject to the requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1.a (discussing the definition of “SCI SRO”) and 
                            <E T="03">infra</E>
                             notes 120-121 and accompanying text. As identified by one commenter, benefits afforded to SROs include, among others, the ability to receive market data revenue and immunity from private liability for regulatory activities. 
                            <E T="03">See supra</E>
                             note 100. 
                            <E T="03">See also</E>
                             ATS Release, 
                            <E T="03">supra</E>
                             note 2, at 70902-03 (discussing generally some of the obligations and benefits to be considered when determining whether to register as a national securities exchange or as a broker-dealer acting as an ATS).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             
                            <E T="03">See supra</E>
                             notes 81-83 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             
                            <E T="03">See supra</E>
                             notes 95-96 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter asserted that, if ATSs are subject to the same requirements of Regulation SCI as exchanges, they similarly should be entitled to the benefits afforded to SROs.
                        <SU>119</SU>
                        <FTREF/>
                         The Commission notes that, as discussed above, SROs are subject to a variety of obligations as self-regulatory organizations under the Exchange Act—including filing proposed rules with the Commission and enforcing those rules and the federal securities laws with respect to their members—that do not apply to other market participants, including ATSs.
                        <SU>120</SU>
                        <FTREF/>
                         Although SRO and non-SRO markets are subject to different regulatory regimes, with a different mix of benefits and obligations, the Commission believes it is appropriate to subject them to comparable requirements for purposes of Regulation SCI given the importance of assuring that the technology of key trading centers, regardless of regulatory status, is reliable, secure, and functions in compliance with the law.
                        <SU>121</SU>
                        <FTREF/>
                         At the same time, while questions have been raised as to whether the broader regulatory regimes for exchanges and ATSs should be harmonized, the Commission does not believe it appropriate to delay implementing Regulation SCI or necessary to resolve these issues before proceeding with Regulation SCI. The Commission notes that ATSs have the ability to apply for registration as a SRO should they so wish and, if such application were to be approved by the Commission, such entities could assume the additional responsibilities that are imposed on SROs, as well as avail themselves of the same benefits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             
                            <E T="03">See supra</E>
                             note 100 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1.a (discussing the definition of “SCI SRO”); 
                            <E T="03">see also</E>
                             Section 19(b) of the Exchange Act, 15 U.S.C. 78s(b)(1), and Section 6(b) of the Exchange Act, 15 U.S.C. 78f(b). Because these important regulatory responsibilities are imposed upon SROs, SROs also are afforded certain unique benefits, such as immunity from private liability with respect to their regulatory functions and the ability to receive market data revenue. 
                            <E T="03">See supra</E>
                             note 116 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             
                            <E T="03">But see</E>
                             discussion 
                            <E T="03">supra</E>
                             regarding potentially different requirements for ATSs and exchanges, including those relating to SCI ATSs and critical SCI systems.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter objected to the regulation's inclusion of ATSs while excluding certain other entities that the commenter believed similarly had the potential to impact the market, concluding that the proposal was therefore arbitrary, capricious, and unfairly discriminatory in nature.
                        <SU>122</SU>
                        <FTREF/>
                         At the same time, this commenter stated that it did not recommend that additional entities be included within the scope of the regulation.
                        <SU>123</SU>
                        <FTREF/>
                         First, as noted above, the Commission has determined to include ATSs meeting the adopted volume thresholds within the scope of Regulation SCI because of their unique role as markets rather than because of their role as traditional broker-dealers. All broker-dealers are subject to Rule 15c3-5 and other FINRA rules as noted by some commenters, which impose certain requirements 
                        <PRTPAGE P="72265"/>
                        related to the capacity, integrity and/or security of a broker-dealer's systems appropriately tailored to their role as broker-dealers. Further, as noted above, the scope of Regulation SCI is rooted in the historical reach of the ARP Inspection Program and Rule 301 of Regulation ATS (which applies to significant-volume ATSs).
                        <SU>124</SU>
                        <FTREF/>
                         The Commission acknowledged in the SCI Proposal that there may be other categories of broker-dealers not included within the definition of SCI entity that, given their increasing size and importance, could pose a significant risk to the market should an SCI event occur.
                        <SU>125</SU>
                        <FTREF/>
                         The Commission solicited comment on whether there are additional categories of market participants that should be subject to all or some of the requirements of Regulation SCI and noted that, were the Commission to decide to apply the requirements of Regulation SCI to such additional entities, it would issue a separate release outlining such a proposal and the rationale therefor.
                        <SU>126</SU>
                        <FTREF/>
                         As discussed above, the Commission believes that, at this time, the entities included within the scope of Regulation SCI, because of their current role in the U.S. securities markets and/or their level of trading activity, have the potential to pose the most significant risk in the event of a systems issue. Further, the Commission believes that a measured approach that takes an incremental expansion from the entities covered under the ARP Inspection Program is an appropriate method for imposing the mandatory requirements of Regulation SCI at this time. As such, while the Commission believes that the types of entities subject to Regulation SCI as adopted are appropriate, the Commission may consider extending the types of requirements in Regulation SCI to additional market participants in the future.
                    </P>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             
                            <E T="03">See supra</E>
                             note 103 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             
                            <E T="03">See supra</E>
                             note 103 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             
                            <E T="03">See supra</E>
                             notes 60-67 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18138-39.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">SCI ATS Thresholds</HD>
                    <P>
                        Several commenters discussed the specific proposed volume thresholds for SCI ATSs, and many offered what they believed to be more appropriate alternative methods for including ATSs within Regulation SCI.
                        <SU>127</SU>
                        <FTREF/>
                         For example, some commenters urged the Commission to retain the existing 20 percent threshold under Regulation ATS for purposes of Regulation SCI or asked the Commission to provide further explanation as to why the current threshold under Regulation ATS should be altered.
                        <SU>128</SU>
                        <FTREF/>
                         One commenter agreed with the Commission that the 20 percent threshold currently in Regulation ATS might be too high, and suggested using a threshold for ATSs trading NMS stocks of five percent or more of the volume in all NMS stocks during a 12-month period, to be determined once a year in the same given month.
                        <SU>129</SU>
                        <FTREF/>
                         Another commenter suggested that the Commission apply its ATS threshold for NMS stocks to only the 500 most active securities.
                        <SU>130</SU>
                        <FTREF/>
                         An additional recommendation by one commenter with regard to NMS stocks was to include only those ATSs with five percent or more of at least five NMS stocks with an aggregate average daily share volume greater than 500,000 shares and 0.25 percent or more of all NMS stocks for four of the previous six months, or those ATSs that have three percent or more of all NMS stocks in four of the previous six months.
                        <SU>131</SU>
                        <FTREF/>
                         Another commenter suggested retaining Rule 301(b)(6) as part of Regulation ATS, but amending the rule by lowering the average daily volume threshold to 2.5 percent.
                        <SU>132</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Direct Edge Letter at 2; SIFMA Letter at 6-7; BIDS Letter at 6; ITG Letter at 10; and OTC Markets Letter at 11. 
                            <E T="03">But see</E>
                             BlackRock Letter at 4 (agreeing with the Commission's approach in the SCI Proposal of lowering the thresholds for SCI ATSs from the thresholds in Rule 301(b)(6) of Regulation ATS).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Direct Edge Letter at 2; and KCG Letter at 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 11. This commenter also suggested leaving in place the existing five percent average daily share volume threshold for the display requirement of Rule 301(b)(3) under Regulation ATS.
                        </P>
                    </FTNT>
                    <P>
                        One commenter requested clarification on the phrase “0.25 percent or more in all NMS stocks, of the average daily dollar volume reported by an effective transaction reporting plan.” 
                        <SU>133</SU>
                        <FTREF/>
                         Because there is more than one transaction reporting plan, this commenter asked whether the proposed volume thresholds would be calculated per plan or calculated based on all NMS volume.
                        <SU>134</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 6-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 6-7.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters provided suggestions with regard to the proposed measurement methodology for the thresholds.
                        <SU>135</SU>
                        <FTREF/>
                         A few commenters argued that the proposed time period measurement of “at least four of the preceding six calendar months” is cumbersome to apply in practice and believed that the time period should be over a longer term.
                        <SU>136</SU>
                        <FTREF/>
                         For example, two commenters stated that the rule should utilize a 12-month measurement period.
                        <SU>137</SU>
                        <FTREF/>
                         Conversely, another commenter generally opposed the thresholds stating that all ATSs should be subject to the rule, but noted that if the rule includes a trading volume metric, the measurement period should be much shorter (such as two to four weeks).
                        <SU>138</SU>
                        <FTREF/>
                         In addition, one commenter stated that the measurement should be based on number of shares traded rather than dollar value.
                        <SU>139</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 6; KCG Letter at 19; SIFMA Letter at 7; and Lauer Letter at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 6; and KCG Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 6; and KCG Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 6.
                        </P>
                    </FTNT>
                    <P>
                        Two commenters also suggested that ATSs should be given six months after meeting the given threshold in the definition of SCI ATS to come into compliance with Regulation SCI.
                        <SU>140</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; and SIFMA Letter at 7.
                        </P>
                    </FTNT>
                    <P>The Commission is adopting the thresholds for ATSs that trade NMS stocks and non-NMSs stock as proposed. In setting the thresholds for Regulation SCI, the Commission believes it is establishing an appropriate and reasonable scope for the application of the regulation. Although commenters provided various suggestions for different thresholds, nothing persuaded the Commission that these suggestions would better accomplish the goals of Regulation SCI than the thresholds the Commission is adopting. As discussed below, the Commission has analyzed the number of entities it believes are likely to be covered by the thresholds it is establishing. The Commission recognizes that these thresholds ultimately represent a matter of judgment by the Commission as it takes the step of promulgating Regulation SCI, and the Commission intends to monitor these thresholds to determine whether they continue to be appropriate.</P>
                    <P>
                        With regard to the threshold for ATSs trading NMS stocks, the Commission has determined to adopt this threshold as proposed. After careful consideration of the comments, the Commission continues to believe that this threshold is an appropriate measure of when a market is of sufficient significance so as to warrant the protections and requirements of Regulation SCI.
                        <SU>141</SU>
                        <FTREF/>
                         The 
                        <PRTPAGE P="72266"/>
                        Commission is, however, making one technical modification in response to a commenter to clarify that the threshold will be calculated based on all NMS volume, rather than on a per plan basis.
                        <SU>142</SU>
                        <FTREF/>
                         The Commission agrees with the commenter that the proposed language should be clarified and, as such, the threshold language within the definition of “SCI ATS” in Rule 1000 is being revised to refer to “applicable effective transaction reporting plans,” rather than “an effective transaction reporting plan.” 
                        <SU>143</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             The numerical thresholds in the definition of SCI ATS reflect an informed assessment by the Commission, based on qualitative and quantitative analysis, of the likely economic consequences of the specific numerical thresholds included in the definition. In making such assessment and, in turn, selecting the numerical thresholds, in addition to considering the views of commenters, the Commission has reviewed relevant data. 
                            <E T="03">See infra</E>
                             notes 150 and 175 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             
                            <E T="03">See supra</E>
                             note 134 and accompanying text. As noted above, this commenter asked the Commission for clarification on this aspect of the rule.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             Because the threshold has two prongs, one of which is based on 
                            <E T="03">all</E>
                             NMS volume, it is necessary to specify that there is more than one transaction reporting plan that would be applicable in calculating all NMS stock trading volume. At the same time, since the other prong of the threshold is based on the trading volume of single NMS stocks, it is necessary to also add the term “applicable” before the term “transaction reporting plans” as only one transaction reporting plan would be applicable per security. The definition of “eligible securities” in each of the transaction reporting plans are mutually exclusive, ensuring that each security is subject to only one transaction reporting plan. 
                            <E T="03">See</E>
                             CTA Plan, available at: 
                            <E T="03">http://www.nyxdata.com/cta;</E>
                             and Nasdaq UTP Plan, available at: 
                            <E T="03">http://www.utpplan.com.</E>
                        </P>
                    </FTNT>
                    <P>
                        Under the adopted definition of SCI ATS, with regard to NMS stocks, an ATS will be subject to Regulation SCI if, during at least four of the preceding six calendar months, it had: (i) Five percent or more in any single NMS stock, and 0.25 percent or more in all NMS stocks, of the average daily dollar volume reported by applicable effective transaction reporting plans, or (ii) one percent or more, in all NMS stocks, of the average daily dollar volume reported by applicable effective transaction reporting plans.
                        <SU>144</SU>
                        <FTREF/>
                         The Commission continues to believe that this threshold will identify those ATSs that could have a significant impact on the overall market or that could have a significant impact on a single NMS stock and some impact on the market as a whole at the same time.
                        <SU>145</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             
                            <E T="03">But see</E>
                              
                            <E T="03">infra</E>
                             notes 169-170 and accompanying text (discussing a six-month compliance period for SCI entities satisfying the thresholds for the first time).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             Under the adopted thresholds, because of the requirement to meet the threshold for at least four of the preceding six calendar months, inactive and newly operating ATSs would not be included in the definition of SCI ATS. 
                            <E T="03">See infra</E>
                             note 152.
                        </P>
                    </FTNT>
                    <P>
                        While some commenters advocated for thresholds higher than those proposed and/or retaining the 20 percent threshold in Regulation ATS,
                        <SU>146</SU>
                        <FTREF/>
                         as the Commission discussed in the SCI Proposal, the securities markets have significantly evolved since the time of the adoption of Regulation ATS, resulting in trading activity in stocks being more dispersed among a variety of trading centers. For example, in today's markets, national securities exchanges, once the predominant type of venue for trading stocks, each account for no more than approximately 19 percent of volume in NMS stocks.
                        <SU>147</SU>
                        <FTREF/>
                         By way of contrast, based on data collected from ATSs pursuant to FINRA Rule 4552 for 18 weeks of trading in 2014, the trading volume of ATSs accounted for approximately 18 percent of the total dollar volume in NMS stocks, with no individual ATS executing more than five percent.
                        <SU>148</SU>
                        <FTREF/>
                         Given this dispersal of trading volume among an increasing number of trading venues, the increasingly interconnected nature of the markets, and the increasing reliance on a variety of automated systems, the Commission believes that there is a heightened potential for systems issues originating from a number of sources to significantly affect the market. Due to these developments, the Commission believes that the 20 percent threshold as adopted in Regulation ATS is no longer an appropriate measure for determining those entities that can have a significant impact on the market and thus should be subject to the protections of Regulation SCI. Rather, the Commission believes that lower volume thresholds are appropriate, and as noted in the SCI Proposal, the Commission believes that the adopted thresholds would include ATSs having NMS stock dollar volume comparable to or in excess of the NMS stock dollar volume of certain national securities exchanges subject to Regulation SCI.
                        <SU>149</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             
                            <E T="03">See supra</E>
                             note 128 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             
                            <E T="03">See supra</E>
                             note 106.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             
                            <E T="03">See infra</E>
                             note 150.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18094.
                        </P>
                    </FTNT>
                    <P>
                        Based on data collected from ATSs pursuant to FINRA Rule 4552 for 18 weeks of trading in 2014,
                        <SU>150</SU>
                        <FTREF/>
                         the Commission believes that approximately 12 ATSs trading NMS stocks would exceed the adopted thresholds and fall within the definition of SCI entity, accounting for approximately 66 percent of the dollar volume market share of all ATSs trading NMS stocks.
                        <SU>151</SU>
                        <FTREF/>
                         The Commission acknowledges that its analysis of the FINRA ATS data did not reveal an obvious threshold level above which a particular subset of ATSs may be considered to have a significant impact on individual NMS stocks or the overall market, as compared to another subset of ATSs. However, for the following reasons, the Commission continues to believe that the adopted thresholds for ATSs trading NMS stock are an appropriate measure to identify those ATSs that should be subject to the requirements of Regulations SCI. First, by imposing both a single NMS stock threshold and an all NMS stocks threshold in the first prong of the definition, the thresholds will help to ensure that Regulation SCI will not apply to an ATS that has a large volume in a small NMS stock and little volume in all other NMS stocks. At the same time, the Commission believes that inclusion of the dual-prong dollar volume thresholds is appropriate. Specifically, it will require not only that ATSs that have significant trading volume in all NMS stocks are subject to the requirements of Regulation SCI, but also that ATSs that have large trading volume in a single NMS stock and could significantly affect the market for that stock are also covered by the safeguards of Regulation SCI provided they have levels of trading in all NMS stocks that could allow such ATSs to also have some impact on the market as a whole. The Commission also believes that, as discussed further below, the adopted thresholds will also appropriately capture not only ATSs that have significant trading volume in active stocks, but also those that have significant trading volume in less active stocks. The Commission believes that a systems issue at an ATS that is a significant market for the trading of a less actively traded stock could similarly impose significant risks to the market for such securities, because a systems outage at such a venue could significantly impede the ability to trade 
                        <PRTPAGE P="72267"/>
                        such securities, thereby having a significant impact on the market for such less-actively traded securities. In addition, the Commission continues to believe that thresholds that account for 66 percent of the dollar volume market share of all ATSs trading NMS stocks is a reasonable level that would not exclude new entrants to the ATS market.
                        <SU>152</SU>
                        <FTREF/>
                         Further, as noted above, the thresholds would include ATSs having NMS stock dollar value comparable to the NMS stock dollar volume of the equity exchanges subject to Regulation SCI. Finally, the Commission believes that the adopted thresholds are appropriate to help ensure that entities that have determined to participate (in more than a limited manner) in the national market system as markets that bring buyers and sellers together, are subject to the requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 71341 (January 17, 2014), 79 FR 4213 (January 24, 2014) (approving FINRA Rule 4552 requiring each ATS to report to FINRA weekly volume information and number of securities transactions). Commission staff analyzed FINRA ATS data for the period of May 19, 2014 through September 19, 2014. The recently available FINRA ATS data is consistent with the OATS data used in the SCI Proposal. In addition, the analysis of FINRA ATS data examines a threshold of trading volume over four out of six time periods, each period defined as a period of three consecutive weeks as a rough approximation of the threshold test on four out of the preceding six calendar months as prescribed in the definition of SCI ATS. The Commission noted in the SCI Proposal that the staff analysis of OATS data may overestimate the number of ATSs that may meet the proposed thresholds. While the calculation based on FINRA ATS data may not overestimate the number of ATSs as much as the data analysis in the proposal, it could still overestimate the number of ATSs that would meet the thresholds. Nevertheless, the Commission believes the analysis of FINRA ATS data offers useful insights. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18094.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             According to the FINRA ATS data, during this time period, a total of 44 ATSs traded NMS stocks. The Commission notes that the number of ATSs exceeding the adopted thresholds, and the percentage of volume of trading in NMS stocks that they represent, may change over time in response to market and competitive forces.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             Consistent with the Commission's statement in the SCI Proposal, the Commission has considered barriers to entry and the promotion of competition in setting the threshold such that new ATSs trading NMS stocks would be able to commence operations without, at least initially, being required to comply with—and thereby not incurring the costs associated with—Regulation SCI. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at n. 102. In particular, a new ATS could engage in limited trading in any one NMS stock or all NMS stocks, until it reached an average daily dollar volume of five percent or more in any one NMS stock and 0.25 percent or more in all NMS stocks, or one percent in all NMS stocks, over four of the preceding six months. Because a new ATS could begin trading in NMS stocks for at least three months (
                            <E T="03">i.e.,</E>
                             less than four of the preceding six months), and conduct such trading at any dollar volume level without being subject to Regulation SCI, and would have to exceed the specified volume levels for the requisite period to become so subject, the Commission believes that these thresholds should not prevent a new ATS entrant from having the opportunity to initiate and develop its business. Further, the Commission notes that, as discussed below, it is adopting an additional six-month compliance period (in addition to the general nine-month compliance period from the Effective Date of Regulation SCI afforded to all SCI entities) for ATSs newly meeting the thresholds, so that once an ATS meets the threshold, it will have six months from that time to become fully compliant with Regulation SCI. 
                            <E T="03">See infra</E>
                             Section IV.F (discussing effective dates and compliance periods). The Commission believes that, for ATSs that have newly entered the market, this additional compliance period will give such ATSs additional opportunity to develop and grow their business without incurring the costs of compliance with Regulation SCI during this time. This additional compliance period should also provide such ATSs with time to plan on how they would meet the requirements of Regulation SCI, and could also potentially allow SCI ATSs to become more equipped to bear the cost of Regulation SCI once compliance is required, and thus not significantly discourage new ATSs from entering the market and growing. 
                            <E T="03">See infra</E>
                             Section VI.C.1.c (discussing further barriers to entry and the potential effects on competition of the adopted thresholds).
                        </P>
                    </FTNT>
                    <P>
                        As noted above, several commenters provided specific suggestions for alternative standards for determining which ATSs should be included within the scope of Regulation SCI.
                        <SU>153</SU>
                        <FTREF/>
                         While the Commission recognizes that some of the suggested alternatives could have certain benefits, it also believes that each recommended standard also has corresponding limitations, and thus believes that the adopted thresholds are an appropriate measure for identifying those ATSs that should be subject to Regulation SCI. First, as described above, the Commission believes that adopting a two-prong standard is necessary to identify those ATSs that, in the event of a systems issue, could have a significant impact on the overall market or that could have a significant impact on a single NMS stock and some impact on the market as a whole at the same time. The Commission notes that several of the thresholds suggested by commenters lacked such a dual-prong standard (and, in particular, the prong relating to individual NMS stocks) and thus do not provide the advantages associated with the adopted threshold in protecting the trading venues for a single NMS stock. With regard to one commenter's suggestion that the first prong of the threshold should, among other things, consider five NMS stocks, rather than a single stock, the Commission does not believe the commenter has provided any clear rationale for this standard.
                        <SU>154</SU>
                        <FTREF/>
                         As discussed, the purpose of the first prong is to identify significant trading venues (or markets) for a single security where a systems disruption could have a significant effect on the market for that security, and setting the threshold to consider five NMS securities could potentially exclude trading venues that host large trading activity for a single NMS security. Additionally, the Commission notes that the suggested alternative approach would be unlikely to have any significant practical effect when used in conjunction with the second prong of the threshold, which looks at trading across all NMS stocks, because the second prong would likely capture an ATS with five percent or more volume in five NMS stocks. With regard to one commenter's suggestion to apply the threshold to only the 500 most active NMS stocks 
                        <SU>155</SU>
                        <FTREF/>
                         and another commenter's suggestion to include only stocks with an aggregate average daily share volume greater than 500,000,
                        <SU>156</SU>
                        <FTREF/>
                         the Commission disagrees that the threshold should be structured to capture only ATSs that have significant trading volume in active stocks. Rather, the first prong of the adopted threshold is designed to capture any ATS that has five percent or more of the trading volume of 
                        <E T="03">any</E>
                         NMS stock, irrespective of how actively traded it is, so that Regulation SCI can effectively address risks relating to the trading of all NMS stocks, and not only the most active of NMS stocks. If the Commission were to apply the threshold only to the 500 most active NMS stocks or stocks only with average daily share volumes greater than 500,000, an ATS that, for example, served as the primary venue for the trading of less actively traded NMS stocks, but had negligible market share for more actively traded NMS stocks, would not be subject to Regulation SCI. However, an SCI event that resulted in an outage of such an ATS could have a significant impact on the market for such less actively traded NMS stocks. As such, failure to include such an ATS within the scope of Regulation SCI would be contrary to the goals of the regulation. Finally, with regard to one commenter's suggestion to retain Rule 301(b)(6) as part of Regulation ATS and amend the threshold to 2.5 percent,
                        <SU>157</SU>
                        <FTREF/>
                         as discussed throughout this release, Regulation SCI is intended to expand upon the requirements of Rule 301(b)(6) and to supersede and replace such requirements for ATSs that trade NMS stocks.
                        <SU>158</SU>
                        <FTREF/>
                         For the reasons noted above, the Commission believes it is appropriate to include ATSs meeting the adopted volume thresholds within the scope of Regulation SCI, and the Commission does not believe it is appropriate to retain Rule 301(b)(6) as part of Regulation ATS, thereby subjecting ATSs to a separate and differing set of regulatory requirements than other SCI entities with regard to systems capacity, integrity, resiliency, availability, security, and compliance.
                        <SU>159</SU>
                        <FTREF/>
                         For all of the reasons discussed above, the Commission does not believe that any of the alternative standards suggested by commenters would better capture those entities that 
                        <PRTPAGE P="72268"/>
                        have the potential to pose significant risk to the market.
                    </P>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             
                            <E T="03">See supra</E>
                             notes 127-132 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             
                            <E T="03">See supra</E>
                             note 131 and accompanying text. This commenter argued generally that the thresholds should be revised so as to only include those entities that would have an “immediate and substantial impairment of a functioning marketplace.” However, the commenter did not explain why it advocated the use of five NMS stocks, rather than a single NMS stock. 
                            <E T="03">See</E>
                             ITG Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             
                            <E T="03">See supra</E>
                             note 130 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             
                            <E T="03">See supra</E>
                             note 131 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             
                            <E T="03">See supra</E>
                             note 132 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             
                            <E T="03">But see</E>
                              
                            <E T="03">infra</E>
                             notes 189-192 and accompanying text (discussing the Commission's determination to retain the applicability of Rule 301(b)(6) to fixed-income ATSs).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             The Commission notes that, with regard to the specific threshold level suggested by this commenter (2.5%), the Commission believes the adopted thresholds to be an appropriate measure to identify those ATSs that should be subject to the requirements of Regulations SCI for the reasons discussed above. 
                            <E T="03">See supra</E>
                             note 141.
                        </P>
                    </FTNT>
                    <P>
                        One commenter urged the Commission to utilize number of shares traded rather than dollar value, stating that while most of the world uses value traded, available data for the U.S. equity markets is share-based.
                        <SU>160</SU>
                        <FTREF/>
                         The Commission disagrees with this commenter and notes that daily dollar volume is readily available from a number of sources, including the SIPs.
                        <SU>161</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             
                            <E T="03">See supra</E>
                             note 139 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18094 (stating that the use of dollar thresholds may better reflect the economic impact of trading activity).
                        </P>
                    </FTNT>
                    <P>
                        The time measurement period for ATSs that trade NMS stocks and non-NMS stocks is also being adopted as proposed. Thus, ATSs will be subject to Regulation SCI only if they meet the numerical thresholds for at least four of the preceding six months.
                        <SU>162</SU>
                        <FTREF/>
                         The Commission notes that the adopted time measurement period is consistent with the current standard in Rule 301(b)(6) of Regulation ATS.
                        <SU>163</SU>
                        <FTREF/>
                         The Commission believes that this time measurement period is an appropriate time period over which to evaluate the trading volume of an ATS and should help to ensure that it does not capture ATSs with relatively low trading volume that may have had an anomalous increase in trading on a given day or few days. Contrary to concerns raised by some commenters,
                        <SU>164</SU>
                        <FTREF/>
                         under this time measurement methodology, an ATS would not qualify as an SCI entity simply by trading a single large block of an illiquid security during one month (or even two or three months). While one commenter suggested that the time measurement period be shorter and recommended a period of two to four weeks,
                        <SU>165</SU>
                        <FTREF/>
                         the Commission believes that this could cause ATSs to fall within the scope of the definition solely as a result of an atypical, short-term increase in trading or a small number of large block trades that is not reflective of ATSs' general level of trading. Specifically, with such a short period of measurement, a short-term spike in trading volume uncharacteristic of an ATS's overall trading volume history could (and if large enough, likely would) skew the overall trading volume for that time period, causing an ATS to meet the volume thresholds and thus become subject to Regulation SCI even though the overall risk posed by the ATS does not warrant it. Further, the Commission believes that such a shorter time measurement period could provide more barriers to entry for ATSs, because new ATSs would not have as long of a time period to develop their business prior to having to incur the costs of compliance associated with being subject to the requirements of Regulation SCI.
                        <SU>166</SU>
                        <FTREF/>
                         This potential to incur such costs almost immediately after the initial start of operations could act as a barrier to entry for some new ATSs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (definition of “SCI ATS”). The Commission notes that if an ATS that was not previously subject to Regulation SCI meets the SCI ATS volume threshold for four consecutive months, it would become subject to Regulation SCI at the end that four-month period. However, as discussed further below, such an ATS would have an additional six months from that time to comply with the requirements of Regulation SCI. 
                            <E T="03">See infra</E>
                             text accompanying notes 169-170.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             17 CFR 242.301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             
                            <E T="03">See supra</E>
                             note 138 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             
                            <E T="03">See supra</E>
                             note 152 and accompanying text. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Section VI.C.1.c (discussing barriers to entry and the effects on competition of the adopted thresholds and time measurement period for SCI ATSs).
                        </P>
                    </FTNT>
                    <P>
                        Other commenters recommended a longer measurement period, such as 12 months.
                        <SU>167</SU>
                        <FTREF/>
                         The Commission does not believe, however, that a longer time period is necessary or more appropriate to identify those entities that play a significant role in the market for a particular asset class and/or that have the potential to significantly impact investors or the market, warranting inclusion in the scope of Regulation SCI. The Commission believes that the adopted time measurement period provides sufficient trading history data so as to indicate an ATS's significance to the market, and that the structure of the test (
                        <E T="03">i.e.,</E>
                         requiring an ATS to meet the threshold for four out of six months) ensures sustainability of such trading levels. In addition, modifying the time measurement period to 12 months (and thus eliminating the four out of six month measurement period) would make such a measure more susceptible to capturing ATSs that have a major but isolated spike in trading during a single month. Specifically, as noted above, a single anomalous large increase in trading volume during one month (or such a spike in two or three months) could never result in an ATS becoming subject to Regulation SCI solely as a result of such a spike in trading, because the ATS would meet the threshold only for one month, rather than the four months required by the rule. On the other hand, a threshold based on an average over 12 months could be skewed by the occurrence of one large spike in trading that results in the overall average for the 12-month period being increased to such a level that it meets the volume threshold levels. Thus, contrary to one commenter's suggestion that a 12-month period would require “a sustained trading level at the threshold,” 
                        <SU>168</SU>
                        <FTREF/>
                         the Commission believes that the structure of the adopted measurement period test (
                        <E T="03">i.e.,</E>
                         four out of six months) may be a better indicator of actual sustained trading levels at the threshold warranting the protections of the rule. Further, the Commission believes that 12 months is a less appropriate time measurement period than the period adopted because, for example, an ATS could have significant trading volume early on during such a time period such that it may pose significant risk to the markets in the event of a systems issue at such an ATS without being subject to Regulation SCI for a significant period of time. The Commission believes that the adopted time period strikes an appropriate balance between being a long enough period so as to not be triggered by atypical periods of increased trading or a few occurrences of very large trades, while also not causing unnecessary delay in requiring that ATSs playing an important role in the market are subject to Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             
                            <E T="03">See supra</E>
                             notes 136-137 and accompanying text. One of these commenters noted that the “four out of the preceding six months” measurement is cumbersome to apply in practice. 
                            <E T="03">See</E>
                             KCG Letter at 19. The Commission does not believe this measurement period to be overly cumbersome to apply in practice, as it would require only that an ATS undertake an assessment once at the end of each month as to whether the ATSs had exceeded the volume thresholds set forth in the rule and then make a determination at the end of a six month period whether the ATS met this threshold for four out of the six preceding months.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             notes 136-137 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Finally, as discussed further in Section IV.F, the Commission agrees with commenters that it is appropriate to provide ATSs meeting the volume thresholds in the definition of SCI ATS for the first time a period of time before they are required to comply with Regulation SCI.
                        <SU>169</SU>
                        <FTREF/>
                         Thus, consistent with the recommendation of these commenters, the Commission is revising the definition of SCI ATS to provide that an SCI ATS will not be required to comply with the requirements of Regulation SCI until six months after satisfying any of the applicable thresholds in the definition of SCI ATS for the first time.
                        <SU>170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             
                            <E T="03">See supra</E>
                             note 140 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>170</SU>
                             
                            <E T="03">See</E>
                             Rule 1000 (definition of SCI ATS).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ATSs Trading Non-NMS Stocks</HD>
                    <P>
                        Some commenters addressed whether Regulation SCI should apply to ATSs trading non-NMS stocks.
                        <SU>171</SU>
                        <FTREF/>
                         Specifically, 
                        <PRTPAGE P="72269"/>
                        one commenter stated that the rules should apply only to trading in NMS securities because non-NMS stock trading—which is dispersed among broker-dealers—does not have a single point of failure and is therefore less susceptible to rapid, widespread issues that occur as a result of a high degree of linkage or inter-dependency.
                        <SU>172</SU>
                        <FTREF/>
                         Another commenter stated that, with respect to non-NMS stocks (as well as municipal securities and corporate debt securities), the proposed five percent threshold was too low and would unnecessarily include ATSs for these product types that are “not systemic to maintaining fair, orderly, and efficient markets” and asked the Commission to further study the appropriate threshold for these ATSs.
                        <SU>173</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>171</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OTC Markets Letter at 7; SIFMA Letter at 7; TMC Letter at 1-3 (asserting that retail 
                            <PRTPAGE/>
                            fixed-income ATSs should not be subject to Regulation SCI); and KCG Letter at 3, 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>172</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>173</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 7.
                        </P>
                    </FTNT>
                    <P>
                        With regard to equity securities that are not NMS stocks and for which transactions are reported to a self-regulatory organization, the adopted thresholds remain unchanged from the SCI Proposal. Thus, for such securities, an ATS will be subject to the requirements of Regulation SCI if, during four of the preceding six calendar months, it had five percent or more of the average daily dollar volume as calculated by the self-regulatory organization to which such transactions are reported.
                        <SU>174</SU>
                        <FTREF/>
                         The Commission continues to believe that this threshold will appropriately identify ATSs that play a significant role in the market for those securities and, thus, should be subject to the requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>174</SU>
                             However, as noted above, an ATS meeting the definition of SCI ATS for the first time will be afforded a six-month compliance period. 
                            <E T="03">See supra</E>
                             notes 169-170 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Using data from the second quarter of 2014, an ATS executing transactions in non-NMS stocks at a level exceeding five percent of the average daily dollar volume traded in the United States would be executing trades at a level exceeding $45.2 million daily.
                        <SU>175</SU>
                        <FTREF/>
                         Based on data collected from Form ATS-R for the second quarter of 2014, the Commission estimates that two ATSs would exceed this threshold and fall within the definition of SCI entity, accounting for approximately 99 percent of the dollar volume market share of all ATSs trading non-NMS stocks.
                        <SU>176</SU>
                        <FTREF/>
                         These thresholds reflect an assessment by the Commission, based on qualitative and quantitative analysis, of the likely consequences of the specific quantitative thresholds included in the definition. From this analysis and in conjunction with considering the views of commenters, the Commission has derived what it believes to be an appropriate threshold to identify those ATSs that should be subject to the requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>175</SU>
                             In the Proposing Release, the Commission used data from the first six months of 2012 to estimate that an ATS executing transactions in non-NMS stocks at a level exceeding five percent of the average daily volume traded in the United States would be executed trades at a level exceeding $31 million daily. See Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at n.111 and accompanying text. The Commission has updated this estimate using over-the-counter reporting facility data available from FINRA.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>176</SU>
                             The Commission notes that the number of ATSs exceeding the adopted threshold, and the percentage of volume of trading in non-NMS stocks that they represent, may change over time in response to market and competitive forces.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, one commenter objected to the inclusion of ATSs trading non-NMS stocks within the scope of Regulation SCI.
                        <SU>177</SU>
                        <FTREF/>
                         This commenter argued that non-NMS trading is not susceptible to the issues that Regulation SCI is designed to address because such trading is dispersed among broker-dealers and does not create the types of single points of failure that pose widespread systemic risk.
                        <SU>178</SU>
                        <FTREF/>
                         First, as noted above, while the Commission is particularly concerned with systems issues that pose the greatest risk to our markets and have the potential to cause the most widespread effects and damage (such as those that are single points of failure), Regulation SCI is intended to address a broader set of risks of systems issues. Accordingly, the adopted threshold for non-NMS stock ATSs is designed to identify those ATSs that play a significant role in the market for such securities. Further, the Commission disagrees with the commenter's assertion that trading in non-NMS stocks cannot result in widespread disruptions.
                        <SU>179</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>177</SU>
                             
                            <E T="03">See supra</E>
                             note 172 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>178</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>179</SU>
                             
                            <E T="03">See supra</E>
                             note 33 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        While one commenter stated that the five percent threshold was too low, this commenter did not provide an alternative threshold but rather asked the Commission to further study this issue.
                        <SU>180</SU>
                        <FTREF/>
                         As noted above, based on qualitative and quantitative analysis, the Commission believes the five percent threshold to be an appropriate measure to determine which ATSs are of sufficient significance in the current market for non-NMS stocks to warrant their inclusion within the scope of Regulation SCI. The Commission notes that it intends to monitor the level of this threshold, and other thresholds being adopted today, to ensure that they continue to be appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>180</SU>
                             
                            <E T="03">See supra</E>
                             note 173.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that adoption of a higher threshold for non-NMS stocks than for NMS stocks reflects the Commission's acknowledgement of certain differences between the two markets. In particular, as noted in the SCI Proposal, while the Commission believes that similar concerns about the trading of NMS stocks on ATSs apply to the trading of non-NMS stocks, the Commission also believes that certain characteristics of the market for non-NMS stocks, such as the lower degree of automation, electronic trading, and interconnectedness, generally result in an overall lower risk to the market in the event of a systems issue.
                        <SU>181</SU>
                        <FTREF/>
                         In particular, the Commission believes that a systems issue at an SCI entity that trades non-NMS stocks would not be as likely to have as significant or widespread an impact as readily as a systems issue at an SCI entity that trades NMS stocks. Therefore, the Commission believes that there is less risk of market impact in the markets for those securities at this time. As such, the Commission has determined not to adopt the same, more stringent, thresholds that would trigger the requirements of Regulation SCI that the Commission is adopting for ATSs trading NMS stocks. The Commission also believes that imposition of a threshold that is set too low in markets that lack automation could have the unintended effects of discouraging automation in these markets and discouraging new entrants into these markets. Specifically, it could increase the cost of automation in relation to other methods of executing trades, and thus market participants might make a determination that the costs associated with becoming subject to Regulation SCI preclude a shift to automated trading or the development of a new automated trading system, particularly given the expected lower trading volume when beginning operations. Further, the Commission notes that it has traditionally provided special safeguards with regard to NMS stocks in its rulemaking efforts relating to market structure.
                        <SU>182</SU>
                        <FTREF/>
                         For these reasons, the Commission believes that it is appropriate at this time to apply a different threshold to ATSs trading NMS stocks than those ATSs trading non-NMS stocks.
                    </P>
                    <FTNT>
                        <P>
                            <SU>181</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18096.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>182</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Regulation NMS, 17 CFR 242.600-612; Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 27496 (June 29, 2005) (Regulation NMS Adopting Release).
                        </P>
                    </FTNT>
                    <PRTPAGE P="72270"/>
                    <HD SOURCE="HD3">ATSs Trading Fixed-Income Securities</HD>
                    <P>
                        Several commenters specifically addressed the inclusion of municipal security and corporate debt security ATSs within the scope of Regulation SCI, stating that these ATSs should not be subject to Regulation SCI or that the proposed thresholds should be modified.
                        <SU>183</SU>
                        <FTREF/>
                         These commenters identified differences in the nature of fixed-income trading as compared to the markets for NMS securities and concluded that the thresholds were inappropriate and would be detrimental to the market for these types of securities.
                        <SU>184</SU>
                        <FTREF/>
                         In particular, commenters stated that inclusion of fixed-income ATSs and/or the adoption of the proposed thresholds would impose unduly high costs on these entities given their size, scope of operations, lack of automation, low speed, and resulting low potential to pose risk to systems.
                        <SU>185</SU>
                        <FTREF/>
                         Further, one commenter noted that the cost of compliance for these types of entities would discourage the shift from manual fixed-income trading in the OTC markets to more transparent and efficient automated trading venues.
                        <SU>186</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>183</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 7; TMC Letter at 1-3; and KCG Letter at 2-3, 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>184</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 7; TMC Letter at 1-3; and KCG Letter at 2-3, 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>185</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 7; TMC Letter at 1-3; and KCG Letter at 2-3, 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>186</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 3, 10-11 (noting that the vast majority of fixed-income trades are done in the OTC markets and only a few ATSs for the fixed-income market have emerged in recent years).
                        </P>
                    </FTNT>
                    <P>
                        In addition, one commenter stated that if retail fixed-income ATSs are included in the final rule, a better measurement would be to look at par amount traded rather than volume.
                        <SU>187</SU>
                        <FTREF/>
                         Finally, one commenter requested that the Commission clarify that ATSs relating to listed-options are not subject to the obligations of proposed Regulation SCI.
                        <SU>188</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>187</SU>
                             
                            <E T="03">See</E>
                             TMC Letter at 1-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>188</SU>
                             
                            <E T="03">See</E>
                             LiquidPoint Letter at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        While the adopted definition of SCI ATS remains unchanged from the proposal for NMS stocks and non-NMS stocks, the Commission, after considering the views of commenters, has determined to exclude ATSs that trade only municipal securities or corporate debt securities from the definition of SCI ATS at this time.
                        <SU>189</SU>
                        <FTREF/>
                         Accordingly, such fixed-income ATSs will not be subject to the requirements of Regulation SCI. Rather, fixed-income ATSs will continue to be subject to the existing requirements in Rule 301(b)(6) of Regulation ATS regarding systems capacity, integrity and security if they meet the twenty percent threshold for municipal securities or corporate debt securities provided by that rule.
                        <SU>190</SU>
                        <FTREF/>
                         The Commission believes that this change is warranted given the unique nature of the current fixed-income markets, as noted by several commenters. In particular, fixed-income markets currently rely much less on automation and electronic trading than markets that trade NMS stocks or non-NMS stocks.
                        <SU>191</SU>
                        <FTREF/>
                         In addition, the municipal and corporate fixed-income markets tend to be less liquid than the equity markets, with slower execution times and less complex routing strategies.
                        <SU>192</SU>
                        <FTREF/>
                         As such, the Commission believes that a systems issue at a fixed-income ATS would not have as significant or widespread an impact as in other markets. Thus, while ensuring the capacity, integrity and security of the systems of fixed-income ATSs is important, the benefits of lowering the threshold applicable to fixed-income ATSs from the current twenty percent threshold in Regulation ATS and subjecting such ATSs to the safeguards of Regulation SCI would not be as great as for ATSs that trade NMS stock or non-NMS stock. As commenters pointed out, the cost of the requirements of Regulation SCI could be significant for fixed-income ATSs relative to their size, scope of operations, and more limited potential for systems risk. The Commission is cognizant that lowering the current threshold applicable to fixed-income ATSs in Regulation ATS and subjecting such ATSs to the requirements of Regulation SCI could have the unintended effect of discouraging automation in these markets and discouraging the entry of new fixed-income ATSs into the market, which could impede the evolving transparency and efficiency of these markets and negatively impact liquidity in these markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>189</SU>
                             
                            <E T="03">See supra</E>
                             notes 183-186.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>190</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>191</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 183-186 and accompanying text (discussing the unique nature of fixed-income trading). 
                            <E T="03">See also</E>
                             Tracy Alloway and Michael Mackenzie, “Goldman Retreats from Bond Platform,” Fin. Times, February 17, 2014 (noting that, despite efforts to make the market for bond trades more electronic, large bond trading continues to occur overwhelmingly by `voice-brokered' transactions); and Lisa Abramowicz, “Humans Beat Machines as Electronic Trading Slows: Credit Markets,” Bloomberg, February 19, 2014 (stating that a shift in corporate bond transactions to electronic systems is failing to keep up with total volume).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>192</SU>
                             
                            <E T="03">See, e.g.,</E>
                             TMC Bonds Letter at 1 (stating that fixed-income markets have significantly lower volumes and slower execution times than equity markets and have no meaningful connectivity between fixed-income ATS participants).
                        </P>
                    </FTNT>
                    <P>For these reasons, the Commission believes that it is appropriate to continue to apply the requirements in Rule 301(b)(6) of Regulation ATS to fixed-income ATSs that meet the volume thresholds of that rule and to exclude ATSs that trade only municipal securities or corporate debt securities from the scope of Regulation SCI at this time.</P>
                    <HD SOURCE="HD3">c. Plan Processor</HD>
                    <P>
                        Under Proposed Rule 1000(a), the term “plan processor” had the meaning set forth in Rule 600(b)(55) of Regulation NMS, which defines “plan processor” as “any self-regulatory organization or securities information processor acting as an exclusive processor in connection with the development, implementation and/or operation of any facility contemplated by an effective national market system plan.” 
                        <SU>193</SU>
                        <FTREF/>
                         The Commission is adopting the definition of “plan processor” as proposed.
                        <SU>194</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>193</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.600(b)(55).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>194</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release 
                            <E T="03">supra</E>
                             note 13, at Section III.B.1.
                        </P>
                    </FTNT>
                    <P>
                        The Commission received no comments on the proposed definition of “plan processor.” 
                        <SU>195</SU>
                        <FTREF/>
                         As noted in the SCI Proposal, the ARP Inspection Program included the systems of the plan processors of four national market system plans—the CTA Plan, CQS Plan, Nasdaq UTP Plan, and OPRA Plan.
                        <SU>196</SU>
                        <FTREF/>
                          
                        <PRTPAGE P="72271"/>
                        Although an entity selected as the processor of an SCI Plan acts on behalf of a committee of SROs, such entity is not required to be an SRO, nor is it required to be owned or operated by an SRO.
                        <SU>197</SU>
                        <FTREF/>
                         The Commission believes, however, that the systems of such entities, because they deal with key market data, are central features of the national market system 
                        <SU>198</SU>
                        <FTREF/>
                         and should be subject to the same systems standards as SCI SROs. The inclusion of plan processors in the definition of SCI entity is designed to ensure that the processor for an SCI Plan, regardless of its identity, is independently subject to the requirements of Regulation SCI. The Commission believes that it is important for such plan processors to be subject to the requirements of Regulation SCI because of the important role they serve in the national market system: Operating and maintaining computer and communications facilities for the receipt, processing, validating, and dissemination of quotation and/or last sale price information generated by the members of the plan.
                    </P>
                    <FTNT>
                        <P>
                            <SU>195</SU>
                             However, some commenters did support the overall scope of the term “SCI entity” or agreed specifically that plan processors should be included within the definition of that term. 
                            <E T="03">See, e.g.,</E>
                             Lauer Letter at 3 (urging the Commission to expand the scope of entities covered) and KCG Letter at 5-6 (recommending that Regulation SCI be targeted to services offered by only one or a few entities, such as plan processors). In addition, one commenter, although commenting specifically on the definition of “SCI system,” stated that Regulation SCI should be tailored to focus only on systems impacting the core functions of the overall market, which should include the exclusive SIPs that transmit market data. 
                            <E T="03">See</E>
                             OTC Markets Letter at 12-13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>196</SU>
                             
                            <E T="03">See</E>
                             ARP I Release, 
                            <E T="03">supra</E>
                             note 1, at n. 8 and n. 17. Each of the CTA Plan, CQS Plan, Nasdaq UTP Plan, and OPRA Plan, is a “national market system plan” (“NMS Plan”) as defined under Rule 600(a)(43) of Regulation NMS under the Exchange Act, 17 CFR 242.600(a)(43). Rule 600(a)(55) of Regulation NMS under the Exchange Act, 17 CFR 242.600(a)(55), defines a “plan processor” as “any self-regulatory organization or securities information processor acting as an exclusive processor in connection with the development, implementation and/or operation of any facility contemplated by an effective national market system plan.” Section 3(a)(22)(B) of the Exchange Act, 15 U.S.C. 78c(22)(B), defines “exclusive processor” to mean “any securities information processor or self-regulatory organization which, directly or indirectly, engages on an exclusive basis on behalf of any national securities exchange or registered securities association, or any national securities exchange or registered securities association which engages on an exclusive basis on its own behalf, in collecting, processing, or preparing for distribution or publication any information with respect to (i) transactions or quotations on or effected or made by means of any facility of such exchange or (ii) quotations 
                            <PRTPAGE/>
                            distributed or published by means of any electronic system operated or controlled by such association.” 
                        </P>
                        <P>As a processor involved in collecting, processing, and preparing for distribution transaction and quotation information, the processor of each of the CTA Plan, CQS Plan, Nasdaq UTP Plan, and OPRA Plan meets the definition of “exclusive processor;” and because each acts as an exclusive processor in connection with an NMS Plan, each also meets the definition of “plan processor” under Rule 600(a)(55) of Regulation NMS, as well as Rule 1000(a) of Regulation SCI. For ease of reference, an NMS Plan having a current or future “plan processor” is referred to herein as an “SCI Plan.” The Commission notes that not every processor of an NMS Plan would be a “plan processor” under Rule 1000, and therefore not every processor of an NMS Plan would be an SCI entity subject to the requirements of Regulation SCI. For example, the processor of the Symbol Reservation System associated with the National Market System Plan for the Selection and Reservation of Securities Symbols (File No. 4-533) would not be a “plan processor” subject to Regulation SCI because it does not meet the “exclusive processor” statutory definition, as it is not involved in collecting, processing, and preparing for distribution transaction and quotation information.</P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>197</SU>
                             Pursuant to Section 11A of the Exchange Act (15 U.S.C. 78k-1), and Rule 609 of Regulation NMS thereunder (17 CFR 242.609), such entities, as “exclusive processors,” are required to register with the Commission as securities information processors on Form SIP. 
                            <E T="03">See</E>
                             17 CFR 249.1001 (Form SIP, application for registration as a securities information processor or to amend such an application or registration).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>198</SU>
                             
                            <E T="03">See</E>
                             Concept Release on Equity Market Structure, 
                            <E T="03">supra</E>
                             note 4, at 3594-95.
                        </P>
                    </FTNT>
                    <P>
                        Recent SIP incidents further highlighted the importance of plan processors to the U.S. securities markets and the necessity of including such processors within the scope of Regulation SCI.
                        <SU>199</SU>
                        <FTREF/>
                         As evidenced by the incidents, the availability of consolidated market data is central to the functioning of the securities markets. The unavailability of a system, such as a plan processor, that is a single point of failure with no backups or alternatives can result in a significant impact on the entire national market system. Accordingly, the Commission believes that that it is essential to ensure that the automated systems of the entities responsible for the consolidation and processing of important market data, namely, plan processors, have adequate levels of capacity, integrity, resiliency, availability, and security.
                        <SU>200</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>199</SU>
                             As noted above, a disruption of the Nasdaq SIP on August 22, 2013 resulted in a three hour halt in trading in all Nasdaq-listed securities because of the SIP's inability to process quotes. 
                            <E T="03">See supra</E>
                             note 32 and accompanying text. Also as noted above, on October 30, 2014, according to the NYSE, a network hardware failure impacted the Consolidated Tape System, Consolidated Quote System, and Options Price Reporting Authority data feeds at the primary data center, and SIAC switched over to the secondary data center for these data feeds. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>200</SU>
                             Systems directly supporting functionality relating to the provision of consolidated market data are included within the definition of “critical SCI systems,” for which heightened obligations under Regulation SCI will apply. 
                            <E T="03">See</E>
                             adopted Rule 1000. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.A.2.c (discussing the definition of “critical SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        Further, pursuant to its terms, each SCI Plan is required to periodically review its selection of its processor, and may in the future select a different processor for the SCI Plan than its current processor.
                        <SU>201</SU>
                        <FTREF/>
                         Thus, the definition of “plan processor” covers any entity selected as the processor for a current or future SCI Plan.
                        <SU>202</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>201</SU>
                             
                            <E T="03">See</E>
                             CTA Plan Section V(d) and CQS Plan Section V(d), available at: 
                            <E T="03">http://www.nyxdata.com/cta;</E>
                             OPRA Plan Section V, available at: 
                            <E T="03">http://www.opradata.com/pdf/opra_plan.pdf;</E>
                             and Nasdaq UTP Plan Section V, available at: 
                            <E T="03">http://www.utpplan.com.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>202</SU>
                             Currently, SIAC is the processor for the CTA Plan, CQS Plan, and OPRA Plan, and Nasdaq is the processor for the Nasdaq UTP Plan. SIAC is wholly owned by NYSE Euronext. Both SIAC and Nasdaq are registered with the Commission as securities information processors, as required by Section 11A(b)(1) of the Exchange Act, 15 U.S.C. 78k-1(b)(1), and in accordance with Rule 609 of Regulation NMS, 17 CFR 242.609.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. Exempt Clearing Agency Subject to ARP</HD>
                    <P>Proposed Rule 1000(a) defined the term “exempt clearing agency subject to ARP” to mean “an entity that has received from the Commission an exemption from registration as a clearing agency under Section 17A of the Act, and whose exemption contains conditions that relate to the Commission's Automation Review Policies, or any Commission regulation that supersedes or replaces such policies.” This definition is being adopted as proposed.</P>
                    <P>
                        As noted in the SCI Proposal, this definition of “exempt clearing agency subject to ARP” currently covers one entity, Omgeo Matching Services—US, LLC (“Omgeo”).
                        <SU>203</SU>
                        <FTREF/>
                         In its comment letter, Omgeo stated that it believed its inclusion as an SCI entity was reasonable because clearing agencies that provide matching services, such as Omgeo, perform a critical role in the infrastructure of the U.S. financial markets in handling large amounts of highly confidential proprietary trade data.
                        <SU>204</SU>
                        <FTREF/>
                         Omgeo requested, however, that the Commission clarify that other similarly situated clearing agencies would also be subject to the requirements of Regulation SCI, and further requested that the Commission expand the definition of SCI entity, as applied to clearing agencies, to include, without limitation, any entity providing either matching services or confirmation/affirmation services for depository eligible securities that settle in the United States, as contemplated by FINRA Rule 11860.
                        <SU>205</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>203</SU>
                             On April 17, 2001, the Commission issued an order granting Omgeo an exemption from registration as a clearing agency subject to certain conditions and limitations in order that Omgeo might offer electronic trade confirmation and central matching services. 
                            <E T="03">See</E>
                             Global Joint Venture Matching Services—US, LLC; Order Granting Exemption from Registration as a Clearing Agency, Securities Exchange Act Release No. 44188 (April 17, 2001), 66 FR 20494 (April 23, 2001) (File No. 600-32) (“Omgeo Exemption Order”). Because the Commission granted it an exemption from clearing agency registration, Omgeo is not a self-regulatory organization.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>204</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>205</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that the adopted definition of “exempt clearing agency subject to ARP” does provide that any entity that receives from the Commission an exemption from registration as a clearing agency under Section 17A of the Act, and whose exemption contains conditions that relate to the Automation Review Policies or any Commission regulation that supersedes or replaces the Commission's Automation Review Policies (such as Regulation SCI) would be included within the scope of Regulation SCI. Therefore, clearing agencies that are similarly situated as Omgeo (
                        <E T="03">i.e.,</E>
                         those that are subject to an exemption that contains the relevant conditions) will be subject to Regulation SCI.
                        <SU>206</SU>
                        <FTREF/>
                         The Commission does not believe, therefore, that an expansion of the definition as suggested by Omgeo is necessary to further clarify that 
                        <PRTPAGE P="72272"/>
                        similarly situated entities will be subject to the requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>206</SU>
                             Any entity seeking an exemption from registration as a clearing agency is responsible for requesting and obtaining such an exemption from the Commission.
                        </P>
                    </FTNT>
                    <P>
                        Among the operational conditions required by the Commission in the Omgeo Exemption Order were several that directly related to the ARP policy statements.
                        <SU>207</SU>
                        <FTREF/>
                         For the same reasons that it required Omgeo to abide by the conditions relating to the ARP policy statements set forth in the Omgeo Exemption Order, the Commission believes it is appropriate that Omgeo (or any similarly situated exempt clearing agency) should be subject to the requirements of Regulation SCI, and thus is including any “exempt clearing agency subject to ARP” within the definition of SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>207</SU>
                             These conditions require Omgeo to, among other things: Provide the Commission with an audit report addressing all areas discussed in the Commission ARP policy statements; provide annual reports prepared by competent, independent audit personnel in accordance with the annual risk assessment of the areas set forth in the ARP policy statements; report all significant systems outages to the Commission; provide advance notice of any material changes made to its electronic trade confirmation and central matching services; and respond and require its service providers to respond to requests from the Commission for additional information relating to its electronic trade confirmation and central matching services, and provide access to the Commission to conduct inspections of its facilities, records and personnel related to such services. 
                            <E T="03">See supra</E>
                             note 203.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. SCI Systems, Critical SCI Systems, and Indirect SCI Systems</HD>
                    <HD SOURCE="HD3">a. Overview</HD>
                    <P>
                        Regulation SCI, as adopted, distinguishes three categories of systems of an SCI entity: “SCI systems;” “critical SCI systems,” and “indirect SCI systems.” The SCI Proposal broadly defined SCI systems to mean “all computer, network, electronic, technical, automated, or similar systems of, or operated by or on behalf of, an SCI entity, whether in production, development, or testing, that directly support trading, clearance and settlement, order routing, market data, regulation, or surveillance.” The SCI Proposal also defined the term SCI security systems (to which only the provisions of Regulation SCI relating to security and intrusions would apply) as: “any systems that share network resources with SCI systems that, if breached, would be reasonably likely to pose a security threat to SCI systems.” 
                        <SU>208</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>208</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.2.
                        </P>
                    </FTNT>
                    <P>
                        Many commenters stated that the proposed definitions of SCI systems and SCI security systems were too broad and urged the Commission to target systems that pose the greatest risk to the market if they malfunction.
                        <SU>209</SU>
                        <FTREF/>
                         After careful consideration of the comments, and as discussed more fully below, the Commission agrees that certain types of systems included in the proposed definition of SCI systems may be appropriately excluded from the adopted definition. However, because U.S. securities market infrastructure is highly interconnected and seemingly minor systems problem at a single entity can spread rapidly across the national market system, the Commission does not believe it is appropriate to apply Regulation SCI only to the most critical SCI systems, as some commenters suggested. Instead, the adopted regulation applies to a broader set of systems than urged by some commenters, but a more targeted set of systems than proposed. In addition, the adopted approach recognizes that some systems pose greater risk than others to the maintenance of fair and orderly markets if they malfunction. To this end, adopted Regulation SCI identifies three broad categories of systems of SCI entities that are subject to the regulation: “SCI systems,” “critical SCI systems,” and “indirect SCI systems,” with each category subject to differing requirements under Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>209</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 10; Joint SROs Letter at 5; Omgeo Letter at 4; KCG Letter at 3; DTCC Letter at 4; FIF Letter at 3; Liquidnet Letter at 3; and OTC Markets Letter at 12-13.
                        </P>
                    </FTNT>
                    <P>As discussed more fully below, the adopted definition of “SCI systems” includes those systems that directly support six areas that have traditionally been considered to be central to the functioning of the U.S. securities markets, namely trading, clearance and settlement, order routing, market data, market regulation, and market surveillance. SCI systems are subject to all provisions of Regulation SCI, except for certain requirements applicable only to critical SCI systems.</P>
                    <P>
                        In addition, the Commission is adopting a definition of “critical SCI systems,” a subset of SCI systems that are subject to certain heightened resilience and information dissemination provisions of Regulation SCI. Guided significantly by commenters' views on those systems that are most critical, the Commission is defining the term “critical SCI systems” as SCI systems that: (1) Directly support functionality relating to: (i) Clearance and settlement systems of clearing agencies; (ii) openings, reopenings, and closings on primary trading markets; (iii) trading halts; (iv) initial public offerings; (v) the provision of consolidated market data (
                        <E T="03">i.e.,</E>
                         SIPs); or (vi) exclusively-listed securities; or (2) provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets.
                        <SU>210</SU>
                        <FTREF/>
                         As more fully discussed below, systems in this category are those that, if they were to experience systems issues, the Commission believes would be most likely to have a widespread and significant impact on the securities markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>210</SU>
                             
                            <E T="03">See</E>
                             Rule 1000.
                        </P>
                    </FTNT>
                    <P>In addition, the Commission is adopting a definition of “indirect SCI systems,” in place of the proposed definition of “SCI security systems.” “Indirect SCI systems” are subject only to the provisions of Regulation SCI relating to security and intrusions. The term “indirect SCI systems” is defined to mean “any systems of, or operated by or on behalf of, an SCI entity that, if breached, would be reasonably likely to pose a security threat to SCI systems” and, if an SCI entity puts in place appropriate security measures, is intended to refer to few, if any, systems of the SCI entity.</P>
                    <HD SOURCE="HD3">b. SCI Systems</HD>
                    <HD SOURCE="HD3">SCI Systems Generally</HD>
                    <P>
                        Proposed Rule 1000(a) defined the term “SCI systems” to mean “all computer, network, electronic, technical, automated, or similar systems of, or operated by or on behalf of, an SCI entity, whether in production, development, or testing, that directly support trading, clearance and settlement, order routing, market data, regulation, or surveillance.” 
                        <SU>211</SU>
                        <FTREF/>
                         After careful consideration of the comments, the Commission is refining the scope of the systems covered by the definition of “SCI systems.” As adopted, the term “SCI systems” in Rule 1000 means “all computer, network, electronic, technical, automated, or similar systems of, or operated by or on behalf of, an SCI entity that, with respect to securities, directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>211</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.2.
                        </P>
                    </FTNT>
                    <P>
                        One commenter generally supported the proposed definition of SCI systems, and stated that the definition should be expanded to include any technology system that has direct market access.
                        <SU>212</SU>
                        <FTREF/>
                         In response to this comment, the Commission believes that many systems with direct market access are captured by the adopted definition. However, as 
                        <PRTPAGE P="72273"/>
                        discussed above, the Commission has determined not to propose to expand the scope of Regulation SCI to include other broker-dealer entities and their systems at this time.
                        <SU>213</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>212</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>213</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1 (discussing scope of SCI entities covered by Regulation SCI) and 
                            <E T="03">infra</E>
                             Section IV.E (discussing comments on the inclusion of broker-dealers generally within the scope of Regulation SCI).
                        </P>
                    </FTNT>
                    <P>
                        Contrary to the commenter who urged expansion of the proposed definition, many commenters believed the term to be too broad and recommended that it be revised in various ways.
                        <SU>214</SU>
                        <FTREF/>
                         These commenters argued that the definition was over-inclusive, with some believing that it could potentially apply to all systems of an SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>214</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 10-11; Omgeo Letter at 3-6; MSRB Letter at 7-9; FIF Letter at 3; ICI Letter at 4; BIDS Letter at 15-16; ITG Letter at 5; Liquidnet Letter at 3; CME Letter at 5; DTCC Letter at 3-5; OCC Letter at 3-4; Joint SROs Letter at 5; FINRA Letter at 5-10; SIFMA Letter at 8; Oppenheimer Letter at 3; OTC Markets Letter at 12; and Direct Edge Letter at 2.
                        </P>
                    </FTNT>
                    <P>
                        Specifically, several commenters recommended that the definition of SCI systems be revised to include a more limited set of systems than proposed.
                        <SU>215</SU>
                        <FTREF/>
                         Commenters advocating this general approach provided various suggestions for the specific standard that they believed should apply. For example, among commenters' recommendations were suggestions that the definition of SCI systems should include only those systems: whose failure or degradation would reasonably be expected to have an adverse material impact on the sound operation of financial markets; 
                        <SU>216</SU>
                        <FTREF/>
                         that are highly critical to functioning as an SCI entity; 
                        <SU>217</SU>
                        <FTREF/>
                         that have the potential to impact the protection of securities investors and the maintenance of fair and orderly markets; 
                        <SU>218</SU>
                        <FTREF/>
                         that directly support trading, clearance and settlement, order routing, market data, regulation, or surveillance in real-time; 
                        <SU>219</SU>
                        <FTREF/>
                         that support the SCI entity's “core functions . . . which the SCI entity performs pursuant to applicable Commission regulations;” 
                        <SU>220</SU>
                        <FTREF/>
                         that are reasonably likely to pose a plausible risk to the markets (namely, systems that route or execute orders, clear and settle trades, or transmit required market data); 
                        <SU>221</SU>
                        <FTREF/>
                         or that impact the core functions of the overall market, which, according to the commenter, would include exclusive SIPs that transmit market data and systems responsible for primary NMS auction markets that set daily opening and closing prices.
                        <SU>222</SU>
                        <FTREF/>
                         In addition, one commenter suggested that the term should be defined as a production system that connects to and is part of the electronic network that comprises the market.
                        <SU>223</SU>
                        <FTREF/>
                         This commenter also noted that the definition should distinguish between systems that connect to the markets and those that are used to run a business.
                        <SU>224</SU>
                        <FTREF/>
                         Another commenter suggested that, if Regulation SCI were to apply only to exchanges and ATSs, the term should be limited to exchange and ATS systems operated by the entity and should not include, for example, brokerage systems.
                        <SU>225</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>215</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 10; Joint SROs Letter at 5; Omgeo Letter at 4; KCG Letter at 3; DTCC Letter at 4; FIF Letter at 3; Liquidnet Letter at 3; and OTC Markets Letter at 12-13. 
                            <E T="03">See infra</E>
                             text accompanying notes 216-225.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>216</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>217</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 3. 
                            <E T="03">See also</E>
                             ICI Letter at 3 and Oppenheimer Letter at 3 (stating generally that the proposed definitions should be revised to more specifically focus on system events that are truly disruptive to the markets and the systems themselves that are likely to pose a risk to the fair and orderly operation of the markets or participants in the markets).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>218</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>219</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 5. This group of commenters further stated that non-real-time systems should not be included, as they do not warrant the level of oversight and added costs that the regulation imposes.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>220</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>221</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 3, 10. In addition, this commenter added that the key to whether a proposed “supporting” function should be included is whether or not it is critical to the proper operation of a core functionality.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>222</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>223</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 15-16. Thus, this commenter argued that, for a venue that does not route orders, the reporting of trade executions to the tape should not be enough to qualify such a system as an “SCI system.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>224</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>225</SU>
                             
                            <E T="03">See</E>
                             Liquidnet Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is further focusing the scope of the definition of SCI systems in response to these comments.
                        <SU>226</SU>
                        <FTREF/>
                         The Commission is replacing the proposed language referring to “systems . . . whether in production, development, or testing that directly support trading, clearance and settlement, order routing, market data, regulation, or surveillance” with the following language: “systems, with respect to securities, that directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance.” As such, the adopted definition has been limited to apply to production systems that relate to securities market functions, and in particular to those six functions—trading, clearance and settlement, order routing, market data, market regulation, or market surveillance—that traditionally have been considered to be central to the functioning of the U.S. securities markets, as urged by several commenters.
                        <SU>227</SU>
                        <FTREF/>
                         The Commission believes that systems providing these six functions may pose a significant risk to the maintenance of fair and orderly markets if their capacity, integrity, reliability, availability or security is compromised, and therefore that they should be covered by the definition of “SCI systems.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>226</SU>
                             
                            <E T="03">See supra</E>
                             notes 215-218, 220-222, and 224-225, and accompanying text. The definition is not limited strictly to real-time systems, however, or those that “connect to” and are “part of the electronic network that comprises the market,” because those limitations could exclude relevant systems, such as certain market regulation or market surveillance systems operated by or on behalf of an SCI entity, which the Commission views as integral to one or more of the six functions identified in the definition. In response to the commenter requesting that “brokerage” systems be excluded from the definition of SCI systems, the Commission notes that the adopted definition of SCI systems applies to systems that directly support the enumerated six functions, operated by or on behalf of an SCI entity. The definition therefore would exclude systems, including brokerage systems, that are not operated by or on behalf of an SCI entity. 
                            <E T="03">See,</E>
                             respectively, 
                            <E T="03">supra</E>
                             notes 219 and 223 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>227</SU>
                             
                            <E T="03">See supra</E>
                             notes 219-221 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Although some commenters pointed to the phrase “directly support” in the proposed rule as vague and overbroad,
                        <SU>228</SU>
                        <FTREF/>
                         the Commission has retained this phrase in the adopted definition. The term “directly support,” is retained to acknowledge that systems of SCI entities are complex and highly interconnected and that the definition of SCI systems should not exclude functionality or supporting systems on which the six identified categories of systems rely to remain operational.
                        <SU>229</SU>
                        <FTREF/>
                         In response to comment that the definition of SCI systems should distinguish between systems that connect to the markets and those that are used to run a business,
                        <SU>230</SU>
                        <FTREF/>
                         the Commission notes that the adopted definition would not include systems “used to run a business” if they are not within the six identified categories of market-related production systems and not necessary to their continued functioning. Further, the adopted definition clarifies that SCI systems encompass only those systems that, 
                        <E T="03">with respect to securities,</E>
                         directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance. The Commission believes 
                        <PRTPAGE P="72274"/>
                        that this change appropriately responds to one commenter's concerns that the proposed definition would capture systems operated by an SCI entity that have “practically no relevance or relation to SEC markets” and suggested that the definition should be revised to include only those systems that would directly impact a market 
                        <E T="03">that was subject to the Commission's jurisdiction.</E>
                         
                        <SU>231</SU>
                        <FTREF/>
                         As a result of this modification, if an SCI SRO does not use its systems to conduct business with respect to securities, its systems would not fall within the definition of “SCI systems.” Further, if an SCI entity operates systems for the trading of both futures and securities, only its trading systems for securities would be subject to the requirements of Regulation SCI.
                        <SU>232</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>228</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 3; and NYSE Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>229</SU>
                             The Commission notes that it believes that specifying that the definition applies to those systems that “directly support” these core functions is necessary so as to not result in a definition that is overly broad and would capture systems that only peripherally or indirectly support these functions. 
                            <E T="03">See generally</E>
                              
                            <E T="03">supra</E>
                             notes 214-225 and accompanying text (discussing comments that urged revisions to the definition of SCI systems). 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Section IV.A.2.d (discussing the definition of “indirect SCI systems”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>230</SU>
                             
                            <E T="03">See supra</E>
                             note 224 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>231</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>232</SU>
                             However, the Commission notes that, if an SCI entity has systems that do not relate to securities, and that have not been properly walled off from its SCI systems for securities, they may be captured by the definition of “indirect SCI systems” (as discussed below) and subject to certain requirements of the rule including those relating to security and intrusions standards. 
                            <E T="03">See infra</E>
                             Section IV.A.2.d (discussing definition of “indirect SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        In addition, one commenter urged that the Commission should initially limit the scope of SCI systems to those systems covered by the ARP Policy Statements (trading, clearance and settlement, and order routing) and phase in other types of systems later.
                        <SU>233</SU>
                        <FTREF/>
                         The Commission believes that the adopted definition of SCI systems obviates the need for such an approach, as many systems for which the commenter urged a delay in compliance will not be covered by the regulation, as adopted.
                    </P>
                    <FTNT>
                        <P>
                            <SU>233</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 9.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">SCI Systems: Inclusions and Exclusions</HD>
                    <P>
                        Various commenters objected to specific categories proposed to be included in the definition of SCI systems. First, many commenters opposed the proposed inclusion of development and testing systems in the definition, noting that issues in development and testing systems would have little or no impact on the operations of SCI entities and that such systems are designed to identify and address problems before they are introduced into production systems.
                        <SU>234</SU>
                        <FTREF/>
                         Some commenters argued that inclusion of development and testing systems in the definition of SCI systems would subject such systems to more requirements under Regulation SCI than was necessary and noted that certain other provisions of Regulation SCI would necessarily include reporting information to the Commission on such systems, even without their inclusion in the definition of SCI systems.
                        <SU>235</SU>
                        <FTREF/>
                         For example, one commenter stated that application of most provisions of Regulation SCI to testing and development systems would provide little benefit, and noted that updates regarding systems in development and material new features of existing systems could instead be done through the semi-annual reports to the Commission under proposed Rule 1000(b)(8).
                        <SU>236</SU>
                        <FTREF/>
                         Similarly, one commenter noted that information regarding the status of systems that are in development and testing would be captured in the notices regarding material systems changes under proposed Rule 1000(b)(6) and in the updates under proposed Rule 1000(b)(8).
                        <SU>237</SU>
                        <FTREF/>
                         Alternatively, this commenter suggested that the Commission could require that any testing errors be corrected (and such corrections be retested) prior to implementation of those changes in production.
                        <SU>238</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>234</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 11; FINRA Letter at 10-11; Omgeo Letter at 5; DTCC Letter at 4; SIFMA Letter at 8; BIDS Letter at 16; MSRB Letter at 7-8; OCC Letter at 5; CME Letter at 6; Joint SROs Letter at 5; and Direct Edge Letter at 2. One commenter qualified this position by stating that, to the extent that a systems issue in a development and testing environment were to give rise to an issue affecting an SCI system, the proposal should apply to that development and testing environment. 
                            <E T="03">See</E>
                             OCC Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>235</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 7; and DTCC Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>236</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>237</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>238</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that certain modifications to the elements of the proposed definition of SCI systems are appropriate. First, in response to comments, the reference to development and testing systems in the proposed definition of SCI systems has been deleted.
                        <SU>239</SU>
                        <FTREF/>
                         As commenters pointed out, development and testing systems are generally designed to identify and address problems before new systems or systems changes are introduced into production systems and, by their nature, can often experience issues, both intentional and unplanned, during the testing process. The Commission believes that systems issues that occur with respect to such systems are less likely to have a significant impact on the operations of an SCI entity or on the securities markets as a whole than issues occurring with respect to production systems. Further, subjecting these systems to the Commission notification requirements in adopted Rule 1002(b) could have the unintended effect of deterring SCI entities from fully utilizing the testing and development processes to test new systems and systems changes and develop solutions to issues prior to implementation of such systems or changes in production. At the same time, the Commission notes that, in order to have policies and procedures reasonably designed to achieve capacity, integrity, resiliency, availability, and security for SCI systems in accordance with adopted Rule 1001(a), an SCI entity will be required to have policies and procedures that include a program to review and keep current systems development and testing methodology for SCI systems.
                        <SU>240</SU>
                        <FTREF/>
                         Accordingly, review of programs relating to systems development and testing for SCI systems is within the scope of Regulation SCI, and an SCI entity should reasonably expect Commission staff to review such processes and systems during the course of its exams and inspections. In addition, the Commission notes that the definition of SCI review in adopted Rule 1000 and corresponding requirements for an annual SCI review in adopted Rule 1003(b) require an assessment of internal control design and effectiveness, which includes development processes.
                        <SU>241</SU>
                        <FTREF/>
                         Further, if development and testing systems are not appropriately walled off from production systems, such systems could be captured under the definition of indirect SCI systems as discussed below and be subject to the requirements of Regulation SCI. If an SCI entity's development and testing systems are not walled off from production systems, the SCI entity should consider whether its policies and procedures should specify safeguards to ensure that its personnel can clearly distinguish the development and testing systems from the production systems, in order to avoid inadvertent errors that may result in an SCI event.
                    </P>
                    <FTNT>
                        <P>
                            <SU>239</SU>
                             Because the Commission is removing development and testing systems from the definition of SCI systems, the reference to production systems in the definition of SCI systems is also being deleted as it is unnecessary to distinguish between development, testing and production systems within the definition. 
                            <E T="03">See</E>
                             adopted Rule 1000 (definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>240</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1001(a) and discussion in 
                            <E T="03">infra</E>
                             Section IV.B.1 (discussing the policies and procedures requirement under adopted Rule 1001(a)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>241</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 and 1003(b) and discussion in 
                            <E T="03">infra</E>
                             Section IV.B.5 (discussing the SCI review requirement). The Commission also notes that development processes include testing processes.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters also opposed the proposed inclusion of regulatory and surveillance systems within the definition of SCI systems or suggested that the Commission refine or clarify the scope of such systems.
                        <SU>242</SU>
                        <FTREF/>
                         Some of these 
                        <PRTPAGE P="72275"/>
                        commenters argued that inclusion of such systems was not necessary because these systems do not operate on a real-time basis or have a real-time impact on trading.
                        <SU>243</SU>
                        <FTREF/>
                         Further, one commenter suggested that periodic reporting of material outages or delays in the operation of regulatory and surveillance systems, pursuant to appropriate policies and procedures, would support the goals of Regulation SCI without imposing undue burdens on SCI entities or raising the risk that market participants would purposefully direct order flow to SCI entities experiencing regulatory or surveillance systems issues.
                        <SU>244</SU>
                        <FTREF/>
                         Another commenter advocated for replacing the terms “regulation” and “surveillance” with “market regulation” and “market surveillance,” respectively, and asked the Commission to clarify the difference between “regulatory” and “surveillance” systems.
                        <SU>245</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>242</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 11; BATS Letter at 5; MSRB Letter at 8-9; and FINRA Letter at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>243</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 11; and Joint SROs Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>244</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 11 (citing concerns regarding the potential that dissemination of information regarding issues with regulatory or surveillance systems to members or participants could provide a “roadmap for violative market behavior”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>245</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        In consideration of these comments, the Commission has determined to limit SCI systems to those systems relating to 
                        <E T="03">market</E>
                         regulation and 
                        <E T="03">market</E>
                         surveillance rather than including all regulation and surveillance systems. As proposed, the definition contained no such limitations and could potentially be interpreted to cover systems used for member regulation and member surveillance. The Commission does not believe that inclusion of member regulation or member surveillance systems such as those, for example, relating to member registration, capital requirements, or dispute resolution, would advance the goals of Regulation SCI. Issues relating to such systems are unlikely to have the same level of impact on the maintenance of fair and orderly markets or an SCI entity's operational capability as those systems identified in the definition of SCI systems. The Commission believes that this change will more appropriately capture only those regulatory and surveillance systems that are related to core market functions, such as trading, clearance and settlement, order routing, and market data.
                        <SU>246</SU>
                        <FTREF/>
                         Another element of the proposed definition of “SCI systems” that some commenters addressed was the inclusion of market data systems. Specifically, one commenter believed that the inclusion of all market data systems was too broad, and argued that only “systems that directly support `the transmission of market data as required by the Exchange Act'” should be included, thus limiting the types of market data systems to those relating to consolidated data and excluding those that transmit proprietary market data.
                        <SU>247</SU>
                        <FTREF/>
                         Although the term “market data” is not defined in Regulation SCI, that term generally refers to price information for securities, both pre-trade and post-trade, such as quotations and transaction reports.
                        <SU>248</SU>
                        <FTREF/>
                         In response to the commenter urging that only market data systems relating to consolidated data be included, the term “market data” does not refer exclusively to consolidated market data, but includes proprietary market data generated by SCI entities as well. The Commission notes that both consolidated and proprietary market data systems are widely used and relied upon by a broad array of market participants, including institutional investors, to make trading decisions, and that if a consolidated or a proprietary market data feed became unavailable or otherwise unreliable, it could have a significant impact on the trading of the securities to which it pertains, and could interfere with the maintenance of fair and orderly markets. Therefore, systems of an SCI entity directly supporting proprietary market data or consolidated market data are both within the scope of the definition of SCI systems and subject to Regulation SCI. However, the Commission has repeatedly emphasized the importance of consolidated market data to the national market system and the protection of investors 
                        <SU>249</SU>
                        <FTREF/>
                         and the severe impact of its unavailability was evidenced by the SIP outage in August 2013.
                        <SU>250</SU>
                        <FTREF/>
                         Thus, as discussed below, systems directly supporting functionality related to the provision of consolidated market data are distinguished by their inclusion in the definition of “critical SCI systems.” 
                        <SU>251</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>246</SU>
                             The Commission notes that Rule 613 of Regulation NMS requires the creation of an NMS plan to govern the creation, implementation, and maintenance of a consolidated audit trail and central repository. 
                            <E T="03">See</E>
                             17 CFR 242.613. 
                            <E T="03">See also</E>
                             Securities Exchange Act Release No. 67457 (July 18, 2012), 77 FR 45722 (August 1, 2012) (“Consolidated Audit Trail Adopting Release”). Although the consolidated audit trail central repository has not yet been created, the Commission believes that the consolidated audit trail repository will be a market regulation system that falls within the definition of SCI systems, and further that it will be an SCI system of each SCI SRO that is a member of an approved NMS plan under Rule 613, because it will be a facility of each SCI SRO that is a member of such plan. 
                            <E T="03">See</E>
                             Consolidated Audit Trail Adopting Release, 77 FR at 45774 (stating, “[T]he central repository will be jointly owned by, and be a facility of, each SRO that is a sponsor of the NMS plan.”). 
                            <E T="03">See also</E>
                             SCI Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18099 (contemplating inclusion of the consolidated audit trail central repository as an SCI system).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>247</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>248</SU>
                             
                            <E T="03">See</E>
                             Exchange Act Section 11A (15 U.S.C. 78K-1(a)(1)(C)(iii)), granting the Commission authority to assure the availability to brokers, dealers, and investors of “information with respect to quotations for and transactions in securities”). 
                            <E T="03">See also</E>
                              
                            <E T="03">Regulation of Market Information Fees and Revenues,</E>
                             Securities Exchange Act Release No. 42208, 64 FR 70613 (December 17, 1999) (describing “market information” as information concerning quotations for and transactions in equity securities and options that are actively traded in the U.S. markets).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>249</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Concept Release on Equity Market Structure, 
                            <E T="03">supra</E>
                             note 198; and Regulation NMS Adopting Release, 
                            <E T="03">supra</E>
                             note 182, at 37503-04.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>250</SU>
                             
                            <E T="03">See supra</E>
                             note 32 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>251</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.A.2.c (discussing definition of “critical SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        Further, one commenter questioned whether the phrase “market data systems” was intended to be limited to data-driven systems devoted to price transparency or whether the Commission also intended to include document-based systems devoted to public disclosure.
                        <SU>252</SU>
                        <FTREF/>
                         In response to this comment, the Commission notes that systems providing or directly supporting price transparency are within the scope of SCI systems.
                        <SU>253</SU>
                        <FTREF/>
                         However, systems solely providing or directly supporting other types of data, such as systems used by market participants to submit disclosure documents, or systems used by SCI entities to make disclosure documents publicly available, are not within the scope of SCI systems, so long as they do not also directly support price transparency.
                    </P>
                    <FTNT>
                        <P>
                            <SU>252</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 8-9 (citing its EMMA Primary Market Disclosure Service and EMMA Continuing Disclosure Service system as an example of a document-based system devoted to public disclosure).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>253</SU>
                             With regard to this particular comment, the Commission notes that the specific systems referenced—the RTRS, EMMA Primary Market Disclosure Service, EMMA Continuing Disclosure Service and SHORT System—all include pricing information for securities, and thus would fall within the definition of “SCI systems.”
                        </P>
                    </FTNT>
                    <P>
                        Several commenters also argued that the term SCI systems should not include systems operated on behalf of an SCI entity by a third party.
                        <SU>254</SU>
                        <FTREF/>
                         Some of these commenters pointed to potential difficulties with meeting the requirements of Regulation SCI with regard to third party systems.
                        <SU>255</SU>
                        <FTREF/>
                         One 
                        <PRTPAGE P="72276"/>
                        commenter specifically suggested that the proposal should be limited to those systems under the control of the SCI entity.
                        <SU>256</SU>
                        <FTREF/>
                         Another commenter noted that the SCI entity should instead be responsible for managing these relationships through due diligence, contract terms, and monitoring of third party performance.
                        <SU>257</SU>
                        <FTREF/>
                         One commenter also requested that the Commission clarify how SCI entities should comply with the oversight of vendor systems as part of Regulation SCI.
                        <SU>258</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>254</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 5-6; DTCC Letter at 4; SIFMA Letter at 8-9; BIDS Letter at 16; and BATS Letter at 4. 
                            <E T="03">See also</E>
                             ITG Letter at 5 (expressing concern about the inclusion of systems of third parties operated on behalf of an SCI entity and systems that are unrelated to the trading operations of an ATS).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>255</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Omgeo Letter at 5-6; and BATS Letter at 4 (arguing that it would be difficult for SCI entities to ensure compliance by third party 
                            <PRTPAGE/>
                            vendors absent their willingness to disclose to SCI entities highly detailed information about their intellectual property and proprietary systems).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>256</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>257</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>258</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        Although several commenters argued that the term SCI systems should not include third-party systems, the Commission continues to believe that, if a system is operated 
                        <E T="03">on behalf of</E>
                         an SCI entity and directly supports one of the six key functions listed within the definition of SCI system, it should be included as an SCI system subject to the requirements of Regulation SCI. The Commission believes that any system that directly supports one of the six functions enumerated in the definition of SCI system is important to the functioning of the U.S. securities markets, regardless of whether it is operated by the SCI entity directly or by a third party. The Commission believes that permitting such systems to be excluded from the requirements of Regulation SCI would significantly reduce the effectiveness of the regulation in promoting the national market system by ensuring the capacity, integrity, resiliency, availability, and security of those systems important to the functioning of the U.S. securities markets. Further, if the definition did not include systems operated on behalf of an SCI entity, the Commission is concerned that some SCI entities might be inclined to outsource certain of their systems solely to avoid the requirements of Regulation SCI, which would further undermine the goals of Regulation SCI. The Commission agrees with the comment that an SCI entity should be responsible for managing its relationship with third parties operating systems on behalf of the SCI entity through due diligence, contract terms, and monitoring of third party performance. However, the Commission believes that these methods may not be sufficient in all cases to ensure that the requirements of Regulation SCI are met for SCI systems operated by third parties. The fact that they might be sufficient some of the time is therefore not a basis for excluding these systems from the definition of SCI systems. Instead, if an SCI entity determines to utilize a third party for an applicable system, it is responsible for having in place processes and requirements to ensure that it is able to satisfy the requirements of Regulation SCI for systems operated on behalf of the SCI entity by a third party. The Commission believes that it would be appropriate for an SCI entity to evaluate the challenges associated with oversight of third-party vendors that provide or support its applicable systems subject to Regulation SCI. If an SCI entity is uncertain of its ability to manage a third-party relationship (whether through due diligence, contract terms, monitoring, or other methods) to satisfy the requirements of Regulation SCI,
                        <SU>259</SU>
                        <FTREF/>
                         then it would need to reassess its decision to outsource the applicable system to such third party.
                        <SU>260</SU>
                        <FTREF/>
                         For example, if a third-party vendor is unwilling to disclose to an SCI entity information regarding the vendor's intellectual property or proprietary system that the SCI entity believes it needs to satisfy the requirements of Regulation SCI, as some commenters suggested might be the case, an SCI entity will need to reassess its relationship with that vendor, because the vendor's unwillingness to provide necessary information or other assurances would not exclude the outsourced system from the definition of SCI systems. Accordingly, the definition of SCI system, as adopted in Rule 1000, retains the reference to systems operated “on behalf of” SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>259</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 16 (suggesting these methods of managing third-party relationships to comply with the proposed rule).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>260</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 3 and FINRA Letter at 22-23 (requesting Commission guidance on how an SCI entity should manage third-party relationships in the context of adopted Regulation SCI). 
                            <E T="03">See also infra</E>
                             notes 851-852 and accompanying text (discussing comments on the risk of noncompliance by an SCI entity in connection with reporting SCI events and material systems changes due to challenges posed by third-party systems).
                        </P>
                    </FTNT>
                    <P>
                        Finally, some commenters asked for clarification on miscellaneous aspects of the definition. For example, one commenter requested that the Commission clarify that the definition of SCI system for purposes of Regulation SCI is separate and distinct from the definition of a facility set forth in Section 3(a)(2) of the Exchange Act.
                        <SU>261</SU>
                        <FTREF/>
                         The Commission notes that the term “SCI system” under Regulation SCI is distinct from the term “facility” in Section 3(a)(2) of the Exchange Act.
                        <SU>262</SU>
                        <FTREF/>
                         Because a facility of an exchange would only fall within the definition of “SCI systems” if it is a system that directly supports any one of the six functions provided in the definition of “SCI systems,” not all systems that are facilities of an exchange will be SCI systems. For example, as noted in the SCI Proposal, the definition of SCI systems would apply to systems of exchange-affiliated routing brokers that are facilities of national securities exchanges.
                        <SU>263</SU>
                        <FTREF/>
                         But a system used for member regulation that may meet the definition of a facility under the Exchange Act, would not be within the scope of the definition of “SCI systems.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>261</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>262</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 78c3(a)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>263</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18099.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter requested confirmation that internal systems are excluded from the definition of SCI system.
                        <SU>264</SU>
                        <FTREF/>
                         The Commission notes that the definition of “SCI system” does not differentiate between “internal systems” and those systems accessed by market participants or other outside parties.
                        <SU>265</SU>
                        <FTREF/>
                         The Commission notes that, while some internal systems of an SCI entity may not meet the definition of SCI system, it does not believe that that all internal systems (as described by this commenter) would be outside of the scope of the definition of SCI system.
                        <SU>266</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>264</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>265</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (definition of SCI systems).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>266</SU>
                             In addition, the Commission notes that, while certain internal systems may not be “SCI systems,” they may instead meet the definition of “indirect SCI systems” under adopted Rule 1000, if they are not properly walled off from SCI systems. However, as discussed below, the Commission is clarifying the meaning of this defined term to note that systems that are effectively physically or logically separated from SCI systems would be outside of the definition of indirect SCI systems and thus outside of the scope of Regulation SCI. 
                            <E T="03">See infra</E>
                             Section IV.A.2.d (discussing the definition of “indirect SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        Other commenters advocated that SCI entities should be permitted to conduct their own risk-based assessment to determine which of their systems should be considered SCI systems.
                        <SU>267</SU>
                        <FTREF/>
                         One commenter noted that SCI entities should be required to develop and maintain an established methodology for identifying which systems qualify as SCI systems,
                        <SU>268</SU>
                        <FTREF/>
                         while other commenters advocated for coordination with the Commission in establishing criteria to be used in conducting such risk-based assessments or review by the Commission of an SCI entity's own risk-based assessment.
                        <SU>269</SU>
                        <FTREF/>
                         The Commission has carefully considered these comments and generally agrees that 
                        <PRTPAGE P="72277"/>
                        certain systems pose greater risk to the markets in the event of a systems issue and are of paramount importance to the functioning of the U.S. securities markets. Rather than include only those in the definition of SCI systems, the Commission believes that it is more prudent to instead identify these systems as “critical SCI systems” subject to certain heightened obligations. Further, adopted Rule 1001(a) requiring SCI entities to have policies and procedures 
                        <E T="03">reasonably designed</E>
                         to ensure that their systems have 
                        <E T="03">adequate</E>
                         levels of capacity, integrity, resiliency, availability, and security is consistent with a risk-based approach.
                        <SU>270</SU>
                        <FTREF/>
                         Specifically, as discussed in further detail below, an SCI entity may tailor its policies and procedures based on the relative criticality of a given SCI system to the SCI entity and to the securities markets generally.
                        <SU>271</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>267</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 3-5; Omgeo Letter at 5-6; and OCC Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>268</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>269</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 3-4; and DTCC Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>270</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1001(a). 
                            <E T="03">See also infra</E>
                             Section IV.B.1 (discussing policies and procedures for operational capability).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>271</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.1.a-b (discussing the use of risk-based considerations to tailor policies and procedures for operational capability).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Critical SCI Systems</HD>
                    <P>
                        As discussed above, in response to comments, the Commission is incorporating a risk-based approach in certain aspects of Regulation SCI.
                        <SU>272</SU>
                        <FTREF/>
                         To that end, the Commission is adopting a definition of “critical SCI systems” to designate SCI systems that the Commission believes should be subject to the highest level of requirements. As a subset of “SCI systems,” “critical SCI systems” are subject to the same provisions as “SCI systems,” except that critical SCI systems are subject to certain heightened resilience and information dissemination provisions of Regulation SCI. In these respects, critical SCI systems are subject to an increased level of obligation as compared to other SCI systems.
                        <SU>273</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>272</SU>
                             
                            <E T="03">See supra</E>
                             notes 53-56 and accompanying text (discussing comments on a risk-based approach).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>273</SU>
                             
                            <E T="03">See infra</E>
                             Sections IV.B.1.b and IV.B.3.d (discussing the two-hour resumption goal for “critical SCI systems” and information dissemination requirement for “major SCI events,” respectively).
                        </P>
                    </FTNT>
                    <P>
                        Rule 1000 defines “critical SCI systems” as “any SCI systems of, or operated by or on behalf of, an SCI entity that: (1) Directly support functionality relating to: (i) Clearance and settlement systems of clearing agencies; 
                        <SU>274</SU>
                        <FTREF/>
                         (ii) openings, reopenings, and closings on the primary listing market; (iii) trading halts; (iv) initial public offerings; (v) the provision of consolidated market data; or (vi) exclusively-listed securities; or (2) provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>274</SU>
                             “Clearance and settlement systems of clearing agencies” includes systems of registered clearing agencies and exempt clearing agencies subject to ARP. 
                            <E T="03">See</E>
                             Rule 1000 (definition of “exempt clearing agency subject to ARP,” which by its terms would also include an entity that has received from the Commission an exemption from registration as a clearing agency under Section 17A of the Act, and whose exemption contains conditions that relate to ARP, or any Commission regulation that supersedes or replaces such policies, including Regulation SCI).
                        </P>
                    </FTNT>
                    <P>
                        As noted above, many commenters advocated for a risk-based approach to Regulation SCI and either suggested that only the entities or systems that pose the greatest risk to the markets should be within the scope of the regulation or, alternatively, that the requirements of Regulation SCI be tailored to the specific risk-profile of a particular entity or particular system.
                        <SU>275</SU>
                        <FTREF/>
                         While the Commission disagrees with commenters who suggested that Regulation SCI should apply only to “critical systems,” as it believes that these are not the only systems that could pose a significant risk to the securities markets, the Commission believes that it is appropriate to hold systems that pose the greatest risk to the markets if they malfunction to higher standards and more stringent requirements under Regulation SCI. Recent events have also demonstrated the importance of certain critical systems functionality, including those that represent “single points of failure” to the securities markets, and the need for more robust market infrastructure, particularly with regard to critical market systems.
                        <SU>276</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>275</SU>
                             
                            <E T="03">See supra</E>
                             notes 53-56 and 216-222 and accompanying text (discussing comments on a risk-based approach and limiting SCI systems to only core or critical systems).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>276</SU>
                             
                            <E T="03">See supra</E>
                             Section II.B (describing recent events involving systems-related issues). In particular, the Nasdaq SIP incident, which caused a disruption in the dissemination of consolidated market data in the equity markets and led to a trading halt in all Nasdaq-listed stocks for several hours, confirmed that disruptions in systems that represent single points of failure can have a major and detrimental impact across an entire national market system.
                        </P>
                    </FTNT>
                    <P>The Commission believes that the adoption of the definition of “critical SCI systems” and heightened requirements for such systems recognizes that some systems are critical to the continuous and orderly functioning of the securities markets more broadly and, as such, ensuring their capacity, integrity, resiliency, availability, and security is of the utmost importance. Therefore, as discussed further below, the Commission believes that it is appropriate for such critical SCI systems to be held to heightened requirements (as compared to those for SCI systems) related to capacity, integrity, resiliency, availability, and security generally; rapid recovery following wide-scale disruptions; and disclosure of SCI events. The Commission believes that the definition of critical SCI systems is appropriately designed to identify those SCI systems whose functions are critical to the operation of the markets, including those systems that represent potential single points of failure in the securities markets. Systems in this category are those that, if they were to experience systems issues, the Commission believes would be most likely to have a widespread and significant impact on the securities markets.</P>
                    <P>
                        The first prong of the definition identifies six specific categories of systems that the Commission believes are the most critical to the securities markets, and the most likely to have widespread and significant market impact should a systems issue occur. These are: clearance and settlement systems of clearing agencies; openings, reopenings, and closings on the primary listing market; trading halts; initial public offerings; the provision of consolidated market data (
                        <E T="03">i.e.</E>
                        , SIPs); and exclusively-listed securities.
                    </P>
                    <P>
                        In the context of suggesting the adoption of a risk-based approach for Regulation SCI, some commenters identified those functions that they believed were most critical to the functioning of the markets. Among those identified were clearance and settlement, opening and closing auctions, IPO auctions, the provision of consolidated market data by the SIPs; and trading of exclusively-listed securities.
                        <SU>277</SU>
                        <FTREF/>
                         The Commission agrees with commenters who characterized these categories of systems as critical. In addition, as discussed below, the Commission believes that systems that directly support functionality relating to 
                        <PRTPAGE P="72278"/>
                        trading halts should be included in the definition of critical SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>277</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Direct Edge Letter at 2 (citing, among others, SIPs and clearance and settlement systems as essential to continuous market-wide operation); KCG Letter at 2-3 (identifying opening and closing auctions, IPO auctions, trading of exclusively-listed options, market data consolidators, and settlement and central clearing as “single points of failure” that should be subject to heightened regulatory requirements); and SIFMA Letter at 4 (stating that highly critical functions should include primary listing exchanges, trading exclusively listed securities, SIPs, clearance and settlement, distribution of unique post-trade transparency information, and real-time market surveillance). Although these commenters were urging that Regulation SCI apply only to these critical systems, as explained above, the Commission believes that such an approach would be too limited.
                        </P>
                    </FTNT>
                    <P>
                        With respect to “clearance and settlement systems of clearing agencies,” the clearance and settlement of securities is fundamental to securities market activity.
                        <SU>278</SU>
                        <FTREF/>
                         Clearing agencies perform a variety of services that help ensure that trades settle on time and at the agreed upon terms. For example, clearing agencies compare transaction information (or report to members the results of exchange comparison operations), calculate settlement obligations (including net settlement), collect margin (such as initial and variation margin), and serve as a depository to hold securities as certificates or in dematerialized form to facilitate automated settlement. Because of their role, clearing agencies are critical central points in the financial system. A significant portion of securities activity flows through one or more clearing agencies. Clearing agencies have direct links to participants and indirect links to the customers of participants. Clearing agencies are also linked to each other through common participants and, in some cases, by operational processes. Safe and reliable clearing agencies are essential not only to the stability of the securities markets they serve but often also to payment systems, which may be used by a clearing agency or may themselves use a clearing agency to transfer collateral.
                        <SU>279</SU>
                        <FTREF/>
                         The safety of securities settlement arrangements and post-trade custody arrangements is also critical to the goal of protecting the assets of investors from claims by creditors of intermediaries and other entities that perform various functions in the operation of the clearing agency.
                        <SU>280</SU>
                        <FTREF/>
                         Investors are more likely to participate in markets when they have confidence in the safety and reliability of clearing agencies as well as settlement systems.
                        <SU>281</SU>
                        <FTREF/>
                         Accordingly, the Commission believes “clearance and settlement systems of clearing agencies” are appropriate for inclusion in the definition of critical SCI systems.
                        <SU>282</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>278</SU>
                             
                            <E T="03">See</E>
                             Clearing Agency Standards Release, 
                            <E T="03">supra</E>
                             note 76, at 66220, 66264.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>279</SU>
                             
                            <E T="03">See</E>
                             Clearing Agency Standards Release, 
                            <E T="03">supra</E>
                             note 76, at 66264.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>280</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>281</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>282</SU>
                             The Commission notes that systems of SCI entities other than clearing agencies that are used in connection with the clearance and settlement of trades are not captured by the definition of “critical SCI systems,” but rather would fall within the definition of “SCI systems,” as discussed above. 
                            <E T="03">See supra</E>
                             Section IV.2. The Commission believes that such systems of other SCI entities, such as SROs and ATSs, do not provide the same critical functions or pose the same level of risk to the market as the clearance and settlement systems of clearing agencies as discussed above.
                        </P>
                    </FTNT>
                    <P>
                        Similarly, reliable openings, reopenings, and closings on primary listing markets are key to the establishment and maintenance of fair and orderly markets. NYSE and Nasdaq, for example, each have an opening cross for their listed securities that solicits trading interest and generates a single auction price that attracts widespread participation and is relied upon as a benchmark by other markets and market participants.
                        <SU>283</SU>
                        <FTREF/>
                         Similar processes are used, and heavy levels of participation typically are generated, at the primary listing markets in the reopening cross that follows a trading halt.
                        <SU>284</SU>
                        <FTREF/>
                         Closing auctions at the primary listing markets also attract widespread participation, and the closing prices they establish are commonly used as benchmarks, such as to value derivative contracts and generate mutual fund net asset values. As such, during these critical trading periods, market participants rely on the processes of the primary listing markets to effect transactions, and establish benchmark prices that are used in a wide variety of contexts so that the unavailability or disruption of systems directly supporting the opening, reopening and closing processes on the primary listing markets could have widespread detrimental effects.
                        <SU>285</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>283</SU>
                             
                            <E T="03">See</E>
                             Nasdaq Rule 4752 (Opening Process) and NYSE Rules 115A (Orders at the Opening) and 123D (Openings and Halts in Trading).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>284</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Nasdaq Rule 4753 (Nasdaq Halt and Imbalance Crosses) and NYSE Rules 115A (Orders at the Opening) and 123D (Openings and Halts in Trading).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>285</SU>
                             For example, press reports indicated that the decision to close the New York Stock Exchange in the wake of Superstorm Sandy, and the resulting lack of availability of the NYSE opening and closing prices, was a significant contributing cause of the unscheduled closure of the U.S. national securities exchanges. 
                            <E T="03">See, e.g.,</E>
                             Jenny Strasburg, Jonathan Cheng, and Jacob Bunge, “Behind Decision to Close Markets,” Wall St. J., October 29, 2012. 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18091 (discussing the effects of Superstorm Sandy on the securities markets). While other exchanges outside of the path of Superstorm Sandy did not experience the same risks to their electronic trading systems as the NYSE and could have otherwise opened for business, the risk that opening and closing prices might not be set by NYSE for its listed securities contributed to the consensus recommendation of market participants that the markets remain closed. 
                            <E T="03">See</E>
                             Jenny Strasburg, Jonathan Cheng, and Jacob Bunge, “Behind Decision to Close Markets,” Wall St. J., October 29, 2012.
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission believes that systems directly supporting functionality relating to trading halts 
                        <SU>286</SU>
                        <FTREF/>
                         are essential to the orderly functioning of the securities markets, and therefore should be included in the definition of critical SCI systems. In the event a trading halt is necessary, it is essential that the systems responsible for communicating the trading halt—typically maintained by the primary listing market—are robust and reliable so that the trading halt is effective across the U.S. securities markets. For example, when there is material “news pending” with respect to an issuer, it is the responsibility of the primary listing market to call a regulatory halt by generating a halt message which, when received by other trading centers, requires them to cease trading the security.
                        <SU>287</SU>
                        <FTREF/>
                         Similar responsibilities are placed on the primary listing market with respect to calling trading halts under the National Market System Plan to Address Extraordinary Market Volatility, as well as on plan processors to disseminate this information to the public.
                        <SU>288</SU>
                        <FTREF/>
                         Thus, systems which communicate information regarding trading halts provide an essential service in the U.S. markets and, should a systems issue occur affecting the ability of an SCI entity to provide such notifications, the fair and orderly functioning of the securities markets may be significantly impacted.
                    </P>
                    <FTNT>
                        <P>
                            <SU>286</SU>
                             For purposes of clarity, the Commission notes that the term “trading halts” as used in this context is intended to capture market-wide halts, such as regulatory halts, rather than a halt to trading for securities on a particular market (for example, caused by a systems issue specific to that market).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>287</SU>
                             
                            <E T="03">See, e.g.</E>
                            , CTA Plan Section IX(a), available at: 
                            <E T="03">http://www.nyxdata.com/cta</E>
                            ; National Market System Plan To Address Extraordinary Market Volatility, Section VII (“Limit Up/Limit Down Plan”); NYSE Arca Rule 7.12, BATS Rule 11.18, and EDGA Rule 11.14. 
                            <E T="03">See also</E>
                             Securities Exchange Act Release No. 67091 (May 31, 2012), 77 FR 33498 (June 6, 2012) (File No. 4-631) (Order Approving, on a Pilot Basis, the National Market System Plan To Address Extraordinary Market Volatility) (“Limit Up/Limit Down Plan Approval Order”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>288</SU>
                             
                            <E T="03">See</E>
                             Limit Up/Limit Down Plan, 
                            <E T="03">supra</E>
                             note 287 and Limit Up/Limit Down Plan Approval Order, 
                            <E T="03">supra</E>
                             note 287.
                        </P>
                    </FTNT>
                    <P>
                        Companies offer shares of capital stock to the general public for the first time through the IPO process, in which the primary listing market initiates public trading in a company's shares. The IPO is conducted exclusively on that exchange, and secondary market trading cannot commence on any other exchange until the opening trade is printed on the primary listing market.
                        <SU>289</SU>
                        <FTREF/>
                         As such, the Commission believes that an exchange's systems that directly support the IPO process and the initiation of secondary market trading are a critical element of the capital formation process and the effective functioning of the securities markets. The Commission believes that these 
                        <PRTPAGE P="72279"/>
                        systems, which are the sole responsibility of the primary listing market, can adversely affect not only the IPO of a particular issuer, but may also result in significant monetary losses and harm to investors if they fail.
                        <SU>290</SU>
                        <FTREF/>
                         As noted in the SCI Proposal, systems issues affecting the two recent high-profile IPOs highlighted how disruptions in IPO systems can have a significant impact on the market.
                        <SU>291</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>289</SU>
                             
                            <E T="03">See</E>
                             Rule 12f-2 under the Exchange Act, 17 CFR 240.12f-2 (providing that a national securities exchange may extend unlisted trading privileges to a security when at least one transaction in the security has been effected on the national securities exchange upon which the security is listed and the transaction has been reported pursuant to an effective transaction reporting plan).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>290</SU>
                             
                            <E T="03">See, e.g.</E>
                            , 
                            <E T="03">supra</E>
                             note 36 (discussing the losses associated with Nasdaq's Facebook IPO).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>291</SU>
                             Specifically, in March 2012, BATS announced that a “software bug” caused BATS to shut down the IPO of its own stock, and in May 2012, issues with Nasdaq's trading systems delayed the start of trading in the IPO of Facebook, Inc. and some market participants experienced delays in notifications of whether orders had been filled. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18089; and Securities Exchange Act Release No. 69655, In the Matter of The NASDAQ Stock Market, LLC and NASDAQ Execution Services, LLC (settled action: May 29, 2013), available at: 
                            <E T="03">http://www.sec.gov/litigation/admin/2013/34-69655.pdf.</E>
                             Nasdaq and Nasdaq Execution Services, LLC consented to an Order Instituting Administrative and Cease-and-Desist Proceedings Pursuant to Sections 19(h)(1) and 21C of the Securities Exchange Act of 1934, Making Findings, and Imposing Sanctions and a Cease-and-Desist Order.
                        </P>
                    </FTNT>
                    <P>
                        Systems directly supporting the provision of consolidated market data are also critical to the functioning of U.S. securities markets and represent potential single points of failure in the delivery of important market information. When Congress mandated a national market system in 1975, it emphasized that the systems for collecting and distributing consolidated market data would be central features of the national market system.
                        <SU>292</SU>
                        <FTREF/>
                         Further, one of the findings of the recent report by the staffs of the Commission and the CFTC on the market events of May 6, 2010 was that “fair and orderly markets require that the standards for robust, accessible, and timely market data be set quite high.” 
                        <SU>293</SU>
                        <FTREF/>
                         Accurate, timely, and efficient collection, processing, and dissemination of consolidated market data provides the public with ready access to a comprehensive and reliable source of information for the prices and volume of any NMS stock at any time during the trading day.
                        <SU>294</SU>
                        <FTREF/>
                         This information helps to ensure that the public is aware of the best displayed prices for a stock, no matter where they may arise in the national market system.
                        <SU>295</SU>
                        <FTREF/>
                         It also enables investors to monitor the prices at which their orders are executed and serves as a data point that helps them to assess whether their orders received best execution.
                        <SU>296</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>292</SU>
                             See H.R. Rep. No. 94-229, 94th Cong., 1st Sess. 93 (1975). 
                            <E T="03">See also</E>
                             Concept Release on Equity Market Structure, 
                            <E T="03">supra</E>
                             note 4, at 3600, and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18108 (each discussing the importance of consolidated market data).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>293</SU>
                             
                            <E T="03">See</E>
                             Findings Regarding The Market Events Of May 6, 2010, Report Of The Staffs Of The CFTC And SEC To The Joint Advisory Committee On Emerging Regulatory Issues, September 30, 2010, at 8 (“May 6 Staff Report”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>294</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>295</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>296</SU>
                             
                            <E T="03">See id.</E>
                             Also, as discussed above, the recent Nasdaq SIP disruption demonstrated that the availability, accuracy, and reliability of consolidated market data is currently central to the functioning of the securities markets, and systems issues affecting such systems can result in major disruptions to the national market system, undermining the maintenance of fair and orderly markets.
                        </P>
                    </FTNT>
                    <P>
                        Finally, systems directly supporting functionality relating to exclusively-listed securities represent single points of failure in the securities markets, because exclusively-listed securities, by definition, are listed and traded solely on one exchange.
                        <SU>297</SU>
                        <FTREF/>
                         As such, a trading disruption on the exclusive listing market necessarily will disrupt trading by all market participants in those securities.
                        <SU>298</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>297</SU>
                             As noted above, commenters identified the systems supporting the trading of exclusively-listed securities as representing critical points of failure or critical functionality in the securities markets. 
                            <E T="03">See, e.g.</E>
                            , KCG Letter at 2-3; and SIFMA Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>298</SU>
                             For example, as noted above, in April 2013, CBOE delayed the opening of trading on its exchange for over three hours due to an internal “software bug,” preventing investors from trading in those products that are singly-listed on CBOE, including options on the S&amp;P 500 Index and the VIX. 
                            <E T="03">See supra</E>
                             note 28 and accompanying text.
                        </P>
                    </FTNT>
                    <P>The second prong of the definition is a broader catch-all provision intended to capture any SCI systems, beyond those specifically identified within the first prong of the definition, that provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets. The Commission is not aware of any SCI systems that would fall under this prong of the critical SCI systems definition at this time, and notes that this prong of the definition is intended to account for further technology advancements and the continual evolution of the securities markets, in recognition that such developments could result in additional or new types of systems that would, similar to the enumerated categories of systems in the first prong of the definition, become so critical to the continuous and orderly functioning of the securities markets such that they should be subject to the requirements of Regulation SCI imposed on those systems specifically enumerated in the first prong of the definition.</P>
                    <P>
                        The Commission also notes that the definition applies to those systems “of, or operated by or on behalf of, an SCI entity.” This language mirrors the language in the definitions of SCI system and indirect SCI system, and as discussed above, is intended to cover systems that are third-party systems operated on behalf of SCI entities.
                        <SU>299</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>299</SU>
                             
                            <E T="03">See supra</E>
                             notes 254-260 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. Indirect SCI Systems (Proposed as “SCI Security Systems”)</HD>
                    <P>
                        Proposed Rule 1000 defined the term “SCI security systems” to mean “any systems that share network resources with SCI systems that, if breached, would be reasonably likely to pose a security threat to SCI systems.” 
                        <SU>300</SU>
                        <FTREF/>
                         As adopted, Regulation SCI includes the new term “indirect SCI systems,” in place of the proposed term “SCI security systems.” The term “indirect SCI systems” is defined to mean “any systems of, or operated by or on behalf of, an SCI entity that, if breached, would be reasonably likely to pose a security threat to SCI systems.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>300</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.2.
                        </P>
                    </FTNT>
                    <P>
                        As an initial matter, the Commission has determined to replace the proposed term “SCI security systems” with the adopted term “indirect SCI systems” because it believes that the latter term, in using the word “indirect,” better reflects that it is intended to cover non-SCI systems only if they are not appropriately secured and segregated from SCI systems, and therefore could indirectly pose risk to SCI systems.
                        <SU>301</SU>
                        <FTREF/>
                         The adopted definition of indirect SCI systems includes systems “of, or operated by or on behalf of” of an SCI entity that, “if breached, would be reasonably likely to pose a security threat to SCI systems.” As discussed below, in response to comment that the proposed term would cover too many systems unrelated to SCI systems, the adopted term excludes the phrase “share network resources.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>301</SU>
                             The Commission also believes that eliminating the word “security” from the defined term will help clarify that the term is not limited to systems relating only to security of the SCI entity and its systems (
                            <E T="03">e.g.</E>
                            , firewalls, VPNs).
                        </P>
                    </FTNT>
                    <P>
                        One commenter expressly supported the definition of SCI security systems and urged that it be expanded to include any technology system that has direct market access.
                        <SU>302</SU>
                        <FTREF/>
                         In response to this comment, the Commission notes that the adopted definition includes any technology system of, or operated by or on behalf of an SCI entity, that has direct market access if that system meets the definition's test: whether a breach of 
                        <PRTPAGE P="72280"/>
                        that system would be reasonably likely to pose a security threat to SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>302</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5.
                        </P>
                    </FTNT>
                    <P>
                        This commenter also suggested that the Commission additionally require SCI entities to have independent security audits performed and allow the auditor to have the ability to define which systems should be included and which can be safely excluded.
                        <SU>303</SU>
                        <FTREF/>
                         The Commission is not requiring “independent security audits” to determine which systems would fall within the definition of indirect SCI system as suggested by this commenter,
                        <SU>304</SU>
                        <FTREF/>
                         because the Commission believes its adopted rule requiring an annual SCI review addresses the commenter's request. The Commission notes that the adopted annual SCI review requirement requires that such review be performed by objective, qualified personnel, and that it include an assessment of logical and physical security controls for SCI systems and indirect SCI systems. The Commission believes that an SCI entity is generally in the best position to assess in the first instance which of its systems may fall within the definition of indirect SCI systems, and that having an independent third party audit to make that determination should be optional rather than required at this time.
                    </P>
                    <FTNT>
                        <P>
                            <SU>303</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>304</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (definition of “SCI review”) and 
                            <E T="03">infra</E>
                             Section IV.B.5 (discussing the SCI review requirement).
                        </P>
                    </FTNT>
                    <P>
                        Contrary to the commenter urging expansion of the proposed definition of SCI security systems, many commenters argued that the proposed definition was overbroad,
                        <SU>305</SU>
                        <FTREF/>
                         with several of these same commenters suggesting that the term be deleted from the rule entirely.
                        <SU>306</SU>
                        <FTREF/>
                         The Commission believes that Regulation SCI warrants inclusion of a definition of indirect SCI systems because an issue or systems intrusion with respect to a non-SCI system still could cause or increase the likelihood of an SCI event with respect to an SCI entity's SCI systems.
                        <SU>307</SU>
                        <FTREF/>
                         In particular, because systems that are not adequately walled off from SCI systems may present potential entry points to an SCI entity's network and thus represent potential vulnerabilities to SCI systems, the Commission believes that it is important that the provisions of Regulation SCI relating to security standards and systems intrusions apply to such systems (
                        <E T="03">i.e.</E>
                        , indirect SCI systems).
                    </P>
                    <FTNT>
                        <P>
                            <SU>305</SU>
                             
                            <E T="03">See, e.g.</E>
                            , NYSE Letter at 11; Omgeo Letter at 6; MFA Letter at 6 (noting specifically that the definition could be read to extend to broker-dealers or other third parties); SIFMA Letter at 8; ITG Letter at 5, 12; BIDS Letter at 16-17; MSRB Letter at 7; OCC Letter at 4; FINRA Letter at 12-13; CME Letter at 6; DTCC Letter at 5; Oppenheimer Letter at 3; and Direct Edge Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>306</SU>
                             
                            <E T="03">See, e.g.</E>
                            , NYSE Letter at 11; Omgeo Letter at 6; MFA Letter at 6; SIFMA Letter at 2; FIF Letter at 3; LiquidPoint Letter at 3; KCG Letter at 18; OCC Letter at 3; and Joint SROs Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>307</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18099.
                        </P>
                    </FTNT>
                    <P>
                        Many commenters objecting to the proposed definition as too broad addressed particular elements of the proposed definition of SCI security systems or provided specific recommendations for modifications or limitations to the definition.
                        <SU>308</SU>
                        <FTREF/>
                         For example, some commenters criticized the use of the phrase “share network resources,” noting that it was vague and too broad, potentially encompassing almost any system of an SCI entity.
                        <SU>309</SU>
                        <FTREF/>
                         Similarly, one commenter stated that the definition of SCI security system should include only systems that “directly” share network resources with an SCI system.
                        <SU>310</SU>
                        <FTREF/>
                         One commenter argued that the definition should only include those systems that are materially and directly connected to the trading operations of an SCI entity.
                        <SU>311</SU>
                        <FTREF/>
                         Several commenters recommended that systems that are logically and/or physically separated from SCI systems should be excluded from the definition.
                        <SU>312</SU>
                        <FTREF/>
                         Some commenters qualified this position by stating that such systems should be excluded, for example, as long as SCI entities monitor those systems for security breaches and have the ability to shut the system off if they detect a security breach; 
                        <SU>313</SU>
                        <FTREF/>
                         or provided that the separation is routinely monitored and has appropriate risk controls in place and the system is “air gapped” (
                        <E T="03">i.e.</E>
                        , has no point of entry) from the public internet.
                        <SU>314</SU>
                        <FTREF/>
                         One commenter believed that the definition should exclude any system with “compensatory controls in place,” which it stated would protect and secure SCI systems from vulnerabilities that could arise from shared network links.
                        <SU>315</SU>
                        <FTREF/>
                         Another commenter asked for greater clarity on the extent to which SCI security systems that are isolated from production, such as email and intranet sites, raise security issues that are within the scope of the proposal.
                        <SU>316</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>308</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 12; BATS Letter at 5-6; ISE Letter at 7-8; BIDS Letter at 16-17; SROs Letter at 15; Direct Edge Letter at 3; FINRA Letter at 13; ISE Letter at 8; and DTCC Letter at 5; and ITG Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>309</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 12; BATS Letter at 5; and ISE Letter at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>310</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 16-17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>311</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 12 (stating that its suggested approach would, in its case, cover systems for order handling and execution, processing of market data, transaction reporting, and clearing and settlement of trades).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>312</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Joint SROs Letter at 15 (stating that the term “SCI security systems” should be deleted, but if retained, should exclude those systems that are physically and logically separated); BATS Letter at 5-6; Direct Edge Letter at 3; FINRA Letter at 13; ISE Letter at 8; and DTCC Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>313</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>314</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>315</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>316</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 8.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of these comments, the Commission believes that inclusion of the phrase “share network resources” in the proposed definition could be interpreted in a manner that would include almost any system that is part of an SCI entity's network. In response to commenters who expressed concern about the breadth of the proposed definition, the Commission has determined to eliminate the phrase “share network resources” from the definition, so that the adopted result-oriented test depends on whether a system “if breached, would be reasonably likely to pose a security threat to SCI systems.” As a result, the inquiry into whether any system is an indirect SCI system will depend on whether it is effectively physically or logically separated from SCI systems. Systems that are adequately physically or logically separated (
                        <E T="03">i.e.</E>
                        , isolated from SCI systems, such that they do not provide vulnerable points of entry into SCI systems) will not fall within the definition of indirect SCI systems.
                    </P>
                    <P>The Commission believes that having adequate separation and security controls should protect SCI systems from vulnerabilities caused by other systems. To the extent that non-SCI systems are sufficiently walled off from SCI systems using appropriate security measures, and thus are not reasonably likely to pose a security threat to SCI systems if breached, they would not be included in the definition of indirect SCI systems, and thus would be outside of the scope of Regulation SCI.</P>
                    <P>
                        The Commission notes that the definition of indirect SCI systems will not include any systems of an SCI entity for which the SCI entity establishes reasonably designed and effective controls that result in SCI systems being logically or physically separated from such non-SCI systems. Thus, the universe of an SCI entity's indirect SCI systems is in the control of each SCI entity, and SCI entities should reasonably expect Commission staff to assess its security controls around SCI systems in connection with an inspection or examination for compliance with Regulation SCI. If these controls are not present or are not reasonably designed, the applicable non-SCI systems would be within the scope of the definition of indirect SCI systems and subject to the security 
                        <PRTPAGE P="72281"/>
                        standards and systems intrusions provisions of Regulation SCI.
                    </P>
                    <P>
                        Some commenters recommended that, rather than including SCI security systems in the scope of the regulation, the Commission should instead require SCI entities to establish policies and procedures designed to ensure the security of their systems.
                        <SU>317</SU>
                        <FTREF/>
                         According to these commenters, such an approach would require an evaluation of the risks posed to SCI systems by non-SCI systems. As noted, the Commission believes that the adopted definition of “indirect SCI systems” will effectively require SCI entities to evaluate the risks posed to SCI systems by non-SCI systems. However, the Commission believes that the adopted approach will incentivize SCI entities to seek to have in place strong security controls around SCI systems. As noted, if an SCI entity designs and implements security controls so that none of its non-SCI systems would be reasonably likely to pose a security threat to SCI systems, then it will have no indirect SCI systems. If, however, an SCI entity does have indirect SCI systems, then certain provisions of Regulation SCI will apply to those indirect SCI systems.
                        <SU>318</SU>
                        <FTREF/>
                         The Commission believes this approach to indirect SCI systems is more appropriate than the policies and procedures approach suggested by some commenters because the Commission believes that its approach is more comprehensive as it includes, for example, the requirements to take corrective action, provide notifications to the Commission, and disseminate information for certain SCI events relating to indirect SCI systems which, by definition, if breached, would be reasonably likely to pose a security threat to SCI systems. Another commenter stated that a more precise definition of SCI security systems is important and that it would be valuable for the Commission to work with representatives within the securities industry to collectively craft the most appropriate definition that will ensure that critical security systems are captured.
                        <SU>319</SU>
                        <FTREF/>
                         In crafting the definition, the Commission has taken into account comments received, with such commenters representing a wide variety of types of participants in the securities markets, and believes the adopted definition of indirect SCI systems, along with the definition of SCI systems, is responsive to a broad range of commenters' concerns.
                        <SU>320</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>317</SU>
                             
                            <E T="03">See, e.g.</E>
                            , NYSE Letter at 12; MFA Letter at 6; SIFMA Letter at 2; FIF Letter at 3; LiquidPoint Letter at 3; KCG Letter at 18; OCC Letter at 3; and Joint SROs Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>318</SU>
                             
                            <E T="03">See infra</E>
                             notes 323-328 (discussing the provisions of Regulation SCI applicable to indirect SCI systems).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>319</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>320</SU>
                             
                            <E T="03">See supra</E>
                             note 17 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter suggested that the definition be limited to systems “of, or operated by or on behalf of, an SCI entity,” noting that the definition of SCI security systems should have parallel construction to the definition of “SCI systems” and without this phrase, SCI entities would be tasked inappropriately with controlling for systems outside of their effective control.
                        <SU>321</SU>
                        <FTREF/>
                         As noted, the adopted definition of “indirect SCI systems” applies to those systems “of, or operated by or on behalf of, an SCI entity.” As a result, the adopted definition of indirect SCI systems provides (as is the case for SCI systems) that systems “of, or operated by or on behalf of” an SCI entity, are included in the definition of indirect SCI systems if their breach would be reasonably likely to pose a security threat to SCI systems.
                        <SU>322</SU>
                        <FTREF/>
                         The Commission believes that the addition of this language is warranted to make clear that security of SCI systems is not limited solely to threats from systems operated directly by the SCI entity. If it were, outsourced systems of SCI entities would not be subject to the requirements of Regulation SCI, which would undermine the goals of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>321</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>322</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the inclusion of third party systems in the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        As discussed in further detail below, unlike SCI systems, those systems meeting the definition of “indirect SCI systems” will only be subject to certain provisions of Regulation SCI. Specifically, references to “indirect SCI systems” are included in the definitions of “responsible SCI personnel,” “SCI review,” and “systems intrusion” in adopted Rule 1000.
                        <SU>323</SU>
                        <FTREF/>
                         Rule 1001(a), requiring reasonably designed policies and procedures to ensure operational capability, will apply to indirect SCI systems only for purposes of security standards.
                        <SU>324</SU>
                        <FTREF/>
                         In addition, Rule 1002, which relates to an SCI entity's obligations with regard to SCI events, will apply to indirect SCI systems only with respect to systems intrusions.
                        <SU>325</SU>
                        <FTREF/>
                         Further, pursuant to Rule 1003(a), the obligations related to systems changes will apply to material changes to the 
                        <E T="03">security</E>
                         of indirect SCI systems.
                        <SU>326</SU>
                        <FTREF/>
                         In addition, the requirements regarding an SCI review will apply to indirect SCI systems.
                        <SU>327</SU>
                        <FTREF/>
                         Finally, Rules 1005 through 1007, relating to recordkeeping and electronic filing and submission of Form SCI, respectively, will also apply to indirect SCI systems.
                        <SU>328</SU>
                        <FTREF/>
                         The Commission believes that it is appropriate to subject indirect SCI systems to only these specified provisions because the Commission believes that the primary risk posed by indirect SCI systems is that they may serve as vulnerable entry points to SCI systems. The Commission's objective with respect to indirect SCI systems is to guard against a non-SCI system being breached in a manner that threatens the security of any SCI system. The Commission believes that its approach to defining indirect SCI systems, and requiring SCI entities to consider, address, and report on security changes and intrusions into systems where vulnerabilities have been identified, is tailored to meet this objective.
                    </P>
                    <FTNT>
                        <P>
                            <SU>323</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>324</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1001(a) and 
                            <E T="03">supra</E>
                             Section IV.B.1 (discussing the policies and procedures requirement under Rule 1001(a)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>325</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (definitions of system compliance and systems disruption, which do not include indirect SCI systems, and the definition of systems intrusion, which includes indirect SCI systems) and 
                            <E T="03">supra</E>
                             Section IV.B.3 (discussing an SCI entity's obligations with respect to SCI events).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>326</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(a)(i) and Section IV.B.4 (discussing requirements relating to material systems changes).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>327</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b) and Section IV.B.5 (discussing the SCI review requirement).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>328</SU>
                             
                            <E T="03">See</E>
                             adopted Rules 1005-1007 and Section IV.C (discussing the recordkeeping and electronic filing of Form SCI).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. SCI Events</HD>
                    <P>
                        Regulation SCI specifies the types of events—
                        <E T="03">i.e.,</E>
                         SCI events—that give rise to certain obligations under the rule, including taking corrective action, reporting to the Commission, and disseminating information about such SCI events.
                        <SU>329</SU>
                        <FTREF/>
                         Proposed Rule 1000(a) defined the term “SCI event” as “an event at an SCI entity that constitutes: (1) A systems disruption; (2) a systems compliance issue; or (3) a systems intrusion.” 
                        <SU>330</SU>
                        <FTREF/>
                         The Commission is adopting the definition of “SCI event” as proposed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>329</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.3 (discussing an SCI entity's obligations with respect to SCI events).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>330</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.3.
                        </P>
                    </FTNT>
                    <P>
                        Many commenters believed that the proposed definition of “SCI event” was vague 
                        <SU>331</SU>
                        <FTREF/>
                         or overly broad because it was not limited to capturing material SCI events 
                        <SU>332</SU>
                        <FTREF/>
                         or events that the commenters believed are truly disruptive and pose a risk to the market.
                        <SU>333</SU>
                        <FTREF/>
                         Specifically, 
                        <PRTPAGE P="72282"/>
                        several commenters recommended that the definition of SCI event include a materiality threshold, so that only events determined by the SCI entity to be material would trigger certain obligations under the rule.
                        <SU>334</SU>
                        <FTREF/>
                         One commenter stated that the definition of SCI event could be interpreted to include trivial events, and therefore believed that the definition needed clarity.
                        <SU>335</SU>
                        <FTREF/>
                         Finally, one commenter suggested that SCI event be defined as outlined in Rule 301(b)(6)(ii)(G) under Regulation ATS,
                        <SU>336</SU>
                        <FTREF/>
                         which requires a qualifying ATS to notify the Commission of material systems outages and significant systems changes.
                        <SU>337</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>331</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 12; and OTC Markets Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>332</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 2; ITG Letter at 12; DTCC Letter at 5; and OTC Markets Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>333</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 3; ICI Letter at 4; Oppenheimer Letter at 3. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra note</E>
                             231 and accompanying text (discussing comment that 
                            <PRTPAGE/>
                            the definition of SCI systems should be revised to cover only those systems where a disruption, compliance issue, intrusion or material systems change would impact investors and markets that are subject to the Commission's jurisdiction).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>334</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FIF Letter at 2 (suggesting factors for determining what is a material SCI event, and urging that only material SCI events be subject to notification requirements); ITG Letter at 12 (suggesting that a Commission notification requirement apply only to those events that have a material impact on the ongoing maintenance of fair and orderly markets in an NMS security); and DTCC Letter at 5 (recommending that each component of the term SCI event be limited by a materiality threshold and be “risk-based” so that the term includes events that cause a disruption to the SCI entity's ability to conduct its core functions).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>335</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>336</SU>
                             17 CFR 242.301(b)(6)(ii)(G).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>337</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 16. In addition, some commenters objected to the inclusion of systems compliance issues within the definition of SCI events. 
                            <E T="03">See infra</E>
                             notes 403-405 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of the views of commenters, although the Commission is adopting the definition of “SCI event” as proposed, the requirements of Regulation SCI are tiered in a manner that the Commission believes is responsive to the concerns of commenters about the breadth of the definition.
                        <SU>338</SU>
                        <FTREF/>
                         Specifically, and as explained in further detail below, the Commission is incorporating a risk-based approach to the obligations of SCI entities with respect to SCI events.
                        <SU>339</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>338</SU>
                             
                            <E T="03">See supra</E>
                             notes 331-337 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>339</SU>
                             Under this risk-based approach, for example, de minimis SCI events will not be subject to the immediate Commission reporting requirements as proposed, but rather, SCI entities will only be required to make, keep, and preserve records regarding de minimis SCI events and submit de minimis systems disruptions and de minimis systems intrusions to the Commission in quarterly summary reports. 
                            <E T="03">See</E>
                             Rule 1002(b)(5).
                        </P>
                    </FTNT>
                    <P>
                        The Commission is not incorporating a materiality threshold as requested by some commenters,
                        <SU>340</SU>
                        <FTREF/>
                         including by limiting the definition of SCI event to only those events that are considered by SCI entities to be truly disruptive to the market.
                        <SU>341</SU>
                        <FTREF/>
                         Rather, the Commission believes that the adopted Commission notification and information dissemination requirements for SCI events will help to focus the Commission's and SCI entities' resources on the more significant SCI events by providing appropriate exceptions from reporting and dissemination for events that have no or de minimis impacts on an SCI entity's operations or market participants. In addition, the Commission believes that SCI event should not be defined as outlined in Rule 301(b)(6)(ii)(G) under Regulation ATS as suggested by one commenter,
                        <SU>342</SU>
                        <FTREF/>
                         because Rule 301(b)(6)(ii)(G) requires Commission notification of “material systems outages.” 
                        <SU>343</SU>
                        <FTREF/>
                         Such an approach would exclude any systems compliance issues or systems intrusions, two types of events that the Commission believes should be included as SCI events. This approach would also create a materiality threshold for systems disruptions, which the Commission believes would not be appropriate, as discussed below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>340</SU>
                             
                            <E T="03">See supra</E>
                             notes 334 and 337 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>341</SU>
                             
                            <E T="03">See supra</E>
                             note 333 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>342</SU>
                             
                            <E T="03">See supra</E>
                             note 337 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>343</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6)(ii)(G). Rule 301(b)(6)(ii)(G) also requires that ATSs promptly notify the Commission of significant systems changes.
                        </P>
                    </FTNT>
                    <P>In addition, by not including a materiality threshold within the definition, SCI entities will be required to assess, take corrective action, and keep records of all such events, some of which may initially seem insignificant to an SCI entity, but which may later prove to be the cause of significant systems issues at the SCI entity. An SCI entity's records of de minimis SCI events may also be useful to the Commission in that they may, for example, aid the Commission in identifying patterns of de minimis SCI events that together might result in a more impactful SCI event, either at an SCI entity or across a group of SCI entities, or circumstances in which an SCI event causes de minimis systems issues for one particular SCI entity but results in significant issues for another SCI entity. The Commission also believes that the ability to view such events in the aggregate and across multiple SCI entities is important to allow the Commission and its staff to be able to gather information about trends related to SCI events that could not otherwise be properly discerned. Information about trends will assist the Commission in fulfilling its oversight role by keeping Commission staff informed about the nature and frequency of the types of de minimis SCI events that SCI entities encounter. Moreover, information about trends and notifications of de minimis SCI events generally can also inform the Commission of areas of potential weaknesses, or persistent or recurring problems, across SCI entities and also should help the Commission better focus on common types of SCI events or issues with certain types of SCI systems across SCI entities. This information also will permit the Commission and its staff to issue industry alerts or guidance if appropriate. In addition, this information would allow the Commission and its staff to review SCI entities' classification of SCI events as de minimis SCI events.</P>
                    <P>
                        In addition, although the definition of SCI event is unchanged, to address commenters' concerns, the Commission has determined to modify the various components of that definition (
                        <E T="03">i.e.,</E>
                         the definition of systems disruption, systems compliance issue, and systems intrusion), in certain respects, as discussed below.
                    </P>
                    <HD SOURCE="HD3">a. Systems Disruption</HD>
                    <P>
                        Proposed Rule 1000(a) would have defined “systems disruption” as “an event in an SCI entity's SCI systems that results in: (1) A failure to maintain service level agreements or constraints; (2) a disruption of normal operations, including a switchover to back up equipment with near-term recovery of primary hardware unlikely; (3) a loss of use of any SCI system; (4) a loss of transaction or clearance and settlement data; (5) significant backups or delays in processing; (6) a significant diminution of ability to disseminate timely and accurate market data; or (7) a queuing of data between systems components or queuing of messages to or from customers of such duration that normal service delivery is affected.” 
                        <SU>344</SU>
                        <FTREF/>
                         As discussed below, in response to comments, the Commission is substantially modifying the proposed definition of systems disruption in adopted Rule 1000.
                    </P>
                    <FTNT>
                        <P>
                            <SU>344</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.3.a.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that the proposed definition of systems disruption was reasonable, but recommended that it be expanded to encompass disruptions originating from a third party.
                        <SU>345</SU>
                        <FTREF/>
                         However, many other commenters believed that the definition of systems disruption was too broad and would include minor events that they believed should be excluded from the 
                        <PRTPAGE P="72283"/>
                        definition.
                        <SU>346</SU>
                        <FTREF/>
                         Several commenters suggested ways to limit the scope of the defined term. For example, some commenters suggested limiting the definition to material disruptions.
                        <SU>347</SU>
                        <FTREF/>
                         One of these commenters added that systems disruptions should exclude any regularly planned outages occurring during the normal course of business.
                        <SU>348</SU>
                        <FTREF/>
                         Another commenter recommended that development and testing environments should be excluded from the definition of systems disruption.
                        <SU>349</SU>
                        <FTREF/>
                         One commenter suggested modifying the definition to include only two elements: (1) Disruptions of either the SCI systems or of the operations of the SCI entity that have the effect of disrupting the delivery of the SCI service provided by those systems; and (2) degradations of SCI systems processing creating backups or delays of such a degree and duration that the delivery of service is effectively disrupted or unusable by the market participants who use the systems.
                        <SU>350</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>345</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>346</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 16; BATS Letter at 9; Omgeo Letter at 7; NYSE Letter at 14; Joint SROs Letter at 6; OCC Letter at 6; SIFMA Letter at 9-10; and OTC Markets Letter at 21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>347</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 6; SIFMA Letter at 9; OCC Letter at 6; OTC Markets Letter at 21; and Joint SROs Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>348</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>349</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 11, 16 (noting also that the many elements of the defined term were vague). 
                            <E T="03">See also</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems,” including the elimination of test and development systems from its definition).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>350</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 11.
                        </P>
                    </FTNT>
                    <P>
                        Two commenters believed that the proposed definition of systems disruption was too rigid and should provide for more flexibility and discretion.
                        <SU>351</SU>
                        <FTREF/>
                         Both commenters were skeptical that an event should be reportable solely because it matched the description of one of the seven elements of the definition.
                        <SU>352</SU>
                        <FTREF/>
                         One of these commenters noted that the Commission's proposed definition seeks to codify as a formal definition language used by the ARP Inspection Program that was meant to provide flexibility and latitude in determining what constitutes a systems disruption.
                        <SU>353</SU>
                        <FTREF/>
                         The other commenter thought that the seven prongs of the proposed definition of “systems disruption” were appropriate considerations in determining whether a systems disruption had occurred, but that an SCI entity should be afforded more discretion and flexibility in determining whether a particular issue meets the definition.
                        <SU>354</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>351</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 7; and OCC Letter at 6-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>352</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 7; and OCC Letter at 6-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>353</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>354</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 6. This commenter also critiqued or requested clarification for each prong of the definition, as discussed further below.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Service Level Agreements</HD>
                    <P>
                        Two commenters believed that the first element of the definition regarding service level agreements should be eliminated.
                        <SU>355</SU>
                        <FTREF/>
                         One of these commenters stated that an SCI entity's regulatory requirements should not depend upon the negotiated language of an agreement between business partners, while the other commenter noted that, in some cases, a private contract might have more stringent requirements than required by regulation, which would, in effect, transform such agreements into new regulatory obligations.
                        <SU>356</SU>
                        <FTREF/>
                         Other commenters stated this element should be revised to capture only the most significant disruptions to a service level agreement.
                        <SU>357</SU>
                        <FTREF/>
                         In addition, one commenter expressed concern that SCI entities may forgo negotiating detailed and stringent service level agreements if the first element were to be adopted as proposed.
                        <SU>358</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>355</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 13; and BATS Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>356</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 13; and BATS Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>357</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 7 (suggesting that the definition capture only the most significant disruptions to a service level agreement that are caused by the SCI entity and that impede its ability to perform its core functions and critical operations); and OCC Letter at 7. 
                            <E T="03">See also</E>
                             Omgeo Letter at 9 (noting concerns that this element could require reporting of events too minor to be noticed by participants and that do not cause any disruptions of service or material risks to the entity or users).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>358</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 7.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Disruptions of Normal Operations</HD>
                    <P>
                        Two commenters stated that the second element of the definition needs clarification because the phrase “disruption of normal operations” is vague and overbroad and therefore could potentially include minor events.
                        <SU>359</SU>
                        <FTREF/>
                         Two commenters stated that, if a switchover is utilized and there is no material impact on the core services, then there should not be a requirement to notify the Commission of a systems disruption.
                        <SU>360</SU>
                        <FTREF/>
                         One of these commenters added that programming errors that occur prior to production and regularly scheduled maintenance should not be considered disruptions.
                        <SU>361</SU>
                        <FTREF/>
                         Several commenters also recommended that testing errors should not be included in the definition,
                        <SU>362</SU>
                        <FTREF/>
                         and one commenter stated that testing errors should only be included if they result in a material impact on an SCI entity's operations.
                        <SU>363</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>359</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 13; and Omgeo Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>360</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 9; and SIFMA Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>361</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>362</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 11; SIFMA Letter at 10; and NYSE Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>363</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 9 (noting that inclusion of testing errors would discourage SCI entities from conducting effective quality assurance programs and could undermine good quality engineering practices).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Loss of Use of Any System</HD>
                    <P>
                        One commenter stated that the term “loss of use of any SCI system” is unclear and expressed concern that the lack of clarity may lead to interpretive differences and inconsistencies in application among SCI entities.
                        <SU>364</SU>
                        <FTREF/>
                         Three commenters discussed failovers to backup systems, with one commenter stating the Commission should clarify whether this constitutes a loss of use of a system,
                        <SU>365</SU>
                        <FTREF/>
                         another commenter stating that it should not be considered a systems disruption,
                        <SU>366</SU>
                        <FTREF/>
                         and the third commenter stating that it should only be considered a systems disruption if there is an impact on normal operations.
                        <SU>367</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>364</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>365</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>366</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>367</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Loss of Data</HD>
                    <P>
                        Several commenters stated that losses of transaction or clearance and settlement data that are immediately retrieved, promptly corrected, or, for clearance and settlement data, resolved prior to the close of the trading day should not be systems disruptions.
                        <SU>368</SU>
                        <FTREF/>
                         One commenter suggested that the rule be revised to include as a systems disruption data that is altered or corrupted in some way.
                        <SU>369</SU>
                        <FTREF/>
                         Another commenter stated that this prong of the definition should include a materiality qualifier.
                        <SU>370</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>368</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 7; DTCC Letter at 7; SIFMA Letter at 10; and Omgeo Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>369</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>370</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 14.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Backups or Delays and Market Data Dissemination</HD>
                    <P>
                        With respect to the fifth and sixth elements of the definition regarding significant backups or delays in processing and a significant diminution of ability to disseminate timely and accurate market data, one commenter expressed support for the inclusion of such performance degradations in the definition of systems disruptions but stated that it believed that the Commission's interpretation of the term “significant” in the SCI Proposal was overly broad because it would encompass delays that are small and, in fact, insignificant.
                        <SU>371</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>371</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 9. 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18101-02.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72284"/>
                    <HD SOURCE="HD3">Data Queuing</HD>
                    <P>
                        With respect to the seventh element, one commenter stated that queuing of data is a very good indicator of a problem, but also noted that it is not necessarily being properly monitored by most firms and suggested that the Commission require SCI entities to monitor queue depth.
                        <SU>372</SU>
                        <FTREF/>
                         However, several other commenters stated that queuing of data is normal and necessary.
                        <SU>373</SU>
                        <FTREF/>
                         Some commenters suggested that the Commission should only require reporting of such queuing if it materially affects the delivery of core services to customers.
                        <SU>374</SU>
                        <FTREF/>
                         One commenter asked for additional clarification on this element because all systems have queues to some extent with normal functionality and only certain queues should trigger recovery actions.
                        <SU>375</SU>
                        <FTREF/>
                         One commenter expressed concern that language in the SCI Proposal stating that “queuing of data is a warning signal of significant disruption” 
                        <SU>376</SU>
                        <FTREF/>
                         would make events that are precursors to system disruptions themselves become system disruptions.
                        <SU>377</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>372</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>373</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 10; DTCC Letter at 7; SIFMA Letter at 10; Omgeo Letter at 10; and Joint SROs Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>374</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 10-11; DTCC Letter at 7; Omgeo Letter at 10; and OCC Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>375</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>376</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18102.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>377</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 9.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Customer Complaints</HD>
                    <P>
                        Several commenters objected to the Commission's discussion in the SCI Proposal regarding customer complaints,
                        <SU>378</SU>
                        <FTREF/>
                         stating that the Commission should not consider each instance in which a customer or systems user complains or inquires about a slowdown or disruption of operations as an indicator of a systems disruption.
                        <SU>379</SU>
                        <FTREF/>
                         For example, one commenter noted that customer complaints are often ultimately determined to be the result of system errors or discrepancies on the customer's end, and stated that requiring an SCI entity to treat these complaints as significant systems disruptions simply because they are made would impose an unnecessary burden on the SCI entity.
                        <SU>380</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>378</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18102.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>379</SU>
                             
                            <E T="03">See, e.g.,</E>
                             DTCC Letter at 7; Omgeo Letter at 10; BATS Letter at 11; NYSE Letter at 14; and OCC Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>380</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 10-11.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Definition of “Systems Disruption” as Adopted</HD>
                    <P>
                        After careful consideration of the views of commenters, the Commission is removing the seven specific types of systems malfunctions that were proposed to define systems disruption. As adopted, “systems disruption” is defined in Rule 1000 to mean “an event in an SCI entity's SCI systems that disrupts, or significantly degrades, the normal operation of an SCI system.” The Commission has considered commenters' suggestions and feedback with respect to the proposed definition, including the criticisms of various aspects of the seven specific types of systems malfunctions delineated in the SCI Proposal and believes that the adopted definition, which largely follows the definition suggested by a commenter, is appropriate.
                        <SU>381</SU>
                        <FTREF/>
                         Specifically, this commenter recommended that the definition of systems disruption be revised to have two elements: (1) Disruptions of either the SCI systems or of the operations of the SCI entity that have the effect of disrupting the delivery of the SCI service provided by those systems; and (2) degradations of SCI systems processing creating backups or delays of such a degree and duration that the delivery of service is effectively disrupted or unusable by the market participants who use the systems.
                        <SU>382</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>381</SU>
                             
                            <E T="03">See id.</E>
                             at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>382</SU>
                             
                            <E T="03">See supra</E>
                             note 353 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission agrees with commenters that the proposed definition of systems disruption had the potential to be both over-inclusive and under-inclusive. The Commission believes that the adopted definition appropriately represents a change in focus of the definition from the prescriptive seven prongs in the SCI Proposal's definition that represented the effects caused by a disruption of an SCI entity's systems to, instead, whether a system is halted or degraded in a manner that is outside of its normal operation. The Commission believes the revised definition sets forth a standard that SCI entities can apply in a wide variety of circumstances to determine in their discretion whether a systems issue should be appropriately categorized as a systems disruption. Further, because the adopted definition of systems disruption takes into account whether a systems problem is outside of normal operations, the Commission also believes that partly addresses the concerns of the commenters suggesting that the definition of systems disruption include a materiality qualifier.
                        <SU>383</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>383</SU>
                             As discussed more fully below, an SCI entity's assessment of the impact of an event meeting the definition of a systems disruption will affect whether it is subject to an immediate Commission notification obligation, or a recordkeeping and quarterly reporting obligation. 
                            <E T="03">See infra</E>
                             Section IV.B.3.c (discussing the exclusion of de minimis systems disruptions from immediate Commission notification requirements in Rule 1002(b)(5)).
                        </P>
                    </FTNT>
                    <P>
                        Because the Commission agrees with commenters regarding the difficulties of the proposed definition of “systems disruption,” it is not including any of the specific types of systems malfunctions in the adopted definition of “systems disruption.” Thus, the Commission believes SCI entities would likely find it helpful to establish parameters that can aid them and their staff in determining what constitutes the “normal operation” 
                        <SU>384</SU>
                        <FTREF/>
                         of each of its SCI systems, and when such “normal operation” has been disrupted or significantly degraded because those parameters have been exceeded. The Commission agrees with commenters who noted that, given its voluntary nature, entities that participate in the ARP Inspection Program are afforded a certain degree of flexibility and discretion in reporting systems outages, and agrees that, given its proposed application to a mandatory rule, the proposed definition limited the flexibility and discretion of SCI entities in a manner that was overly rigid.
                        <SU>385</SU>
                        <FTREF/>
                         Although the specific types of systems malfunctions have been removed from the adopted definition of systems disruption, the Commission nonetheless continues to believe, as suggested by one commenter,
                        <SU>386</SU>
                        <FTREF/>
                         that the types of systems malfunctions that comprised the proposed definition may be useful to SCI entities to consider as indicia of a systems disruption.
                    </P>
                    <FTNT>
                        <P>
                            <SU>384</SU>
                             The Commission notes that, for certain SCI systems, “normal operation” may include a certain degree of operational variability that would allow for a given amount of degradation of functionality (
                            <E T="03">e.g.,</E>
                             some data queuing or some slowing of response times) before the system's operations reach the point of being “significantly degraded.” However, such variability parameters may be included as part of an SCI entity's policies and procedures so that the SCI entity and its personnel would be aware of them before the occurrence of systems issues.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>385</SU>
                             Commenters highlighted many examples where a rigid interpretation of the proposed definition had the potential to incorporate into the definition events that could be considered part of normal operation. 
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 361, 364, 368, 369, 374, and 379 and accompanying text. As adopted, however, such events would not be captured by the definition of systems disruptions because an event that disrupts, or significantly degrades, the normal operation of an SCI system would not be considered the “normal operation” of such SCI system.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>386</SU>
                             
                            <E T="03">See supra</E>
                             note 354 and accompanying text.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72285"/>
                    <P>
                        As discussed in the SCI Proposal 
                        <SU>387</SU>
                        <FTREF/>
                         and by certain commenters,
                        <SU>388</SU>
                        <FTREF/>
                         the seven categories of malfunctions in the proposed definition of “systems disruption” have their origin in ARP staff guidance regarding when ARP participants should notify the Commission of system outages and represent practical examples that SCI entities should consider to be systems disruptions in many circumstances. The Commission notes that the revised definition is intended to address some commenters' concerns with the particular elements of the definition of systems disruption as originally proposed. For example, under the modified definition, if an SCI system experiences an unplanned outage but fails over smoothly to its backup system such that there is no disruption or significant degradation of the normal operation of the system, the outage of the primary system would not constitute a systems disruption. On the other hand, an SCI entity may determine that, even when a primary system fails over smoothly to its backup system such that users are not impacted by the failover, operating from the backup system without additional redundancy would not constitute normal operation. In this case, the outage of the primary system would fall within the definition of systems disruption. Further, the Commission believes it would be appropriate for an SCI entity to take into account regularly scheduled outages or scheduled maintenance as part of “normal operations.” 
                        <SU>389</SU>
                        <FTREF/>
                         In particular, a planned disruption to an SCI system that is a part of regularly scheduled outages or scheduled maintenance would not constitute a systems disruption or be subject to the requirements of Regulation SCI, if such regularly scheduled outages or scheduled maintenance are part of the SCI entity's normal operations. With regard to data queuing, to the extent that such queuing is part of the normal functionality of a system and does not cause a disruption or significant degradation of normal operations, it would not be captured by the rule, which is limited to events occurring to an SCI system that are outside its normal operations.
                        <SU>390</SU>
                        <FTREF/>
                         Additionally, by eliminating the seven types of malfunctions from the definition as proposed, the Commission has responded to commenters who expressed concern that events that are precursors to system disruptions, such as the queuing of data, would themselves be systems disruptions.
                        <SU>391</SU>
                        <FTREF/>
                         Similarly, by eliminating the seven types of malfunctions, the Commission has addressed comments that called for the elimination of specific elements of the proposed definition, such as service level agreements.
                        <SU>392</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>387</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18101.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>388</SU>
                             
                            <E T="03">See supra</E>
                             note 353 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>389</SU>
                             
                            <E T="03">See supra</E>
                             note 361 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>390</SU>
                             
                            <E T="03">See supra</E>
                             notes 372-377 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>391</SU>
                             
                            <E T="03">See supra</E>
                             note 377 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>392</SU>
                             
                            <E T="03">See supra</E>
                             notes 355 and 358 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Further, the Commission agrees with commenters that customer complaints may be indicia of a systems issue,
                        <SU>393</SU>
                        <FTREF/>
                         but that a customer complaint alone would not be determinative of whether a system problem has occurred that meets the definition of systems disruption under Regulation SCI.
                        <SU>394</SU>
                        <FTREF/>
                         With respect to the commenters who stated that losses of transaction or clearance and settlement data that are immediately retrieved, promptly corrected, or, for clearance and settlement data, resolved prior to the close of the trading day should not be systems disruptions, the adopted definition would exclude these events if they do not disrupt or significantly degrade the normal operations of an SCI system.
                        <SU>395</SU>
                        <FTREF/>
                         However, if loss of transaction or clearance and settlement data disrupts or significantly degrades the normal operation of an SCI system, it would constitute a systems disruption and be subject to the requirements of Regulation SCI (
                        <E T="03">e.g.,</E>
                         immediate or quarterly Commission notification, depending on the impact of the disruption).
                    </P>
                    <FTNT>
                        <P>
                            <SU>393</SU>
                             The Commission agrees, as noted by some commenters, that in some instances, customer complaints may be the result of a problem at a system not operated by (or on behalf of) an applicable SCI entity, but rather a system operated by the customer itself. 
                            <E T="03">See supra</E>
                             note 380 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>394</SU>
                             
                            <E T="03">See supra</E>
                             notes 379-380 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>395</SU>
                             
                            <E T="03">See supra</E>
                             note 368. The Commission notes that for clearance and settlement systems, normal operations would include all steps necessary to effectuate timely and accurate end of day settlement. In response to the commenter who stated that the definition of systems disruption should be revised to include data that is altered or corrupted in some way, because the Commission has determined to eliminate the pronged approach to the definition of systems disruption, the Commission notes that, under the adopted definition, data that is altered or corrupted in some way may be a systems disruption if such altered or corrupted data disrupt or significantly degrade the affected SCI system's normal operation. 
                            <E T="03">See supra</E>
                             note 369.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters also suggested that testing errors or other disruptions in development and testing environments should be excluded from the definition of systems disruption.
                        <SU>396</SU>
                        <FTREF/>
                         The Commission notes that, as discussed above, development and testing systems have been excluded from the definition of SCI systems, and thus such disruptions would not be subject to the requirements of Regulation SCI.
                        <SU>397</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>396</SU>
                             
                            <E T="03">See supra</E>
                             notes 361-363 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>397</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission is not incorporating a materiality threshold into the definition of systems disruption as requested by some commenters.
                        <SU>398</SU>
                        <FTREF/>
                         Rather, as discussed below, the requirements of Regulation SCI are tiered in a manner that the Commission believes is responsive to commenters' concerns regarding the breadth of the definition of systems disruption (while stopping short of including a materiality standard).
                        <SU>399</SU>
                        <FTREF/>
                         In particular, the Commission believes that the adopted Commission notification and information dissemination requirements for SCI events (
                        <E T="03">i.e.,</E>
                         quarterly Commission reporting of de minimis systems disruptions, and an exception for de minimis systems disruptions from the information dissemination requirement) will help to focus the Commission's and SCI entities' resources on the more significant systems disruptions. In addition, by not including a materiality threshold within the definition, SCI entities will be required to assess, take corrective action, and keep records of all systems disruptions, some of which may initially seem insignificant to an SCI entity, but which may later prove to be the cause of significant systems disruptions at the SCI entity. An SCI entity's records of de minimis systems disruptions may also be useful to the Commission in that they may, for example, aid the Commission in identifying patterns of de minimis systems disruptions that together might result in a more impactful SCI event, either at an SCI entity or across a group of SCI entities, or circumstances in which a systems disruption causes de minimis systems issues for one particular SCI entity but results in significant issues for another SCI entity. The Commission also believes that the ability to view de minimis SCI events in the aggregate and across multiple SCI 
                        <PRTPAGE P="72286"/>
                        entities is important to the Commission and its staff to be able to gather information about trends related to such systems disruptions that could not otherwise be properly discerned. Information about trends will assist the Commission in fulfilling its oversight role by keeping Commission staff informed about the nature and frequency of the types of de minimis systems disruptions that SCI entities encounter. Moreover, information about trends can also inform the Commission of areas of potential weaknesses, or persistent or recurring problems, across SCI entities and also should help the Commission better focus on common types of systems disruptions with certain types of SCI systems across SCI entities. This information also would permit the Commission and its staff to issue industry alerts or guidance if appropriate. In addition, this information would allow the Commission and its staff to review SCI entities' classification of events as de minimis systems disruptions. Moreover, the Commission believes that, even without adopting a materiality threshold, the adopted definition of SCI systems further focuses the scope of the definition of systems disruption.
                        <SU>400</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>398</SU>
                             
                            <E T="03">See supra</E>
                             note 347 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>399</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5) and 
                            <E T="03">infra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events and requiring a quarterly summary report for de minimis systems disruptions). 
                            <E T="03">See also</E>
                             Rule 1002(c)(4) and 
                            <E T="03">infra</E>
                             Section IV.B.3.d (discussing information dissemination requirement for certain SCI events, but excluding de minimis systems disruptions).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>400</SU>
                             
                            <E T="03">See supra</E>
                             Sections IV.A.2.b (discussing the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission also believes that it is unnecessary to modify the definition of systems disruption specifically to encompass disruptions originating from a third party, as one commenter suggested.
                        <SU>401</SU>
                        <FTREF/>
                         The definition of systems disruption does not limit such events with respect to the source of the disruption, whether an internal source at the SCI entity or an external third party source.
                    </P>
                    <FTNT>
                        <P>
                            <SU>401</SU>
                             
                            <E T="03">See supra</E>
                             note 345.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Systems Compliance Issue</HD>
                    <P>
                        Proposed Rule 1000(a) would have defined the term “systems compliance issue” as “an event at an SCI entity that has caused any SCI system of such entity to operate in a manner that does not comply with the federal securities laws and rules and regulations thereunder or the entity's rules or governing documents, as applicable.” 
                        <SU>402</SU>
                        <FTREF/>
                         The Commission is adopting the definition of systems compliance issue substantially as proposed, with modifications to refine its scope.
                    </P>
                    <FTNT>
                        <P>
                            <SU>402</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.3.b.
                        </P>
                    </FTNT>
                    <P>
                        Two commenters stated that the term “systems compliance issue” should be deleted from the definition of SCI event entirely.
                        <SU>403</SU>
                        <FTREF/>
                         One of these commenters stated that the inclusion of systems compliance issue as an SCI event would be a departure from the ARP Inspection Program and ARP Policy Statements.
                        <SU>404</SU>
                        <FTREF/>
                         The other commenter argued that any report regarding a systems compliance issue is an admission that the SCI entity has violated a law, rule, or one of its governing documents, creating a risk of an enforcement action or other liability for the SCI entity.
                        <SU>405</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>403</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 13; and NYSE Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>404</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>405</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 16.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters stated that the proposed definition is too broad and should be refined to include only those issues that are material or significant.
                        <SU>406</SU>
                        <FTREF/>
                         Commenters' specific recommendations included limiting the definition to those systems compliance issues that: have a material and significant effect on members; 
                        <SU>407</SU>
                        <FTREF/>
                         can be reasonably expected to result in significant harm or loss to market participants or impact the operation of a fair and orderly market; 
                        <SU>408</SU>
                        <FTREF/>
                         or have a materially negative impact on the SCI entity's ability to perform its core functions.
                        <SU>409</SU>
                        <FTREF/>
                         One commenter also noted that the term should be specifically defined to take account of an SCI entity's function, such as clearing agencies' ability to comply with Section 17A.
                        <SU>410</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>406</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint SROs Letter at 2, 8; ISE Letter at 6; SIFMA Letter at 13; Liquidnet Letter at 3; CME Letter at 8; DTCC Letter at 6; OCC Letter at 13; and FINRA Letter at 17 (stating that systems compliance issues should be reportable only if they would directly impact the market or a member firm's ability to comply with FINRA rules). 
                            <E T="03">See also</E>
                             BATS Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>407</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 6-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>408</SU>
                             
                            <E T="03">See</E>
                             Liquidnet Letter at 3; and CME Letter at 8. 
                            <E T="03">See also</E>
                             FINRA Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>409</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 6; and OCC Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>410</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 6. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Sections IV.B.3.c and IV.B.3.d (discussing comments with respect to systems compliance issues and their relation to Commission notification and information dissemination to members or participants).
                        </P>
                    </FTNT>
                    <P>
                        After considering the view of commenters that the proposed definition of systems compliance issue is too broad,
                        <SU>411</SU>
                        <FTREF/>
                         the Commission is revising the definition to mean an event that has caused an SCI system to operate “in a manner that does not comply with the Act” and the rules and regulations thereunder and the entity's rules and governing documents, as applicable.
                        <SU>412</SU>
                        <FTREF/>
                         The Commission believes the refinement from “federal securities laws” to “the Act” (
                        <E T="03">i.e.,</E>
                         the Securities Exchange Act of 1934) will appropriately focus the definition on Exchange Act compliance rather than other areas of the federal securities laws. Although the Commission did not receive specific comment suggesting that it amend the definition of systems compliance issue by using the term “the Act” instead of the broader “federal securities laws,” commenters did suggest that the Commission limit the scope of the definition to only apply to those sections of the Act that are applicable to a particular SCI entity 
                        <SU>413</SU>
                        <FTREF/>
                         or the SCI entity's rules.
                        <SU>414</SU>
                        <FTREF/>
                         The Commission agrees with these commenters insofar as they advocated for focusing the scope to a more specific set of securities laws and for reducing the burden on SCI entities, and further believes this refinement does not compromise the objective of the definition, which is to capture systems compliance issues with respect to SCI entities' obligations under the Exchange Act. The Commission believes that the refinement provides additional clarity to SCI entities that, for purposes of Regulation SCI, their obligations are with respect to compliance with the Exchange Act and the rules and regulations thereunder and the entity's rules and governing documents.
                        <SU>415</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>411</SU>
                             
                            <E T="03">See supra</E>
                             note 406 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>412</SU>
                             As noted above, proposed Rule 1000 defined systems compliance issue as an event at an SCI entity that has caused any SCI system of such entity to operate “in a manner that does not comply with the federal securities laws” and rules and regulations thereunder or the entity's rules and governing documents, as applicable.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>413</SU>
                             
                            <E T="03">See supra</E>
                             note 410 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>414</SU>
                             
                            <E T="03">See supra</E>
                             note 406 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>415</SU>
                             Notwithstanding this provision's focus on compliance with the Exchange Act and the rules and regulations thereunder and the entity's rules and governing documents, the Commission notes that its objective in adopting Regulation SCI is not, for example, to change the obligations of SCI entities that are public companies with respect to their disclosure obligations under the Securities Act of 1933. 
                            <E T="03">See</E>
                             15 U.S.C. 77a 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission disagrees with commenters who suggested removing systems compliance issues from the definition of SCI event altogether.
                        <SU>416</SU>
                        <FTREF/>
                         Although systems compliance issues have not been within the scope of the ARP Inspection Program,
                        <SU>417</SU>
                        <FTREF/>
                         the Commission believes that inclusion of systems compliance issues in the definition of SCI event and the resulting applicability of the Commission reporting, information dissemination, and recordkeeping requirements to systems compliance issues is important to help ensure that SCI systems are operated by SCI entities in compliance with the Exchange Act, rules thereunder, and their own rules and governing documents.
                    </P>
                    <FTNT>
                        <P>
                            <SU>416</SU>
                             
                            <E T="03">See supra</E>
                             notes 403-405 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>417</SU>
                             
                            <E T="03">See supra</E>
                             note 404 and accompanying text. 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18087.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72287"/>
                    <P>
                        In addition, the Commission is not adopting a materiality qualifier 
                        <SU>418</SU>
                        <FTREF/>
                         or other limiting threshold 
                        <SU>419</SU>
                        <FTREF/>
                         in the definition of systems compliance issue as suggested by some commenters. Instead, the requirements of Regulation SCI are tiered in a manner that the Commission believes is responsive to commenters' concerns regarding the breadth of the definition of systems compliance issue.
                        <SU>420</SU>
                        <FTREF/>
                         In particular, the Commission believes that the adopted Commission notification requirement and the information dissemination requirement (each of which provides an exception for systems compliance issues that have no or de minimis impacts on an SCI entity's operations or market participants) will help to focus the Commission's and SCI entities' resources on those systems compliance issues with more significant impacts. In addition, by not including a materiality threshold within the definition, SCI entities will be required to assess, take corrective action, and keep records of all systems compliance issues, some of which may initially seem to have little or no impact, but which may later prove to be the cause of significant systems compliance issues at the SCI entity. The Commission notes that all SCI entities are required to comply with the Exchange Act, the rules and regulations thereunder, and their own rules, as applicable. Therefore, even if an SCI entity determines that a systems compliance issue has no or a de minimis impact, the Commission believes that it is important that it have ready access to records regarding such de minimis systems compliance issues to allow it to more effectively oversee SCI entities' compliance with the Exchange Act and relevant rules. An SCI entity's records of de minimis systems compliance issues may also be useful to the Commission in that they may, for example, aid the Commission in identifying areas of potential weaknesses, or persistent or recurring problems, at an SCI entity or across multiple SCI entities. This information also would permit the Commission and its staff to issue industry alerts or guidance if appropriate. In addition, this information would allow the Commission and its staff to review SCI entities' classification of events as de minimis systems compliance issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>418</SU>
                             
                            <E T="03">See supra</E>
                             notes 406-407 and 409 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>419</SU>
                             
                            <E T="03">See supra</E>
                             note 408.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>420</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5) and 
                            <E T="03">infra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events and the exclusion for de minimis systems compliance issues). 
                            <E T="03">See also</E>
                             Rule 1002(c)(4) and 
                            <E T="03">infra</E>
                             Section IV.B.3.d (discussing the information dissemination requirement for certain SCI events, but excluding de minimis systems compliance issues).
                        </P>
                    </FTNT>
                    <P>Finally, the Commission believes that, even without adopting a materiality threshold, the adopted definition of SCI systems, as described in Section IV.A.2 above, further focuses the scope of the definition of systems compliance issue.</P>
                    <P>
                        With respect to a commenter's concern that any report regarding a systems compliance issue would be an admission of a violation and thus create a risk of enforcement action or other liability,
                        <SU>421</SU>
                        <FTREF/>
                         the Commission notes that the Commission notification requirement is not triggered until a responsible SCI personnel has a reasonable basis to conclude that a systems compliance issue has occurred.
                        <SU>422</SU>
                        <FTREF/>
                         The Commission acknowledges that it could consider the information provided to the Commission in determining whether to initiate an enforcement action. However, the Commission notes that the occurrence of a systems compliance issue also does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation.
                        <SU>423</SU>
                        <FTREF/>
                         With respect to the potential for other types of liability as suggested by this commenter, many entities that fall within the definition of SCI entity already currently disclose to the Commission and their members or participants certain information regarding systems issues, including issues that may potentially give rise to liability.
                        <SU>424</SU>
                        <FTREF/>
                         Moreover, the Commission recognizes that compliance with Regulation SCI will increase the amount of information about SCI events available to the Commission and SCI entities' members and participants, and that the greater availability of this information has some potential to increase litigation risks for SCI entities, including the risk of private civil litigation. The Commission believes that the value of disclosure to the Commission, market participants and investors justifies the potential increase in litigation risk. Moreover, the Commission notes that, to the extent members and participants or the public suffer damages when SCI events occur, SCI entities are already subject to litigation risk.
                    </P>
                    <FTNT>
                        <P>
                            <SU>421</SU>
                             
                            <E T="03">See supra</E>
                             note 405 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>422</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>423</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">infra</E>
                             notes 626-628 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>424</SU>
                             
                            <E T="03">See supra</E>
                             Section II.B (discussing recent events related to systems issues).
                        </P>
                    </FTNT>
                    <P>
                        As adopted, Rule 1000 defines “systems compliance issue” as “an event at an SCI entity that has caused any SCI system of such entity to operate in a manner that does not comply with the Act and the rules and regulations thereunder or the entity's rules or governing documents, as applicable.” As noted in the SCI Proposal, a systems compliance issue could, for example, occur when a change to an SCI system is made by information technology staff, without the knowledge or input of regulatory staff, that results in the system operating in a manner that does not comply with the Act and rules thereunder or the entity's rules and other governing documents.
                        <SU>425</SU>
                        <FTREF/>
                         For an SCI SRO, systems compliance issues would include SCI systems operating in a manner that does not comply with the SCI SRO's rules as defined in the Act and the rules thereunder.
                        <SU>426</SU>
                        <FTREF/>
                         For a plan processor, systems compliance issue would include SCI systems operating in a manner that does not comply with an applicable effective national market system plan. For an SCI ATS or exempt clearing agency subject to ARP, a systems compliance issue would include SCI systems operating in a manner that does not comply with documents such as subscriber agreements and any rules provided to subscribers and users and, for an ATS, described in its Form ATS filings with the Commission.
                        <SU>427</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>425</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18103.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>426</SU>
                             The rules of an SCI SRO include, among other things, its constitution, articles of incorporation, and bylaws. 
                            <E T="03">See</E>
                             15 U.S.C. 78c(a)(27)-(28). 
                            <E T="03">See also</E>
                             17 CFR 240.19b-4(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>427</SU>
                             Subscriber agreements and other similar documents that govern operations of SCI ATSs and exempt clearing agencies subject to ARP are generally not publicly available, but are typically provided to subscribers and users of such entities. 
                            <E T="03">See</E>
                             17 CFR 242.301(b) for a description of the filing requirements for ATSs.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Systems Intrusion</HD>
                    <P>
                        Proposed Rule 1000(a) defined “systems intrusion” as “any unauthorized entry into the SCI systems or SCI security systems of an SCI entity.” 
                        <SU>428</SU>
                        <FTREF/>
                         The proposed definition is being adopted as proposed, with one technical modification to replace the term “SCI security systems” with “indirect SCI systems.” 
                        <SU>429</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>428</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.B.3.c.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>429</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.d (discussing the definition of “indirect SCI systems”).
                        </P>
                    </FTNT>
                    <P>
                        While one commenter noted its general support for the inclusion of systems intrusions within the scope of 
                        <PRTPAGE P="72288"/>
                        Regulation SCI,
                        <SU>430</SU>
                        <FTREF/>
                         this commenter and others stated that the proposed definition was too broad or vague.
                        <SU>431</SU>
                        <FTREF/>
                         Several commenters asserted that the proposed definition would capture too many insignificant and minor incidents.
                        <SU>432</SU>
                        <FTREF/>
                         Some commenters recommended limiting the definition to material systems intrusions, and offered various suggestions for how to do so.
                        <SU>433</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>430</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>431</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 15; BATS Letter at 12; DTCC Letter at 7; Omgeo Letter at 11; SIFMA Letter at 10-11; and Joint SROs Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>432</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 12; DTCC Letter at 7; Omgeo Letter at 11; SIFMA Letter at 10-11; and Joint SROs Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>433</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 15 (recommending that the definition include only major intrusions that pose a plausible risk to the trading, routing, or clearance and settlement operations of the exchange or to required market data transmission); Omgeo Letter at 11-12 (expressing concern that the definition did not contain a reference to the materiality of an intrusion, nor the intrusion's impact on markets or market participants); DTCC Letter at 7 (suggesting that the definition capture only unauthorized entries where the SCI entity has reason to believe such entry could materially impact its ability to perform its core functions or critical operations); Joint SROs Letter at 7 (stating that the definition should include only those intrusions that the SCI entity reasonably estimated would result in significant harm or loss to market participants); FINRA Letter at 18 (arguing that only intrusions that have a material impact on the SCI system or a direct impact on the market or market participants should be included); and OCC Letter at 13 (suggesting, as an alternative to a “risk-based” approach, that the definition be limited to any unauthorized entry into the SCI systems or SCI security systems of an SCI entity, which the SCI entity reasonably believes may materially impact its ability to perform its core functions or critical operations).
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that the proposed definition was overbroad because it would include both intentional and unintentional conduct, as well as events that have no adverse impact.
                        <SU>434</SU>
                        <FTREF/>
                         Another commenter also stated that the definition should be modified to make clear that an intrusion that is inadvertent would not qualify as a systems intrusion.
                        <SU>435</SU>
                        <FTREF/>
                         This commenter further stated that a systems intrusion should be limited to unauthorized access to confidential information or to the SCI systems of an SCI entity that materially disrupts the operations of such systems.
                        <SU>436</SU>
                        <FTREF/>
                         Another commenter suggested that the definition focus on the unauthorized control of the confidentiality, integrity, or availability of an SCI system and/or its data.
                        <SU>437</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>434</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>435</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>436</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>437</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 15.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters noted that the proposed definition of systems intrusion did not take into account the multi-layered nature of today's technology systems. Two commenters stated that the multi-layered protections of systems architecture are designed to anticipate intrusions into the outer layer without material risk or impact, thus intrusions into such a peripheral system should not constitute a systems intrusion under the rule.
                        <SU>438</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>438</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 11; and Omgeo Letter at 12. The Commission discusses below the comments that advocated greater Commission use of FS-ISAC for reporting systems intrusions.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters stated that only successful systems intrusions should be covered in the definition.
                        <SU>439</SU>
                        <FTREF/>
                         One commenter suggested that this concept be made explicit in the rule text by adding the term “successful” to the definition.
                        <SU>440</SU>
                        <FTREF/>
                         Two commenters, while supporting the inclusion of only successful systems intrusions in the definition, pointed out the value of sharing information regarding unsuccessful systems intrusions, stating that this practice already occurs today among SCI entities, their regulators, and appropriate law enforcement agencies.
                        <SU>441</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>439</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 17; SIFMA Letter at 11; NYSE Letter at 15; DTCC Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>440</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>441</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 17; and DTCC Letter at 8.
                        </P>
                    </FTNT>
                    <P>
                        As adopted, Rule 1000 defines “systems intrusion” to mean “any unauthorized entry into the SCI systems or indirect SCI systems of an SCI entity.” This definition is intended to cover any unauthorized entry into SCI systems or indirect SCI systems, regardless of the identity of the person committing the intrusion (whether they are outsiders, employees, or agents of the SCI entity), and regardless of whether or not the intrusion was part of a cyber attack, potential criminal activity, or other unauthorized attempt to retrieve, manipulate, or destroy data, or access or disrupt systems of SCI entities. Thus, for example, this definition is intended to cover the introduction of malware or other attempts to disrupt SCI systems or indirect SCI systems provided that such systems were actually breached. In addition, the definition is intended to cover unauthorized access, whether intentional or inadvertent, by employees or agents of the SCI entity that resulted from weaknesses in the SCI entity's access controls and/or procedures. In response to comments, the Commission emphasizes that the definition of systems intrusion does not include unsuccessful attempts at unauthorized entry because an unsuccessful systems intrusion is much less likely to disrupt the systems of an SCI entity than a successful intrusion. The Commission believes that it is unnecessary and redundant to specifically state in the definition of systems intrusion that unauthorized entries must be “successful” because the term “entry” incorporates the concept of 
                        <E T="03">successfully</E>
                         gaining access to an SCI system or indirect SCI system.
                    </P>
                    <P>
                        Further, the Commission is not incorporating a materiality threshold for the definition of systems intrusion or otherwise limiting the definition of systems intrusion to only those systems intrusions that are major or significant as requested by some commenters. The Commission believes that, even without adopting a materiality threshold, the adopted definitions of SCI systems and indirect SCI systems further focus the scope of the definition of systems intrusion. Further, because any unauthorized entry into an SCI system or indirect SCI system is a security breach of which the Commission, having responsibility for oversight of the U.S. securities markets, should be notified, the Commission is not including a materiality threshold. In addition, as discussed below, the requirements of Regulation SCI are tiered in a manner that the Commission believes is responsive to commenters' concerns regarding the breadth of the definition of systems intrusion.
                        <SU>442</SU>
                        <FTREF/>
                         By not including a materiality threshold within the definition, SCI entities will be required to assess, take corrective action, and keep records of all systems intrusions, some of which may initially seem insignificant to an SCI entity, but which may later prove to be the cause of significant systems issues at the SCI entity. An SCI entity's records of de minimis systems intrusions may also be useful to the Commission in that they may, for example, aid the Commission in identifying patterns of de minimis systems intrusions that together might result in a more impactful SCI event, either at an SCI entity or across a group of SCI entities, or circumstances in which a systems intrusion causes de minimis systems issues for one particular SCI entity but results in significant issues for another SCI entity. The Commission also believes that the ability to view de minimis systems intrusions in the aggregate and across multiple SCI entities is important to allow the Commission and its staff to be able to gather information about trends related to such systems intrusions that could not otherwise be properly discerned. Information about trends will 
                        <PRTPAGE P="72289"/>
                        assist the Commission in fulfilling its oversight role by keeping Commission staff informed about the nature and frequency of the types of de minimis systems intrusions that SCI entities encounter. Moreover, information about trends and notifications of de minimis systems intrusions generally can also inform the Commission of areas of potential weaknesses, or persistent or recurring problems, across SCI entities and also should help the Commission better focus on common types of systems intrusions or issues with certain types of SCI systems across SCI entities. This information also would permit the Commission and its staff to issue industry alerts or guidance if appropriate. In addition, this information would allow the Commission and its staff to review SCI entities' classification of events as de minimis systems intrusions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>442</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5) and 
                            <E T="03">infra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events and requiring a quarterly summary report for de minimis systems intrusions). 
                            <E T="03">See also</E>
                             Rule 1002(c)(4) and 
                            <E T="03">infra</E>
                             Section IV.B.3.d (discussing information dissemination requirement for certain SCI events, but excluding de minimis systems intrusions).
                        </P>
                    </FTNT>
                    <P>
                        The Commission also is not distinguishing between intentional and unintentional systems intrusions, as suggested by some commenters.
                        <SU>443</SU>
                        <FTREF/>
                         The Commission acknowledges that intentional systems intrusions may result in more severe disruptions to the systems of an SCI entity than unintentional or inadvertent intrusions. On the other hand, the Commission believes that it should be notified of successful unintentional or inadvertent systems intrusions because they can still indicate weaknesses in a system's security controls. To the extent that these systems intrusions have no or a de minimis impact on the SCI entity's operations or on market participants, they will only be subject to a quarterly reporting requirement and will be excepted from the information dissemination requirement.
                        <SU>444</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>443</SU>
                             
                            <E T="03">See supra</E>
                             notes 434-435 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>444</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5) and 
                            <E T="03">infra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events and requiring a quarterly summary report for de minimis systems intrusions). 
                            <E T="03">See</E>
                             Rule 1002(c)(4), and 
                            <E T="03">infra</E>
                             Sections IV.B.3.d (discussing the information dissemination requirements for certain SCI events, but excluding de minimis systems intrusions).
                        </P>
                    </FTNT>
                    <P>
                        Additionally, the Commission does not agree that the definition of systems intrusion should be limited to unauthorized access to confidential information 
                        <SU>445</SU>
                        <FTREF/>
                         or should be focused on the unauthorized control of the confidentiality, integrity, or availability of an SCI system and/or its data 
                        <SU>446</SU>
                        <FTREF/>
                         because the Commission believes that these modifications would create a definition that would limit the Commission's ability to be aware of events that fall outside the limited definition that commenters suggested but that could, for example, have industry-wide implications. Similarly, with respect to the comment that intrusions into a peripheral system should not constitute a systems intrusion because the multi-layered protections of systems architecture are designed to anticipate intrusions into the outer layer and help prevent material risk or impact,
                        <SU>447</SU>
                        <FTREF/>
                         the Commission believes that its discussion of indirect SCI systems in Section IV.A.2.d above responds to commenters' concerns by explaining that systems intrusions into an indirect SCI system could cause or increase the likelihood of an SCI event with respect to an SCI system. And to the extent a system intrusion occurs with respect to an SCI system or indirect SCI system but the SCI entity's multi-layered systems architecture helps prevent material risk or impact, the Commission notes that de minimis systems intrusions (if such a system intrusion was determined to be de minimis) would be subject to less frequent Commission reporting requirements and would not be subject to the information dissemination requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>445</SU>
                             
                            <E T="03">See supra</E>
                             note 436 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>446</SU>
                             
                            <E T="03">See supra</E>
                             note 437 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>447</SU>
                             
                            <E T="03">See supra</E>
                             note 438 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Obligations of SCI Entities—Rules 1001-1004</HD>
                    <P>
                        Proposed Rules 1000(b)(1)-(9) are renumbered as adopted Rules 1001-1004. Adopted Rule 1001 corresponds to proposed Rules 1000(b)(1)-(2) and contains the policies and procedures requirements for SCI entities with respect to operational capability and the maintenance of fair and orderly markets (Rule 1001(a)), systems compliance (Rule 1001(b)), and identification and designation of responsible SCI personnel and escalation procedures (Rule 1001(c)).
                        <SU>448</SU>
                        <FTREF/>
                         Adopted Rule 1002 corresponds to proposed Rules 1000(b)(3)-(5) and contains the obligations of SCI entities with respect to SCI events, which include corrective action, Commission notification, and information dissemination. Adopted Rule 1003 corresponds to proposed Rules 1000(b)(6)-(8) and contains requirements relating to material systems changes and SCI reviews. Finally, adopted Rule 1004 corresponds to proposed Rule 1000(b)(9) and contains requirements relating to business continuity and disaster recovery plan testing, including requiring participation of designated members or participants of SCI entities in such testing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>448</SU>
                             The discussion of Rule 1001(c), which relates to the triggering standard for Rule 1002, is discussed below in Section IV.B.3.a.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Policies and Procedures To Achieve Capacity, Integrity, Resiliency, Availability and Security—Rule 1001(a)</HD>
                    <HD SOURCE="HD3">a. Proposed Rule 1000(b)(1)</HD>
                    <P>Proposed Rule 1000(b)(1) would have required an SCI entity to: (1) Establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, SCI security systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets; and (2) include certain required elements in such policies and procedures. As proposed, these policies and procedures were required to provide for: (A) The establishment of reasonable current and future capacity planning estimates; (B) periodic capacity stress tests of systems to determine their ability to process transactions in an accurate, timely, and efficient manner; (C) a program to review and keep current systems development and testing methodology; (D) regular reviews and testing of systems, including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters; (E) business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse to ensure next business day resumption of trading and two-hour resumption of clearance and settlement services following a wide-scale disruption; and (F) standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data.</P>
                    <P>
                        Proposed Rule 1000(b)(1)(i) also provided that an SCI entity's applicable policies and procedures would be deemed to be reasonably designed if they were consistent with “current SCI industry standards.” Proposed Rule 1000(b)(1)(ii) provided that “current SCI industry standards” were to be comprised of “information technology practices that are widely available for free to information technology professionals in the financial sector . . . and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely 
                        <PRTPAGE P="72290"/>
                        recognized organization.” 
                        <SU>449</SU>
                        <FTREF/>
                         The SCI Proposal also included, on “Table A,” a list of publications that the Commission had preliminarily identified as examples of current SCI industry standards in each of nine information security domains.
                        <SU>450</SU>
                        <FTREF/>
                         The SCI Proposal stated that an SCI entity, taking into account its nature, size, technology, business model, and other aspects of its business, could, but would not be required to, use the publications listed on Table A to establish, maintain, and enforce reasonably designed policies and procedures that satisfy the requirements of proposed Rule 1000(b)(1).
                        <SU>451</SU>
                        <FTREF/>
                         The SCI Proposal also stated that “current SCI industry standards” were not limited to those identified in the publications on Table A and could include other publications meeting the proposed criteria for “current SCI industry standards.” 
                        <SU>452</SU>
                        <FTREF/>
                         In addition, proposed Rule 1000(b)(1)(ii) stated that compliance with “current SCI industry standards” would not be the exclusive means to comply with the requirements of proposed Rule 1000(b)(1).
                        <SU>453</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>449</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18178.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>450</SU>
                             The domains covered in Table A of the SCI Proposal are: application controls; capacity planning; computer operations and production environment controls; contingency planning; information security and networking; audit; outsourcing; physical security; and systems development methodology. 
                            <E T="03">See id.</E>
                             at 18111.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>451</SU>
                             
                            <E T="03">See id.</E>
                             at 18110.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>452</SU>
                             
                            <E T="03">See id.</E>
                             at 18110 (stating that an SCI entity could elect standards contained in publications other than those identified on proposed Table A to comply with the rule).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>453</SU>
                             
                            <E T="03">See id.</E>
                             at 18109.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments Received on Proposed Rule 1000(b)(1) and Commission Response</HD>
                    <HD SOURCE="HD3">i. Policies and Procedures Generally—Rules 1001(a)(1) and (3)</HD>
                    <P>
                        The Commission received a wide range of comments on proposed Rule 1000(b)(1). With respect to policies and procedures generally, some commenters believed the proposal was too prescriptive.
                        <SU>454</SU>
                        <FTREF/>
                         Several characterized it as a “one-size-fits-all” approach that did not adequately take into account differences between SCI entities and SCI entity systems.
                        <SU>455</SU>
                        <FTREF/>
                         Several commenters objecting to the rule as too prescriptive urged that the adopted rule incorporate a risk-based framework, so that SCI entities and/or systems of greater criticality would be required to adhere to a stricter set of policies and procedures than SCI entities and/or systems of lesser criticality.
                        <SU>456</SU>
                        <FTREF/>
                         These commenters maintained that each SCI entity should have discretion to calibrate its policies and procedures based on its own assessment of the criticality of the SCI entity and its systems to market stability, or that the Commission should “tier” the obligations of SCI entities or SCI entity systems based on their market function.
                        <SU>457</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>454</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Angel Letter at 2, 8; BIDS Letter at 7; FIF Letter at 3-4; Joint SROs Letter at 4; LiquidPoint Letter at 3-4; MFA Letter at 3; and SIFMA Letter at 12-13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>455</SU>
                             
                            <E T="03">See, e.g.</E>
                            , FIF Letter at 3-4; FINRA Letter at 31; Joint SROs Letter at 4; KCG Letter at 2-3, 6-8; Liquidpoint Letter at 3-4; MFA Letter at 3; OCC Letter at 3-4; SIFMA Letter at 12-13; UBS Letter at 2-4; Tellefsen Letter at 13; and BIDS Letter at 2-3, 6-9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>456</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Joint SROs Letter at 4; LiquidPoint Letter at 3; MFA Letter at 3; and SIFMA Letter at 8, 12-13. 
                            <E T="03">See also</E>
                             FIF Letter at 4; MSRB Letter at 3; Fidelity Letter at 2; NYSE Letter at 3, 4, 21; FINRA Letter at 13-14; and OCC Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>457</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Joint SROs Letter at 4; FINRA Letter at 13-14; MSRB Letter at 3; MFA Letter at 6; NYSE Letter at 3, 4, and 21; SIFMA Letter at 12-13; FIF Letter at 4; Fidelity Letter at 2; and OCC Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        In contrast, some commenters stated that the Commission's proposed approach was too vague or insufficient.
                        <SU>458</SU>
                        <FTREF/>
                         For example, one commenter characterized the minimum elements of policies and procedures in proposed Rule 1000(b)(1)(A)-(F) as “so vague that they will fail to provide any meaningful improvement in technological systems.” 
                        <SU>459</SU>
                        <FTREF/>
                         Another commenter stated that the proposed scope of required policies and procedures was appropriate, but that further elaboration on the details was warranted.
                        <SU>460</SU>
                        <FTREF/>
                         One commenter stated that the proposed rule lacked adequate discussion of what it means for policies and procedures to be reasonably designed “to maintain . . . operational capability and promote the maintenance of fair and orderly markets.” 
                        <SU>461</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>458</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 3-5; CAST Letter at 4; CISQ Letter at 2, 5; CISQ2 Letter at 5; and Direct Edge Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>459</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>460</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>461</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 4.
                        </P>
                    </FTNT>
                    <P>The Commission has carefully considered the views of commenters on its proposed policies and procedures approach to ensuring adequate capacity, integrity, resiliency, availability, and security of SCI systems (and security for indirect SCI systems). The Commission agrees with commenters who stated that requiring SCI entities to have policies and procedures relating to the capacity, integrity, resiliency, availability, and security of SCI systems (and security for indirect SCI systems) should not be a “one-size-fits-all” approach and, as discussed in detail below, is therefore clarifying that the adopted rule is consistent with a risk-based approach, as it allows an SCI entity's policies and procedures to be tailored to a particular system's criticality and risk. As noted above, while some commenters characterized the proposed rule as too vague and sought further specificity, others found the rule to be too prescriptive. The Commission believes that the adopted rule provides an appropriate balance between these two opposing concerns by providing a framework that identifies the minimum areas that are required to be addressed by an SCI entity's policies and procedures without prescribing the specific policies and procedures that an SCI entity must follow, or detailing how each element in Rule 1001(a)(2) should be addressed. Given the various types of systems at SCI entities, each of which represent a different level of criticality and risk to each SCI entity and to the securities markets more broadly, the adopted rule seeks to provide flexibility to SCI entities to design their policies and procedures consistent with a risk-based approach, as discussed in further detail below. At the same time, because the Commission believes that additional guidance on how an SCI entity may comply with the rule is warranted in certain areas, the Commission is providing further guidance below. In response to comment, the Commission is adopting Rule 1001(a) with modifications that it believes will better provide SCI entities with sufficient flexibility to develop their policies and procedures to achieve robust systems, while also providing guidance on how an SCI entity may comply with the final rule. Specifically, adopted Rule 1001(a) is modified to: (i) Clarify that the rule is consistent with a risk-based approach that requires more robust policies and procedures for higher-risk systems and provides an SCI entity with flexibility to tailor its policies and procedures to the nature of its business, technology, and the relative criticality of each of its SCI systems; (ii) make clear that an SCI entity's reasonable policies and procedures remain subject to ongoing self-assessment; (iii) provide increased flexibility in the manner in which an SCI entity may satisfy the minimum elements of required policies and procedures; and (iv) revise the criteria for “current SCI industry standards.” In addition, proposed Table A is recharacterized and will be issued as staff guidance that will evolve over time.</P>
                    <HD SOURCE="HD3">Response to Commenters Advocating a Risk-Based Approach</HD>
                    <P>
                        Adopted Rule 1001(a)(1) requires each SCI entity to establish, maintain, and enforce written policies and procedures 
                        <PRTPAGE P="72291"/>
                        reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. The text of this part of the rule is largely unchanged from the proposal. Although several commenters expressed concern that the proposed rule would have imposed a “one-size-fits-all” approach, requiring all SCI entities to hold all of their SCI systems to the same standards,
                        <SU>462</SU>
                        <FTREF/>
                         this was not the intent of proposed Rule 1000(b)(1), nor is it what adopted Rule 1001(a)(1) requires. By requiring an SCI entity to have policies and procedures “reasonably designed” and “adequate” to maintain operational capability and promote the maintenance of fair and orderly markets, the adopted rule provides an SCI entity with flexibility to determine how to tailor its policies and procedures to the nature of its business, technology, and the relative criticality of each of its SCI systems.
                        <SU>463</SU>
                        <FTREF/>
                         Although the adopted rule does not assign differing obligations to an SCI entity based on its registration status, or its general market function, as some commenters urged, by allowing each SCI entity to tailor its policies and procedures accordingly, the adopted approach recognizes that there are differences between, and varying roles played by, different systems at various SCI entities. In tandem with the refined definition of “SCI systems,” the modified definition of “SCI security systems” (adopted as “indirect SCI systems”), and the new definition of “critical SCI systems,
                        <SU>464</SU>
                        <FTREF/>
                         adopted Rule 1001(a)(1) explicitly recognizes that policies and procedures that are “reasonably designed” and “adequate” to maintain operational capability and promote the maintenance of fair and orderly markets for critical SCI systems may differ from those that are “reasonably designed” and “adequate” to maintain operational capability and promote the maintenance of fair and orderly markets for other SCI systems, or indirect SCI systems. As such, the Commission believes that its adopted approach in Regulation SCI is consistent with a risk-based approach, and that adopted Regulation SCI may result in the systems of certain SCI entities (for example, those that have few or no critical SCI systems) generally being subject to less stringent policies and procedures than the systems of other SCI entities. Thus, a risk assessment is appropriate for an SCI entity to determine how to tailor its policies and procedures for its SCI systems and indirect SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>462</SU>
                             
                            <E T="03">See supra</E>
                             note 455 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>463</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18109 (stating: “The Commission intends to . . . provide SCI entities sufficient flexibility, based on the nature, size, technology, business model, and other aspects of their business, to identify appropriate policies and procedures that would meet the articulated standard, namely that they be reasonably designed to ensure that their systems have levels of capacity, integrity, resiliency, availability, and security adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>464</SU>
                             As a result of these changes, the adopted rule applies to fewer systems than as proposed, and only to those types of systems that the Commission believes pose significant risk to market integrity if not adequately safeguarded.
                        </P>
                    </FTNT>
                    <P>The Commission also believes that requiring an SCI entity to tailor its policies and procedures so that they are reasonably designed and adequate will entail that an SCI entity assess the relative criticality and risk of each of its SCI systems and indirect SCI systems. Evaluation of the risk posed by any particular SCI system to the SCI entity's operational capability and the maintenance of fair and orderly markets will be the responsibility of the SCI entity in the first instance. The Commission believes this approach will achieve the goal of improving Commission review and oversight of U.S. securities market infrastructure, but will do so within a more focused framework than as proposed. By being subject to requirements for a more targeted set of SCI systems, and guided by consideration of the relative risk of each of its SCI systems, SCI entities may more easily determine how to allocate their resources to achieve compliance with the regulation than they would have under the proposed regulation.</P>
                    <P>
                        As noted above, one commenter urged the Commission to discuss what it means for policies and procedures to be reasonably designed “to maintain . . . operational capability and promote the maintenance of fair and orderly markets.” 
                        <SU>465</SU>
                        <FTREF/>
                         This commenter characterized the proposed standard of “maintaining operational capability” as an “introspective standard relevant to the applicable SCI entity,” and the proposed standard of “promoting the maintenance of fair and orderly markets” as implying “some incremental responsibility to the collective market.” 
                        <SU>466</SU>
                        <FTREF/>
                         The Commission agrees with this commenter's characterization and believes that it is appropriate for SCI entities to assess the risk of their systems taking into consideration both objectives, which are related and complementary.
                        <SU>467</SU>
                        <FTREF/>
                         Specifically, the Commission believes that it is important that an SCI entity's policies and procedures are reasonably designed to ensure its own operational capability, including the ability to maintain effective operations, minimize or eliminate the effect of performance degradations, and have sufficient backup and recovery capabilities. At the same time, an SCI entity's own operational capability can have broader effects and, as entities that play a significant role in the U.S. securities markets and/or have the potential to impact investors, the overall market, or the trading of individual securities,
                        <SU>468</SU>
                        <FTREF/>
                         the Commission believes that the policies and procedures should also be reasonably designed to promote the maintenance of fair and orderly markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>465</SU>
                             
                            <E T="03">See supra</E>
                             note 461 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>466</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>467</SU>
                             The Commission notes that the identification of “critical SCI systems” in Regulation SCI emphasizes that some systems pose greater risk than others to the maintenance of fair and orderly markets if they malfunction, and that it is appropriate for an SCI entity to consider the risk to other SCI entities and market participants in the event of a systems malfunction.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>468</SU>
                             
                            <E T="03">See supra</E>
                             note 59 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Periodic Review</HD>
                    <P>
                        Some commenters expressed concern that, when an SCI entity's policies and procedures fail to prevent an SCI event, the Commission might use such failure as the basis for an enforcement action, charging that the policies and procedures were not reasonable.
                        <SU>469</SU>
                        <FTREF/>
                         One commenter suggested that the Commission's focus should be on an entity's adherence to its own set of policies and procedures, developed based on “experience, annual SCI reviews, and other inputs,” rather than a “set of generic standards.” 
                        <SU>470</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>469</SU>
                             
                            <E T="03">See, e.g.</E>
                            , BATS Letter at 3-4; Angel Letter at 2; and FSR Letter at 5. 
                            <E T="03">See also</E>
                             ITG Letter at 14 (stating that no set of policies and procedures could guarantee perfect operational compliance); and NYSE Letter at 32 (urging inclusion of a good faith safe harbor).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>470</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        In response to these comments, the Commission notes that the reasonably designed policies and procedures approach taken in adopted Rule 1001(a) does not require an entity to guarantee flawless systems. But the Commission believes it should be understood to require diligence in maintaining a reasonable set of policies and procedures that keeps pace with changing technology and circumstances and does not become outdated over time. The Commission is therefore adopting a requirement for periodic review by an SCI entity of the effectiveness of its policies and procedures required by Rule 1001(a), and prompt action by the SCI entity to 
                        <PRTPAGE P="72292"/>
                        remedy deficiencies in such policies and procedures.
                        <SU>471</SU>
                        <FTREF/>
                         An SCI entity will not be found to be in violation of this maintenance requirement solely because it failed to identify a deficiency in its policies and procedures immediately after the deficiency occurred if the SCI entity takes prompt action to remedy the deficiency once it is discovered, and the SCI entity had otherwise reviewed the effectiveness of its policies and procedures and took prompt action to remedy those deficiencies that were discovered, as required by Rule 1001(a)(3).
                    </P>
                    <FTNT>
                        <P>
                            <SU>471</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(a)(3).
                        </P>
                    </FTNT>
                    <P>Further, the occurrence of a systems disruption or systems intrusion will not necessarily mean that an SCI entity has violated Rule 1001(a), or that it will be subject to an enforcement action for violation of Regulation SCI. The Commission will exercise its discretion to initiate an enforcement action if the Commission determines that such action is warranted, based on the particular facts and circumstances. While a systems problem may be probative as to the reasonableness of an SCI entity's policies and procedures, it is not determinative.</P>
                    <HD SOURCE="HD3">ii. Minimum Elements of Reasonable Policies and Procedures—Rule 1001(a)(2)</HD>
                    <P>Proposed Rule 1000(b)(1)(i) would have required that an SCI entity's policies and procedures provide for, at a minimum: (A) The establishment of reasonable current and future capacity planning estimates; (B) periodic capacity stress tests of systems to determine their ability to process transactions in an accurate, timely, and efficient manner; (C) a program to review and keep current systems development and testing methodology; (D) regular reviews and testing of systems, including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters; (E) business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse to ensure next business day resumption of trading and two-hour resumption of clearance and settlement services following a wide-scale disruption; and (F) standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data. References to “systems” in the proposed rule were to the proposed definition of SCI systems, and with respect to security standards only, the proposed definition of SCI security systems.</P>
                    <P>
                        Adopted Rule 1001(a)(2) includes the items formerly proposed as Rules 1001(b)(1)(i)(A)-(F) as renumbered Rules 1001(2)(i)-(vi) and a new item (vii), relating to monitoring of SCI systems. Proposed items (A), (D), and (E) are revised in certain respects in response to comment. In addition, the Commission discusses below each of the adopted provisions of Rule 1001(a)(2) in the context of the adopted definitions of SCI systems and indirect SCI systems, where relevant.
                        <SU>472</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>472</SU>
                             In particular, the Commission is adopting the language of items (B) and (C) as proposed (renumbered as Rule 1001(a)(2)(ii) and (iii), respectively) but elaborates on the scope of these provisions, as well as the scope of revised item (D) (renumbered as Rule 1001(a)(2)(iv)) and in the context of the adopted definitions of SCI systems and indirect SCI systems.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Capacity Planning</HD>
                    <P>
                        The SCI Proposal stated that policies and procedures for the establishment of reasonable current and future capacity planning (proposed item (A)) would help an SCI entity determine its systems' ability to process transactions in an accurate, timely, and efficient manner, and thereby help ensure market integrity.
                        <SU>473</SU>
                        <FTREF/>
                         One commenter expressed support for the requirement in proposed item (A),
                        <SU>474</SU>
                        <FTREF/>
                         and another commenter recommended that proposed item (A) be revised to make clear that SCI entity capacity planning estimates apply to “technology infrastructure” capacity, as opposed to capacity with respect to non-technology infrastructure of an SCI entity.
                        <SU>475</SU>
                        <FTREF/>
                         Because the Commission intended proposed item (A) to relate to capacity planning for SCI systems, rather than capacity planning more broadly (for example, in relation to an SCI entity's office space), the Commission is including this suggested clarification in adopted Rule 1001(a)(2)(i), and thus requires that an SCI entity's policies and procedures include the establishment of reasonable current and future 
                        <E T="03">technology</E>
                         infrastructure capacity planning estimates.
                    </P>
                    <FTNT>
                        <P>
                            <SU>473</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18107.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>474</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>475</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 14-15. The Commission also received comments in regard to capacity planning as it relates to proposed industry standards on the capacity planning domain set out in proposed Table A. 
                            <E T="03">See, e.g., infra</E>
                             note 580 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Stress Testing</HD>
                    <P>
                        A few commenters raised concerns about proposed item (B), which required periodic capacity stress tests.
                        <SU>476</SU>
                        <FTREF/>
                         Some of these commenters urged that the adopted rule provide an SCI entity with flexibility to determine, using a risk-based assessment, when capacity stress tests are appropriate.
                        <SU>477</SU>
                        <FTREF/>
                         Others suggested that capacity stress tests be required in specified circumstances or time frames, such as when new capabilities are released into production,
                        <SU>478</SU>
                        <FTREF/>
                         whenever required system capacity increases by 10 percent, on a quarterly basis, or in conjunction with any material systems change.
                        <SU>479</SU>
                        <FTREF/>
                         One commenter suggested that SCI entities should supplement dynamic stress and load testing with static analysis, a technique used to help uncover structural weaknesses in software.
                        <SU>480</SU>
                        <FTREF/>
                         In proposing item (B), the Commission intended for SCI entities to engage in a careful risk-based assessment (as suggested by some commenters) 
                        <SU>481</SU>
                        <FTREF/>
                         of its SCI systems to determine when to stress test its systems.
                        <SU>482</SU>
                        <FTREF/>
                         Rule 1001(a)(2)(ii), as adopted, affords SCI entities the flexibility to consider the factors suggested by commenters, as appropriate for their specific systems and circumstances.
                        <SU>483</SU>
                        <FTREF/>
                         The adopted rule does not prescribe a particular frequency or trigger for stress testing; however, because the Commission believes that, in light of the variability in SCI systems, an SCI entity's experience with its particular systems 
                        <PRTPAGE P="72293"/>
                        and assessment of risk in this area will dictate when capacity stress testing is warranted. The requirement for periodic capacity stress tests of systems to determine their ability to process transactions in an accurate, timely, and efficient manner is therefore adopted as proposed as Rule 1001(a)(2)(ii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>476</SU>
                             
                            <E T="03">See, e.g.</E>
                            , CISQ Letter at 5; DTCC Letter at 14; Lauer Letter at 6; MSRB Letter at 9; OCC Letter at 10; and SIFMA Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>477</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 14; and OCC Letter at 10. 
                            <E T="03">See also</E>
                             SIFMA Letter at 12 (suggesting that periodic capacity monitoring would be more appropriate and cost-effective than periodic capacity stress testing).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>478</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>479</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>480</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 5. 
                            <E T="03">See also infra</E>
                             notes 491 and 497, and 498 and accompanying text (further discussing this comment and the commenter's views on the value of assessing the structural quality of software).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>481</SU>
                             
                            <E T="03">See supra</E>
                             note 477 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>482</SU>
                             In response to the commenter that suggested periodic capacity monitoring would be more appropriate and cost-effective than periodic capacity stress testing, 
                            <E T="03">see supra</E>
                             note 477 and accompanying text, the Commission believes that such monitoring is appropriate and may play an important role in an SCI entity's assessing when to stress tests its systems. However, the Commission continues to believe that stress testing is necessary to help an SCI entity determine its systems' ability to process transactions in an accurate, timely, and efficient manner, and thereby help ensure market integrity. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18107. While monitoring may be a cost-effective method to determine when a stress test is warranted, the Commission does not believe monitoring alone will be an effective substitute for stress testing, which, unlike monitoring, is designed to challenge systems capacity.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>483</SU>
                             
                            <E T="03">See supra</E>
                             notes 478-479 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Systems Development and Testing Methodology</HD>
                    <P>
                        In the SCI Proposal, the Commission explained that proposed item (C), which would require SCI entities to have policies and procedures for a “program to review and keep current systems development and testing methodology,” would help an SCI entity monitor and maintain systems capacity and availability.
                        <SU>484</SU>
                        <FTREF/>
                         The Commission is adopting the language of this item as proposed as Rule 1001(a)(2)(iii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>484</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18107.
                        </P>
                    </FTNT>
                    <P>
                        Two commenters supported this requirement as proposed.
                        <SU>485</SU>
                        <FTREF/>
                         Another commenter argued that sufficient controls were in place with respect to production systems, as proposed, and therefore that separate policies and procedures specifically for the development and testing environment would be unnecessary and duplicative.
                        <SU>486</SU>
                        <FTREF/>
                         This commenter added that, if development and testing systems were not excluded from the definition of SCI systems altogether, then the policies and procedures requirements regarding systems development and testing methodology should not apply separately to these environments. The Commission agrees with this comment, and believes it logically follows that policies and procedures requiring a program to review and keep current systems development and testing methodology for SCI systems, and indirect SCI systems, as applicable, are important if development and testing systems are excluded from the definition of SCI systems, as they are under the adopted regulation.
                        <SU>487</SU>
                        <FTREF/>
                         An SCI entity's systems development and testing methodology is a core part of the systems development life cycle for any SCI system. Therefore, the Commission believes that if an SCI entity did not have a program to review and keep current systems development and testing methodology for SCI systems, and indirect SCI systems, as applicable, its ability to assess the capacity, integrity, reliability, availability and security of its SCI systems and indirect SCI systems, as applicable, would be undermined. In complying with this adopted requirement, an SCI entity may wish to consider how closely its testing environment simulates its production environment; whether it designs, tests, installs, operates, and changes SCI systems through use of appropriate development, acquisition, and testing controls by the SCI entity and/or its third-party service providers, as applicable; whether it identifies and corrects problems detected in the development and testing stages; whether it verifies change implementation in the production stage; whether development and test environments are segregated from SCI systems in production; and whether SCI entity personnel have adequately segregated roles between the development and/or test environment, and the production environment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>485</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 2; and MSRB Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>486</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>487</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”). Because development and testing systems are not part of the adopted definition of “SCI systems,” systems issues with regard to development and testing systems would not be subject to the requirements of adopted Rule 1002 relating to corrective action, Commission notification, and dissemination of information on SCI events; or Rule 1003(a) regarding notification of systems changes.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Reviews of SCI Systems and Indirect SCI Systems</HD>
                    <P>
                        The SCI Proposal explained that proposed item (D), which would have required an SCI entity to establish, maintain, and enforce policies and procedures to review and test regularly SCI systems (and SCI security systems, as applicable), including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters, would assist an SCI entity in ascertaining whether such systems are and remain sufficiently secure and resilient.
                        <SU>488</SU>
                        <FTREF/>
                         Proposed item (D) garnered a range of comments. Some commenters addressing this item focused on internal SCI entity testing,
                        <SU>489</SU>
                        <FTREF/>
                         whereas others focused more broadly on industry-wide testing and testing of backup systems.
                        <SU>490</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>488</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18107.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>489</SU>
                             
                            <E T="03">See, e.g.</E>
                            , CAST Letter at 4; CISQ Letter at 3-7; FIA PTG Letter at 4; Lauer Letter at 6; and MSRB Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>490</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Angel Letter at 2; CoreOne Letter at 3-5; DTCC Letter at 13; FIA PTG Letter at 2; FIX Letter at 1-2; Tradebook Letter at 1-4; UBS Letter at 4; and CISQ Letter at 6. 
                            <E T="03">See also infra</E>
                             Section IV.B.6 (discussing adopted Rule 1004, requiring business continuity and disaster recovery testing, including required participation of designated members or participants of SCI entities in such testing).
                        </P>
                    </FTNT>
                    <P>
                        With respect to comments on internal testing, one commenter suggested that the proposed requirement be expanded beyond testing to cover a range of “quality assurance activities” with each release of software into production.
                        <SU>491</SU>
                        <FTREF/>
                         Two commenters advocated for requiring an SCI entity to focus on identifying structural deficiencies, which they stated pose much greater risks than functional deficiencies.
                        <SU>492</SU>
                        <FTREF/>
                         A few commenters urged that groups independent of the team that designed and developed the systems should be involved in testing to offer a diverse perspective.
                        <SU>493</SU>
                        <FTREF/>
                         One of these commenters further suggested that enforcement of the policies governing development and testing activities should be conducted by a “process audit” role that evaluates compliance with policies, provides guidance to development and testing teams on how to comply, and reports on compliance to senior management.
                        <SU>494</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>491</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 3-7 (encouraging the Commission to require quality assurance activities other than testing, including that an SCI entity evaluate and measure the structural quality of its SCI systems because “the attributes of an SCI system most critically affecting its capacity, integrity, resiliency, availability, and security are predominantly structural (engineering) rather than functional (correctness)”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>492</SU>
                             
                            <E T="03">See</E>
                             CAST Letter at 4; and CISQ Letter at 3-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>493</SU>
                             
                            <E T="03">See, e.g.</E>
                            , CISQ Letter at 7; and Lauer Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>494</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 7. This commenter further recommended that such process audits be conducted at least annually for each SCI system, and more often for SCI systems with operational problems, a record of non-compliance, or those being developed, tested, or operated by an inexperienced staff, and stated that process auditors who perform a mentoring role to software teams have proven a cost-effective mechanism for on-the-job training.
                        </P>
                    </FTNT>
                    <P>After careful consideration of the comments, the Commission is adopting this provision with modifications as Rule 1001(a)(2)(iv). Specifically, adopted Rule 1001(a)(2)(iv) requires an SCI entity's reasonably designed policies and procedures to include “[r]egular reviews and testing, as applicable, of [its SCI systems and, for purposes of security standards, indirect SCI systems], including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters.”</P>
                    <P>
                        As adopted, this provision will afford an SCI entity greater flexibility, through the addition of the phrase “as applicable,” to determine how to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters. Specifically, the adopted rule replaces the proposed rule's requirement that an SCI entity conduct “regular reviews and testing” of relevant systems (including backup systems) with a more flexible requirement that an SCI entity conduct “regular reviews and 
                        <PRTPAGE P="72294"/>
                        testing, as applicable” of relevant systems, including backup systems. In response to some commenters' concerns that the proposed requirement focused too much on regular testing and not enough on other methods to assess systems operation,
                        <SU>495</SU>
                        <FTREF/>
                         the adopted rule provides an SCI entity the flexibility to determine an assessment methodology that would be most appropriate for a given system, or particular functionality of a system. Thus, consistent with commenters' views, the adopted provision does not specifically require both regular reviews and regular testing in connection with an SCI entity's identification of vulnerabilities. Instead, the provision requires reviews or testing (or both) to occur as applicable, so long as the approach is effective to identify vulnerabilities in SCI systems, and indirect SCI systems, as applicable.
                    </P>
                    <FTNT>
                        <P>
                            <SU>495</SU>
                             
                            <E T="03">See supra</E>
                             notes 491-492 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        While Rule 1001(a)(2)(iv) specifically identifies reviews and testing as means to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters, it does not dictate the precise manner or frequency of reviews and testing, and does not prohibit an SCI entity from determining that there are methods other than reviews and testing that may be effective in identifying vulnerabilities. For example, reviews and testing would each be one of the methods that an SCI entity could employ, and each SCI entity would be able to determine which method(s) are most appropriate for each SCI system (or indirect SCI system, as applicable) or particular functionality of a given system, as well as the frequency with which such method(s) should be employed.
                        <SU>496</SU>
                        <FTREF/>
                         In addition, in response to commenters advocating that SCI entities should focus on identifying structural vulnerabilities or weaknesses,
                        <SU>497</SU>
                        <FTREF/>
                         an SCI entity may also find it useful to conduct reviews of its software and systems architecture and design to assess whether they have flaws or dependencies that constitute structural risks that could pose a threat to SCI systems' operational capability.
                        <SU>498</SU>
                        <FTREF/>
                         Likewise, an inspection by an SCI entity of its physical premises may be a method of assessing some of the vulnerabilities listed in the rule (such as physical hazards).
                    </P>
                    <FTNT>
                        <P>
                            <SU>496</SU>
                             Rule 1001(a)(2)(iv) would also permit an SCI entity to engage personnel independent of the team that designed and developed the systems in testing, or to employ a process audit role, to comply with this requirement, as some commenters suggested. 
                            <E T="03">See supra</E>
                             notes 493-494 and accompanying text. Like other methods of review and testing, such engagements could identify vulnerabilities in a number of ways, such as through assessments of the SCI entity's compliance with applicable standards, its risk management and control framework, or its use of resources.
                        </P>
                        <P>In response to the comment suggesting that process audits be conducted at least annually for each SCI system, and more often for SCI systems with operational problems, a record of non-compliance, or those being developed, tested, or operated by an inexperienced staff, the Commission notes that Rule 1001(a)(2)(iv) does not specify the precise manner or frequency of reviews and tests. Rather, Rule 1001(a)(2)(iv) provides flexibility to an SCI entity in determining the precise manner and frequency of reviews and/or tests. For example, an SCI entity could determine that, in order for its policies and procedures to be reasonably designed, as required by Rule 1001(a), its policies and procedures should provide that process audits be conducted at least annually for some SCI systems, and more frequently for certain other SCI systems.</P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>497</SU>
                             
                            <E T="03">See supra</E>
                             note 492 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>498</SU>
                             As noted by one commenter, static analysis could be a technique SCI entities could choose to utilize to help uncover structural weaknesses in software. 
                            <E T="03">See supra</E>
                             note 480 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Business Continuity and Disaster Recovery</HD>
                    <P>
                        Proposed item (E) would have required an SCI entity to have business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse to ensure next business day resumption of trading and two-hour resumption of clearance and settlement services following a wide-scale disruption. The Commission received significant comment on this aspect of the proposal, with several commenters questioning or challenging the principle that securities market infrastructure resilience is achieved by requiring both geographic diversity and specific recovery times for the backup and recovery capabilities of all SCI entities.
                        <SU>499</SU>
                        <FTREF/>
                         Although several commenters were supportive of the broad goals of the proposed requirement,
                        <SU>500</SU>
                        <FTREF/>
                         others maintained that, because the national market system has built-in redundancies, the proposed geographic diversity and resumption requirements need not apply to all SCI entities to ensure securities market resilience.
                        <SU>501</SU>
                        <FTREF/>
                         Some of these commenters urged that the specific redundancy requirement implicit in the proposed geographic diversity provision should apply to a more limited set of SCI entities.
                        <SU>502</SU>
                        <FTREF/>
                         In addition, some commenters stated that proposed time frames were too inflexible.
                        <SU>503</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>499</SU>
                             
                            <E T="03">See, e.g.</E>
                            , BIDS Letter at 8; FIA PTG Letter at 4; FIF Letter at 3; Group One Letter at 2-3; KCG Letter at 6-8, 11-14; FINRA Letter at 35-36; Angel Letter at 12; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>500</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 4; FINRA Letter at 35; ISE Letter at 2; and MSRB Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>501</SU>
                             
                            <E T="03">See, e.g.</E>
                            , BIDS Letter at 8; FIA PTG Letter at 4; FIF Letter at 3; Group One Letter at 2-3; and KCG Letter at 6-8, 11-14. According to these commenters, because of the ease with which market participants are able to shift their order flow when there is an issue at one or more markets, the proposed requirements are burdensome and unnecessary. 
                            <E T="03">See also</E>
                             Angel Letter at 12 (stating that, if an exchange experiences an issue, other exchanges have more than enough capacity to handle the trading volume, and suggesting that it is not necessary for each exchange to have totally redundant backup facilities if the market network as a whole has sufficient capacity).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>502</SU>
                             
                            <E T="03">See, e.g.</E>
                            , FIA PTG Letter at 4. 
                            <E T="03">See also supra</E>
                             note 53 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>503</SU>
                             
                            <E T="03">See, e.g.</E>
                            , SIFMA Letter at 13; and Joint SROs Letter at 17.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered commenters' views and is revising this provision from the proposal to: (i) Specify that the stated recovery timeframes in Regulation SCI are goals, rather than inflexible requirements; 
                        <SU>504</SU>
                        <FTREF/>
                         and (ii) provide that the stated two-hour recovery goal applies to critical SCI systems generally. In addition, the Commission is adopting the geographic diversity requirement, which does not specify any minimum distance for an SCI entity's backup and recovery facilities, as proposed. As explained below, the Commission continues to believe that geographic diversity of physical facilities is an important component of every SCI entity's BC/DR plan.
                    </P>
                    <FTNT>
                        <P>
                            <SU>504</SU>
                             
                            <E T="03">See</E>
                             Interagency Paper on Sound Practices to Strengthen the Resilience of the U.S. Financial Systems, Securities Exchange Act Release No. 47638 (April 7, 2003), 68 FR 17809, 17812 (April 11, 2003) (“Interagency White Paper”), stating: “Recovery-time objectives provide concrete goals to plan for and test against. They should not be regarded as hard and fast deadlines that must be met in every emergency situation;” and 2003 Policy Statement on Business Continuity Planning for Trading Markets, Securities Exchange Act Release No. 48545 (September 25, 2003), 68 FR 56656, 56658 (October 1, 2003) (“2003 BCP Policy Statement”), stating: “Consistent with the approach taken in the Interagency Paper, the next-day resumption objective should provide a concrete goal to plan for and test against. This should not be regarded as a hard and fast deadline that must be met in every emergency situation.”
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Recovery Timeframes as Goals</HD>
                    <P>
                        Several commenters addressing proposed item (E) focused their comments specifically on the proposed recovery timeframes.
                        <SU>505</SU>
                        <FTREF/>
                         A few commenters that are clearing agencies specifically expressed concern about the proposed requirement for the two-hour resumption of clearance and settlement services, urging that the two-hour standard be a goal rather than a requirement.
                        <SU>506</SU>
                        <FTREF/>
                         One commenter noted 
                        <PRTPAGE P="72295"/>
                        that the “Interagency White Paper itself recognizes that `various external factors surrounding a disruption such as time of day, scope of disruption, and status of critical infrastructure—particularly telecommunications can affect actual recovery times,' and concludes that `[r]ecovery-time objectives provide concrete goals to plan for and test against . . . they should not be regarded as hard and fast deadlines that must be met in every emergency situation.' ” 
                        <SU>507</SU>
                        <FTREF/>
                         Several commenters suggested that SCI entities generally be given more discretion to decide when to resume trading following a wide-scale disruption.
                        <SU>508</SU>
                        <FTREF/>
                         Other commenters stated more broadly that the proposed recovery timeframes were too rigid and inconsistent with the Interagency White Paper and the 2003 BCP Policy Statement.
                        <SU>509</SU>
                        <FTREF/>
                         Other commenters similarly noted that it might be in the public interest and consistent with the protection of investors and the maintenance of fair and orderly markets for the markets to remain closed following a wide-scale disruption.
                        <SU>510</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>505</SU>
                             
                            <E T="03">See, e.g.</E>
                            , SIFMA Letter at 3, 13, 18; KCG Letter at 11-12; DTCC Letter at 15; OCC Letter at 9-10; Omgeo Letter at 27-28; Angel Letter at 16-17; Direct Edge Letter at 4-5; ISE Letter at 2-5; Joint SROs Letter at 16-17; FINRA Letter at 36; MSRB Letter at 10; Tellefsen Letter at 6; and Group One Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>506</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 15 (“[P]roposed Rule 1000(b)(l)(i)(E) has made what is currently a target within the 2003 Interagency White Paper that 
                            <PRTPAGE/>
                            clearing and settling services be resumed within 2 hours of a disruption into a requirement that may not be attainable in all circumstances. . . .”); OCC Letter at 9-10 (“While a two-hour recovery time objective is a laudable goal . . . current guidelines remain appropriate to recover and resume clearing and settlement activities within the business day on which the disruption occurs, with the overall aspiration of achieving recovery and resumption within two hours”); and Omgeo Letter at 27-28 (“While Omgeo agrees that SCI entities should be required to rapidly recover from a wide-scale disruption and resume operations to avoid disrupting the critical markets beyond a single business day, it is unreasonable to require these operations to be resumed within two hours.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>507</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 27-28.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>508</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 16-17; Direct Edge Letter at 4-5; ISE Letter at 2; Joint SROs Letter at 16-17; and Group One Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>509</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 13 (noting that the Interagency White Paper recommends that “core clearing and settlement organizations develop the capacity to recover and resume clearing and settlement activities within the business day on which the disruption occurs with the overall goal of achieving recovery and resumption within two hours after an event.” 
                            <E T="03">See also</E>
                             Joint SROs Letter at 17 (noting that the 2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, provides that rapid recovery should not be regarded as a hard and fast deadline that must be met in every emergency situation).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>510</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Angel Letter at 16-17; Direct Edge Letter at 4-5, 9; ISE Letter at 2-5; and Joint SROs Letter at 16-17.
                        </P>
                    </FTNT>
                    <P>
                        In response to comments that the proposed two-hour recovery time frame was too inflexible,
                        <SU>511</SU>
                        <FTREF/>
                         the Commission is eliminating the proposed requirement that an SCI entity must “ensure” next business day resumption of trading and two-hour resumption of clearance and settlement services following a wide-scale disruption. The Commission acknowledges that a hard and fast resumption timeframe may not be achievable in each and every case, given the variety of disruptions that potentially could arise and pose challenges even for well-designed business continuity and disaster recovery. For this reason, the Commission is revising the proposed requirement by replacing it with a requirement that an SCI entity have policies and procedures that include “business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are 
                        <E T="03">reasonably designed to achieve</E>
                         next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption.” Replacement of the phrase “to ensure” with the phrase “reasonably designed to achieve” means that Regulation SCI's enumerated recovery timeframes are concrete goals, consistent with the Interagency White Paper and 2003 BCP Policy Statement.
                        <SU>512</SU>
                        <FTREF/>
                         As such, the rule's specified recovery timeframes are the standards against which the reasonableness of business continuity and disaster recovery (“BC/DR”) plans will be assessed by the Commission and its inspection staff. Moreover, as recovery goals, rather than hard and fast deadlines, the enumerated time frames in the rule will continue to allow for SCI entities to account for the specific facts and circumstances that arise in a given scenario to determine whether it is appropriate to resume a system's operation following a wide-scale disruption.
                    </P>
                    <FTNT>
                        <P>
                            <SU>511</SU>
                             
                            <E T="03">See supra</E>
                             notes 506-510 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>512</SU>
                             
                            <E T="03">See</E>
                             Interagency White Paper, 
                            <E T="03">supra</E>
                             note 504, at 17812-13, and the 2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56658.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Recovery Timeframe Distinctions </HD>
                    <P>
                        In the SCI Proposal, the Commission solicited comment on whether the proposed next business day resumption of trading following a wide-scale disruption and proposed two-hour resumption of clearance and settlement services following a wide-scale disruption were appropriate.
                        <SU>513</SU>
                        <FTREF/>
                         The Commission also solicited comment on whether it should consider revising the proposed next business day resumption requirement for trading to a shorter period for certain entities that play a significant role within the securities markets.
                        <SU>514</SU>
                        <FTREF/>
                         One commenter stated that it agreed with imposing more stringent requirements for resumption of clearance and settlement services than for trading services following a wide-scale disruption.
                        <SU>515</SU>
                        <FTREF/>
                         However, this commenter also urged more broadly that the Commission take into account the criticality of the functions performed by an SCI entity to the maintenance of fair and orderly markets in order to tailor the obligations of the rule more effectively.
                        <SU>516</SU>
                        <FTREF/>
                         According to this commenter, “[n]otification and remediation requirements . . . should be tailored to the time sensitivity of each of the functions performed, not applied uniformly across all activities of an SCI entity.” This commenter identified “highly critical functions” as including the primary listing exchanges, trading of securities on an exclusive basis, securities information processors, clearance and settlement agencies, distribution of unique post-trade transparency information, and real-time market surveillance,” and urged the Commission to “leverage the best practices of the Interagency White Paper, and expand them to include the [highly] critical functions. . . .” 
                        <SU>517</SU>
                        <FTREF/>
                         Other commenters also urged the Commission to consider the criticality of SCI systems functionality and tailor requirements accordingly.
                        <SU>518</SU>
                        <FTREF/>
                         One 
                        <PRTPAGE P="72296"/>
                        commenter noted that the August 2013 Nasdaq SIP outage revealed each of SIAC and Nasdaq (in their roles as plan processors) as a potential “single point of failure” in the national market system, and specifically urged improved backup capabilities for these systems.
                        <SU>519</SU>
                        <FTREF/>
                         Another commenter, in the context of questioning the need for all markets to have geographically diverse backups, acknowledged that specific redundancy might be appropriate in certain areas, such as where an instrument is traded only on one exchange or in the case of a primary market during the open and closing periods of the market.
                        <SU>520</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>513</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18112, question 73.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>514</SU>
                             
                            <E T="03">See id.</E>
                             at 18112, question 76.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>515</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 12-13. Specifically, this commenter noted that the Interagency White Paper, 
                            <E T="03">supra</E>
                             note 504, distinguishes between “core clearing and settlement organizations” and firms that play “significant roles in the financial markets” and recommended that the Commission continue to distinguish between SCI entities that are responsible for the highly critical function of centralized counterparties (
                            <E T="03">e.g.,</E>
                             clearing agencies registered with the Commission) and SCI entities that are not.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>516</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>517</SU>
                             
                            <E T="03">See id.</E>
                             at 4, 18. SIFMA also listed the distribution of unique post-trade transparency information and real-time market surveillance as highly critical functions. While such systems are not specifically identified in the first prong of the definition of critical SCI systems (as are SCI systems that directly support functionality relating to: (1) Clearance and settlement systems of clearing agencies; (2) openings, reopenings, and closings on the primary listing market; (3) trading halts; (4) initial public offerings; (5) the provision of consolidated market data; or (6) exclusively-listed securities), the Commission notes that systems that provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets are considered critical SCI systems under its second prong. 
                            <E T="03">See supra</E>
                             Section IV.A.2.c (discussing the definition of “critical SCI systems”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>518</SU>
                             
                            <E T="03">See, e.g.,</E>
                             KCG Letter at 8, 13-14 (suggesting that proposed item (E) apply only to SCI entities that perform critical, unique functions in the market), and at 5 (stating “when critical services are provided, additional heightened regulatory requirements, as proposed in Regulation SCI, may be appropriate”). 
                            <E T="03">See also</E>
                             UBS Letter at 3 (urging the Commission to take into consideration the difference between “interruptions of activities that hold significant implications for the National Market System” and “low criticality activities [that] are much more manageable and localized in impact 
                            <PRTPAGE/>
                            . . . because market participants are not directly touched or are equipped to quickly route around the problem”). According to this commenter, activities that hold such significant implications would include: “disruption at primary exchange during [the] open/close, [a] problem with protected quote data, [an] outage at listing exchange during [an] IPO, [and] SIP data disruptions.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>519</SU>
                             
                            <E T="03">See</E>
                             Angel Letter 2 at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>520</SU>
                             
                            <E T="03">See</E>
                             FIA PTG Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered these comments and believes they support revising the proposed rule to provide that the two-hour recovery goal specified in the adopted rule, as the standard against which BC/DR plans are to be assessed, should apply not only to “clearance and settlement services,” but more generally to the functions performed by critical SCI systems. Given that the securities markets are dependent upon the reliable operation of critical SCI systems, the Commission believes it is reasonable to distinguish the two-hour and next-business day recovery goals in a manner consistent with other provisions of adopted Regulation SCI: Specifically, to have the shorter recovery goal apply to critical SCI systems, and the longer recovery goal apply to resumption of trading by non-critical SCI systems. The Commission also notes that, because the proposed recovery timeframes are being adopted as concrete goals that the policies and procedures must be reasonably designed to achieve, rather than hard and fast requirements, the adopted approach is somewhat more flexible than that proposed. Accordingly, adopted Rule 1001(a)(2)(v) holds BC/DR plans for critical SCI systems (as defined in Rule 1000) to a higher standard than BC/DR plans for resumption of trading operations more generally. Specifically, an SCI entity responsible for a given critical SCI system will be expected to design BC/DR plans that contemplate resumption of critical SCI system functionality to meet a recovery goal of two hours or less. The Commission believes that this approach is consistent with the broader risk-based approach urged by commenters.
                        <SU>521</SU>
                        <FTREF/>
                         The Commission also believes that its approach to holding critical SCI systems to stricter resiliency standards than other systems is an appropriate measure that responds not only to comments received, but also to recent events highlighting the effects of malfunctions in critical SCI systems.
                        <SU>522</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>521</SU>
                             
                            <E T="03">See supra</E>
                             notes 53-57 and accompanying text (summarizing commenters' recommendations with regard to adopting a risk-based approach generally).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>522</SU>
                             
                            <E T="03">See supra</E>
                             Section II.B (discussing recent systems issues, including a systems problem that resulted in certain exclusively-listed securities being unable to trade for over three hours, and a systems problem affecting the SIP that halted trading in all Nasdaq-listed securities for more than three hours).
                        </P>
                    </FTNT>
                    <P>
                        Two commenters requested clarification on the expectations for resumption of SCI systems that are not related to trading, clearance, or settlement.
                        <SU>523</SU>
                        <FTREF/>
                         In response to this comment, the Commission notes that the adopted definition of SCI systems has been refined from the proposed definition of SCI systems and that all SCI systems could be considered to be “related to” trading. However, systems that directly support market regulation and/or market surveillance will not be held to the resumption goals of Rule 1001(a)(2)(v) (unless they are critical SCI systems) because the Commission believes that the resumption of trading and critical SCI systems could occur following a wide-scale disruption without the immediate availability of market regulation and/or market surveillance systems (unless they are critical SCI systems). However, systems that directly support trading, order routing, and market data would be subject to the next-business day resumption goal, unless they are also critical SCI systems, in which case they would be subject to the two-hour resumption goal. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>523</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 36; and MSRB Letter at 10.
                        </P>
                    </FTNT>
                    <P>
                        One commenter questioned what the expectations are with respect to next-day resumption if an SCI entity loses functionality towards the end of the trading day.
                        <SU>524</SU>
                        <FTREF/>
                         In response to this comment, the Commission notes that neither the next-business day resumption of trading goal nor the two-hour recovery goal for critical SCI systems is dependent on the time of day that the loss of functionality occurs. Consistent with the Interagency White Paper and 2003 BCP Policy Statement, however, the Commission acknowledges that the time of day of a disruption can affect actual recovery times.
                        <SU>525</SU>
                        <FTREF/>
                         The Commission believes it is important, particularly with respect to clearing agencies, that SCI entities endeavor to take all steps necessary to effectuate end of day settlement. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>524</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>525</SU>
                             
                            <E T="03">See</E>
                             Interagency White Paper, 
                            <E T="03">supra</E>
                             note 504, at 17812, and the 2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56658.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Geographic Diversity To Ensure Resilience </HD>
                    <P>
                        Several commenters addressing proposed item (E) expressed concern about the proposed geographic diversity requirement.
                        <SU>526</SU>
                        <FTREF/>
                         Some commenters cited a reluctance on the part of SCI entity members or participants to incur the cost or assume the risk of connecting to a backup site that would only be used infrequently.
                        <SU>527</SU>
                        <FTREF/>
                         In addition, some commenters cited concerns, such as challenges to market makers generating quotes, if a backup site did not have the same low latency as the primary site.
                        <SU>528</SU>
                        <FTREF/>
                         One of these commenter suggested that allowing other fully operational exchanges to fill in and perform the duties of an exchange experiencing an outage would offer the advantages of continued operation on tested systems and the introduction of fewer variables.
                        <SU>529</SU>
                        <FTREF/>
                         Another of these commenters argued that, in many respects, the goal of resilient and redundant markets is already in place due to the existence of multiple competing and interconnected venues, operating as a collective system under Regulation NMS.
                        <SU>530</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>526</SU>
                             
                            <E T="03">See, e.g.,</E>
                             KCG Letter at 13; FIA PTG Letter at 3-4; Group One Letter at 2-3; ISE Letter at 2-5; BIDS Letter at 8; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>527</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 13; FIA PTG Letter at 3-4; and Group One Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>528</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 13; and FIA PTG Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>529</SU>
                             
                            <E T="03">See</E>
                             Group One Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>530</SU>
                             
                            <E T="03">See</E>
                             FIA PTG Letter at 4. 
                            <E T="03">See also</E>
                             Angel 2 Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        One commenter agreed that it is a best business practice for a market to have backup disaster recovery facilities and robust BC/DR plans, but stated that “significant geographic diversity” should not be an absolute requirement,” because a wide-scale disruption in New York or Chicago would make next day resumption difficult, even with a geographically diverse backup.
                        <SU>531</SU>
                        <FTREF/>
                         This commenter noted that the more remote the backup, the more difficult it would be to staff such a facility, and even more so in a surprise disaster, unless the backup was fully staffed at all times.
                        <SU>532</SU>
                        <FTREF/>
                         Several commenters also argued that SCI entities that are ATSs are less critical to market stability, and therefore 
                        <PRTPAGE P="72297"/>
                        should be subject to less stringent geographic diversity and recovery requirements.
                        <SU>533</SU>
                        <FTREF/>
                         One commenter suggested eliminating the reference to “geographic diversity” in favor of requiring “comprehensive business continuity and disaster recovery plans with recovery time objectives of the next business day for trading and two hours for clearance and settlement,” and emphasizing as guidance that geographic diversity of physical facilities would be an expected component of any such plan.
                        <SU>534</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>531</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 2-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>532</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>533</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 8; FIA PTG Letter at 4; ITG Letter at 15; and KCG Letter at 8, 13. These commenters believed that the proposed geographic diversity requirements are burdensome and unnecessary because of the ease with which market participants are able to shift their order flow when there is an issue at one or more markets. In addition, two commenters argued that, because ATSs are subject to FINRA regulations with respect to BC/DR plans, further regulation would be redundant and unnecessary. 
                            <E T="03">See</E>
                             ITG Letter at 15; and OTC Markets Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>534</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered commenters' views on the proposed geographic diversity requirement and continues to believe that geographic diversity of physical facilities is an important component of every SCI entity's BC/DR plan.
                        <SU>535</SU>
                        <FTREF/>
                         The Commission believes that challenges to recovery are increased when a disruption impacts a broad geographic area, and therefore that an SCI entity's arrangements to assure resilience in the event of a wide-scale disruption cannot reliably be achieved without geographic diversity of its BC/DR resources.
                        <SU>536</SU>
                        <FTREF/>
                         The Commission does not agree with commenters who argued that the existence of multiple competing and interconnected venues operating as a collective system under Regulation NMS obviates the need for geographic diversity at the individual SCI entity level.
                        <SU>537</SU>
                        <FTREF/>
                         For example, a wide-scale disruption, such as a natural disaster or man-made attack, could affect a large number of SCI entities, and absent individual SCI entity responsibility for maintaining geographic diversity, there could be a greater likelihood that a critical mass of SCI entities would not be operational, so that the continued maintenance of fair and orderly markets could be impacted. The Commission notes that some of the practical difficulties commenters cited as the basis for objecting to a backup site requirement, such as the cost and operational risk of maintaining a redundant connection to an SCI entity backup facility that would be used infrequently, are concerns raised on behalf of SCI entity members and participants.
                        <SU>538</SU>
                        <FTREF/>
                         In response to commenters who expressed concern regarding the cost for members or participants to co-locate their systems at backup sites to replicate the speed and efficiency of the primary site, the Commission emphasizes that adopted Rule 1001(a)(2)(v) does not require an SCI entity to require members or participants to use the backup facility in the same way it uses the primary facility. Rather, the assessment of the effectiveness of a BC/DR plan that includes geographically diverse backup facilities is whether it is reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>535</SU>
                             The Commission's view is consistent with the 2003 BCP Policy Statement. 
                            <E T="03">See</E>
                             2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56658. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Section VI.C.2.b (discussing the benefits of geographic diversity).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>536</SU>
                             
                            <E T="03">See, e.g.,</E>
                             2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56657 (stating that a critical “lesson learned” from the events of September 11, 2001 is the need for more rigorous business continuity planning in the financial sector to address problems of wider geographic scope and longer duration than those previously addressed).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>537</SU>
                             
                            <E T="03">See supra</E>
                             notes 530 and 533 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>538</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.6 (discussing SCI entity BC/DR testing requirements for members or participants).
                        </P>
                    </FTNT>
                    <P>
                        In response to comments that geographic diversity should be encouraged but not required for all SCI entities, the Commission does not believe that it would be appropriate to eliminate the proposed requirement that SCI entities maintain geographically diverse backup and recovery capabilities (which the Commission understands many SCI entities already have) because, as stated, absent individual SCI entity responsibility for maintaining geographic diversity, there could be a greater likelihood that a critical mass of SCI entities would not be operational following a wide-scale disruption. In response to comment that ATSs are less critical to market stability, and therefore should be subject to less stringent geographic diversity and recovery requirements, the Commission notes that ATSs that do not have critical SCI systems will be subject to less stringent geographic diversity and recovery requirements than SCI entities that do.
                        <SU>539</SU>
                        <FTREF/>
                         However, because the Commission believes that SCI ATSs have the potential to significantly impact investors, the overall market, and the trading of individual securities as a result of an SCI event, the Commission believes that these entities are appropriate for inclusion in the definition of SCI entity and for the application of the geographic diversity requirement.
                        <SU>540</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>539</SU>
                             In addition, in response to commenters who argued that, because ATSs are subject to FINRA regulations with respect to BC/DR plans further regulation would be redundant and unnecessary (
                            <E T="03">see supra</E>
                             note 533), the Commission notes that FINRA Rule 4370 generally requires that a member maintain a written continuity plan identifying procedures relating to an emergency or significant business disruption. Unlike Regulation SCI, however, the FINRA rule does not include the requirement that the business continuity and disaster recovery plans be reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption, nor does it require the functional and performance testing and coordination of industry or sector-testing of such plans, which the Commission believes to be instrumental in achieving the goals of Regulation SCI with respect to SCI entities. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 115.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>540</SU>
                             
                            <E T="03">See supra</E>
                             notes 107-109 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Like the proposed rule, the adopted rule does not specify any particular minimum distance or geographic location that would be necessary to achieve geographic diversity.
                        <SU>541</SU>
                        <FTREF/>
                         However, as stated in the SCI Proposal, the Commission continues to believe that backup sites should not rely on the same infrastructure components, such as for transportation, telecommunications, water supply, and electric power.
                        <SU>542</SU>
                        <FTREF/>
                         The Commission also continues to believe that an SCI entity should have a reasonable degree of flexibility to determine the precise nature and location of its backup site depending on the particular vulnerabilities associated with those sites, and the nature, size, technology, business model, and other aspects of its business.” 
                        <SU>543</SU>
                        <FTREF/>
                         In response to comment that a geographically diverse backup facility is impractical if key personnel do not live sufficiently close to the backup facility, the Commission notes that adopted Regulation SCI does not require an SCI entity to have a geographically diverse backup facility so distant from the primary facility that the SCI entity may not rely primarily on the same labor pool to staff both facilities if it believed it to be appropriate.
                        <SU>544</SU>
                        <FTREF/>
                         Given that the Commission did not propose a specified minimum distance to achieve geographic diversity, the Commission believes that the geographic diversity requirement is reasonable and appropriate for all SCI entities. The 
                        <PRTPAGE P="72298"/>
                        geographic diversity requirement is therefore adopted as proposed. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>541</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18108, n. 182 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>542</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>543</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>544</SU>
                             An SCI entity with critical SCI systems subject to a two-hour recovery goal may, however, find it prudent to establish back-up facilities a significant distance away from their primary sites, or otherwise address the risk that a wide-scale disruption could impact either or both of the sites and their labor pool. 
                            <E T="03">See</E>
                             Interagency White Paper, 
                            <E T="03">supra</E>
                             note 504, at 17813.
                        </P>
                    </FTNT>
                    <P>In sum, the Commission believes that adopted Rule 1001(a)(2)(v), requiring an SCI entity to have business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption, is consistent with, and builds upon, both the Interagency White Paper and the 2003 BCP Policy Statement by applying their principles to SCI entities in today's trading environment, one with a heavy reliance on technological infrastructure. The Commission believes that individual SCI entity resilience is fundamental to achieving the goal of improving U.S. securities market infrastructure resilience.</P>
                    <HD SOURCE="HD3">Robust Standards for Market Data</HD>
                    <P>
                        Proposed item (F), requiring an SCI entity to have standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data, received little comment. One commenter supported the proposed requirement, subject to further clarification about what constitutes market data.
                        <SU>545</SU>
                        <FTREF/>
                         Another commenter believed that this proposed requirement is redundant because SROs and other market participants are already subject to substantial requirements for market data.
                        <SU>546</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>545</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>546</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 19.
                        </P>
                    </FTNT>
                    <P>
                        While consolidated market data is collected and distributed pursuant to a variety of Exchange Act rules and joint industry plans,
                        <SU>547</SU>
                        <FTREF/>
                         the Commission does not believe that existing requirements have the same focus on ensuring the operational capability of the systems for collecting, processing, and disseminating market data. Thus, the Commission believes that this provision, while consistent with existing rules, acts as a complement to such requirements and is not redundant. Further, as explained above, the term “market data” is not intended to include only consolidated market data, but proprietary market data as well and, as such, SCI systems directly supporting proprietary market data or consolidated market data are subject to the requirements of item (F). As stated in the SCI Proposal, the Commission believes that the accurate, timely, and efficient processing of data is important to the proper functioning of the securities markets. The Commission continues to believe that it is important that each SCI entity's market data systems are reasonably designed to maintain market integrity and that the proposed requirement would facilitate that goal.
                        <SU>548</SU>
                        <FTREF/>
                         This element, requiring that an SCI entity's policies and procedures include standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data, is adopted as proposed, as Rule 1001(a)(2)(vi).
                    </P>
                    <FTNT>
                        <P>
                            <SU>547</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Rules 601-604 of Regulation NMS and Rule 301(b)(3) of Regulation ATS. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.A.1.c (discussing definition of plan processor) and Concept Release on Equity Market Structure, 
                            <E T="03">supra</E>
                             note 4, at 3600 (discussing various rules and requirements relating to consolidated market data).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>548</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18108.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Monitoring</HD>
                    <P>
                        The Commission is adopting an additional provision, designated as Rule 1001(a)(2)(vii), that requires an SCI entity's policies and procedures to provide for monitoring of SCI systems, and, for purposes of security standards, indirect SCI systems, to identify potential SCI events. Several commenters argued that Regulation SCI should allow entities to adopt and follow escalation procedures instead of providing that obligations under Regulation SCI are triggered by one employee's awareness of a systems issue.
                        <SU>549</SU>
                        <FTREF/>
                         The Commission is modifying Regulation SCI in three respects in response to these comments: revising the definition of responsible SCI personnel to focus on senior managers; requiring that an SCI entity have policies and procedures to identify, designate, and escalate potential SCI events to responsible SCI personnel; and explicitly requiring policies and procedures for monitoring.
                        <SU>550</SU>
                        <FTREF/>
                         The requirement that an SCI entity have policies and procedures to provide for monitoring of SCI systems and, for purposes of security standards, indirect SCI systems, is added to make explicit that escalation of a systems problem should occur not only if a systems problem is identified by chance, but rather that an SCI entity should have a monitoring process in place so that systems problems are able to be identified as a matter of standard operations and pursuant to parameters reasonably established by the SCI entity. In addition, the Commission believes that the reliability of escalation of potential SCI events to designated responsible SCI personnel for determination as to whether they are, in fact, SCI events is likely to be more effective when it occurs in connection with established procedures for monitoring of SCI systems and indirect SCI systems and pursuant to a process for the communication of systems problems by those who are not responsible SCI personnel to those who are. The Commission notes that several commenters discussed the role that technology staff play in monitoring and identifying potential systems problems and escalating issues up the chain of command to management as well as legal and/or compliance personnel. Although systems monitoring may already be routine in many SCI entities, there are expected benefits of monitoring and thus it is appropriate to require an SCI entity's policies and procedures to provide for monitoring of SCI systems, and, for purposes of security standards, indirect SCI systems, to identify potential SCI events. The Commission believes that monitoring in tandem with escalation to responsible SCI personnel is an appropriate approach to ensuring SCI compliance. As noted, the requirement that an SCI entity have policies and procedures for monitoring provides an SCI entity with flexibility to establish parameters that define the types of systems problems to which technology personnel should be alert, as well as the frequency and duration of monitoring. The Commission also believes this requirement is consistent with a risk-based approach, and that an SCI entity's policies and procedures for monitoring may be tailored to the relative criticality of SCI systems, with critical SCI systems likely to be subject to relatively more rigorous policies and procedures for monitoring than other SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>549</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 12; FINRA Letter at 25-26; Omgeo Letter at 13; FIF Letter at 5; and NYSE Letter at 19-20. 
                            <E T="03">See also</E>
                             infra notes 758-761 and accompanying text (discussing comments on the proposed “becomes aware” standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>550</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.3.a (discussing the Commission's determination to further focus the definition of “responsible SCI personnel”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Policies and Procedures Consistent With “Current SCI Industry Standards”—Rule 1001(a)(4)</HD>
                    <P>
                        Proposed Rule 1000(b)(1)(ii) stated that an SCI entity's policies and procedures would be deemed to be reasonably designed if they are consistent with “current SCI industry standards,” such as those listed on proposed Table A. “Current SCI industry standards” were not limited to those listed on proposed Table A, but 
                        <PRTPAGE P="72299"/>
                        were proposed to be required to be: (A) Comprised of information technology practices that are widely available for free to information technology professionals in the financial sector; and (B) issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization. The rule further stated that “compliance with such current SCI industry standards . . . shall not be the exclusive means to comply with the requirements of paragraph (b)(1).”
                    </P>
                    <P>
                        The goal of proposed Rule 1000(b)(1)(ii) was to provide guidance to SCI entities on policies and procedures that would meet the articulated standard of being “reasonably designed to ensure that their systems have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain their operational capability and promote the maintenance of fair and orderly markets.” The proposal sought to provide this guidance by identifying example information technology publications describing processes, guidelines, frameworks, and/or standards that SCI entities could elect to look to in developing its policies and procedures. Proposed Table A set forth an example of one set of technology publications that the Commission preliminarily believed was an appropriate set of reference documents. The SCI Proposal acknowledged that “current SCI industry standards” would not be limited to the publications identified on proposed Table A. As such, an SCI entity's choice of a current SCI industry standard in a given domain or subcategory thereof could appropriately be different from those contained in the publications identified in proposed Table A.
                        <SU>551</SU>
                        <FTREF/>
                         Many commenters, however, objected to the proposed objective criteria for reference publications, and/or one or more of the specific publications listed on proposed Table A. The Commission has carefully considered commenters' views and is adopting Rule 1000(b)(1)(ii), renumbered as Rule 1001(a)(4), with certain modifications as described below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>551</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18109.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Criteria for Identifying SCI Industry Standards: Comments Received and Commission Response</HD>
                    <P>
                        Some commenters disagreed with the Commission's proposal to require SCI industry standards to be “comprised of information technology practices that are widely available for free to information technology professionals in the financial sector.” Several commenters argued that there were significant disadvantages to requiring that standards be available free of charge.
                        <SU>552</SU>
                        <FTREF/>
                         One of these commenters stated that requiring standards to be available for free “may encourage SCI entities to use standards that may be outdated when more suitable standards may be available and would be more appropriate.” 
                        <SU>553</SU>
                        <FTREF/>
                         Another of these commenters stated that “the cost or lack thereof of a technology standard or standard framework has no bearing on the quality or appropriateness of such standard or framework and bears no significance to the maintenance of fair and orderly markets.” 
                        <SU>554</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>552</SU>
                             
                            <E T="03">See</E>
                             ANSI Letter at 1; DTCC Letter at 15; OCC Letter at 9; Omgeo Letter at 33-34; and X9 Letter at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>553</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>554</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 33 (noting also that the proposed criteria would eliminate appropriate standards such ITIL and ISO 27000).
                        </P>
                    </FTNT>
                    <P>
                        Two standard setting organizations commented regarding the use of consensus standards, citing OMB Circular No. A-119, which directs agencies to use voluntary consensus standards (
                        <E T="03">i.e.,</E>
                         standards developed by professional standards organizations), and urged the Commission to eliminate the requirement that SCI industry standards be “available for free.” 
                        <SU>555</SU>
                        <FTREF/>
                         Another commenter similarly urged that it was important for SCI entities to use publications generated by professional organizations that regularly update their standards and employ open processes for gathering industry input.
                        <SU>556</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>555</SU>
                             
                            <E T="03">See</E>
                             ANSI Letter at 1; and X9 Letter at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>556</SU>
                             
                            <E T="03">See</E>
                             CISQ2 Letter at 6. 
                            <E T="03">See also</E>
                             Angel Letter at 8 (suggesting that the proposed criteria could potentially result in the creation of race-to-the-bottom standards organizations that establish lax standards).
                        </P>
                    </FTNT>
                    <P>
                        The Commission agrees that the cost or lack thereof of a technology standard or standard framework has no bearing on the quality or appropriateness of such standard, and also that SCI entities should be encouraged to use appropriate standards developed by professional organizations that regularly update their standards and employ open processes for gathering industry input. While the Commission did not propose to require that particular standards be used, in response to comment, the Commission is adopting Rule 1001(a)(4) without the criterion in the SCI Proposal that a technology standard be available free of charge. The other criteria are adopted as proposed. Thus, to qualify as an “SCI industry standard,” a publication must be comprised of information technology practices that are widely available to information technology professionals in the financial sector and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization. The Commission believes that this criterion is sufficiently flexible to include technology practices issued by professional organizations, including the professional organizations referenced by commenters.
                        <SU>557</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>557</SU>
                             
                            <E T="03">See infra</E>
                             notes 583-601 and accompanying text. The Commission expresses no view, however, on any particular publication that is not specifically identified in 
                            <E T="03">infra</E>
                             notes 584-601, or standards that remain in development (
                            <E T="03">e.g.,</E>
                             a standard being drafted by AT 9000) (
                            <E T="03">see infra</E>
                             note 601 and accompanying text).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Proposed Table A: Comments Received</HD>
                    <P>
                        The SCI Proposal stated that written policies and procedures that are consistent with the relevant examples of SCI industry standards contained in the publications identified in Table A would be deemed to be “reasonably designed” for purposes of proposed Rule 1000(b)(1).
                        <SU>558</SU>
                        <FTREF/>
                         Proposed Table A listed publications covering nine inspection areas, or “domains,” that Commission staff historically has evaluated under the ARP Inspection Program.
                        <SU>559</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>558</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18109.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>559</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Proposed Table A elicited significant and varied comment. Some commenters objected generally to the Table A framework.
                        <SU>560</SU>
                        <FTREF/>
                         Others objected more specifically to Table A's proposed content,
                        <SU>561</SU>
                        <FTREF/>
                         and some commenters objected to Table A as a premature attempt to establish consensus on SCI industry standards where consensus has not yet emerged.
                        <SU>562</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>560</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter at 8-9; BATS Letter at 6-7; BIDS Letter at 7; Direct Edge Letter at 2; Joint SROs Letter at 4; MSRB Letter at 11-12; and NYSE Letter at 20-21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>561</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter at 8-9; BATS Letter at 6-7; FIF Letter at 3-4; ISE Letter at 11-12; CAST Letter at 10; MSRB Letter at 11-12; DTCC Letter at 15; FINRA Letter at 31; Omgeo Letter at 33; CISQ Letter at 1-2; OCC Letter at 9; Lauer Letter at 5-7; BIDS Letter at 7; and Liquidnet Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>562</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FIF Letter at 3-4; Liquidnet Letter at 3-4; UBS Letter at 7; and ISE Letter at 11-12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">Table A Framework and Process</HD>
                    <P>
                        One group of commenters suggested that, in lieu of the publications identified in Table A, the Commission should characterize policies and procedures as reasonably designed if they comply with “generally accepted standards.” 
                        <SU>563</SU>
                        <FTREF/>
                         Another commenter similarly suggested that the Commission replace the proposed rule's reference to “current SCI industry standards” with 
                        <PRTPAGE P="72300"/>
                        the phrase “generally accepted technology principles,” and delete Table A and the proposed Table A criteria.
                        <SU>564</SU>
                        <FTREF/>
                         These commenters viewed proposed Table A as flawed in concept.
                        <SU>565</SU>
                        <FTREF/>
                         Specifically, one of these commenters expressed concern that the standards set forth in Table A might not keep pace with a constantly evolving technological landscape and that, despite this evolution, Commission staff might take a checklist approach to its review of policies and procedures, which would result in unintended consequences.
                        <SU>566</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>563</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>564</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 20-21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>565</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 4; and NYSE Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>566</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 4. Other commenters similarly expressed concern that SCI entities would closely adhere to the publications listed in Table A (even though the SCI Proposal specified that such adherence would not be the exclusive means to comply with the requirements of proposed Rule 1000(b)(1)), rather than take advantage of the flexibility built into the proposed rule out of concern that if they did not, they would expose themselves to potential regulatory action for failure to comply with Regulation SCI. 
                            <E T="03">See, e.g.,</E>
                             MSRB Letter at 11; Angel Letter at 8; BATS Letter at 6; and NYSE Letter at 20-21.
                        </P>
                    </FTNT>
                    <P>
                        The other commenter stated that it was more common, and more appropriate in any industry that relies heavily on technology, for an entity to review a variety of different standards for frameworks or best practices, and then adopt a derivative of multiple standards, customizing them for the systems at issue.
                        <SU>567</SU>
                        <FTREF/>
                         According to this commenter, SCI entities would be unlikely to comply with all aspects of any particular standard in Table A at any particular time, thereby “obviating its usefulness.” 
                        <SU>568</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>567</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>568</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Other commenters argued that the Table A concept was flawed because Table A would always be on the verge of being outdated. For example, one commenter characterized the proposed Table A publications as “soon-to-be outdated” and stated that it is crucial that SCI entity policies and procedures be “forward-looking” and able to respond to future threats.
                        <SU>569</SU>
                        <FTREF/>
                         Another commenter stated that the proposed process for updating Table A 
                        <SU>570</SU>
                        <FTREF/>
                         would not be sufficiently nimble to assure that SCI entities adhere to the best possible then-current standards, and suggested that the Commission defer to the expertise of the organizations that have established the listed standards and rely on the updates provided by these organizations.
                        <SU>571</SU>
                        <FTREF/>
                         Another commenter stated that any “hard coded” solutions are likely to become obsolete very quickly.
                        <SU>572</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>569</SU>
                             
                            <E T="03">See id.</E>
                              
                            <E T="03">See also</E>
                             ISE Letter at 10 (stating that the standards listed in Table A are not the most current or appropriate standards). 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             notes 577-578 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>570</SU>
                             In the SCI Proposal, the Commission stated that it “preliminarily believes that, following its initial identification of one set of SCI industry standards . . . it would be appropriate for Commission staff, from time to time, to issue notices to update the list of previously identified set of SCI industry standards after receiving appropriate input from interested persons. . . . However, until such time as Commission staff were to update the identified set of SCI industry standards, the then-current set of SCI industry standards would be the [relevant] standards. . . .” Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18111.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>571</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 11-12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>572</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 2.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of these comments, the Commission acknowledges that the proposed framework for identifying and updating publications on Table A may not be sufficiently nimble to assure that its list of publications does not become obsolete as technology and standards change. The Commission agrees that, in an industry that relies heavily on technologies that are constantly evolving, the prescription of hard-coded solutions that may become quickly outdated is not the better approach. However, because several commenters stated that there is currently a lack of consensus on what constitutes generally accepted standards or principles in the securities industry,
                        <SU>573</SU>
                        <FTREF/>
                         the Commission continues to believe that there is value in identifying example publications for SCI entities to consider looking to in establishing policies and procedures that are consistent with “current SCI industry standards.” 
                        <SU>574</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>573</SU>
                             
                            <E T="03">See supra</E>
                             note 633 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>574</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(a)(4), which states: “For purposes of [complying with Rule 1001(a)], such policies and procedures shall be deemed to be reasonably designed if they are consistent with current SCI industry standards, which shall be comprised of information technology practices that are widely available to information technology professionals in the financial sector and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization. Compliance with such current SCI industry standards, however, shall not be the exclusive means to comply with [Rule 1001(a)].”
                        </P>
                    </FTNT>
                    <P>
                        After considering the potential disadvantages of “hard-coding” Table A in a Commission release, and the potential benefits of providing further guidance to SCI entities on the meaning of “current SCI industry standards,” the Commission has determined that, rather than the Commission issuing Table A in this release, Commission staff should issue guidance to assist SCI entities in developing policies and procedures consistent with “current SCI industry standards” in a manner that is consistent with the Commission's response to comments received on proposed Table A, as discussed in this Section IV.B.1.b.iii, and periodically update such guidance as appropriate. The Commission believes that guidance issued by the Commission staff will have the advantage of easier updating and allow for emerging consensus on standards more focused on the securities industry. Thus, concurrent with the Commission's adoption of Regulation SCI, Commission staff is issuing guidance to SCI entities on developing policies and procedures consistent with “current SCI industry standards.” 
                        <SU>575</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>575</SU>
                             Staff Guidance on Current SCI Industry Standards will be available on the Commission's Web site at: 
                            <E T="03">www.sec.gov.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">Table A Publications</HD>
                    <P>
                        Many commenters who did not urge elimination of Table A altogether addressed the content of proposed Table A. Those commenters did not express opposition to the identification of certain inspection areas or domains on proposed Table A, but some commenters identified issues with specific publications listed on Table A.
                        <SU>576</SU>
                        <FTREF/>
                         Specifically, two commenters stated that the NIST publication listed for the Systems Development Methodology domain was outdated.
                        <SU>577</SU>
                        <FTREF/>
                         One of these commenters objected to this publication as reflecting a burdensome staged process to software development that favors the “waterfall methodology” over “agile” software development, which generally uses more “nimble processes” and is more typical in the financial services industry today.
                        <SU>578</SU>
                        <FTREF/>
                         Another commenter noted that this publication had both strengths and weaknesses.
                        <SU>579</SU>
                        <FTREF/>
                         Two commenters objected to the FFIEC's Operations IT Examination Handbook in the capacity planning domain as too generic.
                        <SU>580</SU>
                        <FTREF/>
                         One commenter objected to the inclusion of FFIEC's Audit IT Examination Handbook.
                        <SU>581</SU>
                        <FTREF/>
                         Another commenter stated more broadly that the proposed Table A publications focus too heavily 
                        <PRTPAGE P="72301"/>
                        on firm-level risks and do not take into account the technological and economic stability of the U.S. market as a whole.
                        <SU>582</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>576</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter at 9; BATS Letter at 6-7; FIF Letter at 3-4; and ISE Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>577</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 6; and ISE Letter at 10 (objecting to the inclusion of NIST Security Considerations in the System Development Life Cycle (Special Publication 800-64 Rev. 2) as a suitable “current SCI industry standard” in the systems development methodology domain).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>578</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 6-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>579</SU>
                             
                            <E T="03">See</E>
                             CISQ2 Letter at 4-5 (stating that NIST Special Publication 800-64, Rev. 2 and any derivative standard should “be reviewed and if necessary revised by a panel of industry practitioners and technical experts to balance the requirement for rigor with the amount of practices and documentation specified in the standard”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>580</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 10; and FIF Letter at 3-4 (both described this publication as setting forth a process for conducting capacity planning).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>581</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>582</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        In addition, several commenters suggested specific additions to the proposed list of publications on Table A.
                        <SU>583</SU>
                        <FTREF/>
                         For example, more than one commenter suggested the following standards as appropriate for inclusion on Table A: COBIT/ISACA; 
                        <SU>584</SU>
                        <FTREF/>
                         ISO-27000; 
                        <SU>585</SU>
                        <FTREF/>
                         ISO 25000; 
                        <SU>586</SU>
                        <FTREF/>
                         and NFPA-1600.
                        <SU>587</SU>
                        <FTREF/>
                         Other standards or publications mentioned by commenters as useful, particularly in the area of software quality or software security, include the CISQ Software Quality Specification,
                        <SU>588</SU>
                        <FTREF/>
                         the Capability Maturity Model Integration (CMMI) framework, 
                        <SU>589</SU>
                        <FTREF/>
                         “SANS 20 Critical Security Controls,” 
                        <SU>590</SU>
                        <FTREF/>
                         “CWE/SANS Top 25 Most Dangerous Software Errors,” 
                        <SU>591</SU>
                        <FTREF/>
                         the Open Source Security Testing Methodology Manual (OSSTMM),
                        <SU>592</SU>
                        <FTREF/>
                         the BITS Financial Services Roundtable Software Assurance Framework (January 2012),
                        <SU>593</SU>
                        <FTREF/>
                         the “Build Security In Maturity Model” (BSTMM),
                        <SU>594</SU>
                        <FTREF/>
                         Microsoft's SDL,
                        <SU>595</SU>
                        <FTREF/>
                         and resources for defining secure software development practices from organizations such as OWASP, WASC and SAFECode,
                        <SU>596</SU>
                        <FTREF/>
                         and publications issued by Scrum Alliance,
                        <SU>597</SU>
                        <FTREF/>
                         the Association for Software Testing (AST),
                        <SU>598</SU>
                        <FTREF/>
                         the Institute of Electrical and Electronics Engineers (IEEE),
                        <SU>599</SU>
                        <FTREF/>
                         and the Association for Computing Machinery (ACM).
                        <SU>600</SU>
                        <FTREF/>
                         In addition, one commenter suggested a standard currently being drafted by AT 9000, a working group which focuses on trading safety, regulatory requirements, and achieving efficiency and effectiveness of systems involved in automated trading.
                        <SU>601</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>583</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CAST Letter; ISE Letter; MSRB Letter; DTCC Letter; FINRA Letter; Omgeo Letter; CISQ2 Letter; OCC Letter; BIDS Letter; Liquidnet Letter; and X9 Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>584</SU>
                             
                            <E T="03">See</E>
                             CAST Letter at 10; ISE Letter at 11; and MSRB Letter at 11. COBIT (formerly known as Control Objectives for Information and related Technology) is an enterprise information technology governance framework developed by ISACA (formerly known as the Information Systems Audit and Control Association).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>585</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 15; ISE Letter at 11; FINRA Letter at 31; and Omgeo Letter at 33. FINRA recommended ISO-27000 series because it provides “greater specificity” and may be “less burdensome” than the standards identified in proposed Table A. ISE and DTCC recommended ISO 27000 specifically for application controls, information security and networking, and physical security controls. Omgeo stated more broadly that it models aspects of its program on widely accepted international standards and frameworks such as ITIL and ISO 27000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>586</SU>
                             
                            <E T="03">See</E>
                             CAST Letter and CISQ2 Letter. CAST suggested supplementing the SCI industry standards with standards that address development, as well as standards that pertain to structural software quality, such as ISO 25010 and CISQ Software Quality Specification. 
                            <E T="03">See</E>
                             CAST Letter at 5. CISQ2 agreed that standards addressing structural software quality are needed and suggested including CISQ Specification for Automated Quality Characteristic Measures: CISQ-TR-2012-01 in Table A. CISQ also pointed to the Capability Maturity Model Integration (CMMI) as another potential option, noting that it was the most widely adopted process standard for rigorous software development practices. 
                            <E T="03">See</E>
                             CISQ2 Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>587</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 9; and ISE Letter at 11. ISE also specifically recommended BS 25999 as an alternative contingency planning standard.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>588</SU>
                             
                            <E T="03">See</E>
                             CAST Letter at 5; and CISQ Letter at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>589</SU>
                             
                            <E T="03">See</E>
                             CAST Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>590</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>591</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>592</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>593</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>594</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>595</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>596</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>597</SU>
                             
                            <E T="03">See</E>
                             Liquidnet Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>598</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>599</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>600</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>601</SU>
                             
                            <E T="03">See</E>
                             X9 Letter at 2.
                        </P>
                    </FTNT>
                    <P>
                        A few commenters opposed referencing standards in Regulation SCI at the outset and instead supported establishing a process that they believed would, after a certain period of time, yield a coherent set of standards.
                        <SU>602</SU>
                        <FTREF/>
                         One of these commenters urged that best practices should evolve from the Commission's experience with the annual SCI review process and experience with the ARP program, because such best practices will be specific to the securities industry and reflect the actual practices of SCI entities.
                        <SU>603</SU>
                        <FTREF/>
                         Finally, several commenters suggested that the Commission establish a working group to develop SCI industry standards.
                        <SU>604</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>602</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FIF Letter at 4, 6; Liquidnet Letter at 3; UBS Letter at 7; and ISE Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>603</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 4, 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>604</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Liquidnet Letter at 3 (urging that a working group consisting of regulators, industry participants (from exchanges, ATSs and broker-dealers) and security and controls experts be established to develop a security and controls framework for the industry). 
                            <E T="03">See also</E>
                             UBS Letter at 7 (urging the Commission to convene a “cross-industry, multi-disciplinary Working Group” to be responsible for developing recommendations for appropriate standards); and ISE Letter at 11 (recommending that the Commission authorize SCI entities to establish a standards committee to review and recommend specific sets of standards). 
                            <E T="03">See also</E>
                             CISQ Letter at 2, 6 (supporting the Table A approach but also seeing value in tailoring existing standards from professional organizations into an industry-specific set of standards for SCI entities).
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered these comments, and continues to believe that there is value in identifying publications for SCI entities to consider looking to in establishing reasonable policies and procedures, because doing so will provide guidance on how an SCI entity may comply with adopted Rule 1001(a). The Commission therefore believes that issuance of staff guidance that does this, as discussed above, will be useful for SCI entities. However, after careful consideration of commenters' views regarding the publications on proposed Table A, the Commission believes it is useful to characterize how such staff guidance should be used by SCI entities. In particular, the Commission understands that some commenters who objected to the proposed Table A concept and/or the proposed Table A content were more broadly taking issue with the characterization of certain of the documents on proposed Table A, such as the NIST 800-53 document, as a “standard,” rather than a “framework” or a “process.” 
                        <SU>605</SU>
                        <FTREF/>
                         The Commission believes that many commenters implicitly were questioning why certain identified technology frameworks (such as NIST 800-53) were being labeled as, and thereby elevated to, an example of “current SCI industry standards” when many SCI entities were already following ISO 27000, COBIT, or other technology standards that they viewed as more specific, relevant, and/or cost effective than the NIST frameworks identified on proposed Table A.
                        <SU>606</SU>
                        <FTREF/>
                         In response to these comments, the Commission believes it is appropriate that the staff's guidance be characterized as listing examples of publications describing processes, guidelines, frameworks, or standards for an SCI entity to consider looking to in developing reasonable policies and procedures, rather than strictly as listing industry standards. Thus, the Commission believes it is appropriate if Commission staff were to list publications that provide guidance to SCI entities on suitable processes for developing, documenting, and implementing policies and procedures for their SCI systems (and indirect SCI systems, as applicable), taking into account the criticality of each such system.
                    </P>
                    <FTNT>
                        <P>
                            <SU>605</SU>
                             The Commission also notes that this point was made by a member of the third panel at the Cybersecurity Roundtable, 
                            <E T="03">supra</E>
                             note 39. 
                            <E T="03">See also</E>
                             FINRA Letter at 31.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>606</SU>
                             
                            <E T="03">See supra</E>
                             notes 577-601 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the publications commenters suggested for inclusion on proposed Table A, the Commission is not disputing the value of such standards, and believes that each, when considered with respect to a particular system at an SCI entity, may contain appropriate standards for the SCI entity to use as, or incorporate within, its 
                        <PRTPAGE P="72302"/>
                        policies and procedures.
                        <SU>607</SU>
                        <FTREF/>
                         The Commission notes that the guidance is intended to be used as a baseline from which the staff may work with SCI entities and other interested market participants to build consensus on industry-specific standards, as discussed more fully below. Further, the Commission believes that the goal of providing general and flexible guidance to SCI entities does not necessitate providing a lengthy list of all the publications that meet the criteria set forth in Rule 1001(a)(4).
                        <SU>608</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>607</SU>
                             
                            <E T="03">See supra</E>
                             notes 577-601 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>608</SU>
                             
                            <E T="03">See supra</E>
                             note 557 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission continues to believe that it may be appropriate for an SCI entity to choose to adhere to a standard or guideline in a given domain or subcategory thereof that is different from those contained in the staff guidance, and emphasizes that nothing that the staff may include in its guidance precludes an SCI entity from adhering to standards such as ISO 27000, COBIT, or others referenced by commenters to the extent they result in policies and procedures that comply with the requirements of Rule 1001(a).
                        <SU>609</SU>
                        <FTREF/>
                         Moreover, adopted Rule 1001(a)(4) explicitly provides that compliance with current SCI industry standards (
                        <E T="03">i.e.,</E>
                         including those publications identified by the Commission staff) is not the exclusive method of compliance with Rule 1001(a). Accordingly, an SCI entity's determination not to adhere to some or all of the publications included in the staff guidance in developing its policies and procedures does not necessarily mean that its policies and procedures will be deficient or unreasonable for purposes of Rule 1001(a)(1). Importantly, the publications listed by Commission staff should be understood to provide guidance to SCI entities on selecting appropriate controls for applicable systems, as well as suitable processes for developing, documenting, and implementing policies and procedures for their SCI systems (and indirect SCI systems, as applicable), taking into account the criticality of each such system. Thus, for example, the Commission believes it would be reasonable for the most robust controls to be selected and implemented for “critical SCI systems,” as compared to other types of SCI systems, and the Commission believes it would be appropriate that the staff's guidance include publications that require more rigorous controls for higher-risk systems. The staff guidance is not intended to be static, however. As the Commission staff works with SCI entities, as well as members of the securities industry, technology experts, and interested members of the public, and as technology standards continue to evolve, the Commission anticipates that the Commission staff will periodically update the staff guidance as appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>609</SU>
                             Likewise, such guidance would not preclude an SCI entity from adopting a derivative of multiple standards, and/or customizing one or more standards for the particular system at issue, as one commenter suggested. 
                            <E T="03">See supra</E>
                             note 567 and accompanying text. In assessing whether an SCI entity's use of such an approach in designing its policies and policies and procedures would be “deemed” to be reasonably designed, the Commission's inquiry would be into whether its policies and procedures were consistent with standards meeting the criteria in adopted Rule 1001(a)(4).
                        </P>
                    </FTNT>
                    <P>
                        Another way in which the publications identified by Commission staff should provide guidance to SCI entities is by providing transparency on how the staff will, at least initially, prepare for and conduct inspections relating to Regulation SCI. As discussed in the SCI Proposal and above,
                        <SU>610</SU>
                        <FTREF/>
                         for over two decades, ARP staff has conducted inspections of ARP entity systems, with a goal of evaluating whether an ARP entity's controls over its information technology resources in each domain are consistent with ARP and industry guidelines,
                        <SU>611</SU>
                        <FTREF/>
                         as identified by ARP staff from a variety of information technology publications that ARP staff believed were appropriate for securities market participants.
                        <SU>612</SU>
                        <FTREF/>
                         With the adoption of Regulation SCI, and the resultant transition away from the voluntary ARP Inspection Program to an inspection program under Regulation SCI, the Commission believes it is helpful to establish consistency in its approach to examining SCI entities for compliance with Regulation SCI. Importantly, establishing consistency does not mean that the Commission will take a one-size-fits-all or checklist approach. Because the publications identified by Commission staff should be general and flexible enough to be compatible with many widely-recognized technology standards that SCI entities currently use, the Commission believes the publications identified by Commission staff should provide guidance for an SCI entity to self-assess whether its policies and procedures comply with Rules 1001(a)(1)-(2). Moreover, because use of the publications identified by Commission staff is not mandatory, the staff guidance should not be regarded as establishing a checklist, the use of which could result in unintended consequences, but rather a basis for considering how an SCI entity's selected standards relate to the guidance provided by Commission staff and whether they are appropriate standards for use by that particular SCI entity for a given system.
                    </P>
                    <FTNT>
                        <P>
                            <SU>610</SU>
                             
                            <E T="03">See supra</E>
                             Section II.A.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>611</SU>
                             As stated in the SCI Proposal, the domains covered during an ARP inspection depend in part upon whether the inspection is a regular inspection or a “for-cause” inspection. Typically, however, to make the most efficient use of resources, a single ARP inspection will cover fewer than nine domains. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18086.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>612</SU>
                             
                            <E T="03">See id.</E>
                             and 
                            <E T="03">supra</E>
                             Section II.A (discussing the ARP Inspection Program).
                        </P>
                    </FTNT>
                    <P>The Commission believes that it would be appropriate that the publications initially identified by Commission staff at a minimum include the nine inspection areas, or “domains,” that the Commission identified on Table A in the SCI Proposal and that are relevant to SCI entities' systems capacity, integrity, resiliency, availability, and security, namely: Application controls; capacity planning; computer operations and production environment controls; contingency planning; information security and networking; audit; outsourcing; physical security; and systems development methodology.</P>
                    <P>The Commission believes it would be appropriate that each publication identified by Commission staff be identified with specificity and include the particular publication's date, volume number, and/or publication number, as the case may be. Thus, for SCI entities that establish or self-assess their policies and procedures in reliance on the guidance provided by the publications identified by Commission staff, the Commission believes that the publications should be the relevant publications until such time as the list is updated by Commission staff. Of course, SCI entities may elect to use publications describing processes, guidelines, frameworks, and/or standards other than those identified by Commission staff to develop policies and procedures that satisfy the requirements of Rules 1001(a)(1)-(2).</P>
                    <P>
                        As stated in the SCI Proposal, however, the Commission continues to believe that the development of securities-industry specific standards is a worthy goal. Although some commenters urged the Commission not to adopt Table A at the outset, and instead establish a process to achieve that end,
                        <SU>613</SU>
                        <FTREF/>
                         the Commission believes that the better approach is for Commission staff to provide examples of publications through its guidance that form a baseline and remain open to emerging consensus on industry-specific standards. In response to the 
                        <PRTPAGE P="72303"/>
                        commenter that suggested that the Commission leverage the annual SCI review process and the SCI inspection process to yield a coherent set of industry-specific standards that could be referenced on Table A, the Commission believes that such an approach could serve as an appropriate input into the future development of such standards.
                        <SU>614</SU>
                        <FTREF/>
                         In response to the commenter who stated that the proposed Table A publications do not take into account the technological and economic stability of the U.S. market as a whole,
                        <SU>615</SU>
                        <FTREF/>
                         the Commission notes that the technological stability of individual SCI entities, in tandem with a heightened focus on critical SCI systems, are necessary prerequisites to achieving such market-wide goals. Accordingly, the Commission believes that the publications identified by Commission staff today should serve as an appropriate 
                        <E T="03">initial</E>
                         set of publications, processes, guidelines, frameworks, and standards for SCI entities to use as guidance to develop their policies and procedures under Rule 1001(a). With this guidance as a starting point, the Commission expects that the Commission staff will seek to work with members of the securities industry, technology experts, and interested members of the public towards developing standards relating to systems capacity, integrity, resiliency, availability, and security appropriately tailored for the securities industry and SCI entities, and periodically issue staff guidance that updates the guidance with such standards.
                    </P>
                    <FTNT>
                        <P>
                            <SU>613</SU>
                             
                            <E T="03">See supra</E>
                             note 604 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>614</SU>
                             
                            <E T="03">See supra</E>
                             note 602 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>615</SU>
                             
                            <E T="03">See supra</E>
                             note 582 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Policies and Procedures To Achieve Systems Compliance—Rule 1001(b)</HD>
                    <P>Proposed Rule 1000(b)(2)(i) would have required each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in the manner intended, including in a manner that complies with the federal securities laws and rules and regulations thereunder and the SCI entity's rules and governing documents, as applicable.</P>
                    <P>Proposed Rule 1000(b)(2) also would have included safe harbors for an SCI entity and its employees. Specifically, proposed Rule 1000(b)(2)(ii) provided that an SCI entity would be deemed not to have violated proposed Rule 1000(b)(2)(i) if the SCI entity: (1) Established policies and procedures reasonably designed to provide for specified elements; (2) established and maintained a system for applying such policies and procedures which would reasonably be expected to prevent and detect, insofar as practicable, any violations of such policies and procedures by the SCI entity or any person employed by the SCI entity; and (3) reasonably discharged the duties and obligations incumbent upon it by such policies and procedures, and was without reasonable cause to believe that such policies and procedures were not being complied with in any material respect. The safe harbor for SCI entities in proposed Rule 1000(b)(2)(ii) specified that the SCI entity's policies and procedures must be reasonably designed to provide for: (1) Testing of all SCI systems and any changes to such systems prior to implementation; (2) periodic testing of all SCI systems and any changes to such systems after their implementation; (3) a system of internal controls over changes to SCI systems; (4) ongoing monitoring of the functionality of SCI systems to detect whether they are operating in the manner intended; (5) assessments of SCI systems compliance performed by personnel familiar with applicable federal securities laws and rules and regulations thereunder and the SCI entity's rules and governing documents, as applicable; and (6) review by regulatory personnel of SCI systems design, changes, testing, and controls to prevent, detect, and address actions that do not comply with applicable federal securities laws and rules and regulations thereunder and the SCI entity's rules and governing documents, as applicable.</P>
                    <P>In addition, proposed Rule 1000(b)(2)(iii) set forth a safe harbor for individuals. It provided that a person employed by an SCI entity would be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by any other person of proposed Rule 1000(b)(2)(i) if the person employed by the SCI entity has reasonably discharged the duties and obligations incumbent upon such person by the policies and procedures, and was without reasonable cause to believe that such policies and procedures were not being complied with in any material respect.</P>
                    <P>After careful consideration of the comments, proposed Rule 1000(b)(2) is adopted as Rule 1001(b) with modifications, as discussed below.</P>
                    <HD SOURCE="HD3">a. Reasonable Policies and Procedures To Achieve Systems Compliance</HD>
                    <P>
                        The Commission received significant comment on its proposal to require that SCI entities establish, maintain, and enforce written policies and procedures reasonably designed to ensure systems compliance. Some commenters supported the broad goals of a policies and procedures requirement to help ensure that SCI systems operate as intended.
                        <SU>616</SU>
                        <FTREF/>
                         Other commenters questioned whether any set of policies and procedures could guarantee perfect operational compliance.
                        <SU>617</SU>
                        <FTREF/>
                         One commenter emphasized that no set of policies and procedures can guarantee 100% operational compliance and that, historically, the Commission has allowed entities to use a reasonableness standard so that policies and procedures are required to be reasonably designed to promote compliance, and the same should be used for the underlying predicate requirement in Regulation SCI.
                        <SU>618</SU>
                        <FTREF/>
                         A few commenters expressed concern that, in instances where an SCI entity's policies and procedures failed to prevent SCI events, the Commission might use such failures as the basis for an enforcement action, charging that the policies and procedures were not reasonable.
                        <SU>619</SU>
                        <FTREF/>
                         One commenter believed that compliance with Regulation SCI should be measured against a firm's adherence to its own set of policies and procedures that are in keeping with SCI system objectives, and such policies should be reviewed and updated as part of the annual SCI review process.
                        <SU>620</SU>
                        <FTREF/>
                         Another commenter requested that the Commission more clearly distinguish between liability under Regulation SCI and liability for SCI events, stating that compliance with Regulation SCI and compliance with other federal securities laws and rules must remain distinct.
                        <SU>621</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>616</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 12-13; SIFMA Letter at 12; and MFA Letter at 3. Two of these commenters believed that SCI entities that perform critical market functions should be required to have more stringent policies and procedures than less critical SCI entities. 
                            <E T="03">See</E>
                             SIFMA Letter at 12; and MFA Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>617</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 14. 
                            <E T="03">See also</E>
                             BATS Letter at 3-4, 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>618</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>619</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 3-4; Angel Letter at 4; and FSR Letter at 5. One of these commenters considered this possibility as, in effect, imposing a strict liability standard with respect to systems issues, and was concerned that the proposed approach would result in “finger-pointing” and constant enforcement actions for immaterial violations that desensitize people to actual material violations. 
                            <E T="03">See</E>
                             FSR Letter at 3-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>620</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>621</SU>
                             
                            <E T="03">See</E>
                             FSR Letter at 6.
                        </P>
                    </FTNT>
                    <P>
                        Whereas adopted Rule 1001(a) 
                        <SU>622</SU>
                        <FTREF/>
                         concerns the robustness of the SCI entity's systems, adopted Rule 1001(b) 
                        <SU>623</SU>
                        <FTREF/>
                         concerns the operational compliance of an SCI entity's SCI systems with the Exchange Act, the rules and regulations thereunder, and 
                        <PRTPAGE P="72304"/>
                        the SCI entity's governing documents. The Commission continues to believe, as stated in the SCI Proposal, that a rule requiring SCI entities to establish, maintain, and enforce policies and procedures reasonably designed to ensure operational compliance will help to: ensure that SCI SROs comply with Section 19(b)(1) of the Exchange Act; 
                        <SU>624</SU>
                        <FTREF/>
                         reinforce existing SRO rule filing processes to assist market participants and the public in understanding how the SCI systems of SCI SROs are intended to operate; and assist SCI SROs in meeting their obligations to file plan amendments to SCI Plans under Rule 608 of Regulation NMS.
                        <SU>625</SU>
                        <FTREF/>
                         It will similarly help other SCI entities (
                        <E T="03">i.e.,</E>
                         SCI ATSs, plan processors, and exempt clearing agencies subject to ARP) to achieve operational compliance with the Exchange Act, the rules and regulations thereunder, and their governing documents.
                    </P>
                    <FTNT>
                        <P>
                            <SU>622</SU>
                             Adopted Rule 1001(a) was proposed as Rule 1000(b)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>623</SU>
                             Adopted Rule 1001(b) was proposed as Rule 1000(b)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>624</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 78s(b)(1) (requiring each SRO to file with the Commission copies of any proposed rule or any proposed change in, addition to, or deletion from the rules of the SRO).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>625</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18115.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that Rule 1001(b) is intended to help prevent the occurrence of systems compliance issues at SCI entities. The Commission discussed in Section IV.A.3.b the rationale for further focusing the definition of systems compliance issue (
                        <E T="03">i.e.,</E>
                         replacing the reference to operating “in the manner intended, including in a manner that complies with the federal securities laws” with a reference to operating “in a manner that complies with the Act”). To provide consistency between the definition of systems compliance issue and the requirement for policies and procedures to ensure systems compliance, the Commission is similarly revising Rule 1001(b)(1) to require each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate “in a manner that complies with the Act” and the rules and regulations thereunder and the entity's rules and governing documents, as applicable.
                    </P>
                    <P>
                        As noted above, some commenters expressed concern that an SCI entity would be found to be in violation of Rule 1001(b) if an SCI event occurs.
                        <SU>626</SU>
                        <FTREF/>
                         Consistent with the discussion above regarding Rule 1001(a), the Commission emphasizes that the occurrence of a systems compliance issue at an SCI entity does not necessarily mean that the SCI entity has violated Rule 1001(b) of Regulation SCI. As stated in the SCI Proposal, an SCI entity will not be deemed to be in violation of Rule 1001(b) solely because it experienced a systems compliance issue.
                        <SU>627</SU>
                        <FTREF/>
                         The Commission also notes that Rule 1001(b) requires systems compliance policies and procedures to be 
                        <E T="03">reasonably designed.</E>
                        <SU>628</SU>
                        <FTREF/>
                         The Commission acknowledges that reasonable policies and procedures will not ensure the elimination of all systems issues, including systems compliance issues. While a systems compliance issue may be probative as to the reasonableness of an SCI entity's policies and procedures, it is not determinative. Further, the occurrence of a systems compliance issue also does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>626</SU>
                             
                            <E T="03">See supra</E>
                             notes 617-620 and accompanying text. One of these commenters believed that compliance with Regulation SCI should be measured against a firm's adherence to its own set of policies and procedures that are in keeping with SCI systems objectives. 
                            <E T="03">See supra</E>
                             note 620 and accompanying text. The Commission understands this commenter to be expressing the same concern as other commenters that an SCI entity would be found to be in violation of Rule 1001(b) if an SCI event occurs. This commenter also noted that policies and procedures should be reviewed and updated as part of the annual SCI review process. 
                            <E T="03">See supra</E>
                             note 620 and accompanying text. The comment regarding reviews and updates of policies and procedures is addressed below. 
                            <E T="03">See infra</E>
                             note 673 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>627</SU>
                             Also, as noted in the SCI Proposal, an employee of an SCI entity would not be deemed to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by any other person of Rule 1001(b) merely because the SCI entity at which the employee worked experienced a systems compliance issue. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18116.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>628</SU>
                             As stated above, one commenter noted that no set of policies and procedures can guarantee 100% operational compliance and that historically, the Commission has allowed entities to use a reasonableness standard so that policies and procedures are required to be reasonably designed to promote compliance, and the same approach should be used for Regulation SCI. 
                            <E T="03">See supra</E>
                             note 618 and accompanying text. The Commission agrees with this commenter that reasonably designed policies and procedures might not completely eliminate the occurrence of systems compliance issues. Also, adopted Rule 1001(b) is consistent with this commenter's suggestion, because it requires policies and procedures that are “reasonably designed” to ensure systems compliance.
                        </P>
                    </FTNT>
                    <P>
                        In response to one commenter's request that the Commission more clearly distinguish between liability under Regulation SCI and liability for SCI events,
                        <SU>629</SU>
                        <FTREF/>
                         the Commission notes that liability under Regulation SCI is separate and distinct from liability for other violations that may arise from the underlying SCI event. In particular, whether an SCI entity violated Regulation SCI does not affect the determination of whether the underlying SCI event also caused the SCI entity to violate other laws or rules, and compliance with Regulation SCI is not a safe harbor or other shield from liability under other laws or rules. Thus, even if the occurrence of an SCI event does not cause an SCI entity to be found to be in violation of Regulation SCI, the SCI entity may still be liable under other Commission rules or regulations, the Exchange Act, or SRO rules for the underlying SCI event.
                        <SU>630</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>629</SU>
                             
                            <E T="03">See supra</E>
                             note 621 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>630</SU>
                             For example, it is possible for an SCI SRO to have established, maintained, and enforced reasonably designed systems compliance policies and procedures consistent with the requirements of Rule 1001(b) of Regulation SCI, but still potentially violate Section 19(g) of the Exchange Act if the operation of its systems is inconsistent with its own rules. 
                            <E T="03">See</E>
                             15 U.S.C. 78s(g) (requiring every SRO to comply with the Exchange Act, the rules and regulations thereunder, and its own rules).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Proposed Safe Harbor for SCI Entities</HD>
                    <HD SOURCE="HD3">i. Comments Received</HD>
                    <P>
                        In the SCI Proposal, the Commission solicited comment on the proposed approach to include safe harbor provisions in proposed Rule 1000(b)(2) and specifically asked whether commenters agreed with the proposed inclusion of safe harbors.
                        <SU>631</SU>
                        <FTREF/>
                         Many commenters specifically addressed the safe harbors in proposed Rule 1000(b)(2). Two commenters urged elimination of the proposed safe harbors.
                        <SU>632</SU>
                        <FTREF/>
                         One of these commenters stated that the safe harbors were framed so generally that they would be easy to invoke.
                        <SU>633</SU>
                        <FTREF/>
                         This commenter also stated that inclusion of a safe harbor provision for compliance standards would unnecessarily and severely limit the Commission's ability to deter violations through meaningful enforcement actions.
                        <SU>634</SU>
                        <FTREF/>
                         The other commenter stated that, if a safe harbor is adopted, the Commission should be as specific as possible in establishing how to qualify for the safe harbor, and recommended that Commission guidance ensure that SCI entities are actively building and improving upon safety systems and not simply checking boxes and doing the minimal amount necessary to ensure compliance.
                        <SU>635</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>631</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18117, question 104.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>632</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 5-6; and Lauer Letter at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>633</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>634</SU>
                             
                            <E T="03">See id.</E>
                             at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>635</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        In contrast, several commenters supported the inclusion of a safe harbor in proposed Rule 1000(b)(2) in theory, but objected to the proposed 
                        <PRTPAGE P="72305"/>
                        approach.
                        <SU>636</SU>
                        <FTREF/>
                         Some commenters stated that the proposed safe harbor, with its prescriptive requirements, would evolve into the 
                        <E T="03">de facto</E>
                         rule itself as SCI entities decide to adhere to the requirements of the safe harbor rather than risk a potential enforcement action stemming from an SCI event.
                        <SU>637</SU>
                        <FTREF/>
                         One of these commenters noted that the safe harbor merely further defined the elements that the policies and procedures must have by providing a list of points that reasonably designed policies and procedures must cover.
                        <SU>638</SU>
                        <FTREF/>
                         This commenter believed that including a requirement for reasonably designed policies and procedures and providing a safe harbor when those policies and procedures are reasonably designed is inherently circular, and expressed concern about liability under Regulation SCI whenever there is a systems or technology malfunction or error.
                        <SU>639</SU>
                        <FTREF/>
                         This commenter also compared the proposed SCI entity safe harbor to other rules, stating that the other rules requiring policies and procedures recognize the need for those policies and procedures to be reasonably designed in light of the manner in which business is conducted.
                        <SU>640</SU>
                        <FTREF/>
                         This commenter further noted that, if the Commission intends that all SCI entities conform to the standards articulated in the safe harbor, the Commission should set them forth as express provisions of the rule, although this commenter believed that such an approach would be misguided because it would create strictures that impose protocols that may not be suitable for certain market participants.
                        <SU>641</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>636</SU>
                             
                            <E T="03">See, e.g.</E>
                            , Angel Letter; Direct Edge Letter; FSR Letter; ITG Letter; MSRB Letter; NYSE Letter; OCC Letter; OTC Markets Letter; and Joint SROs Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>637</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 14 (stating that “[t]he safe harbor contains so many requirements that it operates as a rule by itself”); and FSR Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>638</SU>
                             
                            <E T="03">See</E>
                             FSR Letter at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>639</SU>
                             
                            <E T="03">See id.</E>
                             at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>640</SU>
                             
                            <E T="03">See</E>
                             FSR Letter at 8-9 (expressing concern that the safe harbor will become the sole yardstick by which conduct is measured and, even if the safe harbor were non-exclusive, it could become the 
                            <E T="03">de facto</E>
                             standard to the exclusion of other, legitimate approaches).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>641</SU>
                             
                            <E T="03">See</E>
                             FSR Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        Several other commenters expressed concern that the proposed safe harbors were unclear.
                        <SU>642</SU>
                        <FTREF/>
                         One group of commenters noted that the provisions in the proposed safe harbors were vague, subjective, and merely duplicate elements that would result from a logical interpretation of Rule 1000(b)(1),
                        <SU>643</SU>
                        <FTREF/>
                         which these commenters believed offered no safe harbor protection at all.
                        <SU>644</SU>
                        <FTREF/>
                         Another commenter stated that the use of a reasonableness standard with respect to the design of systems and the discharge of duties under an SCI entity's policies and procedures would mean that an SCI entity and its employees would never know with certainty whether they met the terms of the safe harbor.
                        <SU>645</SU>
                        <FTREF/>
                         Another commenter similarly stated that SCI entities cannot know if they have complied with the safe harbor unless more guidance is provided on the concept of “reasonable policies and procedures” and the Commission explains what constitutes adequate testing, monitoring, assessments, and review for each system.
                        <SU>646</SU>
                        <FTREF/>
                         One commenter agreed with the need for a safe harbor but stated that the proposed safe harbor is not sufficiently robust because it contains “vague and extensive requirements that are overly subjective” and the Commission therefore would be “likely to review an SCI entity's interpretation of the safe harbor in the event of a systems issue with the benefit of 20/20 hindsight.” 
                        <SU>647</SU>
                        <FTREF/>
                         This commenter expressed concern that the occurrence of a significant systems event would mean that an exchange did not have reasonable policies and procedures and would be outside the terms of the proposed safe harbor.
                        <SU>648</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>642</SU>
                             
                            <E T="03">See, e.g.</E>
                            , FSR Letter; OCC Letter; and OTC Markets Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>643</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 13 (stating that the proposed safe harbor should provide a more objective and transparent approach, and provide SCI entities a clear, affirmative defense from allegations of having violated Regulation SCI).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>644</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>645</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 11. This commenter also questioned the value of the safe harbors as proposed and requested that the Commission consider including bright-line tests and minimum standards in the safe harbor provisions to better guide SCI entities and their employees in avoiding liability under Regulation SCI. 
                            <E T="03">See</E>
                             OCC Letter at 11. 
                            <E T="03">See also</E>
                             NYSE Letter at 30 (noting that the Commission provided no guidance on the phrase “policies and procedures reasonably designed”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>646</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>647</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>648</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        A few commenters suggested specific alternatives to the proposed safe harbors.
                        <SU>649</SU>
                        <FTREF/>
                         One commenter recommended that the Commission adopt a safe harbor with objective criteria to protect SCI entities from enforcement actions under Regulation SCI except in cases of intentional or reckless non-compliance or patterns of non-compliance with Regulation SCI, or if an SCI entity fails to implement reasonable corrective action in response to a written communication from the Commission regarding Regulation SCI.
                        <SU>650</SU>
                        <FTREF/>
                         This commenter urged that, even if the Commission does not include the suggested safe harbor, the adopting release should clearly state that the Commission will not pursue enforcement actions against SCI entities that establish, maintain, and enforce compliance policies and procedures or act in good faith, notwithstanding a violation of Regulation SCI.
                        <SU>651</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>649</SU>
                             
                            <E T="03">See, e.g.</E>
                            , FSR Letter; ITG Letter; OTC Markets Letter; Joint SROs Letter; and NYSE Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>650</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 29, 31-32. This commenter also suggested that SCI entity employees be protected except in instances where employees intentionally or recklessly fail to discharge their duties and obligations under the SCI entity's policies and procedures. 
                            <E T="03">See</E>
                             NYSE Letter at 29, 31-32. This comment and the individual safe harbor are addressed in Section IV.B.2.d below. Another commenter, expressing support for NYSE's suggested approach for SCI entities and their employees, stated that an objective standard would provide the proper incentives for compliance and allow SCI entities to reasonably evaluate their potential exposure when an SCI event occurs and act quickly in the critical moments following an SCI event. 
                            <E T="03">See</E>
                             OTC Markets Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>651</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 32, n. 41.
                        </P>
                    </FTNT>
                    <P>
                        One group of commenters similarly recommended that the Commission adopt an objective safe harbor.
                        <SU>652</SU>
                        <FTREF/>
                         These commenters noted that minor mistakes and unintentional errors occur in the daily operations of running a business, and a safe harbor should provide protection to SCI entities that follow the policies and procedures as intended, including in the resolution and containment of such mistakes and errors.
                        <SU>653</SU>
                        <FTREF/>
                         These commenters believed that it should be sufficient for an SCI entity to qualify for the safe harbor if it adopts policies and procedures reasonably designed to comply with Regulation SCI and does not knowingly violate such policies and procedures.
                        <SU>654</SU>
                        <FTREF/>
                         These commenters further requested that the Commission clarify its views on the protections of the safe harbor for inadvertent violations of other laws and rules despite compliance with Regulation SCI and expand the safe harbor to explicitly cover such instances.
                        <SU>655</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>652</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 13-14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>653</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>654</SU>
                             
                            <E T="03">See id.</E>
                             These commenters suggested a parallel safe harbor for employees of SCI entities. 
                            <E T="03">See id.</E>
                             at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>655</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        One commenter suggested simplifying the safe harbor to require only that an SCI entity adopt reasonable policies and procedures to comply with proposed Regulation SCI, which should include reasonable ongoing responsibilities related to testing and monitoring.
                        <SU>656</SU>
                        <FTREF/>
                         Another commenter believed that the safe harbor should grant immunity from enforcement penalties for all problems that are self-reported by SCI entities and individuals.
                        <SU>657</SU>
                        <FTREF/>
                         One commenter suggested that Regulation SCI should: (1) Encourage parties to discover and 
                        <PRTPAGE P="72306"/>
                        remediate technology errors and malfunctions, and/or deficiencies in their policies and procedures; (2) avoid 
                        <E T="03">ipso facto</E>
                         liability under Regulation SCI for failures by technology or systems; and (3) require some form of causation in order for liability to attach.
                        <SU>658</SU>
                        <FTREF/>
                         This commenter also recommended that the Commission provide safe harbors from liability under both proposed Rules 1000(b)(1) and (2) where either: (1) The SCI entity or SCI personnel discovers and remediates a problem without regulatory intervention and assuming no underlying material violation; or (2) no technology error or problem has occurred, but the policies and procedures might benefit from improvements.
                        <SU>659</SU>
                        <FTREF/>
                         According to this commenter, the remediation safe harbor should also apply to underlying technology problems if the SCI entity had complied with Regulation SCI.
                        <SU>660</SU>
                        <FTREF/>
                         One commenter expressed concern that, without a safe harbor and a guarantee of immunity, the disclosures to the Commission required under Regulation SCI would provide a roadmap for litigation against non-SRO entities.
                        <SU>661</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>656</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>657</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>658</SU>
                             
                            <E T="03">See</E>
                             FSR Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>659</SU>
                             
                            <E T="03">See id.</E>
                             at 9-10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>660</SU>
                             
                            <E T="03">See id.</E>
                             at 3, 9-10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>661</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 15-16 (stating that “entities that do not have SRO immunity, such as ATSs, may be subject to liability based on information reported under Reg. SCI's Rule 1000(b)(4)(iv) . . . [w]ithout a safe harbor and a guarantee of immunity, this kind of disclosure provides a roadmap for litigation against non-SRO SCI entities”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Elimination of Proposed Safe Harbor for SCI Entities and Specification of Minimum Elements</HD>
                    <P>
                        As discussed in greater detail below, after careful consideration of the comments, and in light of the more focused scope of Regulation SCI, the Commission has determined not to adopt the proposed safe harbor for SCI entities.
                        <SU>662</SU>
                        <FTREF/>
                         Rather, Rule 1001(b) sets forth non-exhaustive minimum elements that an SCI entity must include in its systems compliance policies and procedures. The Commission recognizes that the precise nature, size, technology, business model, and other aspects of each SCI entity's business vary. Therefore, the minimum elements are intended to be general in order to accommodate these differences, and each SCI entity will need to exercise judgment in developing and maintaining specific policies and procedures that are reasonably designed to achieve systems compliance. The Commission also believes that SCI entities should consider the evolving nature of the securities industry, as well as industry practices and standards, in developing and maintaining such policies and procedures. As such, the elements specified in Rule 1001(b) are non-exhaustive, and each SCI entity should consider on an ongoing basis what steps it needs to take in order to ensure that its policies and procedures are reasonably designed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>662</SU>
                             The Commission's decision not to adopt an SCI entity safe harbor also addresses a commenter's concern that the inclusion of a safe harbor provision in Rule 1001(b) could unnecessarily and severely limit the Commission's ability to deter violations through meaningful enforcement actions. 
                            <E T="03">See supra</E>
                             notes 633-634 and accompanying text. As discussed in Section IV.B.2.d below, however, the Commission is adopting a safe harbor for personnel of SCI entities.
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission stated that, “[b]ecause of the complexity of SCI systems and the breadth of the federal securities laws and rules and regulations thereunder and the SCI entities' rules and governing documents, the Commission preliminarily believes that it would be appropriate to provide an explicit safe harbor for SCI entities and their employees in order to provide greater clarity as to how they can ensure that their conduct will comply with [Rule 1000(b)(2)].” 
                        <SU>663</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>663</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18115.
                        </P>
                    </FTNT>
                    <P>
                        One reason that the Commission is not adopting the proposed safe harbor for SCI entities is that the Commission has focused the scope of Regulation SCI as adopted. For example, adopted Rule 1001(b) requires policies and procedures that are reasonably designed to ensure compliance with “the Act”—rather than operating “in the manner intended, including in a manner that complies with the federal securities laws” as was proposed—and the rules and regulations thereunder, and the SCI entity's rules and governing documents. Therefore, the requirement under adopted Rule 1001(b) is more targeted than the requirement under proposed Rule 1000(b)(2), and alleviates some of the concern regarding the “breadth of the federal securities laws and rules and regulations thereunder” that was expressed in the SCI Proposal. The Commission expects that SCI entities are familiar with their obligations under the Exchange Act, the rules and regulations thereunder, and their own rules and governing documents. In addition, as discussed in Section IV.A.2.b above, the Commission has further focused the scope of SCI systems, which also alleviates some of the concern regarding the “complexity of SCI systems” that was expressed in the SCI Proposal.
                        <SU>664</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>664</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Further, as noted above, in the SCI Proposal, the Commission stated its preliminary belief that it would be appropriate to provide an explicit safe harbor for SCI entities in order to provide greater clarity on how they could comply with proposed Rule 1000(b)(2).
                        <SU>665</SU>
                        <FTREF/>
                         Rather than achieving this goal, commenters argued that the proposed safe harbor merely further defined the elements that the policies and procedures must have, and did not include sufficient guidance or specificity to SCI entities seeking to rely on it.
                        <SU>666</SU>
                        <FTREF/>
                         For example, one commenter noted that the policies and procedures specified in the safe harbor would still need to be “reasonably designed.” 
                        <SU>667</SU>
                        <FTREF/>
                         Further, the Commission acknowledges some commenters' concern that the proposed safe harbor, “with its prescriptive requirements,” could evolve into the 
                        <E T="03">de facto</E>
                         rule itself.
                        <SU>668</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>665</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>666</SU>
                             
                            <E T="03">See supra</E>
                             notes 638-639, 643-648 and accompanying text. With respect to the group of commenters who suggested that the safe harbor should give SCI entities a clear, affirmative defense from allegations of having violated Regulation SCI, as discussed above, the Commission is eliminating the proposed safe harbor for SCI entities. 
                            <E T="03">See supra</E>
                             note 643. As discussed below, the Commission believes that, by specifying non-exhaustive minimum elements that an SCI entity must include in its systems compliance policies and procedures, the rule will encourage SCI entities to actively build and improve upon the compliance of their systems, rather than limit their compliance to some fixed elements of a safe harbor.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>667</SU>
                             
                            <E T="03">See supra</E>
                             notes 638-639 and accompanying text. This commenter also compared the proposed SCI entity safe harbor to other rules, stating that the other rules requiring policies and procedures recognize the need for those policies and procedures to be reasonably designed in light of the manner in which business is conducted. 
                            <E T="03">See supra</E>
                             note 640 and accompanying text. Rule 1001(b), as adopted, requires policies and procedures to be “reasonably designed” to ensure the compliance of SCI systems. Therefore, Rule 1001(b) recognizes the need for policies and procedures to be reasonably designed in light of the manner in which an SCI entity's business is conducted.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>668</SU>
                             
                            <E T="03">See supra</E>
                             note 637 and accompanying text and 
                            <E T="03">supra</E>
                             note 640. The Commission acknowledges that some commenters who believed that the proposed safe harbor was inadequate also advocated for alternative safe harbors, such as those that require knowledge or recklessness for liability. These comments are discussed below in Section IV.B.2.b.iii.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, the Commission is not adopting a safe harbor for SCI entities. Rather, adopted Rule 1001(b)(1) requires an SCI entity to have reasonably designed policies and procedures to achieve systems compliance and adopted Rule 1001(b)(2) specifies non-exhaustive, general minimum elements that an SCI entity must include in its systems compliance policies and procedures. These minimum elements are based on the elements contained in the proposed safe harbor for SCI entities, but modified in 
                        <PRTPAGE P="72307"/>
                        response to concerns raised by commenters. As adopted, Rules 1001(b)(1) and (b)(2) specify the minimum elements of reasonably designed policies and procedures to achieve systems compliance, and at the same time provide flexibility by permitting an SCI entity to establish policies and procedures that are reasonably designed based on the nature, size, technology, business model, and other aspects of its business. Moreover, the Commission believes that, by specifying non-exhaustive, general minimum elements of systems compliance policies and procedures, the rule will encourage SCI entities to actively build and improve upon the compliance of their systems rather than limit their compliance to bright-line tests or the fixed elements of a safe harbor, and encourage the evolution of sound practices over time. In addition, the Commission notes that there currently are no publicly available written industry standards regarding systems compliance that are applicable to all SCI entities that can serve as the basis for a clear, objective safe harbor, as there is with current SCI industry standards (
                        <E T="03">e.g.</E>
                        , the publications listed in staff guidance) relating to operational capability. Even if such standards existed, the Commission believes that the specificity necessary to achieve the goal of a clear, objective safe harbor would disincentivize SCI entities from continuing to improve their systems over time. Finally, the Commission believes that, because the minimum elements specified in Rule 1001(b)(2) are non-exhaustive, Rule 1001(b) can accommodate the possibility that, as technology evolves, additional or updated elements could become appropriate for SCI entities to include in their systems compliance policies and procedures to ensure that such policies and procedures remain reasonably designed on an ongoing basis.
                    </P>
                    <HD SOURCE="HD3">iii. Response to Other Comments on the SCI Entity Safe Harbor</HD>
                    <P>
                        With respect to commenters who requested clarification on the protection of the safe harbor for inadvertent violations of other laws and rules despite compliance with Regulation SCI,
                        <SU>669</SU>
                        <FTREF/>
                         as noted above, the Commission clarifies that liability under Regulation SCI is separate and distinct from liability for other violations that may arise from the underlying SCI events under other laws and rules. Specifically, Regulation SCI imposes new requirements on SCI entities and is not intended to alter the standards for determining liability under other laws or rules. Therefore, if an SCI entity is in compliance with Regulation SCI but inadvertently violates another law or rule, whether or not the SCI entity will be liable under the other law or rule depends on the standards for determining liability under such law or rule. Because the new requirements under Regulation SCI are separate and distinct from existing requirements under other laws or rules, Regulation SCI is not a shield from liability under such laws or rules.
                    </P>
                    <FTNT>
                        <P>
                            <SU>669</SU>
                             
                            <E T="03">See supra</E>
                             notes 655 and 660 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also does not believe that it would be appropriate to provide a safe harbor for all problems that are self-reported by SCI entities and individuals or that are discovered and remediated without regulatory intervention, as suggested by commenters.
                        <SU>670</SU>
                        <FTREF/>
                         In particular, Rule 1001(b) is intended to help ensure that SCI entities operate their systems in compliance with the Exchange Act and relevant rules in the first place, and thus is not only focused on helping to ensure that SCI entities appropriately respond to a compliance issue (
                        <E T="03">e.g.</E>
                        , by taking corrective action or reporting the issue to the Commission) after it has occurred and impacted the market or market participants. Therefore, the Commission does not believe that the suggested self-report or remediation safe harbors will effectively further this intent of Rule 1001(b). In particular, the Commission notes that reporting and remediation of SCI events are separately required under Rules 1002(b) and (a) of Regulation SCI, respectively. The purposes of Rule 1002(b) include keeping the Commission informed of SCI events after they have occurred. Moreover, Rule 1002(a) is intended to ensure that SCI entities remedy a systems issue and mitigate the resulting harm after the issue has already occurred. The Commission believes that, if an SCI entity is protected from liability under Rule 1001(b) simply because it self-reported systems compliance issues or discovered and remediated systems compliance issues without regulatory intervention, the SCI entity will not be effectively incentivized to have reasonably designed policies and procedures to ensure systems compliance in the first place. As discussed above, the occurrence of an SCI event will not necessarily cause a violation of Regulation SCI. Further, the occurrence of a systems compliance issue also does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>670</SU>
                             
                            <E T="03">See supra</E>
                             notes 657 and 659 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, some commenters expressed concern that the occurrence of a significant systems issue would mean that an SCI entity did not have reasonable policies and procedures and therefore suggested “objective” safe harbors.
                        <SU>671</SU>
                        <FTREF/>
                         The Commission notes that all SCI entities are required to comply with the Exchange Act, the rules and regulations thereunder, and their own rules and governing documents, as applicable, and the purpose of Rule 1001(b) is to effectively help ensure compliance of the operation of SCI systems with these laws and rules. The Commission does not believe that Rule 1001(b) would further this goal to the same degree if the Commission were to adopt commenters' safe harbor suggestions (
                        <E T="03">i.e.</E>
                        , an SCI entity is deemed to be in compliance with Rule 1001(b) so long as: The SCI entity is not knowingly out of compliance; such non-compliance is not intentional, reckless, or in bad faith; or there is no pattern of non-compliance) because, with these suggested “objective” safe harbors, SCI entities may not be effectively incentivized to establish, maintain, and enforce reasonably designed policies and procedures to ensure systems compliance. Moreover, the Commission notes that Rule 1001(b) requires “reasonably designed” policies and procedures, which already provides flexibility to SCI entities in complying with the rule. The Commission also emphasizes again that, while it is eliminating the safe harbor for SCI entities, the occurrence of a systems compliance issue may be probative, but is not determinative, of whether an SCI entity violated Regulation SCI. As noted above, an SCI entity would not be 
                        <PRTPAGE P="72308"/>
                        deemed to be in violation of Rule 1001(b)(1) merely because it experienced a systems compliance issue. Further, the occurrence of a systems compliance issue also does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>671</SU>
                             
                            <E T="03">See supra</E>
                             notes 650-654 and accompanying text. As discussed above, some of these commenters suggested that the safe harbor should protect SCI entities from enforcement action except in cases of intentional or reckless non-compliance, or patterns of non-compliance with Regulation SCI. 
                            <E T="03">See supra</E>
                             note 650 and accompanying text. As an alternative to the intentional and recklessness standard, one of these commenters requested that the Commission specifically state that the Commission will not pursue enforcement actions against SCI entities that establish, maintain, and enforce systems compliance policies and procedures or act in good faith, notwithstanding a violation of Regulation SCI. 
                            <E T="03">See supra</E>
                             note 651 and accompanying text. One commenter noted that it should be sufficient for an SCI entity to qualify for the safe harbor if it adopts policies and procedures reasonably designed to comply with Regulation SCI and does not knowingly violate such policies and procedures. 
                            <E T="03">See supra</E>
                             note 654 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Further, as noted above, one commenter recommended that the Commission provide a safe harbor where no technology error or problem has occurred, but the policies and procedures might benefit from improvements.
                        <SU>672</SU>
                        <FTREF/>
                         The Commission believes that there may be instances where an SCI entity's policies and procedures might benefit from improvement, even though they are reasonably designed. In such instances, the SCI entity is in compliance with Rule 1001(b) and therefore does not need a safe harbor. At the same time, the Commission notes that there may be instances where no technology error or problem has occurred, but an SCI entity's policies and procedures with regard to systems compliance might nonetheless be deficient and not satisfy the requirements of Rule 1001(b). The Commission does not believe that it would be appropriate to provide a safe harbor in these instances. As noted above, Rule 1001(b) is intended to help ensure that SCI entities operate their SCI systems in compliance with the Exchange Act and relevant rules. The Commission does not believe that a safe harbor that effectively insulates deficient policies and procedures will further the intent of this rule. Further, the Commission notes that one requirement of Rule 1001(b)(1) is that an SCI entity “maintain” its policies and procedures. To explicitly set forth an SCI entity's obligation to review and update its policies and procedures, similar to Rule 1001(a), the Commission is adopting a requirement for periodic review by an SCI entity of the effectiveness of its systems compliance policies and procedures, and prompt action by the SCI entity to remedy deficiencies in such policies and procedures.
                        <SU>673</SU>
                        <FTREF/>
                         The Commission notes that an SCI entity will not be found to be in violation of this maintenance requirement solely because it failed to identify a deficiency immediately after the deficiency occurred, if the SCI entity takes prompt action to remedy the deficiency once it is discovered, and the SCI entity had otherwise appropriately reviewed the effectiveness of its policies and procedures and took prompt action to remedy those deficiencies that were discovered.
                    </P>
                    <FTNT>
                        <P>
                            <SU>672</SU>
                             
                            <E T="03">See supra</E>
                             note 659 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>673</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(b)(3). The adoption of this review and update requirement is consistent with the views of some commenters. 
                            <E T="03">See supra</E>
                             notes 620 and accompanying text (discussing a commenter's suggestion that policies and procedures should be reviewed and updated as part of the annual SCI review process) and 658 and accompanying text (discussing a commenter's suggestion that Regulation SCI should encourage parties to discover and remediate deficiencies in policies and procedures). The Commission notes that Rule 1001(b)(3) requires SCI entities to review and update their systems compliance policies and procedures rather than simply “encourage” the discovery and remediation of deficiencies because, in order to achieve the intended benefits of Rule 1001(b), an SCI entity's systems compliance policies and procedures must remain reasonably designed. If the Commission simply encourages SCI entities to review and update their systems compliance policies and procedures, the Commission believes that there would be a greater likelihood that such policies and procedures might become outdated and less effective in preventing systems compliance issues.
                        </P>
                    </FTNT>
                    <P>
                        Finally, as noted above, one commenter believed that, without a safe harbor and a guarantee of immunity (such as the regulatory immunity of SROs), information provided to the Commission pursuant to Rule 1000(b)(4)(iv) would provide a roadmap for litigation. As discussed below in Section IV.B.3.c, the Commission acknowledges that, if an SCI entity experiences an SCI event, it could become the subject of litigation (including private civil litigation). At the same time, the Commission notes that the information submitted to the Commission pursuant to Regulation SCI will be treated as confidential, subject to applicable law.
                        <SU>674</SU>
                        <FTREF/>
                         On the other hand, the Commission acknowledges that it could consider the information provided to the Commission pursuant to Rule 1002(b) in determining whether to initiate an enforcement action. The Commission notes that all SCI entities are required to comply with the Exchange Act, the rules and regulations thereunder, and their own rules and governing documents, as applicable, and the requirement for Commission notification of systems compliance issues is intended to assist the Commission in its oversight of such compliance. With respect to the regulatory immunity of SROs, the Commission notes that, although courts have found that SROs are entitled to absolute immunity from private claims under certain circumstances,
                        <SU>675</SU>
                        <FTREF/>
                         if an SRO fails to comply with the provisions of the Exchange Act, the rules or regulations thereunder, or its own rules, the Commission is still authorized to impose sanctions.
                        <SU>676</SU>
                        <FTREF/>
                         As such, like other SCI entities, SROs are not immune from Commission sanctions. Finally, as discussed in detail above, the Commission does not believe that it would be appropriate to provide a safe harbor for all problems that are self-reported to the Commission by SCI entities and individuals.
                    </P>
                    <FTNT>
                        <P>
                            <SU>674</SU>
                             The Commission notes that the General Instructions to Form SCI, Item G. Paperwork Reduction Act Disclosure, provides that the Commission “will keep the information collected pursuant to Form SCI confidential to the extent permitted by law.” 
                            <E T="03">See infra</E>
                             Section IV.C.2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>675</SU>
                             The Commission notes that SRO immunity applies only under certain circumstances. In particular, “when acting in its capacity as a SRO, [the SRO] is entitled to immunity from suit when it engages in conduct consistent with the quasi-governmental powers delegated to it pursuant to the Exchange Act and the regulations and rules promulgated thereunder.” 
                            <E T="03">See DL Capital Group, LLC</E>
                             v. 
                            <E T="03">NASDAQ Stock Market, Inc.,</E>
                             409 F.3d 93, 97 (2d Cir. 2005) (quoting 
                            <E T="03">D'Alessio</E>
                             v. 
                            <E T="03">New York Stock Exchange, Inc.,</E>
                             258 F.3d 93, 106 (2d Cir. 2001)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>676</SU>
                             
                            <E T="03">See</E>
                             15 U.S.C. 78s(g).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Minimum Elements of Reasonable Policies and Procedures</HD>
                    <P>
                        The safe harbor for SCI entities in proposed Rule 1000(b)(2)(ii) specified that, to qualify for the safe harbor, the SCI entity's policies and procedures must be reasonably designed to provide for: (1) Testing of all SCI systems and any changes to such systems prior to implementation; (2) periodic testing of all SCI systems and any changes to such systems after their implementation; (3) a system of internal controls over changes to SCI systems; (4) ongoing monitoring of the functionality of SCI systems to detect whether they are operating in the manner intended; (5) assessments of SCI systems compliance performed by personnel familiar with applicable federal securities laws and rules and regulations thereunder and the SCI entity's rules and governing documents, as applicable; and (6) review by regulatory personnel of SCI systems design, changes, testing, and controls to prevent, detect, and address actions that do not comply with applicable federal securities laws and rules and regulations thereunder and the SCI entity's rules and governing documents, as applicable. In the SCI Proposal, the Commission asked whether each element of the proposed safe harbor for SCI entities was appropriate.
                        <SU>677</SU>
                        <FTREF/>
                         Several commenters addressed one or more of the proposed safe harbor elements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>677</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18116-17.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, rather than adopting the proposed safe harbor for SCI entities, the Commission is specifying non-exhaustive, general 
                        <PRTPAGE P="72309"/>
                        minimum elements that an SCI entity must include in its systems compliance policies and procedures. The minimum elements are based on the proposed safe harbor. These elements are: (i) Testing of all SCI systems and any changes to SCI systems prior to implementation; (ii) a system of internal controls over changes to SCI systems; (iii) a plan for assessments of the functionality of SCI systems designed to detect systems compliance issues, including by responsible SCI personnel and by personnel familiar with applicable provisions of the Act and the rules and regulations thereunder and the SCI entity's rules and governing documents; and (iv) a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, regarding SCI systems design, changes, testing, and controls designed to detect and prevent systems compliance issues. Each of these elements is discussed below.
                    </P>
                    <P>
                        As noted above, some commenters requested more guidance or certainty regarding the safe harbor elements (
                        <E T="03">e.g.,</E>
                         by including bright-line tests and minimum standards).
                        <SU>678</SU>
                        <FTREF/>
                         As discussed above in Section IV.B.2.b, the Commission is not adopting a safe harbor but is specifying the minimum elements that an SCI entity must include in its systems compliance policies and procedures. By generally requiring policies and procedures to be reasonably designed and specifying non-exhaustive, general minimum elements of systems compliance policies and procedures, the Commission intends to provide specificity on how to comply with Rule 1001(b), and at the same time provide a reasonable degree of flexibility to SCI entities in establishing and maintaining policies and procedures that are appropriately tailored to each SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>678</SU>
                             
                            <E T="03">See supra</E>
                             notes 645-647 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Regarding elements (1) and (2) of the proposed safe harbor, a few commenters opposed the inclusion of a requirement that an SCI entity conduct periodic testing of systems absent systems changes.
                        <SU>679</SU>
                        <FTREF/>
                         One commenter stated that it performs testing prior to implementation of trading systems changes in the production environment and conducts regression testing to ensure that the changes did not introduce any undesired side-effects.
                        <SU>680</SU>
                        <FTREF/>
                         This commenter explained that the proposed periodic testing requirement would impose additional cost and not provide any benefit.
                        <SU>681</SU>
                        <FTREF/>
                         One commenter believed that the pre- and post-implementation testing components of the safe harbor, which would apply to all systems changes, could potentially drive SCI entities to take a narrow view of what constitutes a systems change.
                        <SU>682</SU>
                        <FTREF/>
                         Another commenter sought further guidance from the Commission on the scope of periodic testing of all SCI systems and whether, for example, systems testing would be required following a systems change if the SCI entity has already provided notice of the systems change to the Commission.
                        <SU>683</SU>
                        <FTREF/>
                         One commenter requested clarification that the testing described in proposed Rules 1000(b)(2)(ii)(A)(1) and (2) refers to testing to ensure that SCI systems operate in the manner intended, and noted that testing should not be required to be periodic, but instead should be based on the relative risks of non-compliance arising from any changes being introduced into production or any changes to the applicable laws or rules.
                        <SU>684</SU>
                        <FTREF/>
                         One commenter stated that it believed that the frequency and type of testing under proposed Rules 1000(b)(2)(ii)(A)(1) and (2) are open to interpretation.
                        <SU>685</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>679</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 33; BATS Letter at 7; and ISE Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>680</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>681</SU>
                             
                            <E T="03">See id.</E>
                              
                            <E T="03">See also</E>
                             FINRA Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>682</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 6. This commenter expressed concern that, under the proposed approach, any opening of a customer port, the removal of access rights from a departing employee, and the previously unscheduled closing of the market for the death of a U.S. president all involve “changes” to SCI systems that need to be tracked, approved, and catalogued within the construct of an enterprise-wide change management system. 
                            <E T="03">See id.</E>
                             This commenter stated that these “changes” cannot all be tested, either prior to or after implementation, without an extraordinary amount of redundancy and bureaucracy, if at all. 
                            <E T="03">See id.</E>
                             This commenter therefore suggested requiring instead “[a]ppropriate testing of [SCI] systems and changes to such systems prior to their implementation.” 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>683</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>684</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 13-14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>685</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 30.
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the views of commenters, the Commission believes that testing of SCI systems and changes to such systems prior to implementation is appropriate for inclusion as a required element of systems compliance policies and procedures. As noted in the SCI Proposal, elements (1) and (2) of the proposed safe harbor were intended to help SCI entities to identify potential problems before such problems have the ability to impact markets and investors.
                        <SU>686</SU>
                        <FTREF/>
                         The Commission believes that testing prior to implementation of SCI systems and prior to implementation of any SCI systems changes would likely be an important component for achieving this goal and it is included as a required element of systems compliance policies and procedures.
                        <SU>687</SU>
                        <FTREF/>
                         In contrast, the Commission believes that the value of the proposed element for additional testing in the absence of systems changes may be variable, depending on the SCI system or change to an SCI system at issue.
                        <SU>688</SU>
                        <FTREF/>
                         At the same time, each SCI entity should consider on an ongoing basis what steps it needs to take in order to ensure that its policies and procedures are reasonably designed, including whether its policies and procedures should provide for testing of certain systems changes after their implementation to ensure that they operate in compliance with the Exchange Act and relevant rules.
                    </P>
                    <FTNT>
                        <P>
                            <SU>686</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18115.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>687</SU>
                             With respect to a commenter's concern that “changes” to SCI systems could include, for example, any opening of a customer port, the removal of access rights from a departing employee, and the previously unscheduled closing of the market for the death of a U.S. president, the Commission does not view these as changes to an SCI entity's systems, because the Commission believes that these actions are part of an SCI entity's standard operations. 
                            <E T="03">See supra</E>
                             note 682. In particular, the Commission believes that the opening of a customer port, the removal of access rights, and the closing of the market are existing functionalities at SCI entities, and are routinely performed by SCI entities without the need to change existing functionalities.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>688</SU>
                             
                            <E T="03">See supra</E>
                             notes 681-682 and accompanying text. The Commission notes that a commenter asked about the scope of periodic testing under the proposed safe harbor, and whether systems testing under the proposed safe harbor would be required following a systems change if the SCI entity has already provided notice of the systems change to the Commission. Another commenter noted that testing under the proposed safe harbor should not be required to be periodic, but instead could be based on the relative risks of non-compliance arising from any changes being introduced into production or any changes to applicable laws or rules. The Commission is not requiring periodic testing or testing following systems changes in Rule 1001(b), and, as discussed above, the Commission is not adopting the proposed safe harbor.
                        </P>
                    </FTNT>
                    <P>
                        With regard to element (3) of the proposed safe harbor, one commenter stated that it is unclear what minimum standards are required for the internal controls under proposed Rule 1000(b)(2)(ii)(A)(3).
                        <SU>689</SU>
                        <FTREF/>
                         As discussed above, the Commission believes it is appropriate to set forth minimum elements of systems compliance policies and procedures that are broad enough to provide SCI entities with reasonable flexibility to design their policies and procedures based on the nature, size, technology, business model, and other aspects of their businesses. Therefore, while the Commission believes that a system of internal controls over changes to SCI systems is appropriate for inclusion as a required element of systems compliance policies and 
                        <PRTPAGE P="72310"/>
                        procedures, the Commission is not specifying the minimum standard for internal controls. As stated in the SCI Proposal, a system of internal controls and ongoing monitoring of systems functionality are intended to help ensure that an SCI entity adopts a framework that will help it bring newer, faster, and more innovative SCI systems online without compromising due care, and to help prevent SCI systems from becoming noncompliant resulting from, for example, inattention or failure to review compliance with established written policies and procedures. The Commission believes that such internal controls would likely include, for example, protocols that provide for: Communication and cooperation between legal, business, technology, and compliance departments in an SCI entity; appropriate authorization of systems changes by relevant departments of the SCI entity prior to implementation; review of systems changes by legal or compliance departments prior to implementation; and monitoring of systems changes after implementation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>689</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 30.
                        </P>
                    </FTNT>
                    <P>
                        With regard to elements (4)-(6) of the proposed safe harbor, one commenter noted that the proposed requirement related to ongoing monitoring was too broad and should be eliminated or revised to be more flexible.
                        <SU>690</SU>
                        <FTREF/>
                         This commenter noted that the proposal for “monitoring of the functionality of [SCI] systems to detect whether they are operating in the manner intended” is potentially quite broad and seems to suggest some form of independent validation.
                        <SU>691</SU>
                        <FTREF/>
                         Another commenter asked the Commission to clarify how the testing requirements in proposed Rules 1000(b)(2)(ii)(1) and (2) (testing prior to and after implementation) differ from those in proposed Rule 1000(b)(2)(ii)(A)(5) (assessments of systems compliance by personnel familiar with applicable laws and rules).
                        <SU>692</SU>
                        <FTREF/>
                         One commenter noted that the monitoring, assessments, and reviews under proposed Rules 1000(b)(2)(ii)(A)(4), (5), and (6) are unclear.
                        <SU>693</SU>
                        <FTREF/>
                         Two commenters sought guidance on how an SCI entity could satisfy the requirements related to reviews and assessments by legal and compliance personnel (
                        <E T="03">i.e.,</E>
                         proposed Rules 1000(b)(2)(ii)(A)(5) and (6)).
                        <SU>694</SU>
                        <FTREF/>
                         One of these commenters suggested that each SCI entity be given the discretion to determine the level of familiarity necessary to qualify as personnel able to undertake the assessments and which personnel are regulatory personnel, and asked whether these two categories of personnel are different.
                        <SU>695</SU>
                        <FTREF/>
                         Another commenter also sought clarification on the meaning of the term “regulatory personnel” and suggested that each SCI entity should have discretion in determining which of its employees constitute regulatory personnel.
                        <SU>696</SU>
                        <FTREF/>
                         One commenter expressed concern that review by regulatory personnel of SCI systems would unreasonably expose non-technology persons to potential liability if an SCI entity suffers a malfunction.
                        <SU>697</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>690</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 33-34.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>691</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>692</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>693</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>694</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 34-35; and MSRB Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>695</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 13-14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>696</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 11. 
                            <E T="03">See also</E>
                             FINRA Letter at 34-35 (requesting more guidance on which types of personnel are intended to fulfill the requirements of proposed Rules 1000(b)(2)(ii)(A)(5) and (6)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>697</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 14.
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the views of commenters, the Commission believes that “a plan for assessments of the functionality of SCI systems designed to detect systems compliance issues, including by responsible SCI personnel and by personnel familiar with applicable provisions of the Act and the rules and regulations thereunder and the SCI entity's rules and governing documents” is appropriate for inclusion as a required element of systems compliance policies and procedures. In particular, rather than “ongoing monitoring of the functionality of [SCI] systems to detect whether they are operating in the manner intended” and also “
                        <E T="03">assessments</E>
                         of SCI systems compliance . . . ,” the Commission believes that “
                        <E T="03">a plan for assessments</E>
                        ” of SCI systems compliance would be more appropriate.
                        <SU>698</SU>
                        <FTREF/>
                         The Commission notes that “a plan for assessments” could include, for example, not only a plan for monitoring, but also a plan for testing or assessments, as appropriate, and at a frequency (
                        <E T="03">e.g.,</E>
                         periodic or continuous) that is based on the SCI entity's risk assessment of each of its SCI systems.
                        <SU>699</SU>
                        <FTREF/>
                         The Commission is not specifying the manner and frequency of assessments that must be set forth in such plan because the Commission believes that each SCI entity will likely be in the best position to assess and determine the assessment plan that is most appropriate for its SCI systems. The Commission emphasizes that the nature and frequency of the assessments contemplated by an SCI entity's plan will vary based on a range of factors, including the entity's governance structure, business lines, and legal and compliance framework. The plan for assessments does not require the SCI entity to conduct a specific kind of assessment, nor does it require that assessments be performed at a certain frequency. The plan, however, may address the specific reviews required by Rule 1003(b)(1).
                    </P>
                    <FTNT>
                        <P>
                            <SU>698</SU>
                             The Commission notes that “a plan for assessments” is derived from a combination of the “ongoing monitoring” and “assessments” elements of the proposed SCI entity safe harbor. Because “a plan for assessments” could provide for ongoing (
                            <E T="03">i.e.,</E>
                             periodic or continuous) monitoring, the Commission believes that it would be duplicative to include both monitoring and a plan for assessments as required elements of systems compliance policies and procedures.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>699</SU>
                             
                            <E T="03">See supra</E>
                             note 690 and accompanying text (discussing the view of a commenter that the proposed element of the SCI entity safe harbor related to ongoing monitoring was too broad and should be eliminated or revised to be more flexible) and 
                            <E T="03">supra</E>
                             note 694 and accompanying text (discussing comments seeking guidance on how an SCI entity could satisfy the requirements related to reviews and assessments by legal and compliance personnel). Further, in response to a commenter, a plan for assessments is different from the testing of SCI systems prior to implementation of systems changes. 
                            <E T="03">See supra</E>
                             note 692 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In addition, in response to a commenter's concern that the proposed safe harbor element of “monitoring of the functionality of [SCI] systems to detect whether they are operating in the manner intended” is potentially quite broad and seems to suggest some form of independent validation, the Commission notes that it is not requiring SCI entities to include independent validation in their assessment plans.
                        <SU>700</SU>
                        <FTREF/>
                         However, if an SCI entity determines that its reasonably designed systems compliance policies and procedures should provide for independent validation in its assessment plan under certain circumstances, then the SCI entity should design its policies and procedures accordingly. In that case, pursuant to Rule 1001(b), which requires an SCI entity to establish, maintain, and enforce its written policies and procedures, the SCI entity would be required to enforce its own policies and procedures, including those related to independent validation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>700</SU>
                             
                            <E T="03">See supra</E>
                             note 691 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission believes that “a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, regarding SCI systems design, changes, testing, and controls designed to detect and prevent systems compliance issues” is appropriate for inclusion as a required element of systems compliance policies and procedures. As noted in the SCI Proposal, assessments of SCI systems compliance by personnel familiar with applicable laws and rules 
                        <PRTPAGE P="72311"/>
                        and regulatory personnel review of SCI systems design, changes, testing, and controls are intended to help foster coordination between the information technology and regulatory staff of an SCI entity so that SCI events and other issues related to SCI systems would be more likely to be addressed by a team of staff in possession of the requisite range of knowledge and skills.
                        <SU>701</SU>
                        <FTREF/>
                         They are also intended to help ensure that an SCI entity's business interests do not undermine regulatory, surveillance, and compliance functions and, more broadly, the requirements of the Exchange Act, during the development, testing, implementation, and operation processes for SCI systems.
                        <SU>702</SU>
                        <FTREF/>
                         The Commission believes that a plan of coordination and communication between regulatory and other personnel, including by responsible SCI personnel, would further these same goals.
                    </P>
                    <FTNT>
                        <P>
                            <SU>701</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18116.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>702</SU>
                             For example, profit incentive could lead an SCI entity to introduce a new functionality before regulatory personnel are able to adequately check that the functionality will operate in compliance with relevant laws and rules.
                        </P>
                    </FTNT>
                    <P>
                        The Commission expects that an SCI entity will determine for itself the responsible SCI personnel and other personnel who have sufficient knowledge of relevant laws and rules to be able to effectively implement systems assessments,
                        <SU>703</SU>
                        <FTREF/>
                         such that the SCI entity's policies and procedures are reasonably designed to ensure that SCI systems operate in compliance with the Exchange Act and relevant rules, as required by Rule 1001(b).
                        <SU>704</SU>
                        <FTREF/>
                         Similarly, the Commission expects that an SCI entity will determine for itself the regulatory and other personnel, including responsible SCI personnel, who have sufficient knowledge with respect to the legal and technical aspects of systems design, changes, testing, and controls to engage in coordination and communication regarding such operations, such that the SCI entity's policies and procedures are reasonably designed to ensure that its SCI systems operate in compliance with the Exchange Act and relevant rules, as required by Rule 1001(b).
                        <SU>705</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>703</SU>
                             
                            <E T="03">See supra</E>
                             notes 694-696 and accompanying text (describing comments on the proposed safe harbor related to who would be involved in systems assessments).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>704</SU>
                             Criteria for identification of such personnel could, for example, be set forth in the SCI entity's systems compliance policies and procedures.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>705</SU>
                             Some commenters expressed concern regarding the potential liability for regulatory personnel. 
                            <E T="03">See supra</E>
                             note 697 and accompanying text. The Commission discusses individual liability in Section IV.B.2.d below.
                        </P>
                    </FTNT>
                    <P>
                        One commenter sought clarity on how an SCI entity would satisfy the requirement that it does “not have reasonable cause to believe the policies and procedures were not being complied with.” 
                        <SU>706</SU>
                        <FTREF/>
                         Another commenter stated that there is no guidance for SCI entities on how to appropriately follow the procedures that they have developed and stated that as proposed, it would be reasonable to interpret the safe harbor as excluding any SCI entity that suffers a significant systems event.
                        <SU>707</SU>
                        <FTREF/>
                         One commenter believed that the Commission should resolve any potential ambiguity between the requirements of proposed Rule 1000(b)(2)(ii)(C)(1) (requiring SCI entities to reasonably discharge the duties and obligations set forth in the policies and procedures) and proposed Rule 1000(b)(2)(ii)(C)(2) (requiring that SCI entities not have reasonable cause to believe such policies and procedures were not being complied with).
                        <SU>708</SU>
                        <FTREF/>
                         As discussed throughout this section, the Commission is not adopting the proposed safe harbor for SCI entities. Therefore, as adopted, Rule 1001(b) does not include the provisions of proposed Rules 1000(b)(2)(ii)(B) and (C). Further, the Commission believes that proposed Rules 1000(b)(2)(ii)(B) and (C) reiterated the requirements for SCI entities to establish, maintain, and enforce their systems compliance policies and procedures, and provided an example of how SCI entities could satisfy these requirements. For example, the SCI Proposal noted that proposed Rules 1000(b)(2)(ii)(B) and (C) specified that an SCI entity's policies and procedures must be reasonably designed to achieve SCI systems compliance, and that, as part of such policies and procedures, the SCI entity must establish and maintain systems for applying those policies and procedures, and enforce its policies and procedures, in a manner that would reasonably allow it to prevent and detect violations of the policies and procedures.
                        <SU>709</SU>
                        <FTREF/>
                         The Commission believes that Rule 1001(b), as adopted, provides flexibility to SCI entities regarding their methods for establishing, maintaining, and enforcing their systems compliance policies and procedures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>706</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 35.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>707</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>708</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 13-15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>709</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18116.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. Individual Safe Harbor</HD>
                    <P>Proposed Rule 1000(b)(2)(iii) set forth a safe harbor for individuals. It provided that a person employed by an SCI entity would be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by any other person of proposed Rule 1000(b)(2)(i) if the person employed by the SCI entity has reasonably discharged the duties and obligations incumbent upon such person by the policies and procedures, and was without reasonable cause to believe that such policies and procedures were not being complied with in any material respect.</P>
                    <P>
                        In the SCI Proposal, the Commission asked whether commenters agreed with the requirements of the proposed safe harbor for employees of SCI entities, and whether a similar safe harbor should be available to individuals other than employees of SCI entities.
                        <SU>710</SU>
                        <FTREF/>
                         Some commenters specifically addressed the proposed safe harbor for individuals.
                        <SU>711</SU>
                        <FTREF/>
                         Several commenters urged that individuals not be subject to liability under Regulation SCI absent an intentional act of willful misconduct.
                        <SU>712</SU>
                        <FTREF/>
                         Two commenters questioned the need for a safe harbor for individuals generally,
                        <SU>713</SU>
                        <FTREF/>
                         and one commenter stated 
                        <PRTPAGE P="72312"/>
                        that inclusion of a safe harbor would unnecessarily and severely limit the Commission's ability to deter violations through meaningful enforcement actions.
                        <SU>714</SU>
                        <FTREF/>
                         Two commenters questioned why the proposed safe harbor for individuals was limited to SCI entity employees.
                        <SU>715</SU>
                        <FTREF/>
                         One commenter expressed concern that the proposed safe harbor for individuals could be counterproductive and create an environment of second-guessing and distrust, where employees act in a way to avoid potential liability (
                        <E T="03">i.e.,</E>
                         each person would be effectively deputized to police others' actions).
                        <SU>716</SU>
                        <FTREF/>
                         A few commenters added that the proposed safe harbor for individuals, and the resulting implication of potential individual liability, may have the unintended consequence of limiting the ability of SCI entities to hire the best available talent in information technology, risk-management, and compliance disciplines.
                        <SU>717</SU>
                        <FTREF/>
                         One commenter questioned why the proposed safe harbor for individuals would apply only to actions of aiding any other person and not apply to any actions of the reporting individual.
                        <SU>718</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>710</SU>
                             
                            <E T="03">See id.</E>
                             at 18117, question 103.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>711</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter; Direct Edge Letter; FINRA Letter; FSR Letter; and MSRB Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>712</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 6; and MSRB Letter at 17. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             notes 650 and 654 and accompanying text (discussing comments suggesting individual safe harbors). One commenter suggested that the safe harbor should provide that a person employed by an SCI entity shall be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by any other person unless such violation directly or indirectly relates to the duties and obligations of such person under the policies and procedures described in Rule 1000(b)(2)(i) and such person: (A) Has not reasonably discharged the applicable duty or obligation under such policies and procedures; (B) was not directed by his or her supervisor, SCI entity legal counsel, SCI senior management, or the governing body of the SCI entity to act in a manner that would constitute such a failure to discharge such duty or obligation; and (C) acted recklessly or intentionally with respect to such failure to discharge such duty or obligation. 
                            <E T="03">See</E>
                             MSRB Letter at 17. The Commission believes that elements (A) and (B) of this commenter's suggestion are consistent with the adopted individual safe harbor. In particular, the Commission notes that the safe harbor specifies that an individual must have reasonably discharged the duties and obligations incumbent upon such person by the SCI entity's policies and procedures. The Commission believes that there can be instances where a person has reasonably discharged his or her duties and obligations under the SCI entity's policies and procedures, even though such person was directed by his or her supervisor, SCI entity legal counsel, SCI entity senior management, or the governing body of the SCI entity to act in a manner that is inconsistent with his or her duties that are set forth the policies and procedures. For example, the SCI entity's reasonably designed policies and procedures could specifically set forth circumstances where certain personnel of the SCI entity may direct another person to act outside of his or her duties or obligations that are set forth in the policies and procedures.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>713</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 35; and FSR Letter at 3-8 (stating that the proposed rule lacks clarity over 
                            <PRTPAGE/>
                            why individuals need a safe harbor when the policies and procedures requirement is placed exclusively on SCI entities, and lacks clarity regarding to whom SCI entities or SCI personnel would be liable for a breach and how liability would be apportioned between market participants for an SCI event). 
                            <E T="03">See also</E>
                             MSRB Letter at 15 (seeking further clarification from the Commission regarding the nature of the potential liabilities faced by individuals).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>714</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>715</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 35; and MSRB Letter at 17. These commenters suggested extending the safe harbor to contractors, consultants, and other non-employees used by SCI entities in connection with their SCI systems. 
                            <E T="03">See</E>
                             FINRA Letter at 35; and MSRB Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>716</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 15-17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>717</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 6; and MSRB Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>718</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        After careful consideration of these comments, the Commission is adopting the individual safe harbor with certain modifications. With respect to the commenter who expressed concern that a safe harbor would “unnecessarily and severely” limit the Commission's ability to deter violations through meaningful enforcement actions,
                        <SU>719</SU>
                        <FTREF/>
                         the Commission notes that Regulation SCI only imposes obligations directly on SCI entities and the Commission is not adopting a safe harbor for SCI entities. Further, personnel of SCI entities qualify for the individual safe harbor under Rule 1001(b) only if they satisfy certain requirements.
                        <SU>720</SU>
                        <FTREF/>
                         In particular, in connection with a Commission finding that an SCI entity violated Rule 1001(b), the individual safe harbor will not apply if an SCI entity personnel failed to reasonably discharge his or her duties and obligations under the policies and procedures. In addition, for an SCI entity personnel who is responsible for or has supervisory responsibility over an SCI system, the individual safe harbor also will not apply if he or she had reasonable cause to believe that the policies and procedures related to such an SCI system were not in compliance with Rule 1001(b) in any material respect. Therefore, the Commission does not believe that the individual safe harbor will “unnecessarily and severely” limit the Commission's ability to deter violations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>719</SU>
                             
                            <E T="03">See supra</E>
                             note 714 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>720</SU>
                             As discussed below in this section, the Commission is extending the safe harbor to all personnel of an SCI entity, rather than only persons employed by an SCI entity, as proposed.
                        </P>
                    </FTNT>
                    <P>
                        With respect to commenters who questioned the need for an individual safe harbor because Rule 1001(b) imposes an obligation on SCI entities,
                        <SU>721</SU>
                        <FTREF/>
                         the Commission agrees that Regulation SCI imposes direct obligations on SCI entities, and does not impose obligations directly on personnel of SCI entities. At the same time, as with all other violations of the Exchange Act and rules that impose obligations on an entity, there is a potential for secondary liability for an individual who aided and abetted or caused a violation. The Commission is therefore revising the individual safe harbor to clarify that personnel of an SCI entity shall be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by “an SCI entity” (rather than “any other person”) of Rule 1001(b) if the elements of the safe harbor are satisfied.
                    </P>
                    <FTNT>
                        <P>
                            <SU>721</SU>
                             
                            <E T="03">See supra</E>
                             note 713 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter questioned why the proposed safe harbor for individuals would only apply to actions of aiding another and not apply to any direct violative action of the reporting individual.
                        <SU>722</SU>
                        <FTREF/>
                         The Commission notes that the individual safe harbor only applies to actions of aiding, abetting, counseling, commanding, causing, inducing, or procuring the violation by an SCI entity because Regulation SCI does not impose any direct obligations on personnel of SCI entities. Therefore, individuals could not be found to be in violation of Regulation SCI, except through aiding, abetting, counseling, commanding, causing, inducing, or procuring the violation by an SCI entity of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>722</SU>
                             
                            <E T="03">See supra</E>
                             note 718 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to commenters who suggested extending the individual safe harbor to contractors, consultants, and other non-employees used by SCI entities in connection with their SCI systems,
                        <SU>723</SU>
                        <FTREF/>
                         the Commission agrees with these comments and is extending the safe harbor to all “personnel of an SCI entity,” rather than only persons employed by an SCI entity, as was proposed. Specifically, the Commission believes that contractors, consultants, and other similar non-employees may act in a capacity similar to an SCI entity's employees, and thus should be able to avail themselves of the individual safe harbor if they satisfy its requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>723</SU>
                             
                            <E T="03">See supra</E>
                             note 715 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        To be covered by the individual safe harbor, for which the individual has the burden of proof, personnel of an SCI entity must: (i) Have reasonably discharged the duties and obligations incumbent upon such person by the SCI entity's policies and procedures; and (ii) be without reasonable cause to believe that the policies and procedures relating to an SCI system for which such person was responsible, or had supervisory responsibility, were not established, maintained, or enforced in accordance with Rule 1001(b) in any material respect. Element (i) of the adopted individual safe harbor is substantively unchanged from the proposal. For the reasons discussed below in this section, element (ii) of the adopted individual safe harbor specifies that it applies only to a person who is responsible for or has supervisory responsibility over an SCI system. In addition, rather than requiring an individual to be without reasonable cause to believe that systems compliance policies and procedures “were not being complied with in any material respect” as proposed, element (ii) of the adopted safe harbor requires the applicable personnel to be without reasonable cause to believe that the relevant systems compliance policies and procedures “were not established, maintained, or enforced” in accordance with Rule 1001(b) in any material respect. The Commission notes that element (ii) of the adopted safe harbor tracks the language of the general requirement under Rule 1001(b) that an SCI entity “establish, maintain, and enforce” written policies and procedures reasonably designed to ensure systems compliance, and appropriately reflects the responsibilities of a person who is responsible for or has supervisory responsibility over an SCI system.
                        <SU>724</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>724</SU>
                             As noted below, the Commission believes it is appropriate in the context of the safe harbor that, 
                            <PRTPAGE/>
                            if a person with responsibility over an SCI system becomes aware of potential material non-compliance of the SCI entity's policies and procedures related to that system, such person should take action to review and address, or direct other personnel to review and address, such material non-compliance.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72313"/>
                    <P>
                        The Commission believes that it is appropriate to not provide a safe harbor to a person with responsibility over an SCI system if such person had reasonable cause to believe that the policies and procedures for such system were not established, maintained, or enforced as required by Rule 1001(b) in a material respect. The limited application of this element to such personnel (rather than to any person employed by an SCI entity as proposed) is intended to mitigate commenters' concerns that the proposed safe harbor would create an environment of distrust and limit the ability of SCI entities to hire high quality personnel.
                        <SU>725</SU>
                        <FTREF/>
                         In particular, personnel who are not responsible for and do not have supervisory responsibility over SCI systems can qualify for the individual safe harbor, regardless of their belief regarding the reasonableness of the SCI entity's systems compliance policies and procedures. Therefore, such personnel would not be “deputized to police” the actions of other personnel, as a commenter believed they would.
                        <SU>726</SU>
                        <FTREF/>
                         Further, with respect to personnel who are responsible for or have supervisory responsibility over an SCI system, such personnel likely already have the responsibility to supervise others' activities related to that SCI system, which would provide such personnel with information to form a reasonable belief regarding the reasonableness of the policies and procedures. Because Rule 1001(b) is intended to help prevent the occurrence of systems compliance issues at SCI entities, the Commission believes that it is appropriate for supervisory personnel to be knowledgeable regarding the entity's policies and procedures regarding systems compliance, which may be accomplished through training provided by the SCI entity. Moreover, the Commission believes it is appropriate in the context of the safe harbor that, if a person with responsibility over an SCI system becomes aware of potential material non-compliance of the SCI entity's policies and procedures related to that system, such person should take action to review and address, or direct other personnel to review and address, such material non-compliance. Finally, to further mitigate commenters' concern that potential individual liability may limit the hiring ability of SCI entities,
                        <SU>727</SU>
                        <FTREF/>
                         as noted above, personnel of an SCI entity will not be deemed to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by an SCI entity of Regulation SCI merely because the SCI entity experienced a systems compliance issue, whether or not the person was able to take advantage of the individual safe harbor.
                    </P>
                    <FTNT>
                        <P>
                            <SU>725</SU>
                             
                            <E T="03">See supra</E>
                             notes 716-717 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>726</SU>
                             
                            <E T="03">See supra</E>
                             note 716 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>727</SU>
                             
                            <E T="03">See supra</E>
                             note 717 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, with respect to a personnel of an SCI entity who is not responsible for and does not have supervisory responsibility over SCI systems, the safe harbor provides that such personnel shall be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by an SCI entity of Rule 1001(b) if such person has reasonably discharged the duties and obligations incumbent upon him or her by the systems compliance policies and procedures. Therefore, unlike personnel who are responsible for or have supervisory responsibility over SCI systems, these persons would not be liable even if the SCI entity itself did not have reasonably designed systems compliance policies and procedures or did not enforce its policies and procedures, as long as they discharged their duties and obligations under the policies and procedures in a reasonable manner.
                        <SU>728</SU>
                        <FTREF/>
                         The Commission believes this safe harbor is appropriate because the persons who will seek to rely on this safe harbor are those who do not have responsibility for the establishment, maintenance, and enforcement of the policies and procedures, or the actions of other personnel of the SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>728</SU>
                             The Commission believes that, in order for a person to reasonably discharge his duties and obligations under the SCI entity's policies and procedures, that person must be able to understand his duties and obligations under such policies and procedures, which may be accomplished through training provided by the SCI entity.
                        </P>
                    </FTNT>
                    <P>
                        With respect to commenters who argued that individuals should not be subject to liability under Regulation SCI absent an intentional act of willful misconduct,
                        <SU>729</SU>
                        <FTREF/>
                         the Commission notes again that Regulation SCI imposes direct obligations only on SCI entities, and not on individuals. However, as with all other violations of provisions of the Exchange Act and rules that impose obligations on an entity, there is a potential for secondary liability for an individual who aided and abetted or caused a violation. As discussed above in the context of SCI entities, all SCI entities are required to comply with the Exchange Act, the rules and regulations thereunder, and their own rules and governing documents, as applicable, and the purpose of Rule 1001(b) is to effectively help ensure compliance of the operation of SCI systems with the Exchange Act, the rules and regulations thereunder, and their own rules and governing documents. The Commission does not believe that the rule would further this goal to the same degree if the Commission adopts commenters' suggestions for the individual safe harbor (
                        <E T="03">i.e.,</E>
                         personnel of an SCI entity are permitted to cause an SCI entity to be out of compliance with Rule 1001(b) so long as the personnel did not act intentionally or willfully).
                    </P>
                    <FTNT>
                        <P>
                            <SU>729</SU>
                             
                            <E T="03">See supra</E>
                             note 712 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. SCI Events: Corrective Action; Commission Notification; Dissemination of Information—Rule 1002</HD>
                    <P>Adopted Rule 1002, which corresponds to proposed Rules 1000(b)(3)-(5), requires an SCI entity to take corrective action, notify the Commission, and disseminate information regarding certain SCI events.</P>
                    <HD SOURCE="HD3">a. Triggering Standard</HD>
                    <P>
                        As proposed, the obligation of an SCI entity to take corrective action (proposed Rule 1000(b)(3)), notify the Commission (proposed Rule 1000(b)(4)), and disseminate information (proposed Rule 1000(b)(5)) would have been triggered upon “any responsible SCI personnel becoming aware of” an SCI event.
                        <SU>730</SU>
                        <FTREF/>
                         Proposed Rule 1000(a) defined “responsible SCI personnel” to mean, for a particular SCI system or SCI security system impacted by an SCI event, any personnel, whether an employee or agent, of an SCI entity having responsibility for such system.
                        <SU>731</SU>
                        <FTREF/>
                         In the SCI Proposal, the Commission noted that this proposed definition was intended to include any personnel of the SCI entity having responsibility for the specific system(s) impacted by a given SCI event.
                        <SU>732</SU>
                        <FTREF/>
                         The Commission stated that such personnel would include any technology, business, or operations staff with responsibility for such systems, and with respect to systems compliance issues, any regulatory, legal, or compliance personnel with legal or compliance responsibility for such systems.
                        <SU>733</SU>
                        <FTREF/>
                         The Commission also 
                        <PRTPAGE P="72314"/>
                        explained that “responsible SCI personnel” would not be limited to managerial or senior-level employees of the SCI entity and could include junior personnel with responsibility for a particular system.
                        <SU>734</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>730</SU>
                             
                            <E T="03">See</E>
                             proposed Rules 1000(b)(3), 1000(b)(4)(i)-(ii), and 1000(b)(5)(i)-(ii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>731</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.C.3.a.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>732</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18118.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>733</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>734</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>After considering the views of commenters, the Commission is modifying the proposed standard for triggering corrective action, Commission notification, and dissemination of information obligations in adopted Rule 1002, including by amending the definition of responsible SCI personnel, as discussed below.</P>
                    <HD SOURCE="HD3">Responsible SCI Personnel</HD>
                    <P>
                        Many commenters expressed concern that the proposed definition of responsible SCI personnel was too broad.
                        <SU>735</SU>
                        <FTREF/>
                         These commenters generally urged the Commission to revise the scope of the definition to cover only those employees in management or supervisory roles that have responsibility over an SCI system, rather than including relatively junior or inexperienced employees.
                        <SU>736</SU>
                        <FTREF/>
                         Some of these commenters stated that junior employees and/or technology personnel may not have the training or breadth of knowledge or experience necessary to identify, analyze, and determine whether a systems issue is an SCI event under the rule.
                        <SU>737</SU>
                        <FTREF/>
                         Similarly, one commenter advocated limiting responsible SCI personnel to employees with full knowledge and authority over a system.
                        <SU>738</SU>
                        <FTREF/>
                         Some commenters also suggested that SCI entities should have the discretion to decide which employees are responsible SCI personnel.
                        <SU>739</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>735</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 13; MSRB Letter at 6; BATS Letter at 8; Liquidnet Letter at 3; CME Letter at 7; OCC Letter at 12; Joint SROs Letter at 12; FINRA Letter at 25-26; and OTC Markets Letter at 19. 
                            <E T="03">See also</E>
                             NYSE Letter at 19 (stating that the proposed definition was too vague and suggesting an alternative approach). 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             note 761 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>736</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 13; MSRB Letter at 6, 18; NYSE Letter at 19; BATS Letter at 8; Liquidnet Letter at 3; CME Letter at 7; OCC Letter at 12; Joint SROs Letter at 12; FINRA Letter at 25-26; and OTC Markets Letter at 19. Similarly, with regard to the Commission notification requirement in proposed Rule 1000(b)(4), one commenter stated that the obligation to notify the Commission should only be triggered when the responsible SCI personnel notifies the officer or senior staff responsible for the SCI system or systems generally. 
                            <E T="03">See</E>
                             DTCC Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>737</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 12; FINRA Letter at 25-26; and OTC Markets Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>738</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 3, 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>739</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Liquidnet Letter at 3; NYSE Letter at 19; and Joint SROs Letter at 12.
                        </P>
                    </FTNT>
                    <P>
                        Similarly, several commenters emphasized the importance of escalation policies and procedures, pursuant to which technology staff or junior employees could assess a systems problem and escalate the issue up the chain of command to management as well as legal and/or compliance personnel, who will help determine whether a systems issue was an SCI event and whether the obligations under Regulation SCI are triggered.
                        <SU>740</SU>
                        <FTREF/>
                         These commenters argued that the rule should allow entities to adopt and follow such escalation procedures rather than triggering the obligations under Regulation SCI upon one employee's awareness of a systems issue.
                        <SU>741</SU>
                        <FTREF/>
                         One commenter also asserted that limiting the definition of responsible SCI personnel would be appropriate if the Commission also required a robust escalation procedure.
                        <SU>742</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>740</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 12; FINRA Letter at 25-26; Omgeo Letter at 13; FIF Letter at 5; and NYSE Letter at 19-20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>741</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 12; FINRA Letter at 25-26; Omgeo Letter at 13; FIF Letter at 5; and NYSE Letter at 19-20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>742</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 5.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters also expressed concern about the potential liability that responsible SCI personnel could face if the rule were adopted as proposed, given the breadth of the definition of “responsible SCI personnel.” 
                        <SU>743</SU>
                        <FTREF/>
                         Specifically, commenters asserted that, as a result of including junior and information technology personnel within the definition and the potential liability of such individuals, the proposed provision would make it more difficult for SCI entities to attract and retain high quality information technology employees.
                        <SU>744</SU>
                        <FTREF/>
                         Another commenter noted that responsible operations or technical personnel may not be in a position to make legal determinations about when a compliance issue has arisen.
                        <SU>745</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>743</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 19; BATS Letter at 8; Joint SROs Letter at 13; and OTC Markets Letter at 18. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 717.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>744</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 19; BATS Letter at 8; Joint SROs Letter at 13; and OTC Markets Letter at 18. These commenters therefore recommended that the definition include only senior personnel who would more appropriately be responsible for making a determination as to whether an SCI event had occurred given their knowledge and authority.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>745</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 13.
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the views of commenters, the Commission has revised the term “responsible SCI personnel” to mean, “for a particular SCI system or indirect SCI system impacted by an SCI event, such senior manager(s) of the SCI entity having responsibility for such system, and their designee(s).” 
                        <SU>746</SU>
                        <FTREF/>
                         The Commission agrees that the proposed definition of responsible SCI personnel was broad and, consistent with the views of some commenters, believes that it is appropriate to instead focus the adopted definition on senior personnel of SCI entities that have responsibility for a particular system.
                        <SU>747</SU>
                        <FTREF/>
                         The Commission believes that adopting a more focused definition of responsible SCI personnel to include only senior managers having responsibility for a given system (and their designees) addresses commenters' concerns that the obligations of the rule could have been triggered upon the awareness of junior or inexperienced employees who lack the knowledge or experience to be able to make a determination regarding whether an SCI event had, in fact, occurred.
                        <SU>748</SU>
                        <FTREF/>
                         The Commission believes that the revised definition is a better approach than the proposed definition because, consistent with suggestions from some commenters, it will appropriately allow SCI entities to adopt procedures that would require personnel of an SCI entity to escalate a systems issue to senior individuals who are responsible for a particular system and who have the ability and authority to appropriately analyze and assess the issue affecting the SCI system or indirect SCI system, and their designees, as applicable.
                        <SU>749</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>746</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>747</SU>
                             
                            <E T="03">See generally</E>
                              
                            <E T="03">supra</E>
                             notes 735-738 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>748</SU>
                             
                            <E T="03">See supra</E>
                             notes 736-737. 
                            <E T="03">See also</E>
                             note 738 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>749</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.1.b (discussing Rule 1001(a)(1)(2)(vii), which requires an SCI entity to have policies and procedures to provide for monitoring of SCI systems, and indirect SCI systems, as applicable, to identify potential SCI events, and escalate them to responsible SCI personnel); and 
                            <E T="03">infra</E>
                             notes 758-761 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also notes that, consistent with some commenters' recommendations, under the adopted rule, SCI entities will be afforded flexibility to determine which personnel to designate as “responsible SCI personnel.” 
                        <SU>750</SU>
                        <FTREF/>
                         Specifically, SCI entities will need to affirmatively identify one or more senior managers that have responsibility for each of its SCI systems or indirect SCI systems.
                        <SU>751</SU>
                        <FTREF/>
                         In addition, the Commission notes that the definition of responsible SCI personnel affords SCI entities with the flexibility to designate one or more other personnel as designees for a given system.
                        <SU>752</SU>
                        <FTREF/>
                         The Commission believes that it is important to include designees within the definition of responsible SCI personnel to provide an SCI entity with the flexibility that it may need, and 
                        <PRTPAGE P="72315"/>
                        which the Commission believes is necessary, given the varying sizes, natures, and complexities of each SCI entity. A senior manager may name a designee (or designees) who would also have responsibility for a given system with regard to Regulation SCI, for example, if the senior manager is absent, is occupied with other oversight responsibilities for a period of time, or because of other practical limitations, is otherwise unavailable to assess the SCI entity's obligations under Regulation SCI at a given point in time. The Commission believes it is likely that the designation of a designee and such designee's particular responsibilities with regard to an SCI system or indirect SCI system would be addressed by an SCI entity's policies and procedures, as discussed below. However, the Commission notes that while the definition of “responsible SCI personnel” does not permit the senior manager having responsibility for an applicable system to disclaim responsibility under the rule by delegating it fully to one or more designees (
                        <E T="03">i.e.,</E>
                         the adopted rule reads “
                        <E T="03">and</E>
                         their designees” rather than “
                        <E T="03">or</E>
                         their designees”), it may assist SCI entities in fulfilling their responsibilities under Regulation SCI by allowing them to delegate to personnel other than senior managers such that those designees can also serve in the role of responsible SCI personnel.
                    </P>
                    <FTNT>
                        <P>
                            <SU>750</SU>
                             
                            <E T="03">See supra</E>
                             note 739 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>751</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>752</SU>
                             The Commission notes that the rules do not, however, require SCI entities to have designees. Rather, each SCI entity has the discretion to have designees if they choose to do so.
                        </P>
                    </FTNT>
                    <P>
                        The Commission further believes that the modifications to the definition addresses some commenters' concerns regarding the potential liability of junior SCI personnel, as the obligations of the rule are now triggered only when senior managers, rather than junior employees, having responsibility for a particular system have a reasonable basis to conclude that an SCI event has occurred.
                        <SU>753</SU>
                        <FTREF/>
                         Further, the Commission reiterates that Regulation SCI imposes direct obligations on SCI entities and does not impose obligations directly on personnel of SCI entities. For these reasons, the Commission believes that an SCI entity's ability to attract and retain employees should not be negatively affected by the requirements of Regulation SCI, as adopted.
                        <SU>754</SU>
                        <FTREF/>
                         The Commission also reiterates that the occurrence of an SCI event may be probative, but is not determinative of whether an SCI entity violated Regulation SCI.
                        <SU>755</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>753</SU>
                             
                            <E T="03">See supra</E>
                             notes 743-744 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>754</SU>
                             
                            <E T="03">See supra</E>
                             notes 721 and 743-744 and accompanying text. The Commission notes that commenters' concerns regarding potential liability of employees were related to the scope of the proposed definition of responsible SCI personnel and the effect on the hiring and retention of junior and information technology personnel. Commenters believed that the definition should instead focus on senior managers who could appropriately be held responsible given their responsibilities and authority to take necessary actions under the rule.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>755</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 470 and 627 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In light of the more focused definition of responsible SCI personnel and consistent with commenters' suggestions,
                        <SU>756</SU>
                        <FTREF/>
                         the Commission believes it is appropriate to also adopt a policies and procedures requirement with respect to the designation of responsible SCI personnel and escalation procedures. As discussed above, many commenters highlighted the importance of escalation procedures and advocated for their use as an alternative to the adoption of a broader definition of responsible SCI personnel.
                        <SU>757</SU>
                        <FTREF/>
                         Specifically, the Commission is adopting Rule 1001(c), which requires each SCI entity to “[e]stablish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel, and escalation procedures to quickly inform responsible SCI personnel of potential SCI events.” The Commission believes that it is important for an SCI entity's policies and procedures to have a defined set of criteria for identifying responsible SCI personnel so that such personnel are identified in a consistent manner across all of an SCI entity's operations and with regard to all of its SCI systems and indirect SCI systems. The Commission believes that SCI entities are best suited to establish the appropriate criteria for such a designation but notes that such criteria could include, for example, consideration of the level of knowledge, skills, and authority necessary to take the required actions under the rules. The Commission also believes it is important for policies and procedures to include the designation and documentation of responsible SCI personnel, so that it is clear to all employees of the SCI entity who the designated responsible SCI personnel are for purposes of the escalation procedures and so that Commission staff can easily identify such responsible SCI personnel in the course of its inspections and examinations and other interactions with SCI entities. The Commission also believes that, given the more focused definition of responsible SCI personnel, escalation procedures to quickly inform responsible SCI personnel of potential SCI events are necessary to help ensure that the appropriate person(s) are provided notice of potential SCI events so that any appropriate actions can be taken in accordance with the requirements of Regulation SCI without unnecessary delay. Such escalation procedures would establish the means by which, and actions required for, escalating information regarding a systems issue that may be an SCI event up the chain of command to the responsible SCI personnel, who will be responsible for determining whether an SCI event has occurred and what resulting obligations may be triggered. The Commission notes that each SCI entity may establish escalation procedures that conform to its needs, organization structure, and size. By requiring that responsible SCI personnel are “quickly inform[ed]” of potential SCI events, the Commission intends to require that escalation procedures emphasize promptness and ensure that responsible SCI personnel are informed of potential SCI events without delay. At the same time, the rule does not prescribe a specific time requirement in order to give flexibility to SCI entities in recognition that immediate notification may not be possible or feasible. Further, similar to adopted Rules 1001(a) and 1001(b), Rule 1001(c) requires that an SCI entity periodically review the effectiveness of the policies and procedures related to responsible SCI personnel, and to take prompt action to remedy deficiencies in such policies and procedures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>756</SU>
                             
                            <E T="03">See supra</E>
                             notes 740-742 and accompanying text and 
                            <E T="03">infra</E>
                             notes 759-761 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>757</SU>
                             
                            <E T="03">See supra</E>
                             notes 740-742 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Becomes Aware</HD>
                    <P>
                        Several commenters criticized the proposed requirement that certain obligations under Regulation SCI be triggered when a responsible SCI personnel “becomes aware” of an SCI event. Some commenters stated that the standard was vague and lacked clarity regarding when, exactly, responsible SCI personnel would be deemed to become aware of an SCI event.
                        <SU>758</SU>
                        <FTREF/>
                         Further, some commenters noted that the “becomes aware” standard emphasized immediate action over methodical escalation, diagnosis, and resolution procedures.
                        <SU>759</SU>
                        <FTREF/>
                         As noted above, several commenters emphasized the importance of escalation policies and procedures, and argued that the rule should allow entities to adopt and follow such escalation procedures rather 
                        <PRTPAGE P="72316"/>
                        than triggering the obligations under Regulation SCI upon one employee's awareness of a systems issue.
                        <SU>760</SU>
                        <FTREF/>
                         Another commenter suggested specific revisions to the triggering standard so that the phrase “responsible SCI personnel becoming aware” would be eliminated entirely and replaced with “SCI entity having a reasonable basis to conclude,” which it believed would allow for escalation through a normal chain of command.
                        <SU>761</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>758</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 8-9; NYSE Letter at 19; and Joint SROs Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>759</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 3, 9, and 12. 
                            <E T="03">See also</E>
                             OCC Letter at 12; FINRA Letter at 25-26; Omgeo Letter at 13; FIF Letter at 5; and NYSE Letter at 19-20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>760</SU>
                             
                            <E T="03">See supra</E>
                             notes 740-742 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>761</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 19.
                        </P>
                    </FTNT>
                    <P>
                        With regard to the Commission notification requirements specifically,
                        <SU>762</SU>
                        <FTREF/>
                         one commenter suggested that SCI entities should only be required to notify the Commission “upon confirming the existence of an SCI event,” 
                        <SU>763</SU>
                        <FTREF/>
                         while another commenter stated that the rule should require notification to the Commission as soon as reasonably practicable after responsible personnel becomes aware of the SCI event.
                        <SU>764</SU>
                        <FTREF/>
                         Similarly, one commenter believed that the “becomes aware” standard was problematic because it would require notification before an SCI entity has accurate information upon which to act.
                        <SU>765</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>762</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>763</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>764</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>765</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 5 (urging that notification be required when “accurate and actionable” information is provided to responsible SCI personnel). 
                            <E T="03">See also</E>
                             BATS Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the views of commenters, the Commission has determined to revise the triggering standard so that SCI entities will be required to comply with the obligations of adopted Rule 1002 upon responsible SCI personnel having “a reasonable basis to conclude” that an SCI event has occurred, as suggested by a commenter.
                        <SU>766</SU>
                        <FTREF/>
                         This standard permits an SCI entity to gather relevant information and perform an initial analysis and assessment as to whether a systems issue may be an SCI event, rather than requiring an SCI entity to take corrective action, notify the Commission, and/or disseminate information about an SCI event immediately upon responsible SCI personnel becoming aware of an SCI event.
                        <SU>767</SU>
                        <FTREF/>
                         Thus, the Commission believes that the “reasonable basis to conclude” standard should provide some additional flexibility and time for judgment to determine whether there is a “reasonable basis to conclude” in contrast to the “becomes aware” standard which many commenters noted would be difficult to apply in practice due to the difficulty of determining when an individual, in fact, “becomes aware” of an SCI event.
                        <SU>768</SU>
                        <FTREF/>
                         Further, the Commission believes that, consistent with commenters' recommendations, the revised standard, in conjunction with the revised definition of “responsible SCI personnel,” will allow an SCI entity to adopt and follow its internal escalation policies and procedures to inform senior SCI entity personnel of systems issues, and allow meaningful assessment of the issues by such senior management prior to triggering obligations of the rule.
                        <SU>769</SU>
                        <FTREF/>
                         At the same time, the Commission believes that the obligations of the rule will continue to be triggered in a timely manner because the Commission is adopting a separate requirement in Rule 1001(c), as noted above, for escalation procedures to quickly inform responsible SCI personnel of potential SCI events.
                    </P>
                    <FTNT>
                        <P>
                            <SU>766</SU>
                             
                            <E T="03">See</E>
                             adopted Rules 1002(a), (b), and (c). 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 761.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>767</SU>
                             
                            <E T="03">See supra</E>
                             notes 759 and 763-765 and accompanying text. Additionally, the Commission does not agree with the commenter who stated that notification should be required only as soon as reasonably practicable after responsible personnel become aware of an SCI event because that standard would unnecessarily delay the requirement for an SCI entity to take necessary actions under the rule and the Commission's knowledge of an SCI event. 
                            <E T="03">See supra</E>
                             note 764.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>768</SU>
                             
                            <E T="03">See supra</E>
                             note 758 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>769</SU>
                             
                            <E T="03">See supra</E>
                             notes 758-760 and accompanying text. The Commission believes that the adopted standard similarly allows for escalation of a systems issue to senior officials because the Commission believes that having “a reasonable basis to conclude” is a good indication that an SCI event has likely occurred and does not require that the responsible SCI personnel come to a 
                            <E T="03">definitive</E>
                             conclusion, which would cause unnecessary delay in taking the actions required by Regulation SCI. Rather, once responsible SCI personnel have a 
                            <E T="03">reasonable basis</E>
                             to conclude that an SCI event has occurred, the Commission believes that an SCI entity should begin to take corrective action, provide notice to the Commission, and/or disclose such event, as applicable, because these requirements are designed to ensure that the SCI entity begins to take action in a timely fashion to mitigate potential harm arising from the incident and that the Commission and relevant market participants are kept apprised of an SCI event even where a definitive conclusion is not yet available. The Commission does not agree with the commenter that it should apply the triggering standard only to the SCI entity rather than responsible SCI personnel. The Commission notes, as discussed above, that the adopted definition of responsible SCI personnel imposes obligations only upon the senior personnel of an SCI entity that have responsibility for a particular system. Additionally, the Commission believes that it is important to apply the triggering standard to responsible SCI personnel rather than to the SCI entity because, when combined with an SCI entity's policies and procedures with respect to the designation of responsible SCI personnel and escalation and monitoring procedures, the triggering standard is designed to ensure that senior managers are provided notice of potential SCI events so that any appropriate actions can be taken in accordance with the requirements of Regulation SCI without unnecessary delay.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Corrective Action—Rule 1002(a)</HD>
                    <P>
                        Proposed Rule 1000(b)(3) required an SCI entity, upon any responsible SCI personnel becoming aware of an SCI event, to begin to take appropriate corrective action including, at a minimum, mitigating potential harm to investors and market integrity resulting from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable.
                        <SU>770</SU>
                        <FTREF/>
                         The corrective action requirement is being adopted substantially as proposed, but with the triggering standard modified as discussed above.
                        <SU>771</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>770</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(3) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18117.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>771</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <P>
                        Two commenters supported the corrective action provision generally.
                        <SU>772</SU>
                        <FTREF/>
                         Several commenters stated that the proposed requirement put too great an emphasis on immediately taking corrective action at the expense of thoroughly analyzing the SCI event and its cause, considering potential remedies, and/or acting in accordance with internal policies and procedures before committing to a plan to take corrective action.
                        <SU>773</SU>
                        <FTREF/>
                         One group of commenters suggested that the rule should make clear that “corrective action” should also include a variety of other potential actions, such as communicating with responsible parties, diagnosing the root cause, disclosing to members and the public, and mitigating potential harm by following their policies and procedures.
                        <SU>774</SU>
                        <FTREF/>
                         Another commenter stated that, in certain circumstances, it is “aggressive to presume that one individual's knowledge should prompt an immediate response by the SCI [e]ntity at large.” 
                        <SU>775</SU>
                        <FTREF/>
                         This commenter further stated that a standard requiring an SCI entity to mitigate potential harm to investors is extremely vague.
                        <SU>776</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>772</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 17 and DTCC Letter at 9-10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>773</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 3; OCC Letter at 14; Joint SROs Letter at 11; LiquidPoint Letter at 4; DTCC Letter at 10; and Direct Edge Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>774</SU>
                             
                            <E T="03">See</E>
                             Joint SROs at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>775</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>776</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As adopted, Rule 1002(a) requires an SCI entity, upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, to begin to take appropriate corrective action including, at a minimum, mitigating potential harm to investors and market integrity resulting 
                        <PRTPAGE P="72317"/>
                        from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable. The Commission continues to believe that this provision of Regulation SCI is important to make clear that each SCI entity has the obligation to respond to SCI events with appropriate steps necessary to remedy the problem or problems causing such SCI event and mitigate the negative effects of the SCI event, if any, on market participants and the securities markets more broadly. As discussed below, the specific steps that an SCI entity will need to take to mitigate the harm will be dependent on the particular systems issue, its causes, and the estimated impact of the event, among other factors. To the extent that a systems issue affects not only the particular users of an SCI system, but also has a more widespread impact on the market generally, as may be likely with regard to systems issues affecting critical SCI systems, the SCI entity will need to consider how it might mitigate any potential harm to the overall market to help ensure market integrity. For example, an SCI entity would need to take steps to regain a system's ability to process transactions in an accurate, timely, and efficient manner, or to ensure the accurate, timely, and efficient collection, processing, and dissemination of market data.
                    </P>
                    <P>As noted above, many of the comments on this requirement are related to the standard for triggering the obligation to take corrective action under this provision, namely “upon any SCI responsible personnel becoming aware of” an SCI event. As discussed above, the Commission has further focused the scope of the term “responsible SCI personnel” in response to commenters' concerns that the term was too broad and could inappropriately capture junior and/or inexperienced employees. Further, as discussed above, the Commission has revised the “becomes aware” standard to instead trigger obligations when responsible personnel have “a reasonable basis to conclude” an SCI event has occurred. As explained above, the Commission believes that these important modifications are responsive to commenters' concerns that the corrective action requirement could be triggered upon the knowledge of only one individual or a junior employee of a systems issue without sufficient time to analyze and assess the systems problem and follow internal escalation procedures. Under the adopted standard, only when (i) suspected systems problems are escalated to senior managers of the SCI entity who have responsibility for the SCI system or indirect SCI system experiencing an SCI event and their designees, and (ii) such personnel have “a reasonable basis to conclude” that an SCI event has occurred are the appropriate corrective actions required by Rule 1002(a) triggered.</P>
                    <P>
                        Further, in response to commenters who stated that the proposed rule places too large an emphasis on immediate corrective action,
                        <SU>777</SU>
                        <FTREF/>
                         in addition to the modifications noted above which are intended to allow for appropriate time for an SCI entity to perform an initial analysis and preliminary investigation into a potential systems issue before the obligations under Rule 1002(a) are triggered, the Commission notes that it does not use the term “immediate” in either the proposed or adopted rules. Rather, the Commission emphasizes that the rule requires that corrective action be taken “as soon as reasonably practicable” once the triggering standard has been met. The Commission believes that, because the facts and circumstances of each specific SCI event will be different, this standard ensures that an SCI entity will take necessary corrective action soon after an SCI event, but not without sufficient time to first consider what is the appropriate action to remedy the SCI event in a particular situation and how such action should be implemented.
                    </P>
                    <FTNT>
                        <P>
                            <SU>777</SU>
                             
                            <E T="03">See supra</E>
                             notes 773-775 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Moreover, the Commission has considered the comment that the rule prescribe in more specificity the particular types of corrective action that must be taken by an SCI entity and believes that it is appropriate to adopt, as proposed, a rule that requires more generally that “appropriate” corrective action be taken and requires that, at a minimum, the SCI entity take appropriate steps to mitigate potential harm to investors and market integrity resulting from the SCI event and devote adequate resources to remedy the SCI event. The Commission notes that the rule is designed to afford flexibility to SCI entities in determining how to best respond to a particular SCI event in order to remedy the problem causing the SCI event and mitigate its effects. As a general matter, though, the Commission agrees that such corrective action would likely include a variety of actions, such as those identified by one group of commenters, including determining the scope of the SCI event and its causes, making a determination regarding its known and anticipated impact, following adequate internal diagnosis and resolution policies and procedures, and taking additional action to respond as each SCI entity deems appropriate.
                        <SU>778</SU>
                        <FTREF/>
                         The Commission also notes that certain other specific types of corrective action identified by such commenters are already required by other provisions of Regulation SCI, such as communicating and escalating the issue to responsible personnel and making appropriate disclosures to members or participants regarding the SCI event.
                        <SU>779</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>778</SU>
                             
                            <E T="03">See supra</E>
                             note 774 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>779</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1001(c) (requiring policies and procedures that include, among other things, escalation procedures to quickly inform responsible SCI personnel of potential SCI events) and Rule 1002(c) (requiring dissemination of information regarding SCI events).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Notification—Rule 1002(b)</HD>
                    <HD SOURCE="HD3">i. Proposed Rule 1000(b)(4)</HD>
                    <P>
                        Proposed Rule 1000(b)(4) addressed the Commission notification obligations of an SCI entity upon any responsible SCI personnel becoming aware of an SCI event.
                        <SU>780</SU>
                        <FTREF/>
                         Specifically, proposed Rule 1000(b)(4)(i) required an SCI entity, upon any responsible SCI personnel becoming aware of a systems disruption that the SCI entity reasonably estimated would have a material impact on its operations or on market participants, any systems compliance issue, or any systems intrusion (“immediate notification SCI event”), to notify the Commission of such SCI event, which could be done orally or in writing (
                        <E T="03">e.g.,</E>
                         by email). Proposed Rule 1000(b)(4)(ii) required an SCI entity to submit a written notification pertaining to any SCI event to the Commission within 24 hours of any responsible SCI personnel becoming aware of the SCI event. Proposed Rule 1000(b)(4)(iii) required an SCI entity to submit to the Commission continuing written updates on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, until such time as the SCI event was resolved.
                    </P>
                    <FTNT>
                        <P>
                            <SU>780</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(4) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.C.3.b.
                        </P>
                    </FTNT>
                    <P>
                        Proposed Rule 1000(b)(4)(iv) detailed the types of information that was required for written notifications under proposed Rule 1000(b)(4).
                        <SU>781</SU>
                        <FTREF/>
                         In 
                        <PRTPAGE P="72318"/>
                        addition, proposed Rule 1000(b)(4)(iv)(C) required an SCI entity to provide a copy of any information disseminated regarding the SCI event to its members or participants or on the SCI entity's publicly available Web site.
                    </P>
                    <FTNT>
                        <P>
                            <SU>781</SU>
                             Specifically, the SCI Proposal required written notifications and updates to be made electronically and required initial written notifications to include all pertinent information known about an SCI event, including: (1) A detailed description of the SCI event; (2) the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; (3) the potential impact of the SCI event on the market; and (4) the SCI entity's current assessment of the SCI event, including a discussion of the SCI entity's determination regarding whether the SCI event was a dissemination SCI event or not. In addition, as proposed, to the extent available as of the time of 
                            <PRTPAGE/>
                            the initial notification, Exhibit 1 to Form SCI would have required inclusion of the following information: (1) A description of the steps the SCI entity was taking, or planned to take, with respect to the SCI event; (2) the time the SCI event was resolved or timeframe within which the SCI event was expected to be resolved; (3) a description of the SCI entity's rule(s) and/or governing documents, as applicable, that related to the SCI event; and (4) an analysis of the parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. 
                            <E T="03">See</E>
                             proposed Rule 1000(b)(4)(iv)(A).
                        </P>
                    </FTNT>
                    <P>As described below, adopted Rule 1002(b) retains the general framework of proposed Rule 1000(b)(4) for Commission notification of SCI events, but makes several modifications in response to comments.</P>
                    <HD SOURCE="HD3">Comments Regarding Commission Notification of SCI Events</HD>
                    <P>
                        One commenter generally supported proposed Rule 1000(b)(4), stating that it would enhance transparency and might allow the Commission to see patterns in small, seemingly non-material SCI events that are worthy of attention.
                        <SU>782</SU>
                        <FTREF/>
                         However, many other commenters expressed concerns about proposed Rule 1000(b)(4).
                        <SU>783</SU>
                        <FTREF/>
                         Many of these commenters stated that the scope of proposed Rule 1000(b)(4) was too broad, and that the notification requirement would lead to over-reporting to the Commission.
                        <SU>784</SU>
                        <FTREF/>
                         Commenters also suggested various ways to revise the reporting requirement. For example, several commenters recommended requiring notification to the Commission only for “material” or “significant” events.
                        <SU>785</SU>
                        <FTREF/>
                         For example, one commenter recommended reporting most SCI events as part of the annual SCI review process, while focusing Commission notification on material SCI events.
                        <SU>786</SU>
                        <FTREF/>
                         Similarly, another commenter suggested that SCI entities should only be required to report information relating to “impactful” systems disruptions in an annual report to the Commission rather than in near real time reports.
                        <SU>787</SU>
                        <FTREF/>
                         Another commenter recommended requiring notification only for systems issues that warrant notification to an SCI entity's subscribers or participants.
                        <SU>788</SU>
                        <FTREF/>
                         Some commenters recommended a risk-based approach under which each SCI event would be subject to a risk-based assessment, in which the obligation to notify the Commission would be based on the attendant risk, with only material events requiring notification.
                        <SU>789</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>782</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 6. The Commission also notes that, although many other commenters expressed reservations with proposed Rule 1000(b)(4), many of these commenters also expressed their general support for a notification rule that is more limited in scope. 
                            <E T="03">See, e.g.,</E>
                             ITG Letter at 12 (stating that a reduction in notifications would result in lower costs, reduce the over-reporting of events, and allow the Commission to focus on events that warrant review); and FINRA Letter at 18 (“FINRA fully supports the Commission's goal of ensuring that Commission staff is informed of events that could potentially impact the market”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>783</SU>
                             
                            <E T="03">See, e.g.</E>
                             NYSE Letter at 21; BATS Letter at 12-13; ITG Letter at 12; FINRA Letter at 16-17; Omgeo Letter at 16; SIFMA Letter at 13; ISE Letter at 6; OCC Letter at 11; and CME Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>784</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 22; Omgeo Letter at 16; SIFMA Letter at 14; ISE Letter at 6; and OCC Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>785</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ITG Letter at 12; CME Letter at 9; DTCC Letter at 8; and Omgeo Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>786</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>787</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>788</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 19 (stating that the notification requirement to the Commission should be aligned with the current industry practice of notifying SCI entities' subscribers of material events, explaining that competitive forces motivate entities to promptly notify subscribers about significant issues).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>789</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 13; SIFMA Letter at 13; Omgeo Letter at 1; FINRA Letter at 14; and NYSE Letter at 25.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also identified potential problems resulting from a notification requirement that they perceived as too broad. For example, one commenter stated that the notification requirements have the potential to create efficiency issues, delay system remediation, create substantial resource demands, and create instability, which would diminish an SCI entity's ability to be responsive to investors and damage market efficiency.
                        <SU>790</SU>
                        <FTREF/>
                         Similarly, several commenters stated that the proposed Commission notification provision would require SCI entities to divert resources to comply with the requirement which, in turn, would risk delaying resolution of the SCI event that is being reported on.
                        <SU>791</SU>
                        <FTREF/>
                         Other commenters suggested that the proposed rule would result in large volumes of data and reporting, which would present challenges to, and burdens on, SCI entities as well as Commission staff.
                        <SU>792</SU>
                        <FTREF/>
                         One commenter also questioned the extent to which the reported information provided by the notifications would be useful to the Commission.
                        <SU>793</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>790</SU>
                             
                            <E T="03">See</E>
                             UBS Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>791</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 16; MSRB Letter at 19; and OCC Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>792</SU>
                             
                            <E T="03">See</E>
                             SunGard Letter at 5; and Joint SROs Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>793</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 22.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters focused their comments on the proposal's requirements for Commission reporting of systems intrusions and offered alternative approaches to reporting systems intrusions. One commenter stated that, in order to limit the number of notifications, SCI entities should be required to investigate and keep a record of all systems intrusions that did not cause a material disruption of service, or that were a malicious (but unsuccessful) attempt in gaining unauthorized access to confidential data, and make these records available to the Commission staff if requested.
                        <SU>794</SU>
                        <FTREF/>
                         Another commenter recommended that non-material systems intrusions be recorded within the SCI entity's records.
                        <SU>795</SU>
                        <FTREF/>
                         Another commenter suggested that systems intrusions in a development or testing environment should only be reportable if there is a likelihood that the same issue or vulnerabilities exist in the current production environment and cannot be verified within a certain period, such as, for example, 24 to 48 hours.
                        <SU>796</SU>
                        <FTREF/>
                         In addition, one commenter suggested that, for systems intrusions, rather than impose the Commission notification requirement on SCI entities, the Commission should instead require SCI entities to establish policies and procedures reasonably designed to prevent, detect, and respond to systems intrusions.
                        <SU>797</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>794</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>795</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>796</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 11-12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>797</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 12. This commenter believed that the cost of the proposed requirement would outweigh any benefits because the proposed rule would require SCI entities to “rapidly investigate and report a multitude of minor incidents that regularly occur during the normal course of business.” 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that the Commission should support the enhancement of the Financial Services Information Sharing and Analysis Center (“FS-ISAC”) 
                        <SU>798</SU>
                        <FTREF/>
                         and another commenter suggested that non-material cyber-relevant events be provided to and disseminated through FS-ISAC rather than the Commission.
                        <SU>799</SU>
                        <FTREF/>
                         Some commenters further suggested that certain systems intrusions should be reported to FS-ISAC.
                        <SU>800</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>798</SU>
                             FS-ISAC is a service that gathers information from a multitude of sources related to threat, vulnerability, and risk of cyber and physical security and communicates timely notifications and authoritative information specifically designed to help protect critical systems and assets from physical and cybersecurity threats. 
                            <E T="03">See</E>
                             FS-ISAC: Financial Services—Information Sharing and Analysis Center, available at: 
                            <E T="03">www.fsisac.com.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>799</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 10; and Omgeo Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>800</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 14 (recommending that systems intrusions be reported to FS-ISAC in addition to the Commission); and Omgeo Letter at 12 and 21 (recommending that non-material systems intrusions be reported solely to FS-ISAC).
                        </P>
                    </FTNT>
                    <P>
                        Other commenters stated that reporting a systems compliance issue is 
                        <PRTPAGE P="72319"/>
                        reporting a legal conclusion, and that requiring an SCI entity to do so would overburden them with extensive technical and legal analysis and potentially expose those entities to Commission sanctions or litigation.
                        <SU>801</SU>
                        <FTREF/>
                         Several commenters expressed concerns regarding the confidentiality of the information provided pursuant to proposed Rule 1000(b)(4), and stated that the such information should be confidential and protected from public disclosure.
                        <SU>802</SU>
                        <FTREF/>
                         One of these commenters requested that the Commission confirm in the final rule that the information will remain confidential.
                        <SU>803</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>801</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 16. 
                            <E T="03">See also</E>
                             NYSE Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>802</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 24; Joint SROs Letter at 12; and DTCC Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>803</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 11.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also raised other general concerns and made suggestions with regard to proposed Rule 1000(b)(4). One commenter argued that the proposed rules could cause SCI entities to release information before all relevant factors are known, which could be counterproductive and harmful.
                        <SU>804</SU>
                        <FTREF/>
                         Another commenter was concerned that SCI entities would be required to provide notification reports multiple times to different Commission staff for the same event.
                        <SU>805</SU>
                        <FTREF/>
                         Another commenter suggested that the proposed requirement is onerous and costly and thus, to realize benefits, the Commission, based on notifications received from SCI entities, should provide regular summary-level feedback that communicates the types, frequency, severity, and impact of market incidents across all reporting entities and other related data on the root cause of problems.
                        <SU>806</SU>
                        <FTREF/>
                         Another commenter suggested that the Commission provide examples, such as publications and reference blueprints, which could be useful to SCI entities as they attempt to understand the types of SCI events that warrant Commission notification.
                        <SU>807</SU>
                        <FTREF/>
                         Finally, some commenters broadly questioned the Commission's legal authority to adopt Regulation SCI as proposed, asserting, among other things that the Commission's proposed notification requirement was beyond its legal authority.
                        <SU>808</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>804</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>805</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 22. Another commenter suggested that the notification requirement with respect to system disruptions should make clear that multiple notifications are not required if a disruption impacts multiple SCI entities. 
                            <E T="03">See</E>
                             FINRA Letter at 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>806</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>807</SU>
                             
                            <E T="03">See</E>
                             SunGard Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>808</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 4-6; and OTC Markets at 6. 
                            <E T="03">See infra</E>
                             notes 833-837 and accompanying text (discussing “Commission Legal Authority”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Rule 1002(b) </HD>
                    <P>
                        After careful consideration of the comments on proposed Rule 1000(b)(4), the Commission is adopting Rule 1002(b), with several modifications in response to comments.
                        <SU>809</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>809</SU>
                             Specific comments on proposed Rules 1000(b)(4)(i)-(iii) that are not discussed above are discussed below in conjunction with the Commission's response to those comments.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Overview </HD>
                    <P>The Commission notes that, even without the modifications the Commission is making in adopted Rule 1002(b), the proposed Commission notification rule would require Commission notice of fewer SCI events than as proposed as a result of the adopted definitions of SCI systems, indirect SCI systems, systems disruption, and systems compliance issue, and the revised triggering standard discussed above. In addition, the Commission has determined to refine the scope of the adopted Commission notification requirement by incorporating a risk-based approach that requires SCI entities, for purposes of Commission notification, to divide SCI events into two main categories: SCI events that “[have] had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants” (“de minimis” SCI events); and SCI events that are not de minimis SCI events. De minimis SCI events will not be subject to an immediate Commission notification requirement as proposed. Instead, all de minimis SCI events will be subject to recordkeeping requirements, and de minimis systems disruptions and de minimis systems intrusions will be subject to a quarterly reporting obligation, as set forth in adopted Rule 1002(b)(5). For SCI events that are not de minimis, Commission notification will be governed by adopted Rules 1002(a)(1)-(4), which is substantially similar to proposed Rules 1000(b)(4)(ii)-(iv), but relaxed in certain respects in response to comment, as discussed below. </P>
                    <HD SOURCE="HD3">Effect of Revised Definitions and Revised Triggering Standard on Commission Notification Requirement </HD>
                    <P>
                        The Commission believes that the revisions made to a number of definitions already focus the scope of the Commission notification requirement in adopted Rule 1002(b) from the SCI Proposal. For example, elimination of member regulation and member surveillance systems from the adopted definition of SCI systems will substantially reduce the potential number of SCI events that would be subject to Commission notification under the proposal.
                        <SU>810</SU>
                        <FTREF/>
                         Likewise, systems problems that would otherwise meet the definition of SCI event do not meet the definition of an SCI event if they occur in the development or testing environment.
                        <SU>811</SU>
                        <FTREF/>
                         In addition, the Commission believes that the revised definition of “systems disruption” and “systems compliance issue” also will result in fewer systems issues being identified as SCI events.
                        <SU>812</SU>
                        <FTREF/>
                         In tandem with the revised definitions, the Commission also believes that the revised triggering standard for notification of SCI events, which affords an SCI entity time to evaluate whether a potential SCI event is an actual SCI event, will also result in fewer SCI events being subject to the requirements of Rules 1002(b)(1)-(4).
                        <SU>813</SU>
                        <FTREF/>
                         The Commission believes that these changes respond to comments that proposed Rule 1000(b)(4) was overbroad and overly burdensome for SCI entities.
                        <SU>814</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>810</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>811</SU>
                             
                            <E T="03">See supra</E>
                             note 796 and accompanying text. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”). According to one commenter who supported excluding non-market systems from the definition of SCI systems and the notification and dissemination requirements, applying the reporting requirements to non-market systems “would significantly increase the volume of the reports the Commission receives.” FINRA Letter at 10. (“If the definition of SCI systems is broadly construed to apply to non-market regulatory and surveillance systems, approximately 111 FINRA systems could be subject to Regulation SCI.”) FINRA Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>812</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.3 (discussing the definition of “SCI event,” “systems disruption,” and “systems compliance issue”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>813</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the definition of “responsible SCI personnel”) and Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>814</SU>
                             
                            <E T="03">See supra</E>
                             note 784 and accompanying text. 
                            <E T="03">See also</E>
                             Section VI (discussing comments regarding the burdens associated with proposed Rule 1000(b)(4)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Exclusion of De Minimis SCI Events From Immediate Notification Requirements: Adopted Rule 1002(b)(5) </HD>
                    <P>
                        Adopted Rule 1002(b)(5) states that the requirements of Rules 1002(b)(1)-(4) do not apply to any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. For such de minimis events, Rule 1002(b)(5) requires that an SCI entity: (i) Make, keep, and preserve records relating to all such SCI events; and (ii) submit to the Commission a report, within 30 calendar days after the end of each calendar quarter, containing a summary description of such systems 
                        <PRTPAGE P="72320"/>
                        disruptions and systems intrusions, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such systems disruptions and systems intrusions during the applicable calendar quarter. 
                    </P>
                    <P>The Commission believes that this exception will result in a less burdensome reporting framework for de minimis SCI events than for other SCI events, and therefore responds to comment that the proposed reporting framework was too burdensome. The Commission believes that the quarterly reporting of de minimis systems disruptions and de minimis systems intrusions will reduce the frequency and volume of SCI event notices submitted to the Commission and also will allow both the SCI entity and its personnel, as well as the Commission and its staff, to focus their attention and resources on other, more significant SCI events. Consistent with taking a risk-based approach in other aspects of Regulation SCI, the Commission believes this modification from the SCI Proposal will result in more focused Commission monitoring of SCI events than if this aspect of the SCI Proposal was adopted without modification. Further, by reducing the number of SCI event notices provided to the Commission on an immediate basis as compared to the SCI Proposal, the adopted rule should also impose lower compliance costs and fewer burdens than if this aspect of the SCI Proposal was adopted without modification. </P>
                    <P>
                        However, the Commission has determined not to incorporate a materiality threshold as requested by some commenters,
                        <SU>815</SU>
                        <FTREF/>
                         to limit the Commission reporting requirements to those events that are considered by SCI entities to be truly disruptive to the markets, as suggested by other commenters,
                        <SU>816</SU>
                        <FTREF/>
                         or to limit the Commission reporting requirement only to those events that warrant notification to an SCI entity's subscribers or participants, as suggested by still other commenters.
                        <SU>817</SU>
                        <FTREF/>
                         The Commission has made this determination because while there may be SCI events with little apparent impact on an SCI entity's operations or on market participants and the burden on an SCI entity to provide immediate notice to the Commission every time such an event occurs may not justify the benefit of providing such notice to the Commission on an immediate basis, the Commission does not believe that such de minimis events are irrelevant or that the Commission should never be made aware of them. To fulfill its oversight role, the Commission believes that the Commission and its staff should regularly be made aware of de minimis systems disruptions and de minimis systems intrusions and should have ready access to records regarding de minimis systems compliance issues that SCI entities are facing and addressing because, as the regulator of the U.S. securities markets, it is important that the Commission and its staff have access to information regarding all SCI events (including de minimis SCI events) and their impact on the technology systems and systems compliance of SCI entities, which may also provide useful insights into learning about indications of more impactful SCI events. The Commission has, however, determined to distinguish the timing of its receipt of information regarding SCI events based on their impact: those SCI events that an SCI entity reasonably estimates to have a greater impact are subject to “immediate” notification upon responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred; and those SCI events that an SCI entity reasonably estimates to have no or a de minimis impact are subject to recordkeeping obligations, and for de minimis systems disruptions and de minimis systems intrusions, a quarterly summary notification. Despite commenters' arguments to the contrary that de minimis SCI events do not warrant the Commission's and its staff's attention, the Commission believes that quarterly reporting of de minimis systems disruptions and de minimis systems intrusions and review of records regarding de minimis systems compliance issues is beneficial to the Commission and its staff in understanding SCI entity systems operations at the level of the individual SCI entity, as well as across the spectrum of SCI entities, and to monitor compliance with the Exchange Act and rules thereunder. The Commission notes that, while it is not requiring that de minimis systems compliance issues be submitted to the Commission in quarterly reports, Commission staff may request records relating to such de minimis systems compliance issues as necessary. The Commission encourages and does not intend to inhibit an evaluation by SCI entities of systems compliance issues, including de minimis systems compliance issues, which may inherently involve legal analysis. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>815</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 785 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>816</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 785-787.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>817</SU>
                             
                            <E T="03">See supra</E>
                             note 788.
                        </P>
                    </FTNT>
                    <P>
                        As noted, some commenters focused specifically on systems intrusions, urging the Commission to modify or significantly reduce the instances in which notice of systems intrusions would be required,
                        <SU>818</SU>
                        <FTREF/>
                         or provide that non-material systems intrusions not be reported at all, and only be recorded by the SCI entity.
                        <SU>819</SU>
                        <FTREF/>
                         The Commission believes that the recordkeeping and quarterly reporting requirement for de minimis systems intrusions described in Rule 1002(b)(5) is partially responsive to these comments, but also believes that notice of intrusions in SCI systems and indirect SCI systems is important to allow the Commission and its staff to detect patterns or understand trends in the types of systems intrusions that may be occurring at multiple SCI entities. However, as compared to what would have been required if the SCI Proposal was adopted without modification, the Commission expects that the exception from the immediate reporting requirement provided for de minimis SCI events under Rule 1002(b)(5) will result in a much lower number of systems intrusions that SCI entities will be required to immediately report to the Commission than commenters believed,
                        <SU>820</SU>
                        <FTREF/>
                         and will achieve this result without compromising the Commission's interest in receiving more timely notification of impactful SCI events. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>818</SU>
                             
                            <E T="03">See supra</E>
                             notes 794-797 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>819</SU>
                             
                            <E T="03">See supra</E>
                             notes 794-795 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>820</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 794 and accompanying text (discussing a commenter's suggestion to limit the number of notifications by requiring recordkeeping of all systems intrusions that did not cause a material disruption of service or that were a malicious (but unsuccessful) attempt in gaining unauthorized access to confidential data).
                        </P>
                    </FTNT>
                    <P>
                        In addition, some commenters suggested that certain types of systems intrusions or non-material SCI events be reported exclusively to FS-ISAC or to both the Commission and FS-ISAC, and some advocated that the Commission support the enhancement of FS-ISAC.
                        <SU>821</SU>
                        <FTREF/>
                         The Commission believes that FS-ISAC, and other information sharing services play an important role in assisting SCI entities and other entities with respect to security issues. Consistent with views shared by several members of the third panel at the Cybersecurity Roundtable, to the extent SCI entities determine that such information sharing services are useful, the Commission encourages SCI entities to cooperate with and share information relating to information security threats and related issues with such entities to 
                        <PRTPAGE P="72321"/>
                        further enhance their utility.
                        <SU>822</SU>
                        <FTREF/>
                         At the same time, for the reasons discussed above,
                        <SU>823</SU>
                        <FTREF/>
                         the Commission believes that it is important that the Commission directly receive information regarding systems intrusions from SCI entities, through immediate notifications or quarterly reports, as applicable. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>821</SU>
                             
                            <E T="03">See supra</E>
                             notes 799-800 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>822</SU>
                             
                            <E T="03">See supra</E>
                             notes 39-40 and accompanying text. During the Cybersecurity Roundtable, panelists referenced other services that they believed useful to SROs, including the Financial Services Sector Coordinating Council for Critical Infrastructure Protection and Homeland Security (FSSCC), the Clearing House and Exchange Forum (CHEF), and the Worldwide Federation of Exchange's recently established Global Exchanges Cyber Security Working Group (GLEX). 
                            <E T="03">See supra</E>
                             note 39.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>823</SU>
                             
                            <E T="03">See supra</E>
                             notes 904-906 and accompanying text.
                        </P>
                    </FTNT>
                    <P>In response to comments that recordkeeping of non-material SCI events would be more appropriate than reporting, the Commission believes that quarterly reporting of de minimis systems disruptions and de minimis systems intrusions will better achieve the goal of keeping Commission staff informed regarding the nature and frequency of SCI events that arise but are reasonably estimated by the SCI entity to have a de minimis impact on the entity's operations or on market participants. Importantly, submission and review of regular reports will facilitate Commission staff comparisons among SCI entities and thereby permit the Commission and its staff to have a more holistic view of the types of systems operations challenges that were posed to SCI entities in the aggregate. </P>
                    <P>With regard to de minimis systems compliance issues, however, the Commission believes the goals of Regulation SCI can be achieved through the SCI entity's obligation to keep, and provide to representatives of the Commission upon request, records of such de minimis systems compliance issues. The Commission believes that systems compliance issues generally are more specific to a particular entity's systems and rules and less likely, as compared to systems disruptions and systems intrusions, to raise market-wide issues that could affect several SCI entities. Accordingly, information on such events are less likely to provide valuable insight into trends and risks across the industry and, therefore, the Commission believes that the benefits of receiving quarterly reports on such de minimis systems compliance issues would be less relative to de minimis systems disruptions and de minimis systems intrusions. Further, the Commission notes that, based on Commission staff's experience with notifications of compliance-related issues at SROs, the Commission believes that SCI entities will experience a relatively small number of systems compliance issues each year, and thus, its regular examinations of SCI entities will provide an adequate mechanism for reviewing and addressing de minimis systems compliance issues affecting SCI entities. As noted above, Commission staff may request records relating to such de minimis systems compliance issues as necessary. </P>
                    <P>
                        In response to the concerns raised by one commenter that the notification requirements have the potential to create efficiency issues, delay system remediation, create substantial resource demands, and create instability, the Commission believes that these concerns have been mitigated by the numerous changes made from the proposal, such as the adoption of a quarterly reporting framework for de minimis systems disruptions and de minimis systems intrusions and revised definitions of the terms SCI systems, indirect SCI systems, systems disruption, and systems compliance issue, in addition to the reduction in the obligations SCI entities have with respect to reporting requirements.
                        <SU>824</SU>
                        <FTREF/>
                         In addition, ARP entities today are able to regularly notify the Commission of systems related issues, such as systems outages, and the Commission therefore believes that the notification requirements will not require a majority of SCI entities to develop policies and procedures that are incongruous with their current practice. Moreover, the Commission believes that providing SCI entities with 30 days after the end of each quarter is adequate time for an SCI entity to prepare its report without unduly diverting SCI entity resources away from focusing on SCI events occurring in real time.
                        <SU>825</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>824</SU>
                             
                            <E T="03">See supra</E>
                             note 790.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>825</SU>
                             
                            <E T="03">See supra</E>
                             notes 791-793 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that requiring SCI entities to report de minimis systems disruptions and de minimis systems intrusions quarterly balances the interest of SCI entities in having a limited reporting burden for such types of events with the Commission's interest in oversight of the information technology programs and systems compliance of SCI entities.
                        <SU>826</SU>
                        <FTREF/>
                         Similarly, the Commission believes that requiring recordkeeping of de minimis systems compliance issues allows the Commission to adequately monitor compliance with the Exchange Act and rules thereunder, while reducing the burdens on SCI entities with regard to providing information to the Commission on such de minimis systems compliance issues. Accordingly, the Commission has determined to exclude certain SCI events from the immediate Commission reporting requirements, subject to certain recordkeeping and reporting requirement for such events, as applicable.
                        <SU>827</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>826</SU>
                             The Commission notes an SCI entity should be prepared for the possibility that Commission staff may, whether upon request pursuant to Rule 1002(b)(3), Rule 1005(b)(3), or Rule 1007 or during an examination of its compliance with Regulation SCI, include a review of the entity's classification of SCI events as de minimis SCI events under Rule 1002(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>827</SU>
                             While the facts and circumstances surrounding a particular SCI event will ultimately determine the severity of a given event, including whether the event is reasonably estimated to be a de minimis event, a wide range of factors may be relevant to an SCI entity in making such a determination. For example, such factors could include, but are not limited to: whether critical SCI systems are impacted; the duration of the SCI event; whether there is a loss of redundancy (that negatively impacts, for example, a source of power, telecommunications, or other key service); whether an alternate trading system is available following a trading system disruption; the size of the affected market trading volume; whether the processes for trade completion or clearance and settlement are adversely impacted; whether settlement is completed on time; whether an event is resolved prior to the market's open; whether a post-trade event is resolved before the market closes; whether a failover, despite being successful, results in a given system operating without a backup; and the number of securities symbols that are adversely affected.
                        </P>
                    </FTNT>
                    <P>
                        As described above, the de minimis exception from the immediate Commission notification requirements applies to systems compliance issues as well as systems disruptions and systems intrusions. The Commission believes that this approach strikes a balance that will help focus the Commission's and SCI entities' resources on those systems compliance issues with more significant impacts. Even if an SCI entity determines that the impact of the systems compliance issue is none or negligible, however, the Commission believes that it should have ready access to records regarding such systems compliance issues, and notes that Rule 1002 requires that an SCI entity take corrective action with respect to all SCI events, including de minimis systems compliance issues.
                        <SU>828</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>828</SU>
                             
                            <E T="03">See infra</E>
                             note 829 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission recognizes that in many cases, the discovery of a potential systems compliance issue may be of a different nature than the discovery of potential systems disruptions or systems intrusions, as the latter types of events often have an immediately apparent and negative impact on the operations of a given system of the SCI entity. In contrast, in many instances, a systems compliance issue may require the involvement of various personnel 
                        <PRTPAGE P="72322"/>
                        (potentially including compliance and/or legal personnel) and a period of time may be required to afford such personnel the chance to perform a preliminary legal analysis to analyze whether a systems compliance issue had, in fact, occurred. Because Rule 1002(b)(1) only requires notification to the Commission when responsible SCI personnel have a “reasonable basis to conclude” that a non-de minimis SCI event has occurred, the Commission believes it is appropriate for an SCI entity to notify the Commission of a non-de minimis systems compliance issue after it has conducted such a preliminary legal analysis, unless the nature of the issue makes it readily identifiable as a systems compliance issue.
                        <SU>829</SU>
                        <FTREF/>
                         Further, if an SCI entity determines that a systems compliance issue is de minimis, such event will not be required to be reported immediately to the Commission, but rather the SCI entity will be required to keep, and provide to representatives of the Commission upon request, records of such de minimis systems compliance issue. Thus, the Commission believes that, as adopted, the requirements with respect to systems compliance issues are reasonable because SCI entities are afforded flexibility to assess and understand potential SCI events and are not required to notify the Commission prior to forming a reasonable basis to conclude that an SCI event has occurred. The Commissions also believes that, as part of its oversight of the securities markets, it should have access to information regarding de minimis systems compliance issues when requested. And, although some commenters expressed concern that a systems compliance issue is a legal conclusion that requires time to analyze and could possibly expose the entity to liability if reported,
                        <SU>830</SU>
                        <FTREF/>
                         as discussed above, the Commission believes these concerns will be mitigated by the revised triggering standard for the obligations in Rule 1002.
                        <SU>831</SU>
                        <FTREF/>
                         However, while commenters are correct that the occurrence of a systems compliance issue may expose an SCI entity to liability,
                        <SU>832</SU>
                        <FTREF/>
                         the occurrence of an SCI event will not necessarily cause a violation of Regulation SCI. Further, the occurrence of a systems compliance issue also does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>829</SU>
                             At the same time, the Commission cautions SCI entities against unnecessarily delaying Commission notifications of SCI events, including systems compliance issues. The Commission notes that the notification requirement is triggered when responsible SCI personnel have a 
                            <E T="03">reasonable basis</E>
                             to conclude that an SCI event has occurred and not, for example, when responsible SCI personnel have 
                            <E T="03">definitively</E>
                             concluded that an SCI event has occurred. As discussed above, the Commission does not believe it is appropriate for an SCI entity to delay notifying its regulator of a systems compliance issue once the SCI entity has a reasonable basis to conclude there is one. 
                            <E T="03">See supra</E>
                             note 828 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>830</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 16; and NYSE Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>831</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>832</SU>
                             If an SRO fails to, among other things, comply with the provisions of the Exchange Act, the rules or regulations thereunder, or its own rules, the Commission is authorized to impose sanctions. 
                            <E T="03">See</E>
                             15 U.S.C. 78s(g).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Commission Legal Authority </HD>
                    <P>
                        As noted above, some commenters broadly questioned the Commission's legal authority to adopt certain provisions of Regulation SCI as proposed, including those relating to Commission notification of SCI events, as well as Commission notification of material systems changes.
                        <SU>833</SU>
                        <FTREF/>
                         Section 11A(a)(2) of the Exchange Act directs the Commission, having due regard for the public interest, the protection of investors, and the maintenance of fair and orderly markets, to use its authority under the Exchange Act to facilitate the establishment of a national market system for securities in accordance with the Congressional findings and objectives set forth in Section 11A(a)(1) of the Exchange Act. Among the findings and objectives in Section 11A(a)(1) is that “[n]ew data processing and communications techniques create the opportunity for more efficient and effective market operations” and “[i]t is in the public interest and appropriate for the protection of investors and the maintenance of fair and orderly markets to assure . . . the economically efficient execution of securities transactions.” In addition, Sections 6(b), 15A, and 17A(b)(3) of the Exchange Act impose obligations on national securities exchanges, national securities associations, and clearing agencies, respectively, to be “so organized” and “[have] the capacity to . . . carry out the purposes of [the Exchange Act].” 
                    </P>
                    <FTNT>
                        <P>
                            <SU>833</SU>
                             
                            <E T="03">See supra</E>
                             note 808 and accompanying text. 
                            <E T="03">See infra</E>
                             note 1268 (noting comments relating to the Commission's legal authority for the proposed access provision, which the Commission has determined not to adopt in its final rules because the Commission can adequately assess an SCI entity's compliance with Regulation SCI through existing recordkeeping requirements and examination authority, as well as through the new recordkeeping requirement in Rule 1005 of Regulation SCI).
                        </P>
                    </FTNT>
                    <P>Consistent with this statutory authority, the Commission is adopting Regulation SCI to require, among other things, that SCI entities: (1) Provide certain notices and reports to the Commission to improve Commission oversight of securities market infrastructure; and (2) have comprehensive policies and procedures in place to help ensure the robustness and resiliency of their technological systems, and also that their technological systems operate in compliance with the Exchange Act, rules thereunder, and with their own rules and governing documents. These requirements are important to furthering the directives in Section 11A(a)(2) of the Exchange Act that the Commission, having due regard for the public interest, the protection of investors, and the maintenance of fair and orderly markets, facilitate the establishment of a national market system for securities in accordance with the Congressional findings and objectives set forth in Section 11A(a)(1) of the Exchange Act, including the economically efficient execution of securities transactions. </P>
                    <P>
                        As discussed in Section I, the U.S. securities markets have been transformed in recent years by technological advancements that have enhanced the speed, capacity, efficiency, and sophistication of the trading functions that are available to market participants. Central to these technological advancements have been changes in the automated systems that route and execute orders, disseminate quotes, clear and settle trades, and transmit market data. At the same time, however, these technological advances have generated an increasing risk of operational problems with automated systems, including failures, disruptions, delays, and intrusions. Accordingly, in today's securities markets, properly functioning technology is central to the maintenance of fair and orderly markets, the national market system, and the efficient and effective market operations and the execution of securities transactions. While the Commission's ARP Inspection Program has been active in this area, the Commission has not adopted rules specific to these matters. The Commission believes that the adoption of Regulation SCI, with the modifications from the SCI Proposal as discussed above, and compliance with the regulation by SCI entities, will further the goals of the national market system. It will help to ensure the capacity, integrity, resiliency, availability, and security of the automated systems of entities important 
                        <PRTPAGE P="72323"/>
                        to the functioning of the U.S. securities markets, as well as reinforce the requirement that such systems operate in compliance with the Exchange Act and rules and regulations thereunder, thus strengthening the infrastructure of the U.S. securities markets and improving its resilience when technological issues arise. In addition, Regulation SCI establishes an updated and formalized regulatory framework, thereby helping to ensure more effective Commission oversight of these systems whose proper functioning is central to the maintenance of fair and orderly markets and for the continued operation of the national market system. For these reasons, the Commission disagrees with the comments questioning the Commission's legal authority to adopt Regulation SCI. 
                    </P>
                    <P>More specifically, the Commission disagrees with comment regarding its legal authority under Rule 1002(b) related to Commission notification of SCI events. As discussed above, having immediate notice and continuing updates of non-de minimis SCI events, quarterly reports related to de minimis systems disruptions and de minimis systems intrusions, and recordkeeping requirements for de minimis SCI events, directly enables the Commission to have more effective oversight of the systems whose proper functioning is central to the maintenance of fair and orderly markets and for the continued operation of the national market system. In this respect, Rule 1002(b) is integral to furthering the statutory purposes of Section 11A of the Act under which the Commission is directed to act. Moreover, the Commission underscores that the adopted Commission notification provisions would require immediate Commission notice of fewer SCI events than as proposed because the adopted definitions of SCI systems, indirect SCI systems, systems disruption, and systems compliance issue have been refined from the proposal, and de minimis SCI events are not subject to immediate notice. </P>
                    <P>
                        Some commenters also questioned the Commission's legal authority to require Commission notification of material systems changes.
                        <SU>834</SU>
                        <FTREF/>
                         As discussed in more detail below, the material systems change reports are intended to make the Commission and its staff aware of significant systems changes at SCI entities, and thereby improve Commission oversight of U.S. securities market infrastructure, which directly furthers the findings and objectives set forth in Section 11A(a)(1) of the Exchange Act.
                        <SU>835</SU>
                        <FTREF/>
                         The Commission believes that the adopted material systems change notification requirement will allow the Commission to more efficiently and effectively participate in discussions with SCI entities when systems issues occur and will allow Commission staff to effectively prepare for inspections and examinations of SCI entities. Moreover, Rule 1003(a), as adopted, differs significantly from the proposed requirements as it no longer requires 30-day advance notification, but rather requires quarterly reports of material systems changes. As such, the requirement is designed not to result in “close, minute regulation of computer systems and computer security.” 
                        <SU>836</SU>
                        <FTREF/>
                         Additionally, the Commission notes that Regulation SCI does not provide for a new review or approval process for SCI entities' material systems changes.
                        <SU>837</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>834</SU>
                             
                            <E T="03">See infra</E>
                             note 1046 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>835</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.4 (discussing the requirement to notify the Commission of material systems changes).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>836</SU>
                             
                            <E T="03">See infra</E>
                             note 1046.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>837</SU>
                             As noted below in Section IV.B.4, Commission staff will not use material systems change reports to require any approval of prospective systems changes in advance of their implementation pursuant to any provision of Regulation SCI, or to delay implementation of material systems changes pursuant to any provision of Regulation SCI.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Immediate Commission Notification—Proposed Rule 1000(b)(4)(i) </HD>
                    <P>
                        Commenters also specifically discussed proposed Rule 1000(b)(4)(i) regarding reporting to the Commission on immediate notification SCI events. One commenter stated that it generally supported the immediate notification requirement of proposed Rule 1000(b)(4)(i) in the case of material SCI events,
                        <SU>838</SU>
                        <FTREF/>
                         but other commenters were critical.
                        <SU>839</SU>
                        <FTREF/>
                         For example, some commenters stated that the Commission should adopt a materiality threshold which would only require an SCI entity to immediately report material SCI events.
                        <SU>840</SU>
                        <FTREF/>
                         Similarly, one group of commenters suggested a tiered method that would reserve immediate notification to the Commission for truly critical events “where the Commission's input would contribute to an expedient resolution,” while requiring SCI entities to have written policies and procedures that focus the SCI entity's attention primarily on taking corrective measures during an SCI event and maintaining records to provide information to the Commission and members and participants as appropriate.
                        <SU>841</SU>
                        <FTREF/>
                         Two commenters suggested that different reporting standards should apply to different types of systems, suggesting, for example, that immediate notification should be required only for higher priority systems.
                        <SU>842</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>838</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>839</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>840</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 13; FIF Letter at 4; ITG Letter at 12; NYSE Letter at 23; FINRA Letter at 10, 22; and OCC Letter at 13. One commenter stated that, in considering factors that would determine whether or not an SCI event is material, the Commission should consider the overall market disruption caused by the SCI event, the length of the event, the financial impact of the event, and the inability to meet core regulatory obligations regarding order handling and execution activities. 
                            <E T="03">See</E>
                             ITG Letter at 13. Similarly, two commenters stated that, with respect to systems compliance issues or systems intrusions, immediate notification SCI events should be limited to systems compliance issues or systems intrusions that the SCI entity reasonably estimates would have a material impact on its operations or on market participants. 
                            <E T="03">See</E>
                             MSRB Letter at 18; and Omgeo Letter at 15. Further, in the case of intrusions, one commenter stated that notifications could also include intrusions that would cause a malicious unauthorized access to confidential data, but recommended that other types of intrusions be subject to recordkeeping. 
                            <E T="03">See</E>
                             Omgeo Letter at 15. One group of commenters supported implementing a materiality threshold for systems compliance issues, which it stated should be based on factors such as the number of members affected, financial impact and operation impact, and these guidelines should be articulated in the SCI entities' policies and procedures. 
                            <E T="03">See</E>
                             Joint SROs Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>841</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>842</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 22 (suggesting, for example, that immediate Commission notification should not be required for SCI events that occur in systems that do not provide real-time data to the market); and SIFMA Letter at 13 (stating that that lower priority systems should only be reported on an aggregate and periodic basis).
                        </P>
                    </FTNT>
                    <P>
                        One commenter questioned the adequacy of the Commission's asserted basis and purpose for requiring notification for the vast majority of SCI events.
                        <SU>843</SU>
                        <FTREF/>
                         In this commenter's view, the Commission's asserted rationale for the Commission notification requirement 
                        <SU>844</SU>
                        <FTREF/>
                         would only support requiring immediate notification for a limited number of SCI events, where the Commission's involvement is necessary.
                        <SU>845</SU>
                        <FTREF/>
                         For other SCI events, in which the Commission would only be gathering and analyzing submitted information, the commenter stated that the Commission's rationale for requiring immediate notification is insufficient.
                        <SU>846</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>843</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 21-22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>844</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18119.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>845</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 22; 
                            <E T="03">see also</E>
                             Joint SROs Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>846</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 22.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters addressed the use of the term “immediately” in the proposed rule. One commenter characterized the proposed immediate reporting requirements as rigid, and questioned why reporting could not occur “promptly” with follow-up as reasonably requested by the Commission staff.
                        <SU>847</SU>
                        <FTREF/>
                         Another commenter stated that immediate notification is unrealistic and predicted 
                        <PRTPAGE P="72324"/>
                        that it could trigger an innumerable amount of false alarms.
                        <SU>848</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>847</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>848</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter 8.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters addressed SCI events that occur outside of normal business hours. Two commenters believed that an SCI entity should not be required to notify the Commission of an SCI event outside of normal business hours.
                        <SU>849</SU>
                        <FTREF/>
                         Other commenters stated that material events should require immediate notification to the Commission, but all other types of events should be reported by the next business day.
                        <SU>850</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>849</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 21; and BATS Letter at 12. FINRA also stated that an SCI entity should have one full business day to report an SCI event.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>850</SU>
                             
                            <E T="03">See, e.g.,</E>
                             DTCC Letter at 9 (stating that, outside of normal business hours, an SCI entity should only be required to notify the Commission of the most critical events; 
                            <E T="03">i.e.,</E>
                             those with the potential to impact the core functions and critical operations of the SCI entity); and OCC Letter at 14 (stating that when an event is material because it could have a market-wide impact or impact the core functions of an SCI entity, immediate notification should be required even outside of normal business hours, but all other SCI events should be reported no later than the next business day).
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that immediate notification of an SCI event may be difficult where an SCI entity uses a third party to operate its systems, and therefore believed that an SCI entity should not be responsible for reporting an SCI event caused by a third party unless there is a material impact to the market or the SCI entity's ability to meet its service level agreements.
                        <SU>851</SU>
                        <FTREF/>
                         This commenter stated that the rule should permit SCI entities flexibility on how to address third party issues and requested further guidance from the Commission in this area.
                        <SU>852</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>851</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 22; 
                            <E T="03">see also</E>
                              
                            <E T="03">supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems” as it relates to third parties).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>852</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 22.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Immediate Notification of SCI Events: Adopted Rule 1002(b)(1)</HD>
                    <P>
                        Adopted Rule 1002(b)(1) requires each SCI entity to notify the Commission of an SCI event immediately upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred (unless it is a de minimis SCI event). Such notification may be provided orally (
                        <E T="03">e.g.,</E>
                         by telephone) or in writing (
                        <E T="03">e.g.,</E>
                         by email or on Form SCI). Although many commenters were critical of the immediate notification provision, Rule 1002(b)(1) substantially retains the requirements of proposed Rule 1000(b)(4)(i), but is modified in certain respects in response to comments.
                    </P>
                    <P>
                        The Commission has considered the views of commenters who stated that the Commission should require immediate notification only for material SCI events, or when Commission involvement would contribute to an expedient resolution.
                        <SU>853</SU>
                        <FTREF/>
                         Given the Commission's oversight responsibilities over SCI entities and the U.S. securities market generally, the notification rule is not intended to be limited to instances in which SCI entities might believe that it would be useful for the Commission to provide input. SCI event notifications also serve the function of providing the Commission and its staff with information about the potential impact of an SCI event on the securities markets and market participants more broadly, which potential impacts may not be readily apparent or important to the SCI entity reporting such an event. Moreover, the Commission believes that there will be instances in which an SCI entity will not know the significance of an SCI event at the time of the occurrence of an event, or whether such event (or, potentially, the aggregated impact of several SCI events occurring, for example, across many SCI entities) will warrant the Commission's input or merit the Commission's awareness, nor does the Commission believe it should be solely within an SCI entity's discretion to make such a determination. And SCI entities retain the flexibility to revise their initial assessments should they subsequently determine that the event in question was incorrectly initially assessed to be a de minimis event (or incorrectly initially assessed to not be a de minimis event). Consequently, the Commission does not agree with commenters who stated that only material SCI events should be reported to the Commission immediately.
                        <SU>854</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>853</SU>
                             
                            <E T="03">See supra</E>
                             notes 838-846 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>854</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 842 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has also considered comments that the term “immediately” as used in proposed Rule 1000(b)(4) is rigid and unrealistic.
                        <SU>855</SU>
                        <FTREF/>
                         The Commission, in adopting Rule 1002(b), has retained the requirement that SCI entities must notify the Commission immediately; however, as discussed in detail above,
                        <SU>856</SU>
                        <FTREF/>
                         the triggering standard has been modified so that the notification obligations of Rule 1002(b) are triggered only upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred. The Commission believes this modification responds to commenters concerns that the “immediate” reporting requirement is too rigid or would pose practical difficulties, as it allows additional time for escalation to senior SCI entity personnel and for the performance of preliminary analysis and assessment regarding whether an SCI event has, in fact, occurred before requiring notification to the Commission. As such, the Commission believes that the immediate notification requirement of Rule 1002(b)(1) will not unduly cause “false alarms,” as one commenter stated.
                        <SU>857</SU>
                        <FTREF/>
                         At the same time, the Commission believes that the immediate notification requirement, as adopted, will help ensure that the Commission and its staff are kept apprised of SCI events after they occur, and as their impact unfolds and is mitigated and, ultimately, as the SCI entity engages in corrective action to resolve the SCI events. Additionally, the Commission notes that immediate notifications made pursuant to Rule 1002(b)(1) may be made orally (
                        <E T="03">e.g.,</E>
                         by telephone) or in a written form (
                        <E T="03">e.g.,</E>
                         by email or on Form SCI).
                        <SU>858</SU>
                        <FTREF/>
                         The Commission notes that, by not prescribing the precise method of communication for an immediate notification, SCI entities are afforded the flexibility to determine the most effective and efficient method to communicate with the Commission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>855</SU>
                             
                            <E T="03">See supra</E>
                             note 847 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>856</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>857</SU>
                             
                            <E T="03">See supra</E>
                             note 848 and accompanying text. The Commission notes that, if an SCI entity at some point after submitting an immediate notification concludes after further investigation and analysis that it was incorrect in its initial determination that an SCI event had occurred, the SCI entity should alert the Commission of its updated assessment pursuant to Rule 1002(b)(3). Relatedly, Rule 1002(b) is designed to provide SCI entities flexibility in notifying the Commission of the details regarding an SCI event (for example, through the ability to provide the Rule 1002(b)(2) written notification on a good faith, best efforts basis) and time to assess and analyze the SCI event (for example, by requiring that the Rule 1002(b)(2) written notification only provide a description of the SCI event, including the system(s) affected, and with additional information only required to the extent available at that time).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>858</SU>
                             The Commission notes that, prior to the compliance date of Regulation SCI, Commission staff intends to notify SCI entities of the email addresses, phone numbers, and contact persons that SCI entities should use when notifying the Commission of SCI events under Rule 1002(b).
                        </P>
                    </FTNT>
                    <P>
                        The Commission has also considered comments that immediate notification should not be required outside of normal business hours, or that it should only be required outside of normal business hours in the case of material SCI events.
                        <SU>859</SU>
                        <FTREF/>
                         The Commission notes that the adopted rule will afford SCI entities considerable flexibility in how to communicate an immediate notification to the Commission—that is, SCI entities may satisfy the immediate 
                        <PRTPAGE P="72325"/>
                        notification requirement simply by communicating with the Commission via telephone or email. In addition, because an SCI entity's obligation to report to the Commission is not triggered until responsible SCI personnel has a reasonable basis to conclude that an SCI event has occurred,
                        <SU>860</SU>
                        <FTREF/>
                         the Commission does not believe that timely notification, even outside of normal business, is so onerous that it necessitates allowing a full business day to comply. Particularly because it has determined to exclude de minimis SCI events from the immediate notification requirement, the Commission believes that it is reasonable to require that an SCI event (except those specified in Rule 1002(b)(5)) be reported to the Commission orally (
                        <E T="03">e.g.,</E>
                         by telephone) or in writing (
                        <E T="03">e.g.,</E>
                         by email or on Form SCI) when responsible SCI personnel have a reasonable basis to conclude that an SCI event has occurred, even if such communication may be outside of normal business hours. Because the rule provides flexibility to more easily enable communication—by permitting oral notification—of the fact of an SCI event to the Commission, and because only non-de minimis SCI events are subject to this requirement, the Commission believes notice to the Commission is appropriate sooner rather than later. In addition, as discussed above, the Commission believes that there may be situations where the severity of an SCI event may not be immediately apparent to an SCI entity experiencing the event, but the Commission, from its unique position, may determine as a result of receiving multiple immediate notifications, each related to an SCI event of a similar nature, that the SCI event is part of a pattern of a larger, more significant occurrence. The Commission is therefore adopting Rule 1002(b) to require that an SCI entity notify the Commission of an SCI event immediately upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, without an exception for periods outside of normal business hours.
                    </P>
                    <FTNT>
                        <P>
                            <SU>859</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 849 and 794-797 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>860</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <P>
                        In addition, as noted above, the information submitted to the Commission pursuant to Regulation SCI will be treated as confidential, subject to applicable law 
                        <SU>861</SU>
                        <FTREF/>
                         and, as noted in Sections IV.B.1.b.i and IV.B.2.a, the occurrence of an SCI event does not necessarily mean that an SCI entity has violated Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>861</SU>
                             
                            <E T="03">See supra</E>
                             note 674.
                        </P>
                    </FTNT>
                    <P>
                        The Commission disagrees with the commenter who stated that the Commission should not require SCI entities to be responsible for reporting an SCI event caused by a third party because immediate notification would be difficult.
                        <SU>862</SU>
                        <FTREF/>
                         An SCI event, whether or not caused by a third party system, by definition relates to an SCI system or indirect SCI system. As explained in Section IV.A.2 above (discussing the definitions of “SCI systems” and “indirect SCI systems”), the Commission has adopted the definition of SCI systems to include, specifically, those systems of SCI entities that would be reasonably likely to impact the protection of investors and the maintenance of fair and orderly markets and an SCI entity's operational capability, and has not excluded third party systems from the definition. As stated above, if an SCI entity is uncertain of its ability to manage a third-party relationship to satisfy the requirements of Regulation SCI, then it would need to reassess its decision to outsource the applicable system to such third party.
                        <SU>863</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>862</SU>
                             
                            <E T="03">See supra</E>
                             notes 851-852 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>863</SU>
                             
                            <E T="03">See supra</E>
                             note 260 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In response to comment that SCI entities would be required to provide notification reports multiple times to different Commission staff for the same event,
                        <SU>864</SU>
                        <FTREF/>
                         the Commission notes that rule does not include such a requirement. In addition, the Commission also disagrees with the commenter who stated that, for systems disruptions, notifications should not be required from each separate entity where a disruption impacts multiple SCI entities.
                        <SU>865</SU>
                        <FTREF/>
                         Excusing immediate notification where a given event seems to be affecting multiple SCI entities would not be appropriate because the Commission, as the centralized receiver of notifications, will be the entity that will be in a position to determine whether, in fact, SCI entities are concurrently experiencing the same SCI event. Moreover, even if a given event affects multiple SCI entities, it may be the case that the event impacts each SCI entity and the affected systems in a different manner, and thus the Commission believes it is important to receive individual notifications from each affected SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>864</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 805 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>865</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Written Commission Notification: Proposed Rule 1000(b)(4)(ii)</HD>
                    <P>
                        Commenters also specifically discussed and suggested alternatives to proposed Rule 1000(b)(4)(ii), which would have required an SCI entity, within 24 hours of any responsible SCI personnel becoming aware of any SCI event, to submit a written notification pertaining to such SCI event to the Commission. Many commenters stated that the proposed 24-hour time frame was too short or burdensome.
                        <SU>866</SU>
                        <FTREF/>
                         Several commenters specifically suggested that the Commission extend the time frame to allow SCI entities to attend to the SCI event without also devoting resources to notifying the Commission, suggesting different time frames they believed to be appropriate.
                        <SU>867</SU>
                        <FTREF/>
                         One commenter suggested that SCI entities be given until 24 to 48 hours 
                        <E T="03">after</E>
                         final resolution of the SCI event to submit a written notification.
                        <SU>868</SU>
                        <FTREF/>
                         Another commenter similarly recommended that, where real-time notification is needed, written notification should not be required unless an SCI event remains unresolved after a reasonable period (such as 10 or 15 days).
                        <SU>869</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>866</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 23; FINRA Letter at 19; BATS Letter at 12; DTCC Letter at 9; MSRB Letter at 18; SIFMA Letter at 13; FIF Letter at 5; BIDS Letter at 10; Omgeo Letter at 17; and CME Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>867</SU>
                             Commenters suggested time frames of 48 hours (CME Letter at 9); 72 hours (OCC Letter at 12; DTCC Letter at 9, 11 (noting, however, that details surrounding an SCI event should not be required to be provided in writing until after the investigation of the event is complete and the event has been resolved)); and five business days (BIDS Letter at 10).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>868</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 20. This commenter further suggested that, if an SCI event has not been fully resolved within a reasonable period, 
                            <E T="03">e.g.,</E>
                            10 or 15 days, an SCI entity could be required to submit written notification based on currently available information at the end of that period, with periodic status updates via telephone or email, and a final written submission within 24 to 48 hours after the event has been fully resolved.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>869</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 14.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters also suggested that, if the Commission retains the 24-hour requirement, it should require provision of less information. For example, one commenter suggested that SCI entities should only be required to provide whatever information is sufficiently reliable at that time.
                        <SU>870</SU>
                        <FTREF/>
                         Two other commenters stated that SCI entities should not be required to include an estimate of the markets and participants 
                        <PRTPAGE P="72326"/>
                        impacted by an SCI event or to quantify such impact because this requirement may create a risk of civil liability for the SCI entity.
                        <SU>871</SU>
                        <FTREF/>
                         Another commenter recommended that the rule require only a brief written summary that is one or two paragraphs, which could be supplemented by oral communications and a longer summary within 15 days after an SCI event has been fully resolved.
                        <SU>872</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>870</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 20. This commenter also suggested that the rule require an SCI entity to assess the “business impact” of an SCI event, noting that this information may provide more context than requiring an SCI entity to estimate the number of market participants impacted by an SCI event (which in some cases could be zero, but still have a negative impact on the SCI entity). 
                            <E T="03">See</E>
                             FINRA Letter at 30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>871</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 10; and Omgeo Letter at 30. Omgeo added that such a calculation would be difficult to compute, likely inaccurate, and of little use to the Commission.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>872</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 17.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the information provided to the Commission via notification of an SCI event, one commenter suggested that the rule provide a safe harbor for entities and employees for either inadvertent omissions in a submitted report, or when a good faith, documented determination is made that no report is required.
                        <SU>873</SU>
                        <FTREF/>
                         One commenter stated that that the Commission should expressly provide that initial written submissions are to be made on a best efforts basis and SCI entities will incur no liability or penalty for any unintentional inaccuracies or omissions contained in these submissions.
                        <SU>874</SU>
                        <FTREF/>
                         Some commenters stated that entities should not be liable for information that is later found to be incomplete or inaccurate.
                        <SU>875</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>873</SU>
                             
                            <E T="03">See id.</E>
                             at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>874</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>875</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 14; and UBS Letter at 4 (stating that SCI entities acting in good faith should not be held accountable if details offered in reports to the Commission are substantially different from what is revealed by further analysis).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters 
                        <SU>876</SU>
                        <FTREF/>
                         questioned the purpose of requiring that information disseminated to members and participants (under proposed Rule 1000(b)(5)) be copied and attached to Form SCI as part of notifications to the Commission, and considered it “an overly broad inclusion of communications” that would have “a chilling effect on communications between the SCI entities and their members and participants,” 
                        <SU>877</SU>
                        <FTREF/>
                         while another commenter argued that, when an exchange is having a technology issue, many members may be reaching out to the exchange's staff with requests for information and status. Therefore, that commenter questioned the feasibility, need, and potential impact of the proposed requirement that SCI entities provide a copy of any information disseminated to date regarding the SCI event to their members or participants.
                        <SU>878</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>876</SU>
                             Because the requirement to provide information disseminated to an SCI entity's members or participants is now included in the Final Report (Rule 1002(b)(4)) instead of with the 24-written notification requirement as proposed, the Commission's response to these comments is discussed below in the subsection “Final Report: Adopted Rule 1002(b)(4).”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>877</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>878</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that, to reduce the cost of compliance, the Commission should accept the same notifications of service interruptions that an ATS already provides to its subscribers.
                        <SU>879</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>879</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 11.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also provided suggestions for limiting the circumstances for which 24-hour written notification would be required under proposed Rule 1000(b)(4)(ii). One commenter stated that only SCI events that materially impact an SCI entity's operations or market participants should be subject to the 24-hour written notification requirement, but questioned whether 24 hours was realistic even for those events.
                        <SU>880</SU>
                        <FTREF/>
                         One commenter suggested that proposed Rule 1000(b)(4)(ii) only apply to significant SCI events and that other events only be subject to a recordkeeping requirement.
                        <SU>881</SU>
                        <FTREF/>
                         In addition, some commenters suggested that if an SCI entity has provided oral notification to the Commission, it should not be required to file written notice within 24 hours after the initial report unless reasonably requested by the Commission.
                        <SU>882</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>880</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>881</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>882</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 12; and Omgeo Letter at 17. 
                            <E T="03">See also</E>
                             DTCC Letter at 10; and OCC Letter at 14 (suggesting 72 hours to provide written information after providing verbal notification).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Written Notification Within 24 Hours: Adopted Rule 1002(b)(2)</HD>
                    <P>Adopted Rule 1002(b)(2) requires an SCI entity, within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that the SCI event has occurred, to submit a written notification pertaining to such SCI event to the Commission. Rule 1002(b)(2) allows for such written notifications to be made on a good faith, best efforts basis and requires that it include: (i) A description of the SCI event, including the system(s) affected; and (ii) to the extent available as of the time of the notification: the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event.</P>
                    <P>
                        The Commission has considered comments stating that 24 hours is too short and burdensome a duration for an SCI entity to submit a compliant written notification.
                        <SU>883</SU>
                        <FTREF/>
                         The Commission understands commenters' concerns that SCI entities may still be actively investigating and working to resolve an SCI event and that information it initially provides to the Commission about an SCI event may not ultimately prove correct.
                        <SU>884</SU>
                        <FTREF/>
                         Therefore, in line with commenters' concerns regarding a good faith and best efforts standard,
                        <SU>885</SU>
                        <FTREF/>
                         the Commission has modified the 24-hour written notification requirement in adopted Rule 1002(b) to make clear that the written notification should be provided on a “good faith, best efforts basis.” This modification acknowledges that a written notification provided within 24 hours may provide only a preliminary assessment of the SCI event, that additional information may come to light after the initial 24-hour period, and that the initial assessment may prove in retrospect to be incorrect or incomplete. Consequently, the adopted rule requires that the written notification provided within 24 hours be submitted on a good faith, best efforts basis, and does not require that the written notification be a comprehensive or complete assessment of the SCI event (unless, of course, an SCI entity has completed a full assessment by such time). The Commission believes that a “good faith” standard will help to ensure that SCI entities will not be accountable for unintentional inaccuracies or omissions contained in these submissions, and a “best efforts” standard will help to ensure that SCI entities will make a diligent and timely attempt to provide all the information required by the written notification requirement. The Commission also notes that an SCI entity will not need to submit a written notification where an SCI entity documents that an SCI event is determined to be a de minimis SCI event, other than including de minimis systems disruptions and de minimis systems intrusions in the quarterly report required by Rule 1002(b)(5). As discussed in further detail below, in the event that new information comes to light or previously reported information is found to be materially incorrect, adopted Rule 1002(b)(3) requires an SCI entity to update the information at that 
                        <PRTPAGE P="72327"/>
                        time, and does not require that such updates be written.
                        <SU>886</SU>
                        <FTREF/>
                         The Commission believes these modifications will help ensure that SCI entities are able to provide the information required by Rule 1002(b)(2) within 24 hours, and therefore the Commission is not modifying the timeframe to extend beyond 24 hours, as requested by several commenters.
                        <SU>887</SU>
                        <FTREF/>
                         Moreover, because the information need only be provided on a good faith, best efforts basis and, pursuant to Rule 1002(b)(3), updates can be provided on a regular basis to correct any materially incorrect information previously provided or when new material information is discovered, the Commission disagrees with commenters that stated that the information required by Rule 1002(b) should be provided only after resolution of the SCI event. The Commission continues to believe that Rule 1002(b)(2)'s requirement to provide information to the Commission within 24 hours is appropriately tailored to help the Commission and its staff quickly assess the nature and the scope of an SCI event and will contribute to more timely and effective Commission oversight of systems whose proper functioning is central to the maintenance of fair and orderly markets, and that this would particularly be the case for SCI events that are not yet resolved.
                        <SU>888</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>883</SU>
                             
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 866 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>884</SU>
                             
                            <E T="03">See supra</E>
                             notes 873-875 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>885</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>886</SU>
                             
                            <E T="03">See infra</E>
                             note 909 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>887</SU>
                             
                            <E T="03">See supra</E>
                             notes 867-869 and accompanying text; and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18119.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>888</SU>
                             
                            <E T="03">See supra</E>
                             notes 868 and 872 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Adopted Rule 1002(b)(2) is also responsive to comments urging the Commission to require less information in a 24-hour written notification.
                        <SU>889</SU>
                        <FTREF/>
                         Specifically, whereas proposed Rule 1000(b)(4) required a detailed description of the SCI event, adopted Rule 1002(b)(2)(i) specifies that an SCI entity must only provide “a description of the SCI event, including the system(s) affected.” Additional information is only required to the extent available as of the time of the notification, which includes an “SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event.” 
                        <SU>890</SU>
                        <FTREF/>
                         This information is the type of necessary information that SCI entities are able to provide in a short timeframe and that the Commission has come, over time, to rely upon to properly assess systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>889</SU>
                             
                            <E T="03">See supra</E>
                             notes 870-872 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>890</SU>
                             Rule 1002(b)(2)(ii). The information required to be provided in Rule 1002(b)(2)(ii) is a subset of information proposed to be required under Rule 1000(b)(4)(iv)(A)(1)-(2) of the SCI Proposal.
                        </P>
                    </FTNT>
                    <P>Additionally, the Commission notes that adopted Rule 1002(b) does not require that an SCI entity provide the Commission, at the time of the initial notice to the Commission, with its current assessment of the SCI event, including a discussion of the determination of whether it is subject to a dissemination requirement, as proposed in Rule 1000(b)(4).</P>
                    <P>
                        The Commission has also determined to further refine the scope of information that needs to be reported in the 24-hour written notification by requiring that the following items instead be included in the final report under Rule 1002(b)(4), rather than in the 24-hour written notification required by Rule 1002(b)(2): A description of the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss.
                        <SU>891</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>891</SU>
                             At the same time, if such information is known at the time of the notification, the SCI entity will be required to provide it pursuant to Rule 1002(b)(2)(ii)'s requirement that the SCI entity provide “any other pertinent information known . . . about the SCI event.” Additionally, such information would be provided under the requirement to provide the Commission with regular updates under Rule 1002(b)(3)'s requirement to provide any of the information listed in Rule 1002(b)(2)(ii) if it becomes available after the time of submission of the 24-hour notification. The Commission also notes that Rule 1002(b)(4)(ii) requires that an SCI entity include in the final report a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding an SCI event to any of its members or participants.
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters who suggested that the Commission limit the events for which 24-hour written notification would be required to material events,
                        <SU>892</SU>
                        <FTREF/>
                         the Commission notes that it has partially responded to such comments by providing an exception to the immediate notification requirement for de minimis events in Rule 1002(b)(5). The Commission believes that this exception should reduce the overall number of SCI events subject to immediate notification requirements as compared to what would have been required if the SCI Proposal was adopted without modification and, consequently, the requirement to submit a written notification within 24 hours of an SCI event, thereby alleviating some of the burdens about which commenters expressed concerns. Moreover, the Commission believes that a materiality threshold would likely exclude from the 24-hour written notification a large number of SCI events that are not de minimis SCI events but that the Commission, as part of its oversight role, should be updated on so that the Commission and its staff can quickly assess the nature and scope of those SCI events and potentially assist the SCI entity in identifying the appropriate response, including ways to mitigate the impact of SCI events on investors and promote the maintenance of fair and orderly markets. The Commission reemphasizes that the information to be provided under the 24-hour written notification would represent the SCI entity's preliminary assessment—performed on a good faith, best efforts basis—of the SCI event, and only certain key information is required under the 24-hour written notification, with “other pertinent information” required only where “known by the SCI entity” within the 24-hour timeframe. For these reasons, the Commission has determined not to adopt a materiality threshold for the requirement that an SCI entity update the Commission within 24 hours after it has a reasonable basis to conclude that an SCI event has occurred.
                    </P>
                    <FTNT>
                        <P>
                            <SU>892</SU>
                             
                            <E T="03">See supra</E>
                             note 880 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Additionally, the Commission disagrees with those commenters who stated that written notification should only be required when reasonably requested by the Commission.
                        <SU>893</SU>
                        <FTREF/>
                         The Commission believes that it should be notified of all SCI events and that all SCI events (other than those specified in Rule 1002(b)(5)) should be subject to the 24-hour written notification requirement because, by articulating in a single notification what is currently known about an SCI event and the steps expected to be taken to respond to the SCI event, the Commission will be better able to assess the nature and scope of, and respond to, SCI events and potentially assist SCI entities in identifying the appropriate response, including ways to mitigate the impact of SCI events on investors and promote the maintenance of fair and orderly markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>893</SU>
                             
                            <E T="03">See supra</E>
                             note 882 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In response to the comment that the Commission should accept the same notifications of service interruptions that an ATS provides to its 
                        <PRTPAGE P="72328"/>
                        subscribers,
                        <SU>894</SU>
                        <FTREF/>
                         the Commission believes that SCI ATSs can use the types of information contained in ATS notices to subscribers when completing Form SCI, but nevertheless believes that it is more useful and efficient for the Commission and its staff to be able to have all SCI event notifications standardized in a single format (
                        <E T="03">i.e.,</E>
                         Form SCI).
                    </P>
                    <FTNT>
                        <P>
                            <SU>894</SU>
                             
                            <E T="03">See supra</E>
                             note 879 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, the information required under the adopted 24-hour written notification requirement has been refined as compared with the requirements in the proposal. Consequently, the Commission believes that SCI entities should be able to provide the Commission with this information in a written format, and does not agree that such information should be provided in an oral format, as requested by some commenters, regardless of the manner in which the immediate notification was provided to the Commission.
                        <SU>895</SU>
                        <FTREF/>
                         The Commission emphasizes that regular updates provided under Rule 1002(b)(3) may, however, be provided either orally or in written form.
                        <SU>896</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>895</SU>
                             
                            <E T="03">See supra</E>
                             notes 872 and 882 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>896</SU>
                             
                            <E T="03">See infra</E>
                             note 911 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters that stated SCI entities should not be required to include an estimate of the market participants impacted by an SCI event or to quantify such impact because this requirement may create a risk of civil liability for the SCI entity,
                        <SU>897</SU>
                        <FTREF/>
                         the Commission notes that the information submitted to the Commission pursuant to Regulation SCI will be treated as confidential, subject to applicable law, including amended Rule 24b-2.
                        <SU>898</SU>
                        <FTREF/>
                         Moreover, the requirement to provide a 24-hour written notification does not itself create a risk of civil liability, but the Commission acknowledges that the information provided to it may be subject to FOIA requests.
                    </P>
                    <FTNT>
                        <P>
                            <SU>897</SU>
                             
                            <E T="03">See supra</E>
                             note 871.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>898</SU>
                             
                            <E T="03">See supra</E>
                             notes 802-803 and accompanying text. For a discussion of the amendment to Rule 24b-2, 
                            <E T="03">see infra</E>
                             notes 1245-1248 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Regarding the comment that the requirement to include an estimate of the markets and participants impacted by an SCI event or to quantify such impact would be difficult to compute, likely inaccurate, and of little use to the Commission,
                        <SU>899</SU>
                        <FTREF/>
                         the Commission disagrees. The rule requires an SCI entity to provide its current assessment of the types and number of market participants potentially affected by the SCI event and the potential impact of the SCI event on the market, to the extent this information is available as of the time of the notification, rather than an exact computation. In addition, the rule does not require that the assessment be submitted only if the SCI entity ensures that it is free of inaccuracies. Further, contrary to the commenter's suggestion, the Commission believes that such estimates will be of significant use to the Commission and its staff in understanding the potential severity of the SCI event. In addition, because the SCI entity is likely to be in the best position to assess an SCI event, the Commission also believes that an assessment of the impact of an SCI event on markets and participants is useful because it afford the Commission the opportunity to learn the SCI entity's perspective on the potential or actual impact of an SCI event.
                        <SU>900</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>899</SU>
                             
                            <E T="03">See supra</E>
                             note 871 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>900</SU>
                             The Commission notes that SCI entities retain the flexibility to provide additional information to the Commission as part of their assessments, such as providing the “business impact” of an SCI event, as suggested by one commenter. 
                            <E T="03">See supra</E>
                             note 870.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Written Commission Updates: Proposed Rule 1000(b)(4)(iii)</HD>
                    <P>
                        Commenters also addressed proposed Rule 1000(b)(4)(iii), which required an SCI entity to provide the Commission written updates pertaining to an SCI event on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, until the SCI event was resolved. Some commenters urged the Commission to provide clarity on the definition of “resolved.” 
                        <SU>901</SU>
                        <FTREF/>
                         For example, one commenter suggested that the Commission should define the resolution of an SCI event to be when the affected SCI systems have been normalized,
                        <SU>902</SU>
                        <FTREF/>
                         and another commenter stated that there should be a precise definition of when an SCI event is resolved and that definition should be linked directly to the definition of the SCI event itself.
                        <SU>903</SU>
                        <FTREF/>
                         Other commenters expressed concern that the continuing update requirement could divert resources from resolution of the SCI event and suggested that updates be required only to the extent they would not interfere with event resolution.
                        <SU>904</SU>
                        <FTREF/>
                         One commenter stated that continual updates should only be necessary if the SCI entity had not resolved the event within a reasonable period, such as 10 to 15 days.
                        <SU>905</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>901</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 11; and Omgeo Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>902</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>903</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>904</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 19; and OCC Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>905</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 20.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters addressed the method of providing updates. For example, one commenter stated that only oral communication should be required when an SCI event is ongoing, and that the rule should allow a written supplement to a final or post mortem report if additional information comes to light regarding the SCI event.
                        <SU>906</SU>
                        <FTREF/>
                         Another commenter suggested that updates should be permitted to be in writing or provided orally based on the judgment of the SCI entity.
                        <SU>907</SU>
                        <FTREF/>
                         Finally, one commenter stated that requests for updates regarding SCI events should only be permitted to come from senior staff at the Commission.
                        <SU>908</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>906</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>907</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>908</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 24.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Regular Updates: Adopted Rule 1002(b)(3)</HD>
                    <P>Rule 1002(b)(3) requires that, until such time as an SCI event is resolved, and the SCI entity's investigation of the SCI event is closed, an SCI entity provide the Commission with updates pertaining to the SCI event on a regular basis, or at such frequency as reasonably requested by a representative of the Commission. Updates are required to correct any materially incorrect information previously provided, or when new material information is discovered, including not limited to, any of the information listed in Rule 1002(b)(2)(ii).</P>
                    <P>
                        While the Commission recognizes that providing the Commission with such updates imposes an additional reporting requirement on SCI entities, the Commission also believes that updates are important to allow the Commission to fully monitor the SCI event. In addition, the Commission believes that the update requirement will encourage SCI entities to formalize their processes for gathering information on SCI events, which will help to ensure that responsible SCI personnel receive accurate and updated information on SCI events as they are being resolved, and further, that this process may be helpful to SCI entities when providing information about SCI events to their members or participants. Also, because the Commission has revised the requirements of the 24-hour notification to allow SCI entities to provide information on a good faith, best efforts basis and has limited the scope of information required in that report as discussed above, the Commission believes that updates to the Commission to correct materially incorrect information previously reported or when new material information is 
                        <PRTPAGE P="72329"/>
                        discovered as required by the rule is important to keep the Commission up to date with accurate information, including the following: The SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event. Consequently, the Commission does not agree with the commenter who suggested that updates should be only required if an SCI event has not been resolved within a reasonable amount of time, such as 10 to 15 days.
                        <SU>909</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>909</SU>
                             
                            <E T="03">See supra</E>
                             note 870 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that updates regarding this information are important to enhance the Commission's oversight of the securities markets and its informed and continued understanding of an SCI event. Moreover, the Commission underscores that updates are only required to the extent that they correct any 
                        <E T="03">materially</E>
                         incorrect information previously provided or when new 
                        <E T="03">material</E>
                         information is discovered, including but not limited to, any of the information listed in Rule 1002(b)(2)(ii), thereby alleviating the burden to SCI entities of providing such updates absent such circumstances.
                        <SU>910</SU>
                        <FTREF/>
                         The Commission has also eased the requirements of the proposed update provision by eliminating the proposed requirements that an SCI entity attach a copy of any information disseminated to date regarding the SCI event to its members or participants or on the SCI entity's publicly available Web site; a description of the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. Instead, these information requirements must only be provided as part of the final report required by Rule 1002(b)(4), and the Commission therefore believes that burdens associated with the continuing update requirement will be streamlined because SCI entities will not need to devote resources to providing written updates while an SCI event is ongoing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>910</SU>
                             The requirement that updates regarding new or corrected information be provided on a regular basis (unless an alternative, specific frequency is reasonably requested by a representative of the Commission) is designed to take into account the fact that new or updated information may develop at different frequencies for different SCI events.
                        </P>
                    </FTNT>
                    <P>
                        At the same time, the Commission is cognizant of the burdens associated with requiring written updates and therefore has revised the update requirement in adopted Rule 1002(b)(3) to remove the proposed requirement that such updates be provided in written form. Thus, submission of updates may be provided either orally or in written form, and will result in a lighter burden on SCI entities than the proposed requirement, and is responsive to commenters that suggested that SCI entity resources would be better directed to resolving an SCI event.
                        <SU>911</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>911</SU>
                             
                            <E T="03">See supra</E>
                             note 791 and accompanying text. SCI entities may, but are not required to, utilize Form SCI to submit such updates. 
                            <E T="03">See</E>
                             Section IV.D (discussing Form SCI). The Commission also believes that, to the extent commenters suggested that the Commission permit oral updates, they did so because, at least in part, oral updates are less burdensome to SCI entities than written updates. 
                            <E T="03">See supra</E>
                             notes 906-907 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        In response to comment that the Commission provide guidance to clarify when an SCI event has been “resolved” 
                        <SU>912</SU>
                        <FTREF/>
                         and in line with the particular comment that the concept of resolution should be linked directly to the definition of the SCI event itself,
                        <SU>913</SU>
                        <FTREF/>
                         the Commission believes that an SCI event is resolved when the event no longer meets the definitions of a systems disruption, systems intrusion, or systems compliance issue, as defined in Rule 1000, and that an SCI entity's Rule 1002(b) reporting obligations are completed when an SCI entity submits a final report as required by Rule 1002(b)(4). Further, the Commission does not believe that it is necessary to prescribe that requests to SCI entities regarding updates should come solely from senior Commission staff, as suggested by one commenter.
                        <SU>914</SU>
                        <FTREF/>
                         The Commission believes that requiring an SCI entity to update the Commission at such frequency as reasonably requested by a representative of the Commission provides appropriate flexibility to the Commission to request additional information as necessary, but does not anticipate that requests will be made by multiple members of the Commission staff because the Commission expects that such requests would be coordinated by a particular group of Commission staff that are assigned to handle specific reports from SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>912</SU>
                             
                            <E T="03">See supra</E>
                             notes 902-903 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>913</SU>
                             
                            <E T="03">See supra</E>
                             note 903 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>914</SU>
                             
                            <E T="03">See supra</E>
                             note 802 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Final Report: Adopted Rule 1002(b)(4)</HD>
                    <P>Adopted Rule 1002(b)(4) requires that if an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 days of the occurrence of the SCI event, then within five business days after the resolution of the SCI event and closure of the SCI entity's investigation regarding the SCI event, the SCI entity is to submit a final written notification pertaining to such SCI event to the Commission (“final report”). The final report is required to include: (i) A detailed description of: The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event; (ii) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and (iii) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. Rule 1002(b)(4) also specifies that, if an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 days of the occurrence of the SCI event, then, the SCI entity is required to submit a written notification pertaining to such SCI event to the Commission within 30 days after the occurrence of the SCI event containing the information required in Rules 1002(b)(4)(i)-(iii), to the extent known at the time. Within five business days after the resolution of such SCI event and closure of the investigation regarding such SCI event, the SCI entity is required to submit a final written notification pertaining to such SCI event to the Commission containing the information specified in the rule.</P>
                    <P>
                        As an initial matter, the Commission notes that several of the items that are specifically required to be described in the final report (as specified in adopted Rule 1002(b)(4)) were proposed to be required to be provided to the Commission under proposed Rule 1000(b)(4)(ii), within a shorter time frame.
                        <SU>915</SU>
                        <FTREF/>
                         The Commission believes that 
                        <PRTPAGE P="72330"/>
                        the adopted rule, by requiring that this information be submitted to the Commission after resolution of an SCI event and closure of the SCI entity's investigation, will encourage SCI entities to devote resources first to resolving the SCI event, and providing status reports when required, and then to preparing a comprehensive final report. In particular, as some commenters suggested, certain information would be more accurate, and therefore more useful, if provided after an SCI event is resolved.
                        <SU>916</SU>
                        <FTREF/>
                         The Commission believes that the information required under Rule 1002(b)(4) will provide the Commission with a comprehensive analysis to more fully understand and assess the impact caused by the SCI event. In addition, the Commission ordinarily would expect an SCI entity to include the root cause of an SCI event as part of “any other pertinent information” known about the SCI event. The Commission also believes that certain of the information requested by Rule 1002(b)(4) is more suitable to be provided after, rather than prior to, resolution of an SCI event. Specifically, much of the information required by Rule 1002(b)(4) (an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss) can only be comprehensively known after the final resolution of an SCI event.
                        <SU>917</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>915</SU>
                             The Commission notes that while proposed Rule 1000(b)(4)(iv)(C) specified that an SCI entity 
                            <PRTPAGE/>
                            was required to provide a copy of any information disseminated on the SCI entity's publicly available Web site, adopted Rule 1002(b)(4) specifies that an SCI entity provide a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>916</SU>
                             
                            <E T="03">See supra</E>
                             notes 870-878 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>917</SU>
                             The Commission notes that a notification required pursuant to proposed Rule 1000(b)(4)(ii) required the SCI entity to provide information on the “
                            <E T="03">potential</E>
                             impact of the SCI event on the market,” whereas adopted Rule 1002(b)(4)(ii)(A) requires a description of “
                            <E T="03">the SCI entity's assessment of</E>
                             the impact of the SCI event on the market.” Because adopted Rule 1002(b)(4) requires a final report upon resolution of an SCI event and the closure of the SCI entity's investigation of the SCI event, the Commission believes it is appropriate that an SCI entity provide its assessment of the impact of the SCI event in the final report, rather than information on the SCI event's potential impact.
                        </P>
                    </FTNT>
                    <P>
                        Similarly, the Commission is revising the proposed requirement that SCI entities provide to the Commission a copy of any information disclosed by the SCI entity to date regarding the SCI event to any of its members or participants. First, rather than requiring that SCI entities provide a copy of “any information disclosed by the SCI entity,” the adopted rule requires that SCI entities provide a copy of any information “disseminated pursuant to paragraph (c) of [Rule 1002]” by the SCI entity to date regarding the SCI event to any of its members or participants. The Commission believes that this refined requirement will more appropriately capture only the information needed for the Commission to assess compliance with the dissemination requirements of Rule 1002(c). Further, to limit the burden on, and provide additional flexibility to, SCI entities as they resolve SCI events, the adopted rule does not require this information to be included as part of a Form SCI submission until the final report is to be submitted to the Commission. The Commission believes that it is sufficient to require that this information be included in the final report because it is an important part of the record of an SCI event and SCI entity's response to such event.
                        <SU>918</SU>
                        <FTREF/>
                         As noted above, one commenter questioned the purpose of this requirement and expressed concern that it may negatively impact open communication between an SCI entity and its members and participants,
                        <SU>919</SU>
                        <FTREF/>
                         while another commenter questioned the feasibility, need, and potential impact of this requirement in light of the numerous communications that SCI entities will engage in with their members or participants.
                        <SU>920</SU>
                        <FTREF/>
                         While the Commission recognizes that it is possible that the requirement could have some chilling effect on such communications, it believes that this information is important for SCI entities to share with the Commission because it is an efficient means for the Commission to assess whether SCI entities are complying with the dissemination requirements of Rule 1002(c). Further, the Commission believes that, by requiring that SCI entities provide a copy only of information disseminated pursuant to Rule 1002(c) (rather than all information disclosed to members or participants regarding the SCI event), it addresses one commenter's concern that it would be difficult, unnecessary, and could impede open communication, to provide the Commission with a copy of all information disclosed to members or participants, which could include hundreds of individual communications via email or telephone for each SCI event.
                    </P>
                    <FTNT>
                        <P>
                            <SU>918</SU>
                             Under Rule 1002(b)(4), SCI entities are required to provide a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>919</SU>
                             
                            <E T="03">See supra</E>
                             note 877.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>920</SU>
                             
                            <E T="03">See supra</E>
                             note 878 and accompanying text. Specifically, this commenter noted that there could be hundreds of communications between the SCI entity and its members or participants during a systems incident and questioned the feasibility of, and need for, recreating and providing to the Commission a copy of all such communications. Further, the commenter noted that this requirement could have an unintended effect of discouraging open communication between the SCI entity and its members.
                        </P>
                    </FTNT>
                    <P>The Commission also believes that, if an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 days of the occurrence of the SCI event, it is reasonable to require that an SCI entity submit within thirty business days after the occurrence of the SCI event the information required in Rule 1002(b)(4)(ii), to the extent known at the time, because this timeframe provides SCI entities with flexibility to continue their investigation while also apprising the Commission of relevant information discovered during the course of the SCI entity's investigation. Moreover, the rule takes into account the Commission's recognition that an SCI entity's investigation regarding an SCI may not yet be complete despite the fact that the SCI event itself has resolved. In such cases, within five business days after the SCI event has resolved and the investigation regarding the SCI event has closed, the Commission believes that it is reasonable and necessary to provide it with a comprehensive and complete understanding of the SCI event. Consequently, SCI entities are required to submit a final written notification that contains all information required by Rule 1002(b).</P>
                    <HD SOURCE="HD3">Goals of Adopted Commission Notification Rule</HD>
                    <P>As discussed in greater detail above, the Commission has carefully considered the views of commenters as well as what it believes is necessary for the Commission and its staff with respect to the timing and content of notifications regarding SCI events, and believes that the adopted rule will be less burdensome for SCI entities than if the proposed rule was adopted without modification, while still resulting in meaningful notice to the Commission and its staff with information about SCI events in a timely manner that permits the Commission to fulfill its oversight role.</P>
                    <P>
                        With regard to comments on the resource and efficiency demands of the notification requirements,
                        <SU>921</SU>
                        <FTREF/>
                         the Commission believes that while SCI entities will need to devote resources to fulfilling the notification requirements, the Commission does not believe that these resources will diminish SCI entities' ability to respond to SCI events because it is the Commission's 
                        <PRTPAGE P="72331"/>
                        experience that the staff that engages in corrective action is generally distinct from the staff that has been charged with notifying the Commission of systems issues. Consequently, the Commission does not believe that, due to this requirement, staff that engages in corrective action will be unable to fulfill its responsibilities after implementation of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>921</SU>
                             
                            <E T="03">See supra</E>
                             notes 790-793.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that adopted Rules 1002(b)(1)-(4) are responsive to concerns that the proposed Commission notification requirements would have required SCI entities to notify the Commission of information before all relevant facts are known.
                        <SU>922</SU>
                        <FTREF/>
                         As discussed, in tandem with the revised triggering standard, which affords an SCI entity time to assess whether an SCI event has occurred,
                        <SU>923</SU>
                        <FTREF/>
                         the adopted rule affords an SCI entity the flexibility to gather information for the 24-hour written notification on a good faith best, efforts basis,
                        <SU>924</SU>
                        <FTREF/>
                         and adopted Rule 1002(b)(3) makes clear that an SCI entity is required to update the Commission to correct any materially inaccurate information previously provided, or when pertinent new information is discovered, until such time as the SCI event is resolved, and the SCI entity's investigation of the SCI event is closed. Further, the final report for a given SCI event is only required once, when both the SCI event is resolved and the SCI entity's investigation of the SCI event is closed, with an interim report required only when an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 days of the occurrence of the SCI event. Taken together, the Commission believes that Rule 1002(b) does not require reporting before all relevant fact are known, which one commenter suggested would be counterproductive and harmful.
                        <SU>925</SU>
                        <FTREF/>
                         Instead, the Commission believes that the rule is designed to provide SCI entities with a process that gives them sufficient time to submit information to the Commission when known. In addition, and in response to comment questioning the usefulness of the notification requirement for the Commission,
                        <SU>926</SU>
                        <FTREF/>
                         the Commission believes that adopted Rule 1002(b) will foster a system for comprehensive reporting of SCI events, which should enhance the Commission's review and oversight of U.S. securities market infrastructure and foster cooperation between the Commission and SCI entities in responding to SCI events. The Commission also believes that the aggregated data that will result from the reporting of SCI events will enhance its ability to comprehensively analyze the nature and types of various SCI events and identify more effectively areas of persistent or recurring problems across the systems of all SCI entities. Some commenters suggested that the Commission provide to SCI entities regular summary-level feedback on SCI entities' notifications 
                        <SU>927</SU>
                        <FTREF/>
                         or provide examples of the types of SCI events that warrant notification.
                        <SU>928</SU>
                        <FTREF/>
                         To the extent it believes that guidance or other information, including summary-level feedback, publications, or reference blueprints, would be appropriate to share, the Commission or its staff may do so in the future.
                    </P>
                    <FTNT>
                        <P>
                            <SU>922</SU>
                             
                            <E T="03">See supra</E>
                             note 804 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>923</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>924</SU>
                             
                            <E T="03">See supra</E>
                             discussion of “good faith, best efforts” above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>925</SU>
                             
                            <E T="03">See supra</E>
                             note 804.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>926</SU>
                             
                            <E T="03">See supra</E>
                             note 793.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>927</SU>
                             
                            <E T="03">See supra</E>
                             note 806 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>928</SU>
                             
                            <E T="03">See supra</E>
                             note 807 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. Dissemination of Information—Rule 1002(c)</HD>
                    <HD SOURCE="HD3">i. Proposed Rule 1000(b)(5)</HD>
                    <P>Proposed Rule 1000(b)(5) would have required an SCI entity to provide specified information relating to “dissemination SCI events” to SCI entity members or participants. The term “dissemination SCI event” was proposed to mean an SCI event that is a: (1) Systems compliance issue; (2) systems intrusion; or (3) systems disruption that results, or the SCI entity reasonably estimates would result, in significant harm or loss to market participants.</P>
                    <P>
                        Proposed Rule 1000(b)(5)(i)(A) would have required an SCI entity, promptly after any responsible SCI personnel becomes aware of a dissemination SCI event other than a systems intrusion, to disseminate to its members or participants the following information about such SCI event: (1) The systems affected by the SCI event; and (2) a summary description of the SCI event. Proposed Rule 1000(b)(5)(i)(B) would have required an SCI entity to further disseminate to its members or participants, when known: (1) A detailed description of the SCI event; (2) the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; and (3) a description of the progress of its corrective action for the SCI event and when the SCI event has been or is expected to be resolved. Proposed Rule 1000(b)(5)(i)(C) would have further required an SCI entity to provide regular updates to members or participants on any of the information required to be disseminated under proposed Rules 1000(b)(5)(i)(A) and (i)(B). In the case of a systems intrusion, the proposed rule permitted a limited delay in dissemination if the dissemination would compromise the security of the SCI entity's systems.
                        <SU>929</SU>
                        <FTREF/>
                         Except for the delay in dissemination of information for systems intrusions in specified circumstances, the proposed rule did not distinguish dissemination obligations based on the severity or impact of a dissemination SCI event.
                    </P>
                    <FTNT>
                        <P>
                            <SU>929</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(5)(ii) (permitting a delay in dissemination of information regarding a systems intrusion if “the SCI entity determines that dissemination of such information would likely compromise the security of the SCI entity's SCI systems or SCI security systems, or an investigation of the systems intrusion, and documents the reasons for such determination”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Comments Regarding Information Dissemination</HD>
                    <P>
                        Two commenters generally supported proposed Rule 1000(b)(5).
                        <SU>930</SU>
                        <FTREF/>
                         One commenter characterized it as “one of the major benefits of th[e] proposal.” 
                        <SU>931</SU>
                        <FTREF/>
                         Another commenter suggested broadening the proposal to require an SCI entity to reveal dissemination SCI events to the public at large, and not just to its members or participants.
                        <SU>932</SU>
                        <FTREF/>
                         This commenter believed that public dissemination of the facts of an SCI event would help enhance investor confidence by preventing speculation and misinformation, and would provide important learning opportunities for the industry and other SCI entities.
                        <SU>933</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>930</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 5; and MFA Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>931</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 5. This commenter stated: “Instead of keeping information about hardware failures, system intrusions, and software glitches private, sharing the information will alert others in the industry about such problems and help to reduce system wide costs of diagnosing problems, as well as result in improved responses to technology problems. These will serve as warnings to the other SCI entities to stay vigilant to prevent similar problems from occurring on their platforms.” Angel Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>932</SU>
                             
                            <E T="03">See</E>
                             MFA Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>933</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        In contrast, many commenters urged the Commission to revise the proposed dissemination requirement.
                        <SU>934</SU>
                        <FTREF/>
                         For example, a few commenters expressed concern that the proposal would require dissemination of too much information too soon.
                        <SU>935</SU>
                        <FTREF/>
                         One of these commenters stated that the proposed rule would be counterproductive and harmful because 
                        <PRTPAGE P="72332"/>
                        it would cause the release of information before all relevant facts are known and suggested dissemination should only be required when the SCI entity has credible information that can be acted upon.
                        <SU>936</SU>
                        <FTREF/>
                         Another commenter suggested that dissemination should only be required when the information to be disseminated is certain and clear.
                        <SU>937</SU>
                        <FTREF/>
                         Another commenter urged that, if immediate dissemination is required, then the information required to be disseminated should be limited to communication of the basic fact that there is a systems issue and additional information will be provided when known.
                        <SU>938</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>934</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 28-29; FINRA Letter at 24; BATS Letter at 13; DTCC Letter at 11-12; OCC Letter at 16; CME Letter at 9-10; ICI Letter at 4; Oppenheimer Letter at 2; Direct Edge Letter at 8; Omgeo Letter at 21; ITG Letter at 13; and FIA PTG Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>935</SU>
                             
                            <E T="03">See, e.g.,</E>
                             DTCC Letter at 12, NYSE Letter at 29; and ITG Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>936</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 13. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 804 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>937</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>938</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 29 (stating also that the scope of the information required to be provided is too extensive, particularly given the timing requirements of the proposed rule).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters opposed requiring information dissemination to all members and participants.
                        <SU>939</SU>
                        <FTREF/>
                         For example, some commenters urged that an SCI entity be required to provide information only to members or participants actually impacted by an SCI event, or that interact with the SCI system impacted, rather than to all members or participants of an SCI entity.
                        <SU>940</SU>
                        <FTREF/>
                         One commenter recommended that an SCI entity be required to disseminate information only to persons reasonably likely to be affected by a significant systems issue.
                        <SU>941</SU>
                        <FTREF/>
                         Two commenters stated that SCI entities should have reasonable discretion to determine who among their members and participants should receive notification of an SCI event, as well as the manner and timing for providing notice.
                        <SU>942</SU>
                        <FTREF/>
                         A few commenters more broadly expressed concern that the proposed rule would result in over-reporting of information about SCI events and would have limited usefulness.
                        <SU>943</SU>
                        <FTREF/>
                         Some of these commenters stated that the proposed approach would result in SCI entity members and participants becoming immunized to the notifications because they would receive too many notifications and therefore would not focus on the truly significant events.
                        <SU>944</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>939</SU>
                             
                            <E T="03">See, e.g.,</E>
                             MSRB Letter at 20-21; DTCC Letter at 11; CME Letter at 10; NYSE Letter at 28; FINRA Letter at 24-25; ISE Letter at 6-7; SIFMA Letter at 15; and OCC Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>940</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 20-21; DTCC Letter at 11; CME Letter at 9; NYSE Letter at 28; FINRA Letter at 25; and ISE Letter at 6-7. In addition, one of these commenters sought clarification on whether the term “participant” refers to a formal participant or, more broadly speaking, any market participant that interacts with the SCI system in question. 
                            <E T="03">See</E>
                             MSRB Letter at 20. 
                            <E T="03">See also</E>
                             Omgeo Letter at 21, and 
                            <E T="03">infra</E>
                             note 954.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>941</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 28.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>942</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 15 (urging that an SCI entity should have discretion to determine which participants or members are affected and how to notify them); and OCC Letter at 17 (urging that an SCI entity should be able to limit the communication to those members and participants that are actually affected and to provide the communication on a confidential and secure basis when the SCI entity has reasonable certainty of the information that is required to be provided).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>943</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CME Letter at 9; FIA PTG Letter at 3; and Omgeo Letter at 39. 
                            <E T="03">See also</E>
                             Fidelity Letter at 5 (requesting that the Commission provide greater specificity regarding the types of dissemination SCI events that must be disclosed and to whom disclosure must be made).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>944</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 40; FIA PTG Letter at 3; and CME Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters suggested that the Commission apply the proposed dissemination requirement to fewer types of SCI events.
                        <SU>945</SU>
                        <FTREF/>
                         For example, several commenters stated that information dissemination should only be required for material or significant SCI events.
                        <SU>946</SU>
                        <FTREF/>
                         One commenter suggested that, for an SCI event that is “de minimis,” information dissemination to members or participants should not be required at all.
                        <SU>947</SU>
                        <FTREF/>
                         This commenter suggested that a de minimis SCI event would be one that is limited in impact, brief in duration, or involves little or no member or participant harm.
                        <SU>948</SU>
                        <FTREF/>
                         Another commenter noted that, as proposed, Commission notification would be required for a systems disruption if the systems disruption had a “material impact” on the SCI entity's operations or on market participants, whereas information dissemination to members or participants would be required if an SCI entity reasonably estimated that the systems disruption would result “in significant harm or loss to market participants.” 
                        <SU>949</SU>
                        <FTREF/>
                         This commenter criticized the differing standards for Commission notification and member/participant notification and suggested that the Commission clarify the standards or adopt a uniform standard for both types of notifications.
                        <SU>950</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>945</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 28; FIA PTG Letter at 3; FINRA Letter at 24; BATS Letter at 13; OCC Letter at 16-17; CME Letter at 9-10; ICI Letter at 4; Oppenheimer Letter at 2; and Direct Edge Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>946</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 28; FIA PTG Letter at 3; FINRA Letter at 24; BATS Letter at 13; OCC Letter at 16-17; CME Letter at 9-10; ICI Letter at 4; Oppenheimer Letter at 2; and Direct Edge Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>947</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>948</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>949</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>950</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Several commenters specifically opposed the proposed dissemination requirement for systems compliance issues. Some commenters urged that an SCI entity be required to disseminate information only for material or significant systems compliance issues.
                        <SU>951</SU>
                        <FTREF/>
                         One of these commenters stated that prompt dissemination of information regarding systems compliance issues to members or participants might lead to widespread dissemination of extraneous and potentially inaccurate information.
                        <SU>952</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>951</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 24; Joint SROs Letter at 9; SIFMA Letter at 12; BATS Letter at 13; MSRB Letter at 6; and CME Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>952</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 8.
                        </P>
                    </FTNT>
                    <P>
                        Regarding systems intrusions, a few commenters stated that dissemination of systems intrusions information could raise significant risks and security concerns.
                        <SU>953</SU>
                        <FTREF/>
                         One commenter recommended that a dissemination requirement apply only in the case of members, participants, or clients for whom confidential data was disclosed, processing was impacted, or where such member, participant, or client could take further action to mitigate the risk of such disclosure.
                        <SU>954</SU>
                        <FTREF/>
                         This commenter also expressed support for the limited exception for intrusions that would compromise an investigation or resolution of the systems intrusion, noting that once dissemination would no longer compromise an investigation or the resolution of the issue, the entity should notify materially affected members, participants, or clients.
                    </P>
                    <FTNT>
                        <P>
                            <SU>953</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 11; and NYSE Letter at 29. 
                            <E T="03">See also</E>
                             Direct Edge Letter at 3 (suggesting that, to ensure that sensitive information does not fall into the wrong hands, the Commission should require reporting of systems intrusions to the Commission, and only require public disclosure in instances where there is a risk of significant harm to the SCI entity's customers).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>954</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 21.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that information should not be disseminated regarding disruptions in regulatory or surveillance systems, nor should information be disseminated about intrusions or compliance issues, arguing that the information could be misused, or if disseminated too soon, could be inaccurate and misleading.
                        <SU>955</SU>
                        <FTREF/>
                         Two other commenters also expressed concern that information dissemination should not be required when the information provided might be misused to the detriment of the markets or investors, such as with respect to systems intrusions or issues relating to surveillance systems.
                        <SU>956</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>955</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 29. 
                            <E T="03">See also</E>
                             supra note 935 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>956</SU>
                             
                            <E T="03">See</E>
                             ICI Letter at 4; and Oppenheimer Letter at 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Rule 1002(c)</HD>
                    <P>
                        In the SCI Proposal, the Commission stated that the intended purpose of the proposed rule was twofold: To aid members or participants of SCI entities 
                        <PRTPAGE P="72333"/>
                        in determining whether their trading activity has been or might be impacted by the occurrence of an SCI event at an SCI entity so that they could consider that information in making trading decisions, seeking corrective action or pursuing remedies, or taking other responsive action; and to provide an incentive for SCI entities to devote more resources and attention to improving the integrity and compliance of their systems and preventing the occurrence of SCI events.
                        <SU>957</SU>
                        <FTREF/>
                         Although commenters generally did not object to the Commission's stated rationale for proposed Rule 1000(b)(5), several commenters suggested that the proposed approach did not adequately consider circumstances in which the proposed information dissemination might not be helpful to the market or market participants, or could be detrimental to the markets or market participants. One commenter, however, urged that public dissemination of information regarding SCI events would help to prevent speculation and misinformation regarding such events.
                        <SU>958</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>957</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18120.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>958</SU>
                             
                            <E T="03">See supra</E>
                             note 933 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has carefully considered the views of commenters with respect to proposed Rule 1000(b)(5), and has determined to adopt it as Rule 1002(c), with several modifications in response to comment. In particular, the Commission has determined to eliminate the definition of “dissemination SCI event” from the final rule and adopt an information dissemination requirement that scales dissemination obligations in accordance with the nature and severity of an SCI event. In response to comment that the proposed rule would result in over-reporting of information about SCI events and have limited usefulness, the Commission has further focused the rule from the proposal by requiring dissemination of information about SCI events that are not major SCI events only to affected SCI entity members and participants, and excepting de minimis SCI events and SCI events regarding market regulation or market surveillance systems from the information dissemination requirement.
                        <SU>959</SU>
                        <FTREF/>
                         In the case of a “major SCI event,” the Commission agrees with the commenter who stated that requiring dissemination should help to prevent speculation and misinformation regarding such events.
                        <SU>960</SU>
                        <FTREF/>
                         Therefore, in the case of a “major SCI event,” the adopted rule requires an SCI entity to disseminate information to all of its members or participants. At the same time, as with other SCI events, any SCI event that meets the definition of major SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants is excepted from the information dissemination requirement.
                        <SU>961</SU>
                        <FTREF/>
                         The Commission believes the revised approach will better achieve the purpose of maximizing the utility of information disseminated to SCI entity members and participants while simultaneously reducing compliance burdens for SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>959</SU>
                             
                            <E T="03">See supra</E>
                             notes 943-956 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>960</SU>
                             
                            <E T="03">See supra</E>
                             note 933 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>961</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(c)(4)(ii).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Rule 1002(c)(1): Information Dissemination for Systems Disruptions and Systems Compliance Issues</HD>
                    <P>
                        Adopted Rule 1002(c)(1) generally addresses dissemination requirements for systems disruptions and systems compliance issues. Rule 1002(c)(1)(i) requires an SCI entity, promptly after any responsible SCI personnel has a reasonable basis to conclude that an SCI event that is a systems disruption or systems compliance issue has occurred, to disseminate information about such SCI event, unless an exception applies. When the dissemination obligation is triggered,
                        <SU>962</SU>
                        <FTREF/>
                         Rule 1002(c)(1)(i) requires an SCI entity to disseminate to the persons specified in Rule 1002(c)(3) information on the system(s) affected by the SCI event and a summary description of the SCI event. Thereafter, Rule 1002(c)(1)(ii) provides that, when known, an SCI entity shall promptly further disseminate: A detailed description of the SCI event; the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; and a description of the progress of its corrective action for the SCI event and when the SCI event has been or is expected to be resolved. Rule 1002(c)(1)(iii) provides that, until resolved, an SCI entity shall provide regular updates of any information required to be disseminated under Rules 1002(c)(1)(i) and (ii). The specified types of information and the update requirements are unchanged from the proposal. The Commission continues to believe that, for the dissemination of information to be meaningful, it is necessary for an SCI entity to describe the SCI event in sufficient detail to permit a member or participant to determine whether and how it was affected by the SCI event and make appropriate decisions based on that determination.
                        <SU>963</SU>
                        <FTREF/>
                         Adopted Rule 1002(c)(1)(i) requires that the information initially disseminated include the systems affected by the SCI event and a summary description of the SCI event, and only after responsible SCI personnel have a reasonable basis to conclude that a systems disruption or systems compliance issue has occurred. Implicit in this requirement is that the disseminated information be accurate. Without the dissemination of accurate information, the impact on the SCI entity's members or participants or the market may be more pronounced because market participants may not recognize that an SCI event is occurring, or may mistakenly attribute unusual market activity to some other cause.
                    </P>
                    <FTNT>
                        <P>
                            <SU>962</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.a (discussing the triggering standard).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>963</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18120.
                        </P>
                    </FTNT>
                    <P>
                        Adopted Rule 1002(c)(1) also requires that required information be disseminated “promptly.” 
                        <SU>964</SU>
                        <FTREF/>
                         Although the Commission agrees that SCI entities should not prematurely disseminate information regarding an SCI event, lest it be inaccurate, speculative, misleading, or otherwise unhelpful, as some commenters were concerned about,
                        <SU>965</SU>
                        <FTREF/>
                         the Commission does not agree with the commenter who suggested that information dissemination be provided at a time chosen by the SCI entity.
                        <SU>966</SU>
                        <FTREF/>
                         The Commission believes that accurate information that is timely is more likely to aid a market participant in determining whether its trading activity has been or might be impacted by the occurrence of an SCI event than accurate information that is delayed. However, as compared to Commission notification, which is required to be provided immediately after an SCI entity has a reasonable basis to conclude that an SCI event has occurred, and which notice may be provided orally, dissemination of information to SCI entity members or participants is required to be provided promptly. The requirement for prompt dissemination, as opposed to immediate dissemination, is designed to provide some limited flexibility to an SCI entity to determine an efficient way to disseminate information to multiple potentially affected members or participants, or all of its members or participants, as the case may be, in a timely manner. Likewise, as new information becomes 
                        <PRTPAGE P="72334"/>
                        known, immediate updates are not required, but an SCI entity is obligated to also disseminate updated information “promptly” after it is known. The Commission believes that adopted Rule 1002(c)(1) strikes an appropriate balance by requiring an SCI entity to disseminate specific information about SCI events, but also permits an SCI entity to have time to check relevant facts before disseminating that information. The Commission therefore believes that adopted Rule 1002(c)(1) is responsive to comment that the proposed rule would have required release of information too soon, before it is determined to be credible, or before relevant facts were known.
                        <SU>967</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>964</SU>
                             The persons to whom the required information about systems disruptions and systems compliance issues is to be disseminated are specified in Rules 1002(c)(3) and (4).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>965</SU>
                             
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             notes 935-938 and 933 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>966</SU>
                             
                            <E T="03">See supra</E>
                             note 942 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>967</SU>
                             
                            <E T="03">See supra</E>
                             notes 935-938 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Rule 1002(c)(2): Information Dissemination for Systems Intrusions</HD>
                    <P>
                        Adopted Rule 1002(c)(2) requires an SCI entity, promptly after any responsible SCI personnel has a reasonable basis to conclude that an SCI event that is a systems intrusion has occurred, to disseminate a summary description of the systems intrusion, including a description of the corrective action taken by the SCI entity and when the systems intrusion has been or is expected to be resolved, unless the SCI entity determines that dissemination of such information would likely compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and documents the reasons for such determination. This rule applies to systems intrusions that are not de minimis events. In response to commenters stating that information about a systems intrusion in many cases will be sensitive and raise security concerns, and those urging that the dissemination requirement apply only in limited cases,
                        <SU>968</SU>
                        <FTREF/>
                         the Commission notes that, although it does not wholly exclude systems intrusions from the dissemination requirement, the rule permits a delay in dissemination of any information about a systems intrusion if dissemination would compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and the SCI entity documents the reason for such determination.
                        <SU>969</SU>
                        <FTREF/>
                         Adopted Rule 1002(c)(2) also provides that the content of the required disclosure for a systems intrusion is less detailed than required for other types of SCI events. These provisions are unchanged from the SCI Proposal.
                        <SU>970</SU>
                        <FTREF/>
                         As stated in the SCI Proposal, the Commission continues to believe that there may be circumstances in which the dissemination of information related to a systems intrusion should be delayed to avoid compromising the investigation or resolution of a systems intrusion.
                        <SU>971</SU>
                        <FTREF/>
                         Also, as stated in the SCI Proposal, the affirmative documentation required by Rule 1002(c)(2) is important to allow the Commission to ensure that SCI entities are not improperly invoking the limited exception provided by Rule 1002(c)(2).
                        <SU>972</SU>
                        <FTREF/>
                         This delayed dissemination provision permits an SCI entity to delay providing information about an intrusion to its members or participants to protect legitimate security concerns. However, under Rule 1002(c)(2), if an SCI entity cannot, or can no longer, determine that information dissemination as required by Rule 1002(c)(2) would likely compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion, no delay (or further delay, if applicable) in dissemination is permitted.
                        <SU>973</SU>
                        <FTREF/>
                         Pursuant to Rule 1002(c)(2), information about a systems intrusion is required to be disseminated eventually, as the Commission believes that circumstances permitting a delay (
                        <E T="03">i.e.,</E>
                         dissemination of information would likely compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion), will not continue indefinitely.
                        <SU>974</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>968</SU>
                             
                            <E T="03">See, e.g., supra</E>
                             notes 953-954 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>969</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(c)(4) (excepting de minimis systems intrusions and intrusions into market regulation or market surveillance systems from the dissemination requirement) and Rule 1001(c)(2) (permitting a delay in dissemination).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>970</SU>
                             The persons to whom the required information about a systems intrusion is to be disseminated (provided the circumstances warranting a delay do not apply) is specified in Rules 1002(c)(3) and (4).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>971</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18120.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>972</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>973</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>974</SU>
                             Some commenters urged modifications to the proposed rule that would further circumscribe the proposed dissemination requirement for systems intrusions. 
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 953-954 and accompanying text (urging that dissemination for systems intrusions only be required for affected persons and only if material). These comments are addressed in the discussion of adopted Rules 1002(c)(3) and (4).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Rule 1002(c)(3): To Whom Information Is To Be Disseminated</HD>
                    <P>
                        Adopted Rule 1002(c)(3) provides that the information required to be provided under Rules 1002(c)(1) and (2) promptly after any responsible SCI personnel has a reasonable basis to conclude that an SCI event has occurred, shall be promptly disseminated by the SCI entity to those members or participants of the SCI entity that any responsible SCI personnel has reasonably estimated may have been affected by the SCI event, and promptly disseminated to any additional members or participants that any responsible SCI personnel subsequently reasonably estimates may have been affected by the SCI event. The rule further requires that, for major SCI events, such information shall be disseminated by the SCI entity to all of its members or participants. As noted, several commenters urged that an SCI entity be required to disseminate information relating to an SCI event only to those members or participants affected by the SCI event.
                        <SU>975</SU>
                        <FTREF/>
                         Some suggested that an SCI entity have discretion to determine who should receive information regarding SCI events,
                        <SU>976</SU>
                        <FTREF/>
                         and one suggested that SCI events warrant public disclosure.
                        <SU>977</SU>
                        <FTREF/>
                         Others expressed more general concern that the breadth of the proposed dissemination requirement would result in over-reporting of information about SCI events because they believed that SCI entities would over-report out of an abundance of caution 
                        <SU>978</SU>
                        <FTREF/>
                         or that SCI entity members and participants would become immunized to reports of SCI events and not focus on significant events.
                        <SU>979</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>975</SU>
                             
                            <E T="03">See supra</E>
                             note 940 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>976</SU>
                             
                            <E T="03">See supra</E>
                             note 942 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>977</SU>
                             
                            <E T="03">See supra</E>
                             notes 932-933 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>978</SU>
                             
                            <E T="03">See supra</E>
                             note 943 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>979</SU>
                             
                            <E T="03">See supra</E>
                             notes 943-944 and accompanying text.
                        </P>
                    </FTNT>
                    <P>After careful consideration of the comments, the Commission believes that, to maximize the utility of information dissemination, a more tailored approach to who should receive information about an SCI event is warranted, based on an SCI event's impact. Because information about an SCI event is likely to be of greatest value to those market participants affected by it, who can use such information to evaluate the event's impact on their trading and other activities and develop an appropriate response, adopted Rule 1002(c)(3) requires prompt dissemination to those members or participants of the SCI entity that any responsible SCI personnel has reasonably estimated may have been affected by the SCI event. With respect to more serious SCI events, however, the Commission believes that dissemination to all members or participants of an SCI entity is warranted. Accordingly, under adopted Regulation SCI, certain SCI events will be defined as “major SCI events.”</P>
                    <P>
                        Adopted Rule 1000 defines “major SCI event” as “an SCI event that has 
                        <PRTPAGE P="72335"/>
                        had, or the SCI entity reasonably estimates would have: (1) Any impact on a critical SCI system; or (2) a significant impact on the SCI entity's operations or on market participants.” The Commission believes that dissemination of information regarding a major SCI event to all members or participants of an SCI entity is appropriate because major SCI events are likely to impact a large number of market participants (
                        <E T="03">e.g.</E>
                        , with respect to critical SCI systems, a disruption of consolidated market data or the clearance and settlement system, or an event significantly impacting the operations of an exchange).
                        <SU>980</SU>
                        <FTREF/>
                         As noted, one commenter suggested broadening the proposed rule to generally require an SCI entity to reveal dissemination SCI events (other than intrusions) to the public at large. This commenter expressed the view that public dissemination of the facts of an SCI event would help “enhance investor confidence by presenting the facts of the SCI event, preventing speculation and misinformation, and informing the public of corrective action being taken” and would “serve as an important collective learning opportunity” that would allow for “SCI [e]ntities and market participants [to] learn from [the event] . . . and build upon their policies and controls as appropriate.” This commenter stated further that such an “industry protocol would help strengthen and enhance the integrity and security of our markets.” 
                        <SU>981</SU>
                        <FTREF/>
                         The Commission agrees with this commenter that it is appropriate for an SCI entity to present the facts, prevent speculation and misinformation, and provide transparency about corrective action being taken when the impact of an SCI event is most likely to be felt by many market participants (
                        <E T="03">i.e.</E>
                        , when it is a major SCI event). In the context of a major SCI event, the Commission believes these goals can be achieved by requiring an SCI entity to disseminate information to all of its members or participants (as opposed to the “public at large”). Moreover, the Commission believes it is appropriate to require dissemination of information on major SCI events to all of the SCI entity's members or participants because these market participants are the most likely to act on this information. Based on the experience of the Commission and its staff, when an entity disseminates information about a systems issue to all of its members or participants (
                        <E T="03">e.g.</E>
                        , on the entity's Web site), and that information has the potential to affect the market and investors more broadly (including market participants that may not be members or participants of the SCI entity reporting the event), such information is routinely picked up by financial or other media outlets, and also may be relayed to market participants for whom such information is relevant (
                        <E T="03">e.g.</E>
                        , by members or participants of SCI entities to their own clients). Therefore, the Commission believes that when information about a systems issue with broad potential impact is disseminated to all of an SCI entity's member or participants, such dissemination is tantamount to public dissemination.
                        <SU>982</SU>
                        <FTREF/>
                         As such, the Commission believes that it can achieve the purposes of the rule without requiring public dissemination, and believes that any additional gain in benefits from public dissemination would be minimal. Rule 1002(c)(3) does not specify how an SCI entity is to disseminate information to all of its members or participants when required to do so, but the Commission believes that posting the information on a Web site accessible to, at a minimum, all of its member or participants (for example, on a “systems status alerts” page) would meet the rule's requirements.
                        <SU>983</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>980</SU>
                             At the same time, the Commission recognizes that some SCI events that meet the definition of “major SCI event” could also qualify as de minimis SCI events. Like other de minimis SCI events, they are excepted from the information dissemination requirement. 
                            <E T="03">See</E>
                             Rule 1002(c)(4).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>981</SU>
                             
                            <E T="03">See supra</E>
                             notes 932-933.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>982</SU>
                             The Commission notes that one commenter referred to the dissemination provision in the SCI Proposal as the “public dissemination provision of Proposed Reg SCI.” 
                            <E T="03">See</E>
                             NYSE Letter at 28. 
                            <E T="03">See also</E>
                             ICI Letter at 4 and Oppenheimer Letter at 4 (each supporting “transparency of SCI events to members and participants of an SCI entity” but recommending that the Commission only require “public dissemination” where such information enhances investor protection).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>983</SU>
                             The Commission notes that, irrespective of the medium chosen to disseminate information to the SCI entity members or participants, the SCI entity would also be required to submit the disseminated information to the Commission as part of the report submitted pursuant to Rule 1002(b)(4). 
                            <E T="03">See supra</E>
                             Section IV.B.3.c.
                        </P>
                    </FTNT>
                    <P>
                        For an SCI event that is neither a major SCI event nor an event identified in Rule 1002(c)(4), however, the information specified in Rule 1002(c)(1) or (2), as applicable, is required to be disseminated by the SCI entity to those members or participants of the SCI entity that any responsible SCI personnel has reasonably estimated may have been affected by the SCI event.
                        <SU>984</SU>
                        <FTREF/>
                         The Commission believes that an SCI entity is generally in the best position to identify those of its members or participants that are or are reasonably likely to be affected by such events. Under this approach, as commenters urged, members or participants not reasonably estimated to be affected by such events will not be the recipients of information likely to be irrelevant to them. The Commission believes that SCI entities will be able to analyze which members or participants are or reasonably likely will be impacted, and the rule requires SCI entities to disseminate information to such members or participants. The requirement that information is to be disseminated only to those members or participants that any responsible SCI personnel has reasonably estimated may have been affected by the SCI event (other than a major SCI event or a de minimis SCI event) addresses the concern raised by some commenters that members and participants will become immunized by receiving irrelevant notifications 
                        <SU>985</SU>
                        <FTREF/>
                         because, under the adopted approach, members or participants should only receive notifications relevant to them.
                    </P>
                    <FTNT>
                        <P>
                            <SU>984</SU>
                             In response to the commenter seeking clarification on whether the term “participant” refers to a formal participant or, more broadly speaking, any market participant that interacts with the SCI system in question (
                            <E T="03">see supra</E>
                             note 940), for purposes of adopted Rule 1002, the term “participant” refers to a formal participant. The Commission also notes that, with respect to the MSRB, the term “members” as used in Regulation SCI includes entities that are registered with the MSRB, but does not include “a member of the Board,” which is the definition of “member” in MSRB Rule D-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>985</SU>
                             
                            <E T="03">See supra</E>
                             notes 944 and 952 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Whereas the proposed rule would have required dissemination of information about certain SCI events to all SCI entity members and participants, the adopted rule requires dissemination only to those members and participants reasonably estimated to be affected by an SCI event (other than a major SCI event or a de minimis SCI event). Because it is possible that an SCI entity's reasonable estimate of members or participants affected may change as an SCI event unfolds, the adopted rule also requires prompt dissemination of information to newly identified members or participants reasonably estimated to be affected by an SCI event.
                        <SU>986</SU>
                        <FTREF/>
                         This provision reflects the view that newly identified affected members or participants should receive prompt dissemination of information about an SCI event, just as those originally identified as affected members or participants. Although compliance with this requirement may result in an SCI entity disseminating information at several different times to 
                        <PRTPAGE P="72336"/>
                        different members and participants, consistent with commenters' suggestions, the Commission believes that this requirement is appropriately tailored to result in information dissemination being provided to the relevant members or participants of an SCI entity.
                        <SU>987</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>986</SU>
                             Rule 1002(c)(1) requires that, among other things, the SCI entity must disseminate the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event, and until resolved, provide regular updates of this and any other information required to be disseminated under the rule.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>987</SU>
                             The Commission notes that an SCI entity would be in compliance with the rule if it disseminated the required information to all members or participants, rather than disseminating only to those members and participants it reasonably initially estimated to be affected by the event (which might require subsequent dissemination(s) to additional members or participants if its estimate regarding those members or participants that were affected by a given SCI event changes over time).
                        </P>
                    </FTNT>
                    <P>
                        If an SCI event is a de minimis event—
                        <E T="03">i.e.</E>
                        , is an SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants—the adopted rule does not impose any dissemination requirement.
                        <SU>988</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>988</SU>
                             
                            <E T="03">See</E>
                             discussion of adopted Rule 1002(c)(4) below (excepting, among other things, de minimis systems SCI events from the dissemination requirement). 
                            <E T="03">See also supra</E>
                             Section IV.B.3.c (discussing Rule 1002(b)(5), which requires that, for de minimis SCI events, an SCI entity is required to: (i) Make, keep, and preserve records relating to all such SCI events; and (ii) submit to the Commission a report, within 30 calendar days after the end of each calendar quarter, containing a summary description of such systems disruptions and systems intrusions, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such systems disruptions and systems intrusions during the applicable calendar quarter).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Adopted Rule 1002(c)(4): Exceptions to the General Rules on Information Dissemination</HD>
                    <P>
                        Adopted Rule 1002(c)(4) provides that the requirements of Rules 1002(c)(1)-(3) shall not apply to: (i) SCI events to the extent they relate to market regulation or market surveillance systems; or (ii) any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. The Commission has added the exception in adopted Rule 1002(c)(4)(i) in response to comments that information should not be disseminated regarding disruptions in regulation and surveillance systems, because dissemination of such information to an SCI entity's members or participants or the public at large could encourage prohibited market activity.
                        <SU>989</SU>
                        <FTREF/>
                         The Commission notes that the exception for market regulation or market surveillance systems is limited to dissemination of information about SCI events related to market regulation or market surveillance systems. Information about an SCI event that impacts other SCI systems would still be required to be disseminated in accordance with Rule 1002(c) even if that same SCI event also impacts market regulation or market surveillance systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>989</SU>
                             
                            <E T="03">See supra</E>
                             notes 955-956 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The exception in Rule 1002(c)(4)(ii) for de minimis SCI events is consistent with the Commission's approach to excluding de minimis SCI events from the immediate Commission notification requirements in Rule 1002(b), and is therefore responsive to comment that notification and dissemination of systems disruptions were subject to differing standards under the proposal,
                        <SU>990</SU>
                        <FTREF/>
                         as well as to the comment that a de minimis SCI event should not be subject to dissemination.
                        <SU>991</SU>
                        <FTREF/>
                         With respect to the comment that dissemination should only be required for material or significant SCI events,
                        <SU>992</SU>
                        <FTREF/>
                         while the Commission is not limiting the dissemination requirement as suggested by these commenters, the exception for de minimis SCI events is responsive to this comment, to an extent. Moreover, the Commission believes that a materiality threshold would likely exclude from the information dissemination requirement a large number of SCI events that are not de minimis SCI events, but that an SCI entity's members or participants should be made aware of so that they can quickly assess the nature and scope of those SCI events and identify the appropriate response, including ways to mitigate the impact of the SCI events. The Commission also believes that, even without adopting a materiality threshold, the adopted definitions of SCI systems and indirect SCI systems significantly focus the scope of the Commission dissemination requirements from the SCI Proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>990</SU>
                             
                            <E T="03">See supra</E>
                             notes 949-950 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>991</SU>
                             
                            <E T="03">See supra</E>
                             notes 947-948 and accompanying text; Section IV.B.3.c (discussing Rule 1002(b)) and 
                            <E T="03">supra</E>
                             note 988 and accompanying text. The Commission notes that, because major SCI events are a subset of SCI events, the exception in Rule 1002(c)(4)(ii) also applies to major SCI events that meet the requirements of that rule.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>992</SU>
                             
                            <E T="03">See supra</E>
                             note 946 and accompanying text; 
                            <E T="03">see also supra</E>
                             notes 941 and 944 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Consistent with its statements in the SCI Proposal, the Commission notes that the requirements relating to dissemination of information in Regulation SCI relate solely to Regulation SCI.
                        <SU>993</SU>
                        <FTREF/>
                         Nothing in adopted Regulation SCI should be construed as superseding, altering, or affecting the reporting obligations of SCI entities or their affiliates under other federal securities laws or regulations. Accordingly, in the case of an SCI event, SCI entities or their affiliates subject to the public company reporting requirements of Section 13 or Section 15(d) of the Exchange Act would need to comply with their disclosure obligations pursuant to those provisions (including, for example, with respect to Regulation S-K and Forms 10-K, 10-Q, and 8-K) in addition to their disclosure and reporting obligations under Regulation SCI.
                        <SU>994</SU>
                        <FTREF/>
                         In addition, the Commission also wishes to highlight that the requirements of Rule 1002(c) address to whom and when SCI entities are obligated 
                        <E T="03">under Regulation SCI</E>
                         to disseminate information. Subject to any applicable laws or regulations, SCI entities still retain the flexibility to disseminate information—
                        <E T="03">e.g.</E>
                        , to their members or participants, the public, or market participants that interact with the affected SCI systems—at any time they determine to be appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>993</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18119, n. 235.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>994</SU>
                             As an additional example, nothing in adopted Regulation SCI should be construed as superseding any obligations under Regulation FD. SCI entities may also wish to consider staff guidance on this topic. 
                            <E T="03">See</E>
                             CF Disclosure Guidance: Topic No. 2, Cybersecurity (October 13, 2011), available at: 
                            <E T="03">http://www.sec.gov/divisions/corpfin/guidance/cfguidance-topic2.htm.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Notification of Systems Changes—Rule 1003(a)</HD>
                    <HD SOURCE="HD3">a. Proposed Definition of Material Systems Change, Proposed Rules 1000(b)(6) and (b)(8)(ii)</HD>
                    <P>
                        Proposed Rule 1000(a) would have defined the term “material systems change” as a change to one or more: (1) SCI systems of an SCI entity that: (i) Materially affects the existing capacity, integrity, resiliency, availability, or security of such systems; (ii) relies upon materially new or different technology; (iii) provides a new material service or material function; or (iv) otherwise materially affects the operations of the SCI entity; or (2) SCI security systems of an SCI entity that materially affects the existing security of such systems. In the SCI Proposal, the Commission set forth examples that it preliminarily believed could be included within the proposed definition of material systems change.
                        <SU>995</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>995</SU>
                             These examples included: Major systems architecture changes; reconfiguration of systems that would cause a variation greater than five percent in throughput or storage; the introduction of new business functions or services; changes to external interfaces; changes that could increase susceptibility to major outages; changes that could increase risks to data security; changes that were, or would be, reported to or referred to the entity's board of directors, a body performing a function similar to the board of directors, or senior management; and changes that could require 
                            <PRTPAGE/>
                            allocation or use of significant resources. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18105-06. These examples were cited in the 2001 Staff ARP Interpretive Letter. The Commission also stated its preliminary belief that any systems change occurring as a result of the discovery of an actual or potential systems compliance issue would be material. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <PRTPAGE P="72337"/>
                    <P>Proposed Rule 1000(b)(6)(i) would have required an SCI entity, absent exigent circumstances, to notify the Commission in writing at least 30 calendar days before implementation of any planned material systems changes, including a description of the planned material systems changes as well as the expected dates of commencement and completion of implementation of such changes. If exigent circumstances existed, or if the information previously provided to the Commission regarding any planned material systems change had become materially inaccurate, proposed Rule 1000(b)(6)(ii) would have required the SCI entity to notify the Commission, either orally or in writing, with any oral notification to be memorialized within 24 hours after such oral notification by a written notification, as early as reasonably practicable. A written notification to the Commission made pursuant to proposed Rule 1000(b)(6) would have been required to be made electronically on Form SCI and include all information as prescribed in Form SCI and the instructions thereto.</P>
                    <P>Proposed Rule 1000(b)(8)(ii) would have required each SCI entity to submit to the Commission a report, within 30 calendar days after the end of June and December of each year, containing a summary description of the progress of any material systems change during the six month period ending on June 30 or December 31, as the case may be, and the date, or expected date, of completion of implementation of such changes. A written notification to the Commission made pursuant to proposed Rule 1000(b)(8)(ii) would have been required to be made electronically on Form SCI and include all information as prescribed in Form SCI and the instructions thereto.</P>
                    <HD SOURCE="HD3">b. Quarterly and Supplemental Material Systems Change Reports—Rule 1003(a)</HD>
                    <HD SOURCE="HD3">i. Adopted Rule 1003(a)(1): Quarterly Material Systems Change Reports</HD>
                    <P>
                        Many commenters viewed the proposed 30-day advance notification requirement for material systems changes as burdensome.
                        <SU>996</SU>
                        <FTREF/>
                         For example, one commenter believed that the Commission significantly underestimated the number of material systems changes, and suggested that the proposal might require reporting of as many as 60 material systems changes per week, rather than that same amount per year, as the Commission estimated in the SCI Proposal.
                        <SU>997</SU>
                        <FTREF/>
                         Some commenters stated that many SCI entities implement frequent agile modifications rather than major episodic or “waterfall” changes, and therefore viewed the proposed 30-day advance notification requirement as favoring a model that employs waterfall changes over agile changes.
                        <SU>998</SU>
                        <FTREF/>
                         Several commenters stated more broadly that the proposed requirement would mandate constant reporting that would stifle innovation, interfere with an SCI entity's natural planning and development process, and potentially do more harm than good by curtailing an SCI entity's ability to respond to systems issues with appropriate fixes.
                        <SU>999</SU>
                        <FTREF/>
                         Several commenters also expressed concern that the burden of reporting would incentivize an SCI entity to change its systems less often instead of making smaller and more frequent iterative systems adjustments, which they believed would be inconsistent with current software best practices, curtail innovation, and expose their systems to increased risk.
                        <SU>1000</SU>
                        <FTREF/>
                         One commenter questioned the purpose of the proposed requirement, stating that the Commission has not presented any empirical evidence that major or material technology changes by SCI entities are in fact the leading cause of market disruption, and that non-material systems changes by SCI entities and non-SCI entities have a high likelihood of causing market disruptions, but they are not captured by the proposal.
                        <SU>1001</SU>
                        <FTREF/>
                         At the same time, this commenter stated that providing 30-day advance notification of these non-material systems changes would hamstring SCI entities.
                        <SU>1002</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>996</SU>
                             
                            <E T="03">See, e.g.</E>
                            , NYSE Letter at 26; BATS Letter at 14; ISE Letter at 8; BIDS Letter at 14; UBS Letter at 3-4; SIFMA Letter at 15; ITG Letter at 8 and 13; FIF Letter at 5; MFA Letter at 5-6; CME Letter at 11; FINRA Letter at 27; Joint SROs Letter at 7; and OTC Markets Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>997</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 14. 
                            <E T="03">See also</E>
                             NYSE Letter at 26; and ISE Letter at 8 (stating that the proposal would require reporting of too many routine changes), and 
                            <E T="03">infra</E>
                             discussion of the definition of material systems change.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>998</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; FIF Letter at 5; UBS Letter at 4; and ITG Letter at 8. “Agile” software development, which involves smaller, more frequent changes in software code, is contrasted with the “waterfall” methodology, which involves larger, episodic software overhauls.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>999</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; FIF Letter at 5; UBS Letter at 4; BATS Letter at 14; and ITG Letter at 8. 
                            <E T="03">See also</E>
                             SunGard Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1000</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; FIF Letter at 5; UBS Letter at 4; BATS Letter at 14; and ITG Letter at 8. 
                            <E T="03">See also</E>
                             SIFMA Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1001</SU>
                             
                            <E T="03">See</E>
                             SunGard Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1002</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Some commenters also noted that Regulation ATS already requires an ATS to report material changes to the operation of the ATS at least 20 calendar days prior to their implementation.
                        <SU>1003</SU>
                        <FTREF/>
                         One of these commenters noted that it is common for an ATS to finalize the systems specifications for a change close to when the ATS wants to go live with the change, but the ATS must wait 20 days before implementation, and occasionally the questions from Commission staff can further delay implementation.
                        <SU>1004</SU>
                        <FTREF/>
                         This commenter expressed concern that Regulation SCI would lengthen the notification requirement to 30 calendar days and broaden the requirement to include any significant systems change, not just a material change to the operation of the ATS.
                        <SU>1005</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1003</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 14; and ITG Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1004</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1005</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission continues to believe that it is important to receive notifications of planned and implemented material changes to SCI systems or the security of indirect SCI systems in connection with its oversight of U.S. securities market infrastructure.
                        <SU>1006</SU>
                        <FTREF/>
                         However, after considering the views of commenters regarding the 30-day advance notification requirement, the Commission is instead adopting a quarterly reporting requirement, which will permit the Commission and its staff to have up-to-date information regarding an SCI entity's systems development progress and plans, to aid in understanding the operations and functionality of the systems and any material changes thereto, without requiring SCI entities to submit a notification to the Commission for each 
                        <PRTPAGE P="72338"/>
                        material systems change.
                        <SU>1007</SU>
                        <FTREF/>
                         Specifically, Rule 1003(a)(1) requires an SCI entity, within 30 calendar days after the end of each calendar quarter, to submit to the Commission a report describing completed, ongoing, and planned material systems changes to its SCI systems and security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion.
                        <SU>1008</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1006</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18122, 18144. As noted above, one commenter argued that the Commission has not presented any empirical evidence that major or material technology changes by SCI entities are in fact the leading cause of market disruption, and that non-material systems changes have a high likelihood of causing market disruptions. 
                            <E T="03">See supra</E>
                             note 1001 and accompanying text. The Commission notes that the primary purpose of Rule 1003(a) is not to prevent market disruptions. Rather, it is to keep the Commission and its staff informed of the systems changes that SCI entities determine to be material, which will assist the Commission with its oversight of U.S. securities market infrastructure. While the Commission acknowledges that non-material systems changes could cause market disruptions, the Commission agrees with this commenter that requiring Commission notification of all systems changes would be burdensome. 
                            <E T="03">See supra</E>
                             note 1002 and accompanying text (noting this commenter's view that providing 30-day advance notification of non-material systems changes would hamstring SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1007</SU>
                             As discussed in more detail below, the Commission is also not adopting the proposed definition of material systems change or the proposed semi-annual reporting requirement.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1008</SU>
                             Using the quarter ending December 31, 2014 as an example, an SCI entity would be required to submit a report by January 30, 2015 (
                            <E T="03">i.e.</E>
                            , within 30 calendar days after December 31, 2014) that describes material systems changes that the SCI entity has made (including the dates when those changes commenced and were completed), are currently implementing (including the dates when those changes commenced and are expected to be completed), and plan to make (including the dates those changes are expected to commence and complete) for the period from October 1, 2014 (the beginning of the prior calendar quarter) through June 30, 2015 (the end of the subsequent calendar quarter). The next report that corresponds to the quarter ending March 31, 2015 would be required to be submitted by April 30, 2015. As discussed in more detail below, Rule 1003(a)(2) requires an SCI entity to promptly submit a supplemental report notifying the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a)(1).
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that elimination of the 30-day advance notification requirement for material systems changes is responsive to commenters who were concerned that the proposed approach was unsuited to the agile systems development methodology that some SCI entities use today. In particular, an SCI entity will have the ability to implement material systems changes without having to individually report each material systems change to the Commission 30 days in advance, which commenters noted could lead SCI entities to favor the waterfall methodology of systems changes over the agile methodology.
                        <SU>1009</SU>
                        <FTREF/>
                         The Commission also believes that the adopted quarterly reporting requirement provides more flexibility to SCI entities with respect to the timing of implementing material systems changes. In particular, SCI entities will not be required to wait 30 calendar days after notifying the Commission in order to implement a material systems change. Therefore, the adopted rule is responsive to commenters who stated that the proposed rule would stifle innovation, interfere with an entity's planning and development process, and expose SCI entities' systems to risk. Moreover, the Commission believes that elimination of the proposed 30-day advance notification requirement is responsive to commenters' concern that ATSs are already required to report material changes to the operation of the ATSs at least 20 calendar days prior to implementation, and that proposed Regulation SCI would extend the advance notification period to 30 calendar days.
                        <SU>1010</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1009</SU>
                             At the same time, because systems changes utilizing the waterfall methodology are often planned well in advance, these systems changes would generally be included in the quarterly report, as Rule 1003(a) requires the quarterly report to describe, among other things, planned material systems changes during the subsequent calendar quarter. However, this requirement of Rule 1003(a) is not limited to planned material systems changes utilizing the waterfall methodology, but also would apply to planned material systems changes utilizing other development methodologies, including the agile methodology.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1010</SU>
                             The Commission notes that the adoption of Rule 1003(a) does not affect an SCI ATS's existing obligation under Rule 301(b)(2)(ii) of Regulation ATS to file amendments on Form ATS at least 20 calendar days prior to implementing material change to the operation of the ATS. Therefore, with respect to a material systems change, an SCI ATS may be required to describe such change in a quarterly report under Rule 1003(a) and submit an amendment to Form ATS.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also believes that adopting the quarterly reporting requirement instead of the 30-day advance notification requirement lessens SCI entities' burden of compliance as compared to the proposal.
                        <SU>1011</SU>
                        <FTREF/>
                         For example, rather than submitting a Form SCI for each material systems change, an SCI entity is now required to submit four reports each year pursuant to Rule 1003(a)(1) and, as applicable, supplemental reports pursuant to Rule 1003(a)(2). To the extent certain material systems changes are related or similar, an SCI entity will not be required to separately notify the Commission of each change. Instead, the SCI entity can describe such related changes within the single quarterly report. The Commission also believes that this quarterly report process will provide the Commission and its staff with a more efficient framework to review material systems changes that are described in the larger context afforded by such periodic reports, rather than parsing every submission that reports a material systems change.
                        <SU>1012</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1011</SU>
                             
                            <E T="03">See supra</E>
                             notes 996-997 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1012</SU>
                             The Commission acknowledges that some systems changes deployed by an SCI entity may not by themselves be considered material by the SCI entity, but that, in the aggregate, can be considered material by the SCI entity (
                            <E T="03">e.g.</E>
                            , making a series of small systems changes over time in order to implement a broad systems change). The Commission believes that the adopted quarterly reporting requirement is better suited to capture such changes than the proposed 30-day advance notification requirement (
                            <E T="03">i.e.</E>
                            , 30-day advance notification for each single systems change that is by itself considered material by the SCI entity).
                        </P>
                    </FTNT>
                    <P>
                        One commenter expressed concern that the proposed exception for exigent circumstances was too narrow.
                        <SU>1013</SU>
                        <FTREF/>
                         Because adopted Rule 1003(a)(1) requires quarterly reports of material systems changes rather than 30-day advance notification of each material systems change, the Commission is not adopting the proposed “exigent circumstances” exception. Specifically, the Commission notes that the purpose of the exception was to accommodate situations where it would not be prudent or desirable for an SCI entity to delay a systems change simply to provide 30-day advance notification of the change. At the same time, the Commission notes that, because Rule 1003(a)(1) requires in part a description of completed, ongoing, and planned material systems changes during the prior and current calendar quarters, an SCI entity's quarterly report will be required to include a description of all material changes to its SCI systems or the security of its indirect SCI systems, including those that have been implemented in response to exigent circumstances during the prior and current calendar quarters.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1013</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 15.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters suggested possible alternatives to the proposed requirements related to material systems changes. Some commenters suggested eliminating the proposed advance notification requirement for material systems changes.
                        <SU>1014</SU>
                        <FTREF/>
                         One of these commenters explained that information regarding material systems changes would be available to the Commission during an inspection, but stated that, if an advance notification requirement is adopted, it should be folded into the proposed semi-annual reporting requirement.
                        <SU>1015</SU>
                        <FTREF/>
                         Another commenter similarly urged that the Commission require only semi-annual reporting of material systems changes, as proposed in Rule 1000(b)(8).
                        <SU>1016</SU>
                        <FTREF/>
                         One commenter supported the reporting of material systems changes in the annual SCI review report.
                        <SU>1017</SU>
                        <FTREF/>
                         One commenter believed that information related to systems changes should be reported periodically.
                        <SU>1018</SU>
                        <FTREF/>
                         Another commenter noted that if the Commission retains the 30-day advance notification requirement, it should be limited to material systems changes of only higher priority SCI systems and that 
                        <PRTPAGE P="72339"/>
                        notifications of changes to lower criticality systems could be provided at the time of the change or periodically.
                        <SU>1019</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1014</SU>
                             
                            <E T="03">See</E>
                             MFA Letter at 7 and ITG Letter at 13-14. 
                            <E T="03">See also</E>
                             Joint SROs Letter at 8 (stating that material systems changes should be reported in a periodic, post-hoc basis, as was required under ARP).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1015</SU>
                             
                            <E T="03">See</E>
                             MFA Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1016</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1017</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1018</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 27.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1019</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 15.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters suggested that the Commission provide more flexibility and allow SCI entities more time to report material systems changes.
                        <SU>1020</SU>
                        <FTREF/>
                         One commenter supported giving SCI entities discretion to determine the appropriate timing and format for reporting changes to the Commission, and stated that the current practice under ARP to submit quarterly reports that cover changes for the previous and upcoming quarters has proven effective in keeping the Commission staff apprised of planned and completed systems changes.
                        <SU>1021</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1020</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 27; FINRA Letter at 27; and MSRB Letter at 22. 
                            <E T="03">See also</E>
                             CME Letter at 11 (stating “instead of setting firm time limits under which an entity is required to submit notifications of material systems changes under Rule 1000(b)(6), the Commission should instead simply require `timely advance notice of all material planned changes to SCI systems that may impact the reliability, security, or adequate scalable capacity of such systems'”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1021</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 27.
                        </P>
                    </FTNT>
                    <P>
                        One commenter suggested that SCI entities be required to keep records of all systems changes and technical issues, and make that information available to the Commission upon request.
                        <SU>1022</SU>
                        <FTREF/>
                         If the Commission decides to retain the notification requirement, this commenter recommended that it be satisfied through periodic (ideally, quarterly) reporting of material systems changes.
                        <SU>1023</SU>
                        <FTREF/>
                         One commenter believed the Commission should allow all 30-day advance notifications regarding pending material systems changes to be communicated orally, and only submitted in writing after development and testing is completed and the feature is finalized.
                        <SU>1024</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1022</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1023</SU>
                             
                            <E T="03">See id.</E>
                             This commenter also noted that this would allow for the elimination of proposed Rule 1000(b)(6)(ii), which required notices for material inaccuracies in prior notifications. 
                            <E T="03">See</E>
                             OTC Markets Letter at 20-22. According to this commenter, quarterly updates would disclose material deviations from plans described in a previous report, whether stemming from inaccuracies in prior reports or new information that prompts beneficial deviations from a systems implementation plan. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1024</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 22.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that the adopted quarterly reporting requirement is responsive to commenters who requested additional flexibility or time for material systems change notifications, as well as to commenters who suggested that such notices be submitted on a periodic or quarterly basis.
                        <SU>1025</SU>
                        <FTREF/>
                         The Commission does not agree with the commenters who suggested that the Commission completely eliminate the advance notification requirements. The Commission believes that advance notifications of planned material systems changes will help ensure that the Commission has up-to-date information regarding important future systems changes at an SCI entity, to aid in its understanding of the operations and functionality of the systems post-change.
                        <SU>1026</SU>
                        <FTREF/>
                         As adopted, Rule 1003(a)(1) requires an SCI entity to provide the Commission with advance notification of planned material systems changes in the current and subsequent quarters through the quarterly reports. As noted above, after considering the views of commenters, the Commission is not adopting the proposed 30-day advance notification requirement for each material systems change.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1025</SU>
                             Because the Commission is only adopting a quarterly reporting requirement for material systems changes, the adopted approach is responsive to a commenter's suggestion that notifications of changes to lower criticality systems could be provided at the time of the change or periodically. 
                            <E T="03">See supra</E>
                             note 1019 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1026</SU>
                             The Commission acknowledges that there may occasionally be unexpected material systems changes that are not reported to the Commission in advance, but expects that material systems changes generally will be planned well in advance and reported in the quarterly report accordingly.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is also not adopting commenters' suggestion that material systems changes be reported semi-annually or annually.
                        <SU>1027</SU>
                        <FTREF/>
                         As noted in the SCI Proposal, proposed Rule 1000(b)(8)(ii) required semi-annual reports because the proposal would have separately required information relating to each planned material systems change to be submitted at least 30 calendar days before its implementation.
                        <SU>1028</SU>
                        <FTREF/>
                         Thus, in the SCI Proposal, the Commission stated its preliminary view that requiring ongoing summary reports more frequently would not be necessary.
                        <SU>1029</SU>
                        <FTREF/>
                         At the same time, the Commission expressed the concern that a longer period of time would permit significant updates and milestones relating to systems changes to occur without notice to the Commission.
                        <SU>1030</SU>
                        <FTREF/>
                         Because the Commission is not adopting the 30-day advance notification requirement, the Commission believes that it is appropriate to require more frequent reports of material systems changes than on a semi-annual basis. Further, as noted above, some commenters suggested quarterly reports, which is consistent with the practice of some entities under the ARP Inspection Program.
                        <SU>1031</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1027</SU>
                             
                            <E T="03">See supra</E>
                             notes 1015-1017 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1028</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18124.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1029</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1030</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1031</SU>
                             
                            <E T="03">See supra</E>
                             notes 1021, 1023 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission does not agree with the commenter who suggested that Regulation SCI should only require SCI entities to keep records of all systems changes and make that information available to the Commission upon request.
                        <SU>1032</SU>
                        <FTREF/>
                         Similarly, the Commission does not agree with commenters who suggested that SCI entities be given discretion to determine the timing of the reports.
                        <SU>1033</SU>
                        <FTREF/>
                         The Commission believes that quarterly reporting of material systems changes will help ensure that the Commission has, on an ongoing basis, a comprehensive view and up-to-date information regarding material systems changes at an SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1032</SU>
                             
                            <E T="03">See supra</E>
                             note 1022 and accompanying text. As discussed above, this commenter also stated that, if the Commission decides to retain the notification requirement for material systems changes, the Commission should require periodic (ideally, quarterly) reporting. 
                            <E T="03">See supra</E>
                             note 1023 and accompanying text. Adopted Rule 1003(a)(1) is consistent with this commenter's alternative suggestion.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1033</SU>
                             
                            <E T="03">See supra</E>
                             note 1021 and accompanying text. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 1020.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the commenter who suggested that all 30-day advance material systems change notifications should be provided orally, and submitted in writing only after the changes are fully tested and implemented,
                        <SU>1034</SU>
                        <FTREF/>
                         the Commission notes that it is not adopting the proposed 30-day advance notification requirement for material systems changes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1034</SU>
                             
                            <E T="03">See supra</E>
                             note 1024 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the commenter who suggested giving SCI entities discretion to determine the format for reporting changes to the Commission,
                        <SU>1035</SU>
                        <FTREF/>
                         the Commission notes that Rule 1003(a) does not prescribe a specific style that the quarterly reports should take. The Commission intends for the quarterly report to allow the Commission and its staff to gain a sufficient level of understanding of the material systems changes that have been implemented, are on-going, and are planned for the future, which would aid the Commission and its staff in understanding the operations and functionality of the systems of an SCI entity and any changes to such systems. In particular, the Commission notes that Rule 1003(a)(1) only specifically requires the quarterly reports to “describe” the material systems changes and the dates or expected dates of their commencement and completion. Therefore, Rule 1003(a)(1) gives each 
                        <PRTPAGE P="72340"/>
                        SCI entity reasonable flexibility in determining precisely how to describe its material systems changes in the report in a manner that best suits the needs of that SCI entity as well as the needs of the Commission and its staff.
                        <SU>1036</SU>
                        <FTREF/>
                         In addition, to the extent the Commission seeks additional information about a given change noted in a quarterly report, an SCI entity would be required to provide Commission staff with such information in accordance with Rule 1005 (Recordkeeping Requirements Related to Compliance with Regulation SCI).
                        <SU>1037</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1035</SU>
                             
                            <E T="03">See supra</E>
                             note 1021 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1036</SU>
                             
                            <E T="03">See also</E>
                             Omgeo Letter at 43 (requesting that the Commission specify in the final rule the required content for a planned material systems change notification).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1037</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.C.
                        </P>
                    </FTNT>
                    <P>The Commission also notes that the quarterly reports are required to include descriptions of material systems changes during the prior calendar quarter that were completed, ongoing, or planned. Therefore, if a report for the first quarter of a given year discusses the SCI entity's plan to implement a particular series of material changes to an SCI system, Rule 1003(a)(1) requires that, in the report for the second quarter of that year, the SCI entity describe the material systems changes that were completed, ongoing, and planned in the first quarter, including the planned changes discussed in the prior quarter's report, as applicable.</P>
                    <P>
                        Several commenters expressed concern that the proposed 30-day advance notification requirement would potentially give the Commission new authority to “reject” a Form SCI filing describing material systems changes, similar to the way the Commission may reject an improperly filed proposed rule change pursuant to Rule 19b-4 under the Exchange Act.
                        <SU>1038</SU>
                        <FTREF/>
                         Three commenters requested that the Commission clarify how proposed Rule 1000(b)(6) would relate to Rule 19b-4, suggesting that there may be unnecessary redundancy between the two processes.
                        <SU>1039</SU>
                        <FTREF/>
                         Another commenter suggested limiting the types of changes that would require 30-day advance notification to those changes that are already required to be filed with the Commission as proposed rule changes for immediate effectiveness under Section 19(b)(3)(A) of the Exchange Act (excluding those filings that would not become operative for 30 days after the date of the filing because those filings would already provide the Commission with 30 days' advance notification of the material systems changes).
                        <SU>1040</SU>
                        <FTREF/>
                         This commenter also noted that where a material systems change would be filed for approval under Section 19(b)(2) of the Exchange Act, the Section 19(b)(2) approval process provides the Commission sufficient notification of the systems change.
                        <SU>1041</SU>
                        <FTREF/>
                         One commenter stated that proposed Rule 1000(b)(6) was improperly premised on the notion that the Commission should be responsible for a minutely-detailed understanding of the IT infrastructure of SCI entities and for assessing prospective changes in advance of their implementation.
                        <SU>1042</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1038</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 23; and SIFMA Letter at 16. 
                            <E T="03">See</E>
                             Section 19(b) of the Exchange Act, 15 U.S.C. 78s(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1039</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; Joint SROs Letter at 8; and FIF Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1040</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1041</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 22. This commenter also suggested that material systems changes (other than those filed pursuant to Rule 19b-4 under the Exchange Act) be reported semi-annually, or that de minimis changes be excepted from the notice requirement altogether if the Commission continues to require 30-day advance notification. 
                            <E T="03">See</E>
                             MSRB Letter at 22-23. As discussed above, the Commission is adopting a quarterly reporting requirement for systems changes that an SCI entity determines to be material.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1042</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 1, 8. 
                            <E T="03">See also</E>
                             ITG Letter at 13-14 (stating that the Exchange Act does not enable the Commission to “bootstrap its SRO rule review authority or its national market system authority to force regulated entities to submit upcoming material systems changes for agency approval” and that “the Commission need only receive notifications when they are a significant part of proposed rule changes by SROs or amendments to Form ATS of material changes to the operation of the ATS”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission disagrees with commenters who believed that material systems change reports are redundant given the rule filing requirements of Rule 19b-4 under the Exchange Act, or that material systems change reports should not be required if the SCI entity submitted certain types of rule filings regarding the same change.
                        <SU>1043</SU>
                        <FTREF/>
                         The Commission acknowledges that some systems changes require proposed rule changes under Rule 19b-4, and some Rule 19b-4 proposed rule changes result in systems changes. However, based on Commission staff's experience with the ARP Inspection Program and the rule filing process, the Commission believes that the type of information regarding systems changes included in rule filings is different from the type of information that will be included in reports on material systems changes. In particular, the technical details or specifications of SCI systems and indirect SCI systems are generally not specifically set forth in the rules of an SCI SRO. Therefore, technical information regarding systems changes is usually not set forth in rule filings. In addition, the Commission notes that the rule filing process and the material systems change reports serve different purposes. In particular, the material systems change reports are intended to inform the Commission and its staff of important technical changes to an SCI entity's systems. On the other hand, the rule filing process provides notice of changes to an SCI entity's rules, including, for example, the statutory basis for such changes, and in some cases seeks approval by the Commission of the rule changes. Therefore, if an SCI SRO submits a rule filing regarding a particular systems change and the change is also included in a material systems change report, the information included in the rule filing may not necessarily further the goal of the material systems change reporting requirement, and the information included in the material systems change report may not necessarily assist in the Commission's review of the rule filing. Moreover, commenters' concern regarding the redundancy between the rule filing process and the material systems change reports stemmed from concerns regarding the 30-day advance notification requirement. As discussed above, the Commission is not adopting a 30-day advance notification requirement.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1043</SU>
                             
                            <E T="03">See supra</E>
                             notes 1039-1041 and accompanying text. The Commission notes that the requirement under Regulation SCI to submit reports of material systems changes does not alter an SRO's obligation to file proposed rule changes, the obligation of participants of an SCI Plan to file a proposed amendment to such SCI Plan, or any other obligation any SCI entity may have under the Exchange Act or rules thereunder.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also reiterates that the material systems change reports are intended to inform the Commission and its staff of such changes and help the Commission in its oversight of U.S. securities market infrastructure. Regulation SCI does not provide for a new approval process for SCI entities' material systems changes. As such, Commission staff will not use material systems change reports to require any approval of prospective systems changes in advance of their implementation pursuant to any provision of Regulation SCI,
                        <SU>1044</SU>
                        <FTREF/>
                         or to delay implementation of material systems changes pursuant to any provision of Regulation SCI.
                        <SU>1045</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1044</SU>
                             
                            <E T="03">See supra</E>
                             note 1042 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1045</SU>
                             
                            <E T="03">See supra</E>
                             note 1038 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Three commenters questioned the Commission's legal authority to adopt the proposed material systems change notification requirements, including, in particular, those set forth in proposed Rule 1000(b)(6).
                        <SU>1046</SU>
                        <FTREF/>
                         For the reasons 
                        <PRTPAGE P="72341"/>
                        discussed above in Section IV.B.3.c, the Commission disagrees with these comments and believes that adopted Rule 1003(a) will assist the Commission in its oversight of U.S. securities market infrastructure consistent with its legal authority under the Exchange Act.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1046</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 4 (stating the belief that “[a]uthority to facilitate a national market or assure economically efficient execution of securities transaction is remote from close, minute regulation of computer systems and computer security”); ITG Letter at 13 (stating the belief that the proposed notification requirement for material systems 
                            <PRTPAGE/>
                            changes “would extend the SEC's reach far beyond that of a securities regulator and instead enable it to regulate the IT process of marketplace participants” and that the Exchange Act does not enable the Commission to “bootstrap its SRO rule review authority or its national market system authority to force regulated entities to submit upcoming material systems changes for agency approval”); and KCG Letter at 19 (stating the belief that “[t]he Commission does not have authority to stop implementation of systems changes by ATSs or systems changes that exchanges are not required to submit under Section 19(b) of the Exchange Act”).
                        </P>
                    </FTNT>
                    <P>
                        In light of the 30-day advance notification requirement in proposed Rule 1000(b)(6), some commenters suggested eliminating the semi-annual reporting requirement in proposed Rule 1000(b)(8)(ii) because they considered it duplicative and unnecessary.
                        <SU>1047</SU>
                        <FTREF/>
                         One commenter believed that the required semi-annual reporting requirement was excessive and should instead be incorporated into the annual reporting obligations in proposed Rule 1000(b)(8)(i).
                        <SU>1048</SU>
                        <FTREF/>
                         As discussed above, the Commission is adopting a quarterly reporting requirement under Rule 1003(a)(1) and is not adopting the proposed 30-day advance notification requirement. Therefore, the Commission is not adopting the requirement in proposed Rule 1000(b)(8)(ii) for semi-annual progress reports.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1047</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 24-25; and OCC Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1048</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 11.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Definition of Material Systems Change</HD>
                    <P>
                        Commenters generally opposed the proposed definition of material systems change. Many commenters stated their belief that the term was too broad and would therefore necessitate an excessive number of notifications of material systems changes.
                        <SU>1049</SU>
                        <FTREF/>
                         Some commenters believed that the definition should be revised and offered a variety of suggestions.
                        <SU>1050</SU>
                        <FTREF/>
                         Several commenters advocated for creating a risk-based definition whereby, for example, notifications are only required for those material systems changes that pose a risk to critical operations of an entity.
                        <SU>1051</SU>
                        <FTREF/>
                         One commenter suggested that the requirement focus on SCI systems only.
                        <SU>1052</SU>
                        <FTREF/>
                         One commenter stated that SCI entities should be afforded flexibility to establish reasonable standards for defining material systems changes for their systems.
                        <SU>1053</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1049</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 14; MFA Letter at 6; ICI Letter at 4; BIDS Letter at 14; Liquidnet Letter at 3; FINRA Letter at 24-26; MSRB Letter at 22; NYSE Letter at 26-27; Joint SROs Letter at 7; CME Letter at 5; Oppenheimer Letter at 3; OTC Markets Letter at 20-21; and Direct Edge Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1050</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BATS Letter at 14-15 (recommending that only those material systems changes that are reported to an SCI entity's board of directors or similar body should be required to be reported to the Commission, which BATS stated is the standard it uses currently for the ARP Inspection Program); OCC Letter at 15 (stating that the reporting of systems changes to the board of directors, or to a similar governing body, is a more appropriate standard for determining materiality than reporting to “senior management”); BIDS Letter at 14-15 (stating its belief that the Commission should define a “material systems change” to be a large-scale architectural upgrade, the implementation of industry-wide rules or other market structure changes, or other technology changes that may be required because of changes in trading rules defined in the exchange's or the ATS's trading rule book); and FIF Letter at 5 (recommending that the term be defined to include significant functional enhancements, major technology infrastructure changes, or changes requiring member/participant notifications).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1051</SU>
                             
                            <E T="03">See, e.g.,</E>
                             OCC Letter at 15; DTCC Letter at 16; Liquidnet Letter at 3; MFA Letter at 6; ICI Letter at 4; CME Letter at 5; and Direct Edge at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1052</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 27.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1053</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 27.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters sought guidance from the Commission on the materiality threshold, which commenters believed was unclear, explaining, for example, that the term “material” appears both in the term “material systems change” and in the definition of that term.
                        <SU>1054</SU>
                        <FTREF/>
                         Similarly, several commenters requested that the Commission provide more guidance on the meaning of “material” in the context of systems changes because, although the wording of the proposed definition contained the concept of “materiality,” the commenters believed some of the examples provided in the SCI Proposal to be non-material.
                        <SU>1055</SU>
                        <FTREF/>
                         One commenter asked that the Commission clearly define what types of systems changes are not subject to the prior notification requirement in order to avoid receiving notices of all systems changes, material or otherwise.
                        <SU>1056</SU>
                        <FTREF/>
                         One commenter asked that the Commission clarify the meaning of “material” and confirm that prior notification would not be required for changes that do not pertain to the production environment.
                        <SU>1057</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1054</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 3-4; OCC Letter at 15; and NYSE Letter at 26.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1055</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint SROs Letter at 7; DTCC Letter at 15-16; Omgeo Letter at 23; OCC Letter at 15; FINRA Letter at 27; OTC Markets Letter at 20-21; BIDS Letter at 14; Direct Edge Letter at 3-4; and ISE Letter at 8. 
                            <E T="03">See also</E>
                             supra note 1050.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1056</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1057</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 15-16.
                        </P>
                    </FTNT>
                    <P>Rather than adopting a detailed definition of material systems change as proposed, Rule 1003(a)(1) requires an SCI entity to establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material and to report to the Commission those changes the SCI entity identified as material in accordance with such criteria. This change is responsive to a commenter's suggestion that SCI entities should be granted flexibility to establish reasonable standards for determining whether a systems change is material. In addition, the Commission does not believe that it is appropriate to adopt a precise definition for the term “material systems change” because SCI entities differ in nature, size, technology, business model, and other aspects of their businesses. The Commission notes that there currently is no industry definition of “material systems change” that is applicable to all SCI entities that can serve as the basis for a precise definition of the term “material systems change” in Regulation SCI, and believes that whether a systems change is material is dependent on the facts and circumstances, such as the reason for the change and how it may impact operations. Moreover, requiring SCI entities to establish their own reasonable criteria for identifying material systems changes reflects the Commission's view that an SCI entity is in the best position to determine, in the first instance, whether a change, or series of changes, is material in the context of its systems. Because adopted Rule 1003(a)(1) allows each SCI entity to identify material systems changes, it is responsive to commenters' concern that the proposed definition was too broad and would result in an excessive number of notifications, and to commenters' suggestion that the definition should be revised.</P>
                    <P>
                        Further, the Commission's determination to not adopt the proposed definition of material systems change mitigates commenters' concern that the proposed definition was unclear. In particular, by eliminating the proposed definition of material systems change, the Commission seeks to eliminate the confusion caused by the proposed definition of this term, which contained the word “material.” Moreover, some commenters requested additional clarity on the definition of material systems change because they believed that some of the examples the Commission provided in the SCI Proposal were not material systems changes. Because adopted Rule 1003(a)(1) requires SCI entities to establish reasonable written criteria for identifying material systems changes, SCI entities will not be required to identify material systems changes in accordance with the detailed definition and examples from the SCI 
                        <PRTPAGE P="72342"/>
                        Proposal. Rather, an SCI entity will have reasonable discretion in establishing the written criteria in order to capture the systems changes that it believes are material. Specifically, the Commission believes that adopted Rule 1003(a) is sufficiently flexible to allow each SCI entity to identify changes that it believes are material, which may include some of the suggestions identified by the commenters if an SCI entity determines such changes to be appropriate to include in its criteria for identifying material systems changes. For example, if an SCI entity reasonably believes that its systems changes are material if they involve significant functional enhancements, major technology infrastructure changes, or changes requiring member/participant notifications, and such criteria is set forth in the SCI entity's reasonable written criteria, the SCI entity may identify material systems changes in accordance with such written criteria. Likewise, if an SCI entity reasonably believes that some of the examples of material systems changes identified in the SCI Proposal can appropriately serve as criteria for identifying material systems changes, and such criteria is set forth in the SCI entity's reasonable written criteria, the SCI entity may identify material systems changes in accordance with such written criteria.
                    </P>
                    <P>In response to a commenter's suggestion that the Commission clearly define what types of systems changes are not subject to the prior notification requirement in order to avoid notification of all systems changes, material or otherwise, the Commission notes that Rule 1003(a)(1) specifically requires SCI entities to identify material systems changes and report only material systems changes. With respect to a commenter's question regarding whether prior notification would be required for changes that do not pertain to the production environment, the Commission notes that SCI systems do not include development and testing systems, although indirect SCI systems could include development and testing systems if they are not walled-off from SCI systems. Therefore, Rule 1003(a) could apply to material changes to the security of development and testing systems that are not walled-off from SCI systems. Finally, with respect to a commenter's suggestion that Rule 1003(a) focus only on SCI systems, the Commission believes that notifications of material systems changes regarding the security of indirect SCI systems is important to the Commission's oversight of U.S. securities market infrastructure. At the same time, the Commission notes that Rule 1003(a)(1) provides that each SCI entity establish its own reasonable criteria for identifying a change to the security of its indirect SCI systems as material. Therefore, to the extent that an SCI entity determines that certain changes to the security of its indirect SCI systems are not material in accordance with its reasonable written criteria, such changes are not required to be reported to the Commission.</P>
                    <P>
                        As with an SCI entity's other policies and procedures under Regulation SCI, Commission staff may review an SCI entity's established criteria relating to the materiality of a systems change (
                        <E T="03">e.g.,</E>
                         in the course of an examination) to determine whether it agrees with the SCI entity's assessment that such criteria is reasonable and in compliance with the requirements of Rule 1003(a). The Commission believes that, by providing SCI entities flexibility in establishing the criteria and reviewing SCI entities' established criteria, it strikes the proper balance between granting discretion to SCI entities and ensuring that SCI entities carry out their obligations under Regulation SCI.
                    </P>
                    <HD SOURCE="HD3">iii. Adopted Rule 1003(a)(2): Supplemental Material Systems Change Reports</HD>
                    <P>
                        A commenter who advocated for a quarterly reporting requirement noted that quarterly updates would disclose material deviations from plans described in a previous report, including those stemming from inaccuracies in prior reports.
                        <SU>1058</SU>
                        <FTREF/>
                         Another commenter similarly noted that periodic reporting of any inaccuracies is sufficient for oversight purposes.
                        <SU>1059</SU>
                        <FTREF/>
                         The Commission believes that there may be circumstances in which an SCI entity realizes that information previously provided to the Commission in a quarterly report was materially inaccurate or that the quarterly report omitted material information. The Commission believes that it should, on an ongoing basis, have complete and correct information regarding material systems changes at an SCI entity, rather than waiting until the next quarterly report to receive corrected information, as suggested by these commenters. The Commission is therefore adopting Rule 1003(a)(2), which requires an SCI entity to promptly submit a supplemental report to notify the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a)(1). The Commission notes that the supplemental report requirement applies only if the error or omission in a prior report is material.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1058</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1059</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 28.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">5. SCI Review—Rule 1003(b)</HD>
                    <P>
                        Proposed Rule 1000(b)(7) required an SCI entity to conduct an SCI review of the SCI entity's compliance with Regulation SCI not less than once each calendar year, and submit a report of the SCI review to senior management of the SCI entity no more than 30 calendar days after completion of such SCI review.
                        <SU>1060</SU>
                        <FTREF/>
                         Further, proposed Rule 1000(b)(8)(i) required an SCI entity to submit to the Commission a report of the SCI review required by paragraph (b)(7), together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity.
                        <SU>1061</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1060</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(7) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.C.5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1061</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(8)(i) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.C.6.
                        </P>
                    </FTNT>
                    <P>
                        Proposed Rule 1000(a) defined the term “SCI review” to mean a review, following established procedures and standards, that is performed by objective personnel having appropriate experience in conducting reviews of SCI systems and SCI security systems, and which review contains: (1) A risk assessment with respect to such systems of the SCI entity; and (2) an assessment of internal control design and effectiveness to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards.
                        <SU>1062</SU>
                        <FTREF/>
                         In addition, the proposed definition provided that such review must include penetration test reviews of the SCI entity's network, firewalls, and production systems at a frequency of not less than once every three years.
                        <SU>1063</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1062</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(a) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.C.5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1063</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>The Commission is adopting the provisions relating to SCI reviews with modifications in response to comment. In addition, the Commission is adopting a definition of “senior management” in Rule 1000 for purposes of the SCI review requirement.</P>
                    <P>
                        Some commenters expressed support for the proposed requirements for SCI reviews,
                        <SU>1064</SU>
                        <FTREF/>
                         with a few advocating that the SCI review be conducted by an independent third party, rather than “objective personnel.” 
                        <SU>1065</SU>
                        <FTREF/>
                         One commenter noted that it agreed that annual SCI reviews and reports can have a meaningful impact on improving 
                        <PRTPAGE P="72343"/>
                        technology and business practices.
                        <SU>1066</SU>
                        <FTREF/>
                         Another commenter expressed support for proposed Rule 1000(b)(7), but asked for clarification that any review of a processor under an NMS plan be performed independently of reviews of the same entity in other capacities (
                        <E T="03">e.g.,</E>
                         as an exchange or other SCI entity).
                        <SU>1067</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1064</SU>
                             
                            <E T="03">See, e.g.,</E>
                             MSRB Letter at 23; Lauer Letter at 5; Better Markets Letter at 5; and Direct Edge Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1065</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 5; Better Markets Letter at 5; and BlackRock Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1066</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 6 (expressing support for the SCI review requirement while also providing suggestions for modifications to the rule).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1067</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        With regard to the suggestion that the Commission adopt a requirement that SCI reviews be conducted by an independent third party rather than “objective personnel” as proposed,
                        <SU>1068</SU>
                        <FTREF/>
                         the Commission continues to believe that it is appropriate to permit SCI reviews to be performed by personnel of the SCI entity or an external firm, provided that such personnel are, in fact, objective and, as required by rule, have the appropriate experience to conduct reviews of SCI systems and indirect SCI systems. Experienced personnel should have the knowledge and skills necessary to conduct such reviews. In the SCI Proposal, the Commission noted that to satisfy the criterion that an SCI review be conducted by “objective personnel,” it should be performed by persons who have not been involved in the development, testing, or implementation of such systems being reviewed.
                        <SU>1069</SU>
                        <FTREF/>
                         The Commission continues to believe that persons who were not involved in the process for development, testing, and implementation of the systems being reviewed would generally be in a better position to identify weaknesses and deficiencies that were not identified in the development, testing, and implementation stages. The Commission believes that, given the requirement that such personnel be “objective,” any personnel with conflicts of interest that have not been adequately mitigated to allow for objectivity should be excluded from serving in this role. In particular, the Commission believes that a person or persons conducting an SCI review should not have a conflict of interest that interferes with their ability to exercise judgment, express opinions, and present recommendations with impartiality. While the Commission recognizes that, as one commenter asserted, all personnel of an SCI entity could be viewed as having some level of conflict of interest,
                        <SU>1070</SU>
                        <FTREF/>
                         the Commission believes that SCI entities can have appropriate policies and procedures in place to mitigate such conflicts or to help ensure that certain departments and/or specified personnel (such as internal audit departments) are appropriately insulated from such conflicts so as to be able to objectively conduct SCI reviews.
                        <SU>1071</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1068</SU>
                             
                            <E T="03">See supra</E>
                             note 1065 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1069</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18123.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1070</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1071</SU>
                             For example, the Commission believes that many entities implement a reporting structure pursuant to which internal audit employees or departments report directly to the board of directors or an audit committee of the board. The Commission notes that, while utilizing external personnel (
                            <E T="03">i.e.,</E>
                             third parties) to conduct an SCI entity's SCI review generally would not raise the same concerns regarding objectivity, the SCI entity would likewise need to mitigate any conflicts of interest that would prevent such personnel from meeting the objectivity standard required for an SCI review. For example, among the factors an SCI entity may consider in evaluating the objectivity of a third party review could be who within the SCI entity is managing the third party review, is setting the scope of review, is authorizing payment for such review, and has the authority to review and comment on the third party report, among others. Further, an SCI entity may consider the third party's ability to remain objective in light of any other services provided by the third party to the SCI entity.
                        </P>
                    </FTNT>
                    <P>
                        Accordingly, the Commission believes that the goals of Regulation SCI can be achieved through reviews by either internal objective personnel or external objective personnel. Taking into consideration the advantages and disadvantages associated with each approach, each SCI entity should make its own determination regarding the levels of review or assurance that can be provided by different personnel, the best means to ensure their objectivity, and whether it is appropriate to incur the additional costs of an independent third party review. An SCI entity may, for example, determine that it is appropriate to utilize personnel not employed by the SCI entity (
                        <E T="03">i.e.,</E>
                         third parties) to conduct such review each year or only on a less frequent, periodic basis (
                        <E T="03">e.g.,</E>
                         every three years), or only with regard to certain of its systems. In addition, with regard to one commenter's suggestion that an SCI review should be performed independently for each capacity in which an SCI entity acts, the Commission notes that the definition of SCI review and provisions of Rule 1003(b) require that an SCI entity perform a review, following established procedures and standards, for compliance with Regulation SCI that includes a risk assessment of the SCI entity's SCI systems and indirect SCI systems and an assessment of internal control design and effectiveness of such systems and does not require an SCI entity that serves in two different capacities with respect to Regulation SCI to conduct two independent SCI reviews. The Commission believes that, as a practical matter, an SCI entity may determine that, to comply with these requirements, it is necessary to conduct separate assessments and analysis for each capacity of the SCI entity, because the standards used, risk assessments, applicable policies and procedures, and assessment of internal control design and effectiveness are different with regard to the distinct and differing functions of the SCI entity in each capacity. For example, an entity that meets both the definition of an SCI SRO and a plan processor may determine that it is necessary to conduct separate reviews for each function performed, because, for instance, the findings of a risk assessment determine that certain SCI systems fall into the category of “critical SCI systems” with regard to the functions of the plan processor, but not with regard to the functions of the SRO. At the same time, the Commission notes that, even where separate reviews are conducted, there may be certain overlap in conducting such reviews (for example, the entity may use the same objective reviewer for each function performed), such reviews may be conducted at the same time, and a single SCI review report may contain findings for each capacity.
                    </P>
                    <P>
                        While other commenters also supported some form of review, many of these commenters stated that the term SCI review is defined too broadly and/or that the SCI review requirements should allow more flexibility.
                        <SU>1072</SU>
                        <FTREF/>
                         Some commenters expressed concerns about the need to review all systems on an annual basis, which they argued could be costly, burdensome, and unnecessary.
                        <SU>1073</SU>
                        <FTREF/>
                         Several commenters suggested the adoption of a risk-based approach for determining the scope of the review, which would entail conducting a risk assessment to determine which systems should be reviewed and how often.
                        <SU>1074</SU>
                        <FTREF/>
                         Under such an approach, the highest risk systems would be reviewed more frequently than other, less critical systems, which could be reviewed less frequently than annually or on a rotational basis. Similarly, one 
                        <PRTPAGE P="72344"/>
                        commenter recommended that SCI reviews should be focused only on those core systems capable of having a material impact on members or participants, and “adjacent” systems should not be subject to the review process.
                        <SU>1075</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1072</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 39-41; Omgeo Letter at 23-24; OCC Letter at 19; NYSE Letter at 35; SIFMA Letter at 17; DTCC Letter at 16-17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1073</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 39-41; Omgeo Letter at 23-24; OCC Letter at 19; NYSE Letter at 35; DTCC Letter at 16-17; and BIDS Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1074</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 39-41; OCC Letter at 19; NYSE Letter at 35; SIFMA Letter at 17; DTCC Letter at 16-17; LiquidPoint Letter at 3; and Omgeo Letter at 24. One commenter noted that the proposed SCI review requirement essentially eliminated the ability to utilize its current risk assessment approach to determine the frequency of review for each system (ranging from annually to once every four years). 
                            <E T="03">See</E>
                             FINRA Letter at 40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1075</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 6.
                        </P>
                    </FTNT>
                    <P>
                        After considering the views of commenters, the Commission has determined to adopt the provisions relating to SCI reviews with modifications in response to comment.
                        <SU>1076</SU>
                        <FTREF/>
                         Thus, adopted Rule 1003(b) requires an SCI entity to conduct an SCI review of the SCI entity's compliance with Regulation SCI not less than once each calendar year.
                        <SU>1077</SU>
                        <FTREF/>
                         However, the Commission notes that, because it has revised the scope of the definition of “SCI systems” as described above, fewer systems of each SCI entity will be subject to the SCI review, thereby focusing the overall scope of the SCI review requirement.
                        <SU>1078</SU>
                        <FTREF/>
                         Further, to address some commenters' concerns about the burdens and inflexibility of the proposed rule and the recommendation that the proposed rule utilize a more risk-based approach, the adopted rule is being revised to allow assessments of SCI systems directly supporting market regulation or market surveillance to be conducted, based upon a risk-assessment, at least once every three years, rather than annually.
                        <SU>1079</SU>
                        <FTREF/>
                         SCI entities would be required to determine the specific frequency with which to conduct assessments of these systems depending on the risk assessment that they conduct as part of the annual SCI review, provided that these systems are assessed at least once every three years. The Commission believes that market regulation and market surveillance systems have the potential to pose less risk to an entity or the market than other SCI systems. While the Commission believes that these systems are essential to investor protection and market integrity and that they can pose a significant risk to the markets in the event of a systems issue, the Commission also believes that certain market regulation and market surveillance systems may not have as immediate or widespread of an impact on the maintenance of fair and orderly markets or an entity's operational capability as the other categories of systems included within the definition of SCI systems. While a systems issue affecting a trading system could result in the immediate inability of a market, and thus market participants, to continue trading on such system and potentially impact trading on other markets as well, the Commission believes that the temporary disruption or failure of a SCI entity's market regulation and/or market surveillance systems in the wake of a wide-scale disruption would likely not have as direct an impact on market participants' ability to continue to trade. Thus, after considering commenters' views regarding the costs and burdens of the proposed SCI review requirements, as well as the suggestion that the Commission incorporate more of a risk-based approach in Regulation SCI, the Commission believes that a longer frequency of review of these systems may be appropriate in cases where the risk assessment conducted as part of the SCI review results in such a determination. The Commission also notes that, as originally proposed the rule would have required penetration test reviews of the SCI entity's network, firewalls and development, testing, and production systems at a frequency of not less than once every three years in recognition of the potentially significant costs that may be associated with the performance of such tests.
                        <SU>1080</SU>
                        <FTREF/>
                         However, consistent with modifications to the definition of SCI systems, references to development and test systems have been deleted in adopted Rule 1003(b)(1)(i).
                        <SU>1081</SU>
                        <FTREF/>
                         The Commission notes that SCI entities may, however, determine that based on its risk assessment, it is appropriate and/or necessary to conduct such penetration test reviews more frequently than once every three years.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1076</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b). However, the Commission is moving the clause regarding penetration test reviews from the definition of SCI review into Rule 1003(b), which addresses the timing of reviews. Further, the adopted definition of SCI review will require that the objective reviewer have “appropriate experience to conduct reviews” rather than “appropriate experience in conducting reviews” as proposed. The Commission believes this revision is appropriate given that, prior to the adoption of Regulation SCI today, no individual or entity would have experience in conducting the specific SCI reviews required by Rule 1003(b). Rather, the Commission believes that there are individuals or entities that have experience in conducting reviews, audits, and/or testing similar to the functions that would be necessary to address certain aspects of the SCI review requirement, and thus, the objective reviewer should have this type of appropriate experience that would allow them to conduct SCI reviews in accordance with the requirements of Regulation SCI. Thus, as adopted, the term “SCI review” means “a review, following established procedures and standards, that is performed by objective personnel having appropriate experience to conduct reviews of SCI systems and indirect SCI systems, and which review contains: (1) A risk assessment with respect to such systems of an SCI entity; and (2) An assessment of internal control design and effectiveness of its SCI systems and indirect SCI systems to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards.” 
                            <E T="03">See</E>
                             Rule 1000. Further, the Commission is moving the requirement relating to reports to the Commission on SCI reviews from proposed Rule 1000(b)(8) into Rule 1003(b) so that all provisions regarding SCI reviews are in the same rule.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1077</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1078</SU>
                             The Commission also notes that it has clarified that the definition of “indirect SCI systems” includes only those systems that have not been effectively logically or physically separated from SCI systems. Thus, the scope of the SCI review is also more focused than what some commenters may have believed. It is also further focused by the elimination of references to development and test systems from the penetration test requirement in adopted in Rule 1003(b)(1)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1079</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b)(1)(ii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1080</SU>
                             As noted by some commenters, penetration tests are highly technical and would require special expertise, and thus the Commission believes such testing could potentially require substantial costs. 
                            <E T="03">See, e.g.,</E>
                             DTCC Letter at 17; and Omgeo Letter at 44. 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Sections V.D.2.d and VI.C.2.b.vi (discussing estimated costs associated with the SCI review requirement, which takes into consideration the costs of penetration testing) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18123 (stating that the Commission seeks to balance the frequency of such tests with the costs associated with performing the tests). As noted in the SCI Proposal, the Commission believes that the penetration test reviews should help an SCI entity evaluate the system's security and resiliency in the face of attempted and successful intrusions. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1081</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing elimination of development and test systems from the definition of SCI systems).
                        </P>
                    </FTNT>
                    <P>
                        The Commission is not, however, adopting a broader risk-based approach to determine the required frequency of an SCI review (
                        <E T="03">i.e.,</E>
                         for SCI systems other than market regulation and market surveillance systems), as suggested by some commenters.
                        <SU>1082</SU>
                        <FTREF/>
                         The Commission believes that a critical element to ensuring the capacity, integrity, resiliency, and availability of SCI systems and indirect SCI systems is conducting an annual objective review to assess the risks of an SCI entity's systems and the effectiveness of its internal information technology controls and procedures. Such reviews will not only assist the Commission in improving its oversight of the technology infrastructure of SCI entities, but also each SCI entity in assessing the effectiveness of its information technology practices, helping to ensure compliance with the safeguards provided by the requirements of Regulation SCI, identifying potential areas of weakness that require additional or modified controls, and determining where to best devote resources. Further, the Commission believes that the competitive environment of today's securities markets drives SCI entities to continually update, modify, and introduce new technology and systems, often in an effort to meet specific business needs and achieve “quick-to-market” results, potentially without 
                        <PRTPAGE P="72345"/>
                        adequate focus on ensuring the continuous integrity of its systems. In addition, given today's fast-paced nature of technological advancement, existing controls can quickly become obsolete or ineffective and the relative criticality or risk nature of a system can change over time as well.
                        <SU>1083</SU>
                        <FTREF/>
                         Further, as one commenter noted, it is not uncommon for entities to experience repeated unsuccessful attempts to gain access to their systems,
                        <SU>1084</SU>
                        <FTREF/>
                         which the Commission believes can expose certain vulnerabilities not identified previously and, if successful, also create new vulnerabilities and risk. For these reasons, the Commission believes that it is appropriate to require an SCI entity to conduct an SCI review of its applicable systems not less than once every 12 months.
                        <SU>1085</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1082</SU>
                             
                            <E T="03">See supra</E>
                             note 1074 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1083</SU>
                             In addition, the Commission believes changes in personnel with access to SCI systems throughout the year can create additional risk that should be considered in evaluating the risks of any particular system.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1084</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1085</SU>
                             The Commission notes that, while the rule requires that an SCI review be conducted “not less than once each calendar year,” an SCI entity may determine that it is appropriate to conduct an assessment of an SCI system more frequently, particularly for critical SCI systems. 
                            <E T="03">See</E>
                             adopted Rule 1003(b)(1).
                        </P>
                    </FTNT>
                    <P>
                        Further, the Commission notes that, as described in detail above, Regulation SCI is consistent with a risk-based approach in several areas, and thus, a risk assessment is appropriate in order to determine the standards and requirements applicable to a given SCI system. As such, the Commission believes that it is appropriate to require SCI entities to conduct a risk-based assessment with regard to its SCI systems and indirect SCI systems as part of its SCI review at least annually to help ensure that SCI entities are meeting the requirements of Regulation SCI.
                        <SU>1086</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1086</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b) and Rule 1000 (definition of “SCI review”).
                        </P>
                    </FTNT>
                    <P>
                        For the reasons noted above, the Commission believes it is appropriate to require that SCI reviews be conducted at least annually, rather than utilizing a risk-based approach to determine the 
                        <E T="03">frequency</E>
                         of the required SCI review.
                        <SU>1087</SU>
                        <FTREF/>
                         At the same time, the Commission notes that this provision is consistent with a risk-based approach in that SCI entities may design the scope and rigor of the SCI review for a particular system based on its risk assessment of such system, provided that the review meets the requirements of the rule, such as including an assessment of internal control design and effectiveness to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards 
                        <SU>1088</SU>
                        <FTREF/>
                         and performing penetration test reviews at least once every three years.
                        <SU>1089</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1087</SU>
                             However, as discussed above, an SCI entity may conduct an SCI review of its market regulation and market surveillance systems based upon its risk assessment of such systems, but not less than once every three years. 
                            <E T="03">See</E>
                             adopted Rule 1003(b)(1)(ii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1088</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (definition of “SCI review”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1089</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1003(b)(1)(i).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters sought clarification on various aspects of the SCI review requirement. One commenter stated that the term SCI review, as proposed, expanded significantly on what is required under ARP and asked for greater specificity as to the objectives and intended scope of the SCI review.
                        <SU>1090</SU>
                        <FTREF/>
                         This commenter suggested, as an alternative, that the Commission establish an “agreed upon procedures” approach, which would involve outlining specific SCI review objectives and procedures that would be performed by an objective reviewer.
                        <SU>1091</SU>
                        <FTREF/>
                         One commenter also requested that the Commission clarify whether there is a distinction between the existing ARP report and the SCI review and whether the ARP practice of on-site inspections would be eliminated.
                        <SU>1092</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1090</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 39-40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1091</SU>
                             
                            <E T="03">See id.</E>
                             at 40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1092</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 19.
                        </P>
                    </FTNT>
                    <P>
                        With regard to the comment seeking clarity on the scope of the review as compared to what is done under the current ARP Inspection Program,
                        <SU>1093</SU>
                        <FTREF/>
                         as noted in the SCI Proposal, the requirement for an annual SCI review was intended to formalize a practice in place under the current ARP Inspection Program in which SROs conduct annual systems reviews following established audit procedures and standards that result in the presentation of a report to senior SRO management on the recommendations and conclusions of the review.
                        <SU>1094</SU>
                        <FTREF/>
                         Specifically, the ARP Policy Statements called for each SRO to have its automated systems reviewed annually by an “independent reviewer” 
                        <SU>1095</SU>
                        <FTREF/>
                         and stated that independent reviews and analysis should: “(1) Cover significant elements of the operations of the automation process, including the capacity planning and testing process, contingency planning, systems development methodology and vulnerability assessment; (2) be performed on a cyclical basis by competent and independent audit personnel following established audit procedures and standards; and (3) result in the presentation of a report to senior SRO management on the recommendations and conclusions of the independent reviewer, which report should be made available to Commission staff for its review and comment.” 
                        <SU>1096</SU>
                        <FTREF/>
                         Similar to (1) above, the definition of SCI review requires the review to contain an assessment of internal control design and effectiveness of its SCI systems and indirect SCI systems to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards. Consistent with element (2), an SCI review must be performed by objective personnel having appropriate experience to conduct reviews of SCI systems and indirect SCI systems and must be performed following established procedures and standards. Finally, like item (3), Rule 1003(b)(2)-(3) requires SCI entities to submit a report of the SCI review to senior management after completion of the review, and following submission to senior management, to submit a report of the SCI review to the Commission, along with any response by senior management. Senior management, after reviewing the report, should note, in addition to any other response that may be made, any material inaccuracy or omission that, to their knowledge, is in the report. In this regard, the Commission recognizes that senior managers, by virtue of their positions and experience, may have differing levels of knowledge regarding their entity's SCI systems and indirect SCI systems and compliance with Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1093</SU>
                             
                            <E T="03">See supra</E>
                             note 1092 and accompanying text. 
                            <E T="03">See also supra</E>
                             note 1090 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1094</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18123.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1095</SU>
                             
                            <E T="03">See</E>
                             ARP I, 
                            <E T="03">supra</E>
                             note 1, at 48706-07. ARP I provided that an “independent reviewer” could be either an internal auditor group or an external audit firm so long as the independent reviewer had the competence, knowledge, consistency, and independence sufficient to perform the role.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1096</SU>
                             
                            <E T="03">See</E>
                             ARP II, 
                            <E T="03">supra</E>
                             note 1, at 22491. In ARP II, the Commission also explained that, in its view, “a critical element to the success of the capacity planning and testing, security assessment and contingency planning processes for [automated] systems is obtaining an objective review of those planning processes by persons independent of the planning process to ensure that adequate controls and procedures have been developed and implemented.” 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        While the SCI review requirement in Rule 1003 is based on the ARP review and report, a greater number of automated systems meeting the definition of SCI system or indirect SCI system would be subject to the SCI review requirements because the scope of Regulation SCI expands upon the current ARP Inspection Program. The Commission notes that the SCI review is not a substitute for inspections and 
                        <PRTPAGE P="72346"/>
                        examinations conducted by Commission staff, and therefore SCI entities should expect that technology systems inspections and examinations will continue following the adoption of Regulation SCI. Along with notifications of material systems changes under adopted Rule 1003(a) and SCI event notifications pursuant to adopted Rule 1002(b), one purpose of SCI reviews will be to aid the Commission and its staff in understanding the operations and risks associated with the applicable systems of an SCI entity.
                    </P>
                    <P>
                        In addition, as noted above, one commenter, in seeking further clarity on the scope of the SCI review requirement, suggested that the Commission take an “agreed upon approach” which would outline more specific review objectives and procedures that would be performed by the objective reviewer. The Commission believes that an SCI entity should have the ability to design the specific parameters of an SCI review within the confines of the general framework of the rule, including identifying its own review objectives and procedures, given the SCI entity's in-depth knowledge of, and familiarity with, its own systems and their attendant risks. As such, the adopted rule is designed to provide a general framework for the scope of the SCI review by specifying that the review must include a risk assessment of SCI systems and indirect SCI systems and an assessment of the internal control design and effectiveness of its systems in certain areas.
                        <SU>1097</SU>
                        <FTREF/>
                         At the same time, the rule provides flexibility by permitting the review to be conducted “following established procedures and standards,” which would be identified and established by the SCI entity itself.
                        <SU>1098</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1097</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1000 (defining “SCI review”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1098</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Some commenters expressed views on the provisions requiring SCI entities to submit reports of the SCI review to senior management of the SCI entity and to the Commission. Specifically, two commenters supported the proposed requirement that reports of the SCI review be submitted to senior management of the SCI entity no later than 30 days after completion of the SCI review.
                        <SU>1099</SU>
                        <FTREF/>
                         One commenter urged that senior management of an SCI entity certify the report before it is submitted to the Commission in order to promote accountability at the highest ranks of the SCI entity.
                        <SU>1100</SU>
                        <FTREF/>
                         Another commenter believed that 45 days for submission of such reports to senior management would be more appropriate as a target timeframe given the complexity of the issues addressed in an SCI review, and that should this target fail to be met, the Board of Directors Audit Committee (or similar governing body) should be informed of the reason therefor.
                        <SU>1101</SU>
                        <FTREF/>
                         Two commenters recommended that the distribution cycle within proposed Rule 1000(b)(8)(i) be modified so that individual, focused audit reports resulting from rotational reviews could be bundled and distributed to the Commission on a regular basis (semi-annually or quarterly).
                        <SU>1102</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1099</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 23; and FIF Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1100</SU>
                             
                            <E T="03">See</E>
                             Better Markets Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1101</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1102</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 19; and DTCC Letter at 17.
                        </P>
                    </FTNT>
                    <P>
                        The Commission does not believe that it is necessary to require senior management certification of the report of the SCI review, as suggested by one commenter.
                        <SU>1103</SU>
                        <FTREF/>
                         Adopted Rules 1003(b)(2)-(3) require that the SCI entity submit a report of the SCI review to senior management of the SCI entity no more than 30 calendar days after completion of such SCI review, and that the SCI entity submit a report of the SCI review, together with any response by senior management, to the Commission and the board of directors of the SCI entity or the equivalent of such board within 60 calendar days after its submission to senior management. Because reports of SCI reviews and any responses by senior management are required to be filed using Form SCI under the Exchange Act and Regulation SCI, it is unlawful for any person to willfully or knowingly make, or cause to be made, a false or misleading statement with respect to any material fact in such reports or responses.
                        <SU>1104</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1103</SU>
                             
                            <E T="03">See supra</E>
                             note 1100 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1104</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Section 32(a) of the Exchange Act, 15 U.S.C. 78ff(a).
                        </P>
                    </FTNT>
                    <P>
                        The Commission recognizes that senior management certifications are used in other regulatory contexts, including in some Commission rules and regulations.
                        <SU>1105</SU>
                        <FTREF/>
                         However, at this time, the Commission believes that, in light of the other requirements for an SCI entity, the goals of Regulation SCI can be achieved without the imposition of an additional requirement on SCI entities for senior management certification. Specifically, the Commission believes that the adopted requirements promote the responsibility and accountability of senior management of an SCI entity by helping to ensure that senior management receives and reviews reports of SCI reviews, is made aware of issues relating to compliance with Regulation SCI, and is encouraged to promptly establish plans for resolving such issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1105</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 240.15c3-5(e)(2) (chief executive officer certification under the Market Access Rule); and 17 CFR 240.13a-14 (principal executive and principal financial officer certification of disclosure in annual and quarterly reports).
                        </P>
                    </FTNT>
                    <P>The Commission is also adopting a definition of “senior management” in Rule 1000 to make clear which individuals at an SCI entity must receive and review the report of the SCI review. The Commission believes that, in the context of the SCI review requirement, senior management should not be limited to a single individual or officer of an SCI entity. Thus, “senior management,” for purposes of adopted Rule 1003(b) is defined as an SCI entity's Chief Executive Officer, Chief Technology Officer, Chief Information Officer, General Counsel, and Chief Compliance Officer, or the equivalent of such employees or officers of an SCI entity. The Commission believes that, in order to achieve the goals of the rule to promote increased awareness and oversight of the technology infrastructure at an SCI entity by its most senior employees and officers, it is important that the SCI entity's senior management team receive and carefully review reports of SCI reviews. The Commission believes that these employees and officers, or their functional equivalent, represent the executive, technology, legal, and compliance functions that are necessary to effectively review the reports of SCI reviews. The Commission also believes that awareness by an SCI entity's senior management of SCI reviews and issues with Regulation SCI compliance should help to promote a focus by senior management on such reviews and issues, enhance communication and coordination regarding such reviews and issues among business, technology, legal, and compliance personnel, and, in turn, strengthen the capacity, integrity, resiliency, and availability of the systems of SCI entities. To help ensure that persons at the highest levels of an SCI entity are made aware of any issues raised in the SCI review, the Commission is also adopting a requirement for each SCI entity to submit to its board of directors or the equivalent of such board a report of the SCI review and any response by senior management within 60 calendar days after the submission of the report to senior management of the SCI entity.</P>
                    <P>
                        With regard to one commenter's suggestion that SCI entities should be given 45 days rather than 30 days to submit the report of the SCI review to senior management (and that it should be only a target timeframe rather than a 
                        <PRTPAGE P="72347"/>
                        requirement),
                        <SU>1106</SU>
                        <FTREF/>
                         the Commission notes that the 30-day timeframe is based on the Commission's experience with the current ARP Inspection Program that an ARP entity is able to consider the review and prepare a report for senior management consideration prior to the submission to the Commission.
                        <SU>1107</SU>
                        <FTREF/>
                         The Commission acknowledges that a greater number of systems will be subject to the SCI review requirement than the current ARP Inspection Program given the definitions of SCI system and indirect SCI system,
                        <SU>1108</SU>
                        <FTREF/>
                         and that the issues addressed in an SCI review may be complex. However, the Commission notes that the adopted timeframe, while based on experience with the current ARP Inspection Program, also takes into account these factors.
                        <SU>1109</SU>
                        <FTREF/>
                         Further, the Commission believes that the complexity of the issues presented during an SCI review would more likely affect the timing of conducting and completing the SCI review, rather than the timing for submitting a report of the review to senior management. The Commission, therefore, continues to believe that this requirement is appropriate. The Commission also notes that the requirement to submit the annual report to the Commission within 60 calendar days after its submission to senior management is similarly based on the Commission's experience with the ARP Inspection Program that this time period is a sufficient period to enable senior management to consider such review or report before submitting it to the Commission.
                        <SU>1110</SU>
                        <FTREF/>
                         Because an SCI entity will already have prepared the report and any response by senior management for filing with the Commission, the Commission believes that an SCI entity will not need significant additional time to submit the same report and response to its board of directors or the equivalent of such board.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1106</SU>
                             
                            <E T="03">See supra</E>
                             note 1101 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1107</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18123.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1108</SU>
                             The Commission also notes, however, that as discussed above, the scope of systems subject to Regulation SCI has been refined from what was proposed.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1109</SU>
                             The Commission notes that, while the ARP II Release recommended that an SRO's independent review should result in the presentation of a report to senior SRO management on the recommendations and conclusions of the independent review and such report should be made available to Commission staff, it did not provide recommended time periods for the submission of such reports. 
                            <E T="03">See</E>
                             ARP II Release, 
                            <E T="03">supra</E>
                             note 1. The adopted 30-day time period is based on experience with the ARP Inspection Program, as well as a consideration of the scope of the review required under Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1110</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18124.
                        </P>
                    </FTNT>
                    <P>Contrary to the suggestion of some commenters, the Commission does not believe it is appropriate to allow an SCI entity to delay the submission of SCI review reports to the Commission in order to bundle several reports together and submit them on a quarterly or semi-annual basis. Rather, the Commission believes that it is important to receive such reports in a timely manner after completion of the SCI review, so that the Commission is made aware of potential areas of weakness in an SCI entity's systems that may pose risk to the entity or the market as a whole, as well as areas of non-compliance with the provisions of Regulation SCI, without undue delay.</P>
                    <P>
                        With respect to clearing agencies, two commenters noted that the SCI review requirement potentially might overlap with staff guidance for clearing agencies that calls for an annual report on internal controls and recommended that the Commission consider further coordination on potential redundancies.
                        <SU>1111</SU>
                        <FTREF/>
                         The Commission notes that the section in the guidance provided in the Announcement for Standards for the Registration of Clearing Agencies referenced by commenters is distinct from the adopted SCI review requirement, as such section in the guidance relates to the review and evaluation of clearing agencies' 
                        <E T="03">accounting</E>
                         controls.
                        <SU>1112</SU>
                        <FTREF/>
                         In contrast, the SCI review requirement involves a risk assessment and assessment of internal control design and effectiveness of all of an SCI entity's SCI systems and indirect SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1111</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 19-20; and DTCC Letter at 18 (citing Securities Exchange Act Release No. 16900, 45 FR 41920, available at: 
                            <E T="03">http://sec.gov/rules/other/34-16900.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1112</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 16900 (June 17, 1980), 45 FR 41920 (June 23, 1980).
                        </P>
                    </FTNT>
                    <P>Finally, it should be noted that the required review and timely reporting to the Commission will enable the Commission and Commission staff to monitor the quality of compliance with Regulation SCI, thoroughness and robustness of SCI reviews, and the responses of senior management to such reviews. Accordingly, the Commission will be in a position to consider enhancing these regulatory requirements in the future, if necessary.</P>
                    <HD SOURCE="HD3">6. SCI Entity Business Continuity and Disaster Recovery Plans Testing Requirements for Members or Participants—Rule 1004</HD>
                    <P>Adopted Rule 1004 addresses testing of SCI entity business continuity and disaster recovery plans, including backup systems, by SCI entity members or participants. Rule 1004 corresponds to proposed Rule 1000(b)(9), and is adopted with certain modifications in response to comment, as discussed below.</P>
                    <HD SOURCE="HD3">a. Proposed Rule 1000(b)(9)</HD>
                    <P>Proposed Rule 1000(b)(9)(i) required each SCI entity, with respect to its BC/DR plans, to require participation by designated members or participants in scheduled functional and performance testing of the operation of such plans, in the manner and frequency specified by the SCI entity, at least once every 12 months. Proposed Rule 1000(b)(9)(ii) further required each SCI entity to coordinate the testing of such plans on an industry- or sector-wide basis with other SCI entities. Proposed Rule 1000(b)(9)(iii) would have additionally required each SCI entity to designate those members or participants it deems necessary, for the maintenance of fair and orderly markets in the event of the activation of its BC/DR plans, to participate in the testing of such plans, and notify the Commission of such designations and its standards for such designation on Form SCI.</P>
                    <HD SOURCE="HD3">b. Comments and Commission Response</HD>
                    <P>The Commission received significant comment on proposed Rule 1000(b)(9) and is adopting it with revisions, as Rule 1004. As more fully discussed below, the adopted rule requires designation of a more limited set of SCI entity members and participants for mandatory participation in BC/DR testing than the proposed rule. Further, the adopted rule does not require an SCI entity to file designation standards or member/participant designations with the Commission on Form SCI, as was proposed, but instead an SCI entity must keep records of its standards and designations. The scope, frequency, and coordination aspects of the proposed rule are adopted as proposed.</P>
                    <HD SOURCE="HD3">i. Mandatory BC/DR Testing Generally</HD>
                    <P>
                        Some commenters expressed general support for the goals of proposed Rule 1000(b)(9).
                        <SU>1113</SU>
                        <FTREF/>
                         One commenter in particular stated that “[i]t is vital that as many firms as possible participate in [market-wide] testing with conditions as realistic as possible.” 
                        <SU>1114</SU>
                        <FTREF/>
                         According to this commenter, broader mandatory participation in testing would be “one of the most valuable parts of Regulation SCI and will do the most to ensure improved market network reliability.”
                        <SU>1115</SU>
                        <FTREF/>
                         Another commenter 
                        <PRTPAGE P="72348"/>
                        expressed support for broad participation in BC/DR testing, but also expressed concern that the testing requirement would put SCI entities at a competitive disadvantage versus non-SCI entities.
                        <SU>1116</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1113</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter at 9; UBS Letter at 4-5; and FIF Letter at 6-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1114</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1115</SU>
                             
                            <E T="03">See id.</E>
                             at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1116</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 7.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters objected to the proposed mandatory testing requirement for SCI ATSs.
                        <SU>1117</SU>
                        <FTREF/>
                         For example, two commenters suggested that few ATSs are critical enough to warrant inclusion in the proposed mandatory testing requirement.
                        <SU>1118</SU>
                        <FTREF/>
                         One commenter urged that only SCI entities that provide market functions on which other market participants depend be subject to the requirements for separate backup and recovery capabilities.
                        <SU>1119</SU>
                        <FTREF/>
                         Another commenter stated that the added benefit of requiring fully redundant backup systems is almost impossible to measure while the cost of implementation is significant, and added further that fully redundant systems and increased testing do not guarantee a flawless backup plan.
                        <SU>1120</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1117</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 17; BIDS Letter at 8; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1118</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 5, 8; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1119</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1120</SU>
                             
                            <E T="03">See</E>
                             Group One Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        Two commenters stated that the current voluntary coordinated testing organized by SIFMA 
                        <SU>1121</SU>
                        <FTREF/>
                         already attracts significant participation without any mandate in place.
                        <SU>1122</SU>
                        <FTREF/>
                         However, a different commenter noted the difficulties it has encountered in fostering participation in its voluntary disaster recovery exercises, and stated that, despite encouraging users to participate in its disaster recovery exercises, participation levels were only 20 percent of its targeted high volume client base.
                        <SU>1123</SU>
                        <FTREF/>
                         One commenter sought clarification on whether the requirements of proposed Rule 1000(b)(9) would apply only to trading and clearance systems, or would extend to other SCI systems as well.
                        <SU>1124</SU>
                        <FTREF/>
                         Two commenters asked whether third parties that perform critical market functions for an SCI entity, such as data vendors and service bureaus, would be subject to the proposed requirement.
                        <SU>1125</SU>
                        <FTREF/>
                         One commenter stated that testing by an SCI entity of its business continuity capabilities should not be required to be coordinated with members.
                        <SU>1126</SU>
                        <FTREF/>
                         According to this commenter, “[t]he entire point of [business continuity plan testing] would be to not coordinate it with customers, and assess whether operations out of [backup] facilities was seamless to members and other market participants.” 
                        <SU>1127</SU>
                        <FTREF/>
                         One commenter stated that it would be more appropriate for SCI entities' members and participants to be responsible for their own business continuity plans and testing.
                        <SU>1128</SU>
                        <FTREF/>
                         The Commission has carefully considered commenters' views on the need for all SCI entities to be subject to the proposed mandatory testing requirement. The Commission continues to believe that adopted Rule 1004 should apply to all SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1121</SU>
                             SIFMA organizes an annual industry-wide testing exercise for firms and exchanges to submit and process test orders using their backup facilities. Participation is voluntary. 
                            <E T="03">See http://www.sifma.org/services/bcp/industry-testing/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1122</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 13; and Tellefsen Letter at 7-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1123</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 26 (noting also that it lacks the ability to require participation by its clients).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1124</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 37.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1125</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 39; and MSRB Letter at 25.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1126</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1127</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1128</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 17. In addition, some commenters believed that ATSs should be excluded from requiring members or participants to test, given that ATSs and their broker-dealer participants are already subject to FINRA Rule 4370, which relates to BC/DR plans. 
                            <E T="03">See</E>
                             FIA PTG Letter at 5; and BIDS Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        Whereas adopted Rule 1001(a)(2)(v) requires that each SCI entity's policies and procedures include BC/DR plans and specifies recovery goals and geographic diversity requirements for such plans,
                        <SU>1129</SU>
                        <FTREF/>
                         adopted Rule 1004 sets forth certain minimum requirements for SCI entity testing of its BC/DR plans. Adopted Rule 1004, like proposed Rule 1000(b)(9), aims to reduce the risks associated with an SCI entity's decision to activate its BC/DR plans and help to ensure that such plans operate as intended, if activated, by requiring that an SCI entity include participation by certain members and participants in testing of the SCI entity's BC/DR plans. Although some commenters, including several ATSs, argued that ATSs should be excluded from requiring members or participants to test because, according to these commenters, ATSs are less critical to the orderly functioning of the markets than other SCI entities,
                        <SU>1130</SU>
                        <FTREF/>
                         the Commission believes that eliminating any category of SCI entity—including SCI ATSs—from the testing requirement would undermine the goal of maintaining fair and orderly markets in the wake of a wide-scale disruption, and assuring the smooth and effective implementation of an SCI entity's BC/DR plans.
                        <SU>1131</SU>
                        <FTREF/>
                         The Commission continues to believe that a testing participation requirement will help an SCI entity to ensure that its efforts to develop effective BC/DR plans are not undermined by a lack of participation by members or participants that the SCI entity believes are necessary to the successful activation of such plans.
                        <SU>1132</SU>
                        <FTREF/>
                         As stated in the SCI Proposal, the Commission believes that a factor in the shutdown of the equities and options markets in the wake of Superstorm Sandy was the exchanges' belief regarding the inability of some market participants to adequately operate from the backup facilities of all market centers.
                        <SU>1133</SU>
                        <FTREF/>
                         And, although testing protocols were in place and the chance to participate in such testing was available, the member participation rate was low.
                        <SU>1134</SU>
                        <FTREF/>
                         The Commission does not agree with comments that seamless operation of backup facilities should not require coordination of testing, or that the fact that members and participants have their own BC/DR plans and testing means that they should not be required, if designated, to participate in the testing of an SCI entity's BC/DR plans.
                        <SU>1135</SU>
                        <FTREF/>
                         The Commission continues to believe that testing of the effectiveness of back-up arrangements in recovering from a wide-scale disruption is a sound principle, and that, without the participation of significant members or participants of SCI entities, the effectiveness of such testing could be 
                        <PRTPAGE P="72349"/>
                        undermined. Based on its experience with the ARP Inspection Program, the Commission understands that many SCI entities have already made significant investments in their backup facilities.
                        <SU>1136</SU>
                        <FTREF/>
                         The Commission believes that the requirements of Rule 1004 will help to ensure that such facilities will be effective in the event they are needed.
                        <SU>1137</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1129</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.1.b (discussing the requirement that an SCI entity have reasonable policies and procedures that include business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1130</SU>
                             
                            <E T="03">See supra</E>
                             note 1118 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1131</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1 (discussing the Commission's rationale for adopting the definition of SCI entity as proposed). 
                            <E T="03">See supra</E>
                             Section IV.B.1.b (discussing the BC/DR requirements in Rule 1001(a)(2)(v) for SCI entities). 
                            <E T="03">See also</E>
                              
                            <E T="03">infra</E>
                             Sections VI.C.1.c and VI.C.2.b.vii (discussing competitive concerns raised by requiring SCI entities to require members or participants to participate in the SCI entities' BC/DR testing).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1132</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18125.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1133</SU>
                             
                            <E T="03">See id.</E>
                             at 18158. 
                            <E T="03">See also</E>
                              
                            <E T="03">id.</E>
                             at 18091. The Commission notes that its basis for adopting a mandatory testing rule is independent of whether the market closures in the wake of Superstorm Sandy were appropriate to protect the health and safety of exchange personnel.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1134</SU>
                             
                            <E T="03">See id.</E>
                             at 18158 and text accompanying n. 83 at 18091. In addition, based on the discussions of Commission staff with market participants in the months following Superstorm Sandy, the Commission understands that many market participants had previously engaged in connectivity testing with backup facilities, and yet remained uncomfortable about switching over to the use of backup facilities in advance of the storm.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1135</SU>
                             Nor does the Commission agree that Rule 1004 would be duplicative of FINRA Rule 4370, as Rule 1004 relates to participation by members or participants in the testing of an SCI entity's business continuity plans, whereas FINRA Rule 4370 relates to the testing of the member's or participant's own business continuity plan. 
                            <E T="03">See supra</E>
                             note 539 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1136</SU>
                             
                            <E T="03">See infra</E>
                             Section VI.B.2 (stating that nearly all national securities exchanges already have backup facilities that do not rely on the same infrastructure components as those used by their primary facility).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1137</SU>
                             
                            <E T="03">See</E>
                             2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 512, at 56658 (stating: “The effectiveness of back-up arrangements in recovering from a wide-scale disruption should be confirmed through testing.”). 
                            <E T="03">See also</E>
                             Interagency White Paper, 
                            <E T="03">supra</E>
                             note 512, at 17811 (identifying “a high level of confidence, through ongoing use or robust testing, that critical internal and external continuity arrangements are effective and compatible” as one of three important business continuity objectives). 
                            <E T="03">See also supra</E>
                             Section IV.B.1.b (discussing adopted Rule 1001(a)(2)(v)).
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters who questioned the need for mandatory participation by SCI entity members and participants,
                        <SU>1138</SU>
                        <FTREF/>
                         the Commission believes that current voluntary industry-led testing has been useful because it annually brings together a wide variety of market participants, including many SCI entities, and involves a range of asset classes.
                        <SU>1139</SU>
                        <FTREF/>
                         The current industry-led testing program coordinated by SIFMA therefore could provide a foundation for the development of the testing required by Rule 1004. However, because participation rates by members and participants in voluntary testing generally has been low, the Commission believes that a mandatory participation requirement is the best means to achieve effective and coordinated BC/DR testing with assured participation by the more significant SCI entity members and participants.
                        <SU>1140</SU>
                        <FTREF/>
                         In addition, although the Commission generally agrees with the comment that “[i]t is vital that as many firms as possible participate in [market-wide] testing with conditions as realistic as possible,” 
                        <SU>1141</SU>
                        <FTREF/>
                         because of the burden and costs of requiring participation by all SCI entity members and participants, regardless of their market significance, the Commission believes it is appropriate to adopt a more measured approach to mandatory participation in BC/DR testing.
                        <SU>1142</SU>
                        <FTREF/>
                         The Commission is therefore adopting a BC/DR testing designation requirement that applies to all SCI entities, but does not apply to all members and participants of SCI entities, as discussed below.
                        <SU>1143</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1138</SU>
                             
                            <E T="03">See supra</E>
                             notes 1117-1122 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1139</SU>
                             
                            <E T="03">See http://www.sifma.org/services/bcp/industry-testing/</E>
                             (in which SIFMA describes its annual BC/DR test held annually in October, which includes assets classes such as commercial paper, equities, options, futures, fixed-income, settlement, payments, Treasury auctions and market data).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1140</SU>
                             
                            <E T="03">See supra</E>
                             note 1123 (noting Omgeo's comment that voluntary participation levels are low). 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18091, n. 83 and accompanying text (noting that press reports indicated that a large number of NYSE members did not participate in NYSE's contingency plan testing that occurred seven months prior to Superstorm Sandy).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1141</SU>
                             
                            <E T="03">See supra</E>
                             note 1114 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1142</SU>
                             In addition, because the Commission recognizes that the coordination of such testing is complex and time-consuming, it has provided for a compliance date for the coordination requirement of Rule 1004(d) that is 12 months after the compliance date required for other provisions of Regulation SCI. 
                            <E T="03">See</E>
                             Section IV.F.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1143</SU>
                             In response to commenters seeking clarification on the types of systems that would be subject to the mandatory testing requirement (
                            <E T="03">see supra</E>
                             notes 1124-1125 and accompanying text), because the required testing is BC/DR testing, all systems necessary for an SCI entity to successfully activate it BC/DR plan would be included.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. SCI Entity Designation of Members or Participants for Participation in BC/DR Testing—Rules 1004(a)-(c)</HD>
                    <P>
                        Several commenters raised concerns about the proposed requirement that SCI entities exercise discretion to designate members or participants for participation in coordinated BC/DR testing under proposed Rule 1000(b)(9).
                        <SU>1144</SU>
                        <FTREF/>
                         After careful consideration of the views of commenters, the Commission is adopting the requirement that SCI entities designate certain members or participants to participate in testing BC/DR plans with certain modifications from the proposal. As proposed, the rule would have required each SCI entity to designate those members or participants it “deems necessary, for the maintenance of fair and orderly markets in the event of the activation of its business continuity and disaster recovery plans . . .” The Commission has determined instead to require that each SCI entity designate those members or participants “that the SCI entity reasonably determines are, taken as a whole, the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of such plans.” This change is broadly consistent with the suggestion of one commenter to revise the criteria for designation to those firms “critical to the operation of the SCI entity.” 
                        <SU>1145</SU>
                        <FTREF/>
                         However, the Commission believes that the adopted standard is more appropriate in that it focuses on the ability of the SCI entity to maintain fair and orderly markets under its BC/DR plan.
                        <SU>1146</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1144</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33; FIF Letter at 6-7; Omgeo Letter at 26; Fidelity Letter at 6; and Angel Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1145</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1146</SU>
                             As discussed more fully in Section IV.B.6.b.iv 
                            <E T="03">infra,</E>
                             the Commission also believes that the adopted standard could, but would be unlikely to, cause members or participants to elect to withdraw from participation in an SCI entity (particularly a smaller SCI entity) to save on the cost of connectivity fees.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters suggested eliminating SCI entity discretion and setting forth in the rule clear, objective criteria (such as trading volume) for which members or participants would be required to participate in testing.
                        <SU>1147</SU>
                        <FTREF/>
                         One commenter suggested that the Commission require that all members or participants that represent a meaningful percentage of the volume in the marketplace participate in the testing in order to capture the more significant market participants, while recognizing the financial burden such testing may pose for smaller entities.
                        <SU>1148</SU>
                        <FTREF/>
                         This commenter believed that giving discretion to SCI entities in this area might lead to regulatory arbitrage and a race to the bottom regarding how many and which members or participants are designated to participate in testing.
                        <SU>1149</SU>
                        <FTREF/>
                         On the other hand, another commenter commented that the discretion contemplated by the proposal keeps the rule flexible enough to accommodate SCI entities conducting a diverse range of business activities.
                        <SU>1150</SU>
                        <FTREF/>
                         This commenter also suggested that SCI entities should not be required to report to the Commission who they have designated to test, and instead should only be required to keep a record of who they have designated.
                        <SU>1151</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1147</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33; Omgeo Letter at 26; Angel Letter at 10; and FIF Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1148</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1149</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1150</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1151</SU>
                             
                            <E T="03">See id.</E>
                             at 13.
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters who were concerned about the discretionary aspect of the designation requirement,
                        <SU>1152</SU>
                        <FTREF/>
                         the Commission believes the SCI entity is in the best position to determine which of its members or participants collectively represent sufficient liquidity for the SCI entity to maintain fair and orderly markets in a BC/DR scenario following a wide-scale disruption. The Commission believes such determinations require the exercise of reasonable judgment by each SCI entity, and are not well-suited for a “one-size-fits-all” objective measure determined by the Commission. For example, if the Commission were to establish an objective measure (
                        <E T="03">e.g.,</E>
                         based on a specified percentage of trading volume), 
                        <PRTPAGE P="72350"/>
                        it might represent a meaningful percentage for some SCI entities, but not for others. Thus, the rule requires that each SCI entity establish standards for the designation of those members or participants that the SCI entity “reasonably” determines are, taken as a whole, the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of its BC/DR plans. This adopted provision is in lieu of the proposed requirement, which would have required an SCI entity to designate those members or participants it “deems necessary” for the maintenance of fair and orderly markets in the event of the activation of its BC/DR plans. Because the adopted rule requires an SCI entity's determination to be reasonable, it provides some degree of flexibility to SCI entities but also imposes a check on SCI entity discretion, which the Commission believes should help prevent an SCI entity's designations from being overly limited. In response to concerns that a discretionary designation requirement would lead to regulatory arbitrage and a race to the bottom regarding how many and which members or participants are designated to participate in testing, the Commission believes that this is unlikely to occur because each SCI entity will be subject to the same requirement and will be required to make a reasonable determination that the designated members or participants are those that are the minimum necessary for it to maintain fair and orderly markets in the event of activation of its BC/DR plans. Further, the Commission believes that broad participation in BC/DR testing will enhance the utility of the testing, and that allowing non-designated members or participants the opportunity to participate in such testing generally will further this goal. Therefore, the Commission encourages SCI entities to permit non-designated members or participants to participate in the testing of the SCI entity's BC/DR plans if they request to do so.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1152</SU>
                             
                            <E T="03">See supra</E>
                             notes 1144, 1147-1149 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        Consistent with the recommendation of one commenter, however, the Commission has determined not to require that each SCI entity notify the Commission of its designations and its standards for designation on Form SCI as proposed. Instead, an SCI entity's standards, designations, and updates, if applicable, would be part of its records and therefore available to the Commission and its staff upon request.
                        <SU>1153</SU>
                        <FTREF/>
                         Unlike de minimis systems disruptions and de minimis systems intrusions, which may occur with regularity (and for which a quarterly summary report would aid Commission oversight of systems whose proper functioning is central to the maintenance of fair and orderly markets), the establishment of standards for designation, the designations themselves, and updates to such standards or designations are likely to occur less frequently. Thus, the Commission believes it is sufficient for the Commission to review records relating to such designations when the Commission determines that it is necessary to do so to fulfill its oversight role, such as during its examination of an SCI entity.
                        <SU>1154</SU>
                        <FTREF/>
                         More broadly, the Commission believes this revision is generally consistent with modifications that the Commission has made in response to comment that proposed Regulation SCI would have required unnecessary and burdensome notice and reporting submissions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1153</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.C.1 (discussing SCI entity recordkeeping requirements).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1154</SU>
                             
                            <E T="03">See supra</E>
                             Sections IV.A.3 and IV.B.3.c (discussing the rationale for quarterly reporting of de minimis systems disruptions and de minimis systems intrusions).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters questioned whether many SCI entities, particularly non-SROs and ATSs, have the authority to require their members or participants to participate in such testing.
                        <SU>1155</SU>
                        <FTREF/>
                         Another commenter more generally stated that it was unclear how an SCI entity could enforce a requirement that its customers engage in BC/DR testing.
                        <SU>1156</SU>
                        <FTREF/>
                         In response to these comments, the Commission believes that SCI SRO rulemaking authority and non-SRO contractual arrangements would enable SCI entities to implement this requirement.
                        <SU>1157</SU>
                        <FTREF/>
                         Specifically, SROs have the authority, and legal responsibility, under Section 6 of the Exchange Act, to adopt and enforce rules (including rules to comply with Regulation SCI's requirements relating to BC/DR testing) applicable to their members or participants that are designed to, among other things, foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest.
                        <SU>1158</SU>
                        <FTREF/>
                         Further, SCI entities that are not SROs have the ability to include provisions in their contractual agreements with their participants (such as their subscriber or participant agreements) requiring such parties to engage in BC/DR testing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1155</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 26; MSRB Letter at 24; BIDS Letter at 8; LiquidNet Letter at 4; and SIFMA Letter at 17. 
                            <E T="03">See also</E>
                             ITG Letter at 15-16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1156</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 17-18 (suggesting that the Commission instead adopt a “BCP testing requirement more akin to the `best practices' described in the Interagency White Paper”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1157</SU>
                             While some designated members or participants of SCI entities might choose to withdraw from membership or participation in an SCI entity if they assess the cost of participating in BC/DR testing to be too great, the Commission believes that other aspects of their involvement with the SCI entity, including an interest in maintaining a profitable business relationship, will factor significantly into any decision regarding their continued membership or participation in the SCI entity. 
                            <E T="03">See also infra</E>
                             Sections VI.C.1.c and VI.C.2.b.vii (discussing competition between SCI entities and non-SCI entities in relation to the requirements under Rule 1004).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1158</SU>
                             
                            <E T="03">See</E>
                             Section 6 of the Exchange Act, 15 U.S.C. 78f.
                        </P>
                    </FTNT>
                    <P>
                        Other commenters focused on the potential impact of the rule on the members or participants designated to participate in testing. One commenter pointed out that, without clearly defined industry level coordination, some members or participants may be overburdened by being subject to multiple individual tests with various SCI entities.
                        <SU>1159</SU>
                        <FTREF/>
                         Another commenter asked the Commission to clarify what the obligation is for firms that are members or participants at multiple SCI entities.
                        <SU>1160</SU>
                        <FTREF/>
                         Several commenters expressed concern that the Commission underestimated the costs and burdens of the proposed testing.
                        <SU>1161</SU>
                        <FTREF/>
                         According to some of these commenters, under the proposal, certain firms, such as market makers and other firms performing important market functions, could be required to maintain connections to the backup sites of a number of SCI entities, at significant cost.
                        <SU>1162</SU>
                        <FTREF/>
                         A group of commenters requested that the scope be targeted to only cover those instances in which an SCI entity determines to enact its disaster recovery plans.
                        <SU>1163</SU>
                        <FTREF/>
                         One commenter agreed that the designation requirement could be relaxed and still achieve the provision's aim, because the bulk of the liquidity at a market center is provided by a small number of firms.
                        <SU>1164</SU>
                        <FTREF/>
                         Another commenter asked the Commission to give designated firms the 
                        <PRTPAGE P="72351"/>
                        ability to opt-out if they have a good reason.
                        <SU>1165</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1159</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1160</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1161</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 37-39; OCC Letter at 18; Fidelity Letter at 6; Joint SROs Letter at 15-16; ISE Letter at 9; and Group One Letter at 3. 
                            <E T="03">See also infra</E>
                             Section VI (discussing the costs and burdens of the requirement, including the costs for members or participants to participate in BC/DR testing).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1162</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 37-39; OCC Letter at 18; and Fidelity Letter at 6 (expressing concern an SCI entity might cast a wide net with its designation powers to include more firms than necessary).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1163</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 16 (noting the complexity of testing a scenario in which a market participant may have enacted its business continuity plan but can still access an SCI entity through the primary facility).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1164</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1165</SU>
                             
                            <E T="03">See</E>
                             Fidelity Letter at 6.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that adoption of a more focused designation requirement that requires SCI entities to exercise reasonable discretion to identify those members or participants that, taken as a whole, are the “minimum necessary” for the maintenance of fair and orderly markets in the event of the activation of such plans is likely to result in a smaller number of SCI entity members or participants being designated for participation in testing as compared to the SCI Proposal. Because the Commission believes that SCI entities have an incentive to limit the imposition of the cost and burden associated with testing to the minimum necessary to comply with the rule, it also believes that, given the option, most SCI entities would, in the exercise of reasonable discretion, prefer to designate fewer members or participants to participate in testing, than to designate more. On balance, the Commission believes that adopted rule will incentivize SCI entities to designate those members and participants that are in fact the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of their BC/DR plans, and that this should reduce the number of designations to which any particular member or participant would be subject, as compared to the SCI Proposal, and would potentially simplify efforts for SCI entities to coordinate BC/DR testing, as required by adopted Rule 1004(d). Despite the modifications from the proposal, it remains possible, as some commenters noted, that firms that are members of multiple SCI entities will be the subject of multiple designations, and that multiple designations could require certain firms to maintain connections to and participate in testing of the backup sites of multiple SCI entities. The Commission believes this possibility, though real, may be mitigated by the fact that multiple designations are likely to be made to firms that are already connected to one or more SCI entity backup facilities, since they represent significant members or participants of the applicable SCI entities; and that, because some SCI entity backup facilities are located in close proximity to each other, multiple connections to such backup facilities may be less costly than if SCI entity backup facilities were not so located. The Commission recognizes that there will be greater costs to a firm being designated by multiple SCI entities to participate in the testing of their BC/DR plans than to a firm designated by only one SCI entity. However, the Commission believes that these greater costs are warranted for such firms, as they represent significant participants in each of the SCI entities for which they are designated, and their participation in the testing of each such SCI entity's BC/DR plans is necessary to evaluate whether such plans are reliable and effective. The designation of a firm to participate in the BC/DR testing of an SCI entity means that such firm is significant, as the SCI entity has reasonably determined it to be included in the set of its members or participants that is, “taken as a whole, the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of such plans.” Nonetheless, the Commission acknowledges that there may be instances in which an SCI entity has reasonably designated a firm to participate in BC/DR testing, and the firm is unwilling to bear the cost of participation in BC/DR testing with a given SCI entity. In such instances, there may be firms that opt out of such testing by withdrawing as a member or subscriber of one or more SCI entities, but the Commission believes that is unlikely. In particular, the Commission believes that it is unlikely that a firm determined to be significant enough to be designated to participate in testing by an SCI entity would choose to withdraw its membership or participation in an SCI entity solely because of the costs and burdens of Regulation SCI's BC/DR testing provisions. The Commission also believes that such firm is likely to be a larger firm with greater resources and a significant level of participation in such SCI entity, and is likely to already be connected to the backup facility of the SCI SRO that is designating it to test.
                        <SU>1166</SU>
                        <FTREF/>
                         Moreover, the Commission does not agree with the suggestion made by one commenter that the Commission give designated firms the ability to “opt-out” if they have a good reason,
                        <SU>1167</SU>
                        <FTREF/>
                         because the ability to opt-out in this manner would render participation in BC/DR testing voluntary which, as discussed above, is unlikely to result in adequate BC/DR testing.
                        <SU>1168</SU>
                        <FTREF/>
                         The Commission continues to believe, as stated in the SCI Proposal, that “unless there is effective participation by certain of its members or participants in the testing of [BC/DR] plans, the objective of ensuring resilient and available markets in general, and the maintenance of fair and orderly markets in particular, would not be achieved.” 
                        <SU>1169</SU>
                        <FTREF/>
                         Although the Commission recognizes that testing of a BC/DR plan does not guarantee flawless execution of that plan, the Commission believes that a tested plan is likely to be more reliable and effective than an inadequately tested plan.
                        <SU>1170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1166</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.B.6.b.iv.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1167</SU>
                             
                            <E T="03">See</E>
                             Fidelity Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1168</SU>
                             
                            <E T="03">See supra</E>
                             note 1140 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1169</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18091, 18125.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1170</SU>
                             Further, because the Commission believes that increased participation in BC/DR testing is likely to enhance the utility of the testing, the Commission encourages SCI entities to permit members or participants that do not meet the SCI entity's reasonable designation standards to participate in such testing if they request to do so.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Scope, Timing, and Frequency of BC/DR Testing—Rule 1004(b)</HD>
                    <P>
                        The SCI Proposal specified that the type of testing for which designees would be required to participate was “scheduled functional and performance testing of the operation of [BC/DR] plans, in the manner and frequency specified by the SCI entity, at least once every 12 months.” 
                        <SU>1171</SU>
                        <FTREF/>
                         After careful consideration of the views of commenters, the Commission is adopting the scope, frequency, and timing requirements in the rule as proposed. Specifically, adopted Rule 1004(b) requires that an SCI entity's designees participate in “scheduled functional and performance testing of the operation of [BC/DR] plans, in the manner and frequency specified by the SCI entity, provided that such frequency shall not be less than once every 12 months.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>1171</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(9)(i).
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission noted that functional testing is commonly understood to examine whether a system operates in accordance with its specifications, whereas performance testing examines whether a system is able to perform under a particular workload.
                        <SU>1172</SU>
                        <FTREF/>
                         The Commission added that functional and performance testing should include not only testing of connectivity, but also testing of an SCI entity's systems, such as order entry, execution, clearance and settlement, order routing, and the transmission and/or receipt of market data, as applicable, to determine if they can operate as contemplated by its business continuity and disaster recovery plans.
                        <SU>1173</SU>
                        <FTREF/>
                         With regard to the proposed scope of testing, several commenters expressed specific concerns about the requirement for “functional and performance” testing of BC/DR 
                        <PRTPAGE P="72352"/>
                        plans.
                        <SU>1174</SU>
                        <FTREF/>
                         Specifically, one commenter expressed concern about the logistical challenges of conducting functional and performance testing at the same time.
                        <SU>1175</SU>
                        <FTREF/>
                         Two commenters expressed concern that requiring firms to perform industry-wide, end-to-end testing by processing transactions in their disaster recovery systems would introduce risk to the markets because such testing would increase the chance that test transactions could inadvertently be introduced into production systems.
                        <SU>1176</SU>
                        <FTREF/>
                         Another commenter stated that a full functional test across all primary and recovery data centers for any significant number of members or participants would require substantial time to conduct and may require market downtime, as would a full performance test.
                        <SU>1177</SU>
                        <FTREF/>
                         One group of commenters suggested that the scope of the requirement should be revised to only cover “functional and operational testing” of disaster recovery plans, but requested additional guidance with regard to the scope of testing required to establish the effectiveness of disaster recovery plans.
                        <SU>1178</SU>
                        <FTREF/>
                         This group of commenters expressed concern about the “complexity and cost associated with establishing an effective coordinated test script that captures the significant number of possibilities that may occur to each significant market participant or SCI entity” and recommended that the scope of the coordinated functional and operational testing requirements be revised to cover those instances in which an SCI entity determines to enact its disaster recovery plan.
                        <SU>1179</SU>
                        <FTREF/>
                         Two commenters believed the tests should be “scenario-based” to recreate as closely as possible the actual conditions that would trigger widespread use of BC/DR plans.
                        <SU>1180</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1172</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18125, n. 267.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1173</SU>
                             
                            <E T="03">See id.</E>
                             at 18126.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1174</SU>
                             
                            <E T="03">See, e.g.</E>
                            , FINRA Letter at 37; OCC Letter at 18; and DTCC Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1175</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 37 (stating that combining performance testing with functional testing on weekends would be difficult and possibly not feasible because an end-to-end functional test combined with a stress test would require much more time to accommodate processing volumes than would be afforded in an abbreviated non-business day session).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1176</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 17-18 (stating that its systems and systems of many member firms are configured to prevent test activity from being processed by production or disaster recovery systems); and DTCC Letter at 12 (stating similarly that the testing proposed by Rule 1000(b)(9) (as opposed to communication and connectivity testing) would not be supported by most SCI entities' current systems configurations, and encouraging the Commission to consider this in adopting testing requirements).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1177</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 26-27. This commenter urged a more limited scope of testing. Specifically, this commenter urged the Commission to focus on “smoke testing,” which it characterized as a more limited form of testing to validate that system functionality is fully deployed and operational in the new recovered or resumed production environment, and with respect to the goals of performance testing, a more limited set of system operations to assure that the recovery system would perform those operations at roughly comparable speeds as those performed on the main production systems. This commenter further stated that, in both cases, the purpose of these tests would be to validate that the backup or recovery systems have the necessary functionality to perform the service required of the SCI systems, and have sufficient capacity to process the production workloads at roughly comparable levels of performance, rather than to test the actual functional or performance characteristics of the backup or alternate recovery systems in their own right. 
                            <E T="03">See</E>
                             Omgeo Letter at 27.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1178</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 15-16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1179</SU>
                             
                            <E T="03">See id.</E>
                             at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1180</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 7; and UBS Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        Adopted Rule 1004(b) provides that the scope of required testing is “functional and performance testing of the operation of BC/DR plans.” As stated in the SCI Proposal, such functional and performance testing should include not only testing of connectivity, but also testing of an SCI entity's systems, such as order entry, execution, clearance and settlement, order routing, and the transmission and/or receipt of market data, as applicable, to determine if they can operate as contemplated by its business continuity and disaster recovery plans.
                        <SU>1181</SU>
                        <FTREF/>
                         In response to commenters expressing concern about the breadth of the requirement, the Commission notes that the rule requires functional and performance testing of the “operation of [BC/DR] plans.” While the type of testing required by adopted Rule 1004(b) is more rigorous than some types of testing urged by some commenters, the Commission does not believe that the requirement for “functional and performance testing of the operation of such plans” requires additional testing that is as burdensome as that feared by some of those commenters. Importantly, “functional and performance testing of the operation of [BC/DR] plans” entails testing that goes beyond communication and connectivity testing, and beyond validation testing, which are more limited types of testing urged by some commenters. But the requirement to conduct “functional and performance testing of the operation of [BC/DR] plans” does not mean that a full test of the functional and performance characteristics of each backup facility is required to be conducted all at once and in coordination with other SCI entities all at the same time, as some commenters characterized the proposed requirement.
                        <SU>1182</SU>
                        <FTREF/>
                         Specifically, the Commission notes that the testing of BC/DR plans, which is required by Rule 1004, is different from testing of the function and performance of backup facilities generally.
                        <SU>1183</SU>
                        <FTREF/>
                         What Rule 1004 requires is coordinated testing to evaluate annually whether such backup facilities of SCI entities can function and perform in accordance with the operation of BC/DR plans in the event of wide-scale disruption. In addition, the Commission notes that performance testing, which examines whether a system is able to perform under a particular workload, is not synonymous with “stress testing,” in which capacity limits are tested, and therefore should not require as much time to conduct as one commenter suggested.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1181</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18126.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1182</SU>
                             Conducting the required testing is not intended to require market downtime, but permits a range of possibilities, as SCI entities determine to be appropriate, including weekend testing, as well as testing in segments over the course of a year, if SCI entities determine that, to meet the requirements of the rule, a single annual test cannot be properly conducted within a single period of time (
                            <E T="03">e.g.</E>
                            , over the course of a weekend).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1183</SU>
                             Testing of the function and performance of backup facilities generally would occur before such facilities are launched into production (such as pursuant to Rule 1001(a)), and Regulation SCI does not impose a requirement for coordinating such testing with other SCI entities.
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters concerned that the required testing would necessitate system reconfigurations,
                        <SU>1184</SU>
                        <FTREF/>
                         the Commission understands that the requirement to test backup facilities may require technology adjustments to permit testing activity to be processed by BC/DR systems, and believes that such adjustments to permit testing are warranted to achieve the goal, as discussed above, of achieving reliable and effective BC/DR plans at SCI entities. The Commission also believes that such system reconfigurations would be less burdensome than a Commission rule requiring the establishment of a dedicated environment for safe end-to-end testing that accurately simulates the trading environment, which some commenters suggested might be appropriate. One group of commenters noted the “complexity and cost associated with establishing an effective coordinated test script,” and urged that the scope of the coordinated testing be “narrowed to cover those instances in which an SCI entity determines to enact its disaster recovery plan.” The Commission acknowledges that establishment of an effective coordinated test script will involve 
                        <PRTPAGE P="72353"/>
                        some costs and complexity, but believes that this is an important first step in establishing robust and effective testing under the rule. The Commission encourages SCI entities to develop one or more test scripts contemplating a wide-scale disruption and the enactment by SCI entities in the region of the wide-scale disruption of their BC/DR plans.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1184</SU>
                             
                            <E T="03">See supra</E>
                             note 1176 and accompanying text. 
                            <E T="03">See also</E>
                             Tradebook Letter at 2-3 (stating its view that “the only way to test integration from order generation to allocation and then through to final settlement, is in the production environment” and “test tickers that operate in the production environment are the only way to reliably simulate exactly what will happen in the production environment with a live order”).
                        </P>
                    </FTNT>
                    <P>
                        Further, the Commission notes that nothing in Rule 1001(a) nor Rule 1004 requires that an SCI entity's BC/DR plan specify that its backup site must fully replicate the capacity, speed, and other features of the primary site. Similarly, SCI entity members and participants are not required by Regulation SCI to maintain the same level of connectivity with the backup sites of an SCI entity as they do with the primary sites.
                        <SU>1185</SU>
                        <FTREF/>
                         In the event of a wide-scale disruption in the securities markets, the Commission acknowledges that an SCI entity and its members or participants may not be able to provide the same level of liquidity as on a normal trading day. In addition, the Commission recognizes that the concept of “fair and orderly markets” does not require that trading on a day when business continuity and disaster recovery plans are in effect will reflect the same levels of liquidity, depth, volatility, and other characteristics of trading on a normal trading day. Nevertheless, the Commission believes it is critical that SCI entities and their designated members or participants be able to operate with the SCI entities' backup systems in the event of a wide-scale disruption. Therefore, Rule 1004 requires that an SCI entity's BC/DR plan that meets the requirements of Rule 1001(a)(2)(v) be tested for both its functionality and performance as specified by the SCI entity's BC/DR plan.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1185</SU>
                             
                            <E T="03">See infra</E>
                             Section VI.C.2.b.vii (discussing the estimated costs of adopted Rule 1004).
                        </P>
                    </FTNT>
                    <P>
                        In addition, several commenters addressed testing more generally.
                        <SU>1186</SU>
                        <FTREF/>
                         For example, some commenters urged that comprehensive, industry-wide, end-to-end testing could be enhanced if there were uniform test tickers supported by the testing infrastructure at all SCI entities.
                        <SU>1187</SU>
                        <FTREF/>
                         Two commenters urged the establishment of principles for end-to-end, integrated testing.
                        <SU>1188</SU>
                        <FTREF/>
                         Specifically, one of these commenters suggested that SCI entities, the Commission, and relevant third-parties think about how to establish a dedicated environment where end-to-end testing could be done safely, and where it could accurately simulate the trading environment.
                        <SU>1189</SU>
                        <FTREF/>
                         This commenter also suggested that testing plans concentrate on high volume periods, stress testing common order types, and focusing on securities that generally experience low liquidity.
                        <SU>1190</SU>
                        <FTREF/>
                         This commenter believed that industry-wide testing should include derivatives and cross-asset scenarios, and possibly include some involvement by foreign regulators and markets as well.
                        <SU>1191</SU>
                        <FTREF/>
                         While the suggestions of these commenters are not inconsistent with the rule's requirement for functional and performance testing of BC/DR plans, the Commission has determined not to require them because the Commission does not believe, at this time, that these suggestions are necessary in every instance to achieve reliable and effective BC/DR plans at SCI entities. However, to the extent an SCI entity believes them to be appropriate for its systems, these suggestions could be utilized in its BC/DR plans testing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1186</SU>
                             
                            <E T="03">See</E>
                             Tradebook Letter at 1-3; CAST Letter at 9; FIA PTG Letter at 2; and CoreOne Letter at 3-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1187</SU>
                             
                            <E T="03">See</E>
                             Tradebook Letter at 2-3; CAST Letter at 9; and FIA PTG Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1188</SU>
                             
                            <E T="03">See</E>
                             CoreOne Letter at 3; and Tradebook Letter at 1-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1189</SU>
                             
                            <E T="03">See</E>
                             CoreOne Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1190</SU>
                             
                            <E T="03">See id.</E>
                             at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1191</SU>
                             
                            <E T="03">See id.</E>
                             at 7.
                        </P>
                    </FTNT>
                    <P>Importantly, the adopted rule does not prescribe how SCI entities are to develop plans for functional and performance testing of order entry, execution, clearance and settlement, order routing, and the transmission and/or receipt of market data, as applicable, to determine if these functions can operate as contemplated by SCI entity BC/DR plans. Thus, as with the proposed requirement, the adopted rule provides an SCI entity with discretion to determine the precise manner and content of the BC/DR testing required pursuant to Rule 1004, and SCI entities have discretion to determine, for example, the duration of the testing, the sample size of transactions tested, the scenarios tested, and the scope of the test. Therefore, while comments urging the creation of uniform test tickers, establishment of principles for end-to-end testing, mandatory types of test scripts, and cross-asset and cross-jurisdictional coordination are matters that SCI entities may wish to consider in implementing the testing required by the rule, the Commission does not believe it is appropriate to mandate such details in Regulation SCI. To do so would be more prescriptive than the Commission believes is appropriate, as this requirement is designed to provide SCI entities flexibility and discretion in determining how to meet it. The Commission believes that the adopted testing requirement will help to improve securities market infrastructure resilience by helping to ensure not only that an SCI entity can operate following an event that triggers its BC/DR plans, but also that it can do so with a greater level of confidence that its core members or participants are also ready based on experience during testing. The Commission is adopting Rule 1004(b) substantively as proposed because it gives SCI entities discretion to develop a test that meets the requirements of the rule.</P>
                    <P>
                        One commenter recommended requiring that each entity be run entirely under its backup plan at least one day a year for a full trading day, and that the entire market run off of the backup sites at least once a year.
                        <SU>1192</SU>
                        <FTREF/>
                         While adopted Rule 1004 would not preclude this approach, the Commission notes that other commenters disagreed with the wisdom of it.
                        <SU>1193</SU>
                        <FTREF/>
                         Specifically, one group of commenters stated that the risks of testing in a “live production environment on a periodic basis” outweigh the benefits.
                        <SU>1194</SU>
                        <FTREF/>
                         Another commenter stated that requiring SCI entities to operate using their backup facilities would increase the risk of erroneous quotes and orders entering the marketplace.
                        <SU>1195</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1192</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1193</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 15; and Group One Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1194</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1195</SU>
                             
                            <E T="03">See</E>
                             Group One Letter at 2.
                        </P>
                    </FTNT>
                    <P>After careful consideration of these comments, the Commission has determined not to prescribe the time of day or week during which testing shall occur. In addition, the adopted rule does not require an SCI entity to test its BC/DR plan in live production, but also does not prohibit an SCI entity from testing its BC/DR plans in live production, either, if an SCI entity determines such a method of testing to be appropriate. The Commission continues to believe that SCI entities are in the best position to structure the details of the test in a way that would maximize its utility.</P>
                    <P>
                        With respect to testing frequency, one commenter agreed with the proposal that an SCI entity's BC/DR plans, including its backup systems, be tested “at least once every 12 months.” 
                        <SU>1196</SU>
                        <FTREF/>
                         One commenter stated that the rule should explicitly set forth the required frequency of testing.
                        <SU>1197</SU>
                        <FTREF/>
                         One commenter believed that two coordinated industry tests per year would be more appropriate.
                        <SU>1198</SU>
                        <FTREF/>
                         One commenter 
                        <PRTPAGE P="72354"/>
                        believed that testing once per year is arbitrary, and suggested that a risk-based approach might justify testing certain systems with more or less frequency.
                        <SU>1199</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1196</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 13
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1197</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1198</SU>
                             
                            <E T="03">See</E>
                             FIF Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1199</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 24.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is adopting as proposed the requirement that testing occur not less than once every 12 months. Although commenters offered differing views on the appropriate frequency for the required testing,
                        <SU>1200</SU>
                        <FTREF/>
                         the Commission continues to believe that a testing frequency of once every 12 months is an appropriate minimum frequency that encourages regular and focused attention on the establishment of meaningful and effective testing. In the context of coordinated BC/DR testing, the Commission believes the key is for testing to occur regularly enough to offer practical utility in the event of a wide-scale disruption without imposing undue cost, and that a minimum frequency of one year achieves this balance. This requirement does not prevent SCI entities from testing more frequently, but rather is intended to give SCI entities the flexibility to test their BC/DR plans, including their backup systems, at more frequent intervals if they find it appropriate to do so.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1200</SU>
                             
                            <E T="03">See supra</E>
                             notes 1196-1199.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Industry- or Sector-Wide Coordination—Rule 1004(d)</HD>
                    <P>Proposed Rule 1000(b)(9)(a)(ii) specified that an SCI entity would be required to coordinate the testing of BC/DR plans on an industry- or sector-wide basis with other SCI entities. The Commission received significant comment on this aspect of the proposal.</P>
                    <P>
                        Two commenters supported the coordinated testing requirement.
                        <SU>1201</SU>
                        <FTREF/>
                         Specifically, one of these commenters stated that a coordination requirement targets an area where technology risks have left the markets more vulnerable, namely, the complex ways that firms interact.
                        <SU>1202</SU>
                        <FTREF/>
                         This commenter favored market-wide testing as a way to better manage that risk.
                        <SU>1203</SU>
                        <FTREF/>
                         This commenter also stated that coordination is vital because the more SCI entities and member firms that participate in testing, the more realistic that testing will be.
                        <SU>1204</SU>
                        <FTREF/>
                         Another commenter noted that one of the most important steps in validating and maintaining systems integrity is an effective BC/DR model and urged the Commission to promptly advance a program to introduce a new and more comprehensive BC/DR testing paradigm.
                        <SU>1205</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1201</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 9; and UBS Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1202</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1203</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1204</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1205</SU>
                             
                            <E T="03">See</E>
                             UBS Letter at 4-5. This commenter also stated that improved BC/DR testing should not be delayed until Regulation SCI is adopted. 
                            <E T="03">See</E>
                             UBS Letter at 5.
                        </P>
                    </FTNT>
                    <P>
                        In contrast, some commenters opposed the proposed comprehensive, coordinated testing structure.
                        <SU>1206</SU>
                        <FTREF/>
                         Some commenters stated that coordinating testing presents significant technological and logistical challenges that need to be weighed carefully.
                        <SU>1207</SU>
                        <FTREF/>
                         One commenter stated that coordinated testing is a good aspirational goal, but expressed concern that too much is outside of the control of an individual SCI entity, and therefore the rule should, at most, require SCI entities to attempt to coordinate such testing.
                        <SU>1208</SU>
                        <FTREF/>
                         Another commenter stated that the fixed-income market is so fragmented that coordinated testing is difficult to conduct and much less imperative.
                        <SU>1209</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1206</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 12-13; FINRA Letter at 37-39; OCC Letter at 17-18; and ISE Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1207</SU>
                             
                            <E T="03">See</E>
                             LiquidPoint Letter at 4; and SIFMA Letter at 17-18. 
                            <E T="03">See also supra</E>
                             notes 1175-1177 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1208</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1209</SU>
                             
                            <E T="03">See</E>
                             TMC Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters offered suggestions on how to improve the proposed coordination requirement. One commenter urged that coordination only be required among providers of singular services in the market (
                        <E T="03">i.e.</E>
                        , exchanges that list securities, exclusive processors under NMS plans, and clearing and settlement agencies).
                        <SU>1210</SU>
                        <FTREF/>
                         Some commenters believed that coordination would work best if it was organized by an entity with regulatory authority over SCI entities, or by an organization designated by the Commission to fulfill that role.
                        <SU>1211</SU>
                        <FTREF/>
                         One such commenter supported coordinating testing through a Commission-approved plan, provided SCI entities have the right to maintain the confidentiality of certain critical information.
                        <SU>1212</SU>
                        <FTREF/>
                         Another commenter recommended that the Commission work with the CFTC to adopt a coordinated approach to dealing with technology issues across financial markets, including through participation by derivatives exchanges in testing alongside their equity markets counterparts.
                        <SU>1213</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1210</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1211</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 13; OCC Letter at 18; and NYSE Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1212</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1213</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 12.
                        </P>
                    </FTNT>
                    <P>After careful consideration of the comments, the Commission has determined to adopt the coordination requirement as proposed. Specifically, Rule 1004(d) requires that an SCI entity “coordinate the testing of [BC/DR] plans on an industry- or sector-wide basis with other SCI entities.” The Commission recognizes that coordinating industry- or sector-wide testing among SCI entities and their designated members or participants may present logistical challenges. Because of these challenges, the Commission does not believe that a more prescriptive approach is warranted. Instead, the coordination requirement provides discretion to SCI entities to determine how to meet it.</P>
                    <P>
                        The Commission does not agree with commenters suggesting that the Commission should assume leadership on the organization of coordinated testing, designate an organization to fulfill that role, or require a “Commission-approved plan” for testing, because it believes at this time that SCI entities can achieve coordination more quickly and efficiently without the imposition of a formal procedural framework that these suggestions would entail.
                        <SU>1214</SU>
                        <FTREF/>
                         In response to comment suggesting that coordination should be aspirational rather than required, the Commission believes that, because trading in the U.S. securities markets today is dispersed among a wide variety of exchanges, ATSs, and other trading venues, and is often conducted through sophisticated trading strategies that access many trading platforms simultaneously, requiring SCI entities to coordinate testing would result in testing under more realistic market conditions.
                        <SU>1215</SU>
                        <FTREF/>
                         The Commission also continues to believe that it would be more cost-effective for SCI entity members and participants to participate in testing of SCI entity BC/DR plans on an industry- or sector-wide basis than to test with each SCI entity on an individual basis because such coordination would likely reduce duplicative testing efforts.
                        <SU>1216</SU>
                        <FTREF/>
                         In 
                        <PRTPAGE P="72355"/>
                        addition, if SCI entities that are “providers of singular services” in the markets (
                        <E T="03">i.e.,</E>
                         which the Commission believes would be synonymous with SCI entities that are providers of “critical SCI systems”) lead coordination efforts on behalf of all SCI entities, such an approach would not be impermissible under Rule 1004(d), provided all SCI entities agreed to such an approach.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1214</SU>
                             With respect to the suggestion that there be a Commission approved plan, the Commission notes that Rule 608 of Regulation NMS is designed to facilitate participation in NMS plans by self-regulatory organizations, which does not include SCI entities that are not SCI SROs, including SCI ATSs. The Commission notes that at least one commenter suggested that the Commission work with the CFTC to adopt a coordinated approach to testing. But, as discussed above, the Commission believes that Regulation SCI is an important step to reduce the risks associated with a decision to activate BC/DR plans. And, although the Commission may in the future consider additional initiatives to promote further coordination with the CFTC, in the Commission's view, this initial step of adopting Regulation SCI should not be delayed.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1215</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18126.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1216</SU>
                             In response to comment that coordinated BC/DR testing is not needed in the current fixed-income market, the Commission notes that it has determined to exclude ATSs trading only municipal securities or corporate debt securities from the 
                            <PRTPAGE/>
                            scope of Regulation SCI. 
                            <E T="03">See supra</E>
                             notes 189-192 and accompanying text (discussing the exclusion of ATSs trading only fixed-income securities from the definition of SCI ATS).
                        </P>
                    </FTNT>
                    <P>
                        In response to commenters who more generally expressed concern about the rule subjecting SCI entity members and participants to multiple duplicative and costly testing requirements,
                        <SU>1217</SU>
                        <FTREF/>
                         the Commission notes that the flexibility provided in the adopted coordination requirement, in tandem with the more focused adopted mandatory designation requirement should mitigate these concerns. As discussed above, adoption of a more focused designation requirement that requires SCI entities to exercise reasonable discretion is likely to reduce the extent to which SCI entity member or participant designations overlap and possibly result in a smaller number of SCI entity members or participants being designated for participation in testing than as contemplated by the SCI Proposal, and a fewer number of members or participants designated to participate in testing should simplify efforts to coordinate testing. However, as some commenters noted, it remains possible that, despite coordination, some firms that are members of multiple SCI entities may be designated to participate in testing with multiple SCI entities at greater cost than if they had been designated by only one SCI entity, and may be required to test more than once annually, as this may be necessary for each SCI entity to meet its obligations under the rule. Though the Commission recognizes that the possibility of being designated by multiple SCI entities to participate in the testing of their BC/DR plans may be costly, the Commission ultimately believes that such a cost is appropriate to help ensure that the BC/DR plan of each SCI entity is useful and effective. If, for example, a firm is designated for mandatory testing by multiple SCI entities, it would be so designated because each such SCI entity determines that such firm is necessary to the successful activation of its BC/DR plan. The Commission recognizes that it is conceivable that a firm that is required to participate in testing with multiple SCI entities assesses the costs and burdens of participating in every such test to be too great, and makes its own business decision to withdraw its membership or participation in one or more such SCI entities so as to avoid the costs and burdens of such testing, but believes such scenario to be unlikely. Specifically, the Commission believes that it is unlikely that a firm determined to be significant enough to be designated to participate in testing by an SCI entity (even a smaller SCI entity) would choose to withdraw its membership or participation in an SCI entity solely because of the costs and burdens of Regulation SCI's BC/DR testing provisions. The Commission also believes that such firm is likely to be a larger firm with greater resources and a significant level of participation in such SCI entity, and is likely to already be connected to the backup facility of the SCI SRO that is designating it to test. The Commission continues to believe that SCI entities are best suited to find the most efficient and effective manner in which to test its BC/DR plans.
                        <SU>1218</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1217</SU>
                             
                            <E T="03">See supra</E>
                             notes 1159-1160 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1218</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18126.
                        </P>
                    </FTNT>
                    <P>
                        Furthermore, the Commission is also adopting a longer compliance period with regard to the industry- or sector-wide coordinated testing requirement in adopted Rule 1004(d).
                        <SU>1219</SU>
                        <FTREF/>
                         Specifically, SCI entities will have 21 months from the Effective Date to coordinate the testing of an SCI entity's business continuity and disaster recovery plans on an industry- or sector-wide basis with other SCI entities pursuant to adopted Rule 1004(d). In sum, the Commission believes that Rule 1004, as adopted, will enhance the resilience of the infrastructure of the U.S. securities markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1219</SU>
                             
                            <E T="03">See infra</E>
                             Section IV.F (discussing the delayed implementation time for adopted Rule 1004(d)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Recordkeeping, Electronic Filing on Form SCI, and Access—Rules 1005-1007</HD>
                    <P>Adopted Rules 1005 through 1007 specify several additional requirements of Regulation SCI relating to recordkeeping and electronic filing and submission. As discussed below, the Commission has determined not to adopt the proposed provision regarding Commission access to the systems of an SCI entity because the Commission can adequately assess an SCI entity's compliance with Regulation SCI through existing recordkeeping requirements and examination authority, as well as through the new recordkeeping requirement in Rule 1005 of Regulation SCI.</P>
                    <HD SOURCE="HD3">1. Recordkeeping—Rules 1005-1007</HD>
                    <HD SOURCE="HD3">a. Recordkeeping Related to Compliance With Regulation SCI—Rule 1005</HD>
                    <P>
                        Proposed Rule 1000(c) required SCI SROs to make, keep, and preserve all documents relating to their compliance with Regulation SCI, as prescribed in Rule 17a-1 under the Exchange Act. Proposed Rule 1000(c) required SCI entities other than SCI SROs to: Make, keep, and preserve at least one copy of all documents relating to their compliance with Regulation SCI; keep these documents for not less than five years, the first two years in a place that is readily accessible to the Commission or its representatives for inspection and examination; and promptly furnish to Commission representatives 
                        <SU>1220</SU>
                        <FTREF/>
                         copies of any of these documents upon request. Further, proposed Rule 1000(c) provided that, upon or immediately prior to ceasing to do business or ceasing to be registered under the Exchange Act, an SCI entity must ensure that the required records are accessible to the Commission and its representatives in a manner required by Rule 1000(c) for the remainder of the period required by Rule 1000(c).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1220</SU>
                             As discussed above, the Commission has renamed the ARP Inspection Program the Technology Controls Program. 
                            <E T="03">See supra</E>
                             note 6.
                        </P>
                    </FTNT>
                    <P>
                        The Commission received one comment letter supporting proposed Rule 1000(c).
                        <SU>1221</SU>
                        <FTREF/>
                         The Commission is adopting Rule 1000(c) as proposed, but re-designated as Rule 1005.
                        <SU>1222</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1221</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 25. As discussed above, some commenters suggested recordkeeping in lieu of certain Commission reporting requirements. 
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             note 881 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1222</SU>
                             The Commission notes that adopted Rule 1005 replaces the term “SCI security systems” with “indirect SCI systems” as described in more detail in Section IV.A.2.d. Furthermore, internal cross references to Rules 1000(c)(2)(i) and (c)(2)(ii) in Rule 1000(c)(2)(iii) were updated to paragraphs (b)(1) and (b)(2) of Rule 1005 in accordance with the renumbering of the rule.
                        </P>
                    </FTNT>
                    <P>
                        As noted in the SCI Proposal, SCI entities are already subject to recordkeeping requirements,
                        <SU>1223</SU>
                        <FTREF/>
                         but records relating to Regulation SCI may not be specifically addressed in certain 
                        <PRTPAGE P="72356"/>
                        current recordkeeping rules.
                        <SU>1224</SU>
                        <FTREF/>
                         As adopted, Rule 1005 specifically addresses recordkeeping requirements for SCI entities with respect to records relating to Regulation SCI compliance.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1223</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 240.17a-1, applicable to SCI SROs; 17 CFR 240.17a-3 and 17a-4, applicable to broker-dealers; and 17 CFR 242.301-303, applicable to ATSs.
                        </P>
                        <P> It has been the experience of the Commission that SCI entities presently subject to the ARP Inspection Program (nearly all of whom are SCI SROs that are also subject to the recordkeeping requirements of Rule 17a-1(a)) do generally keep and preserve the types of records that would be subject to the requirements of Rule 1005. Nevertheless, the Commission continues to believe that Regulation SCI's codification of these preservation practices will support an accurate, timely, and efficient inspection and examination process and help ensure that all types of SCI entities keep and preserve such records.</P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1224</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18128.
                        </P>
                    </FTNT>
                    <P>
                        With respect to SCI SROs, Rule 17a-1(a) under the Exchange Act requires every national securities exchange, national securities association, registered clearing agency, and the MSRB to keep and preserve at least one copy of all documents, including all correspondence, memoranda, papers, books, notices, accounts, and other such records as shall be made and received by it in the course of its business as such and in the conduct of its self-regulatory activity.
                        <SU>1225</SU>
                        <FTREF/>
                         In addition, Rule 17a-1(b) requires these entities to keep all such documents for a period of not less than five years, the first two years in an easily accessible place, subject to the destruction and disposition provisions of Rule 17a-6.
                        <SU>1226</SU>
                        <FTREF/>
                         Rule 17a-1(c) requires these entities, upon request of any representative of the Commission, to promptly furnish to the possession of Commission representatives copies of any documents required to be kept and preserved by it pursuant to Rules 17a-1(a) and (b).
                        <SU>1227</SU>
                        <FTREF/>
                         Therefore, as noted in the SCI Proposal, the breadth of Rule 17a-1 under the Exchange Act is such that it would require SCI SROs to make, keep, and preserve records relating to their compliance with Regulation SCI.
                        <SU>1228</SU>
                        <FTREF/>
                         The Commission continues to believe that it is appropriate to cross-reference Rule 17a-1 in Rule 1005 to be clear that all SCI entities are subject to the same recordkeeping requirements regarding compliance with Regulation SCI. The Commission also continues to believe that it is appropriate to adopt recordkeeping requirements for SCI entities other than SCI SROs that are consistent with the recordkeeping requirements applicable to SROs under Rule 17a-1 under the Exchange Act. The Commission believes it is important to require such records be kept at both SCI SROs and SCI entities other than SCI SROs because such records are essential to understanding whether an SCI entity is meeting its obligations under Regulation SCI, to assess whether an SCI entity has appropriate policies and procedures with respect to its technology systems, to help identify the causes and consequences of an SCI event, and to understand the types of material systems changes occurring at an SCI entity.
                        <SU>1229</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1225</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.17a-1(a). Such records would, for example, include copies of incident reports and the results of systems testing.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1226</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.17a-1(b). Rule 17a-6(a) under the Exchange Act states: “Any document kept by or on file with a national securities exchange, national securities association, registered clearing agency or the Municipal Securities Rulemaking Board pursuant to the Act or any rule or regulation thereunder may be destroyed or otherwise disposed of by such exchange, association, clearing agency or the Municipal Securities Rulemaking Board at the end of five years or at such earlier date as is specified in a plan for the destruction or disposition of any such documents if such plan has been filed with the Commission by such exchange, association, clearing agency or the Municipal Securities Rulemaking Board and has been declared effective by the Commission.” 17 CFR 240.17a-6(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1227</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.17a-1(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1228</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18128.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1229</SU>
                             To achieve the goals for which the recordkeeping requirements are designed, and to comply with the recordkeeping requirements of Rule 17a-1 and Rule 1005 of Regulation SCI, SCI entities must ensure that the records that they make, keep, and maintain are complete and accurate.
                        </P>
                    </FTNT>
                    <P>
                        Further, as noted above, the definitions of SCI system and indirect SCI system include systems operated “on behalf of” an SCI entity by third parties. An SCI entity retains legal responsibility for systems operated on its behalf and, as such, is responsible for producing to Commission representatives records required to be made, kept, and preserved under Regulation SCI, even if those records are maintained by third parties, and the SCI entity is responsible for ensuring that such third parties produce those requested documents, upon examination or other request. Accordingly, the Commission believes that an SCI entity should have processes and requirements in place, such as contractual provisions with a third party, to ensure that it is able to satisfy the requirements of Regulation SCI for systems operated on its behalf by a third party, including the recordkeeping requirements in Rule 1005.
                        <SU>1230</SU>
                        <FTREF/>
                         The Commission believes that if an SCI entity is unable to ensure compliance with Regulation SCI with regard to third party systems or recordkeeping, it should reassess its decision to outsource its systems or recordkeeping.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1230</SU>
                             
                            <E T="03">See also</E>
                             Rule 1007, which states that, if records required to be filed or kept by an SCI entity under Regulation SCI are prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity is required to ensure that the records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service, signed by a duly authorized person at such service bureau or other recordkeeping service.
                        </P>
                    </FTNT>
                    <P>The Commission believes that Rule 1005 will facilitate its inspections and examinations of SCI entities and assist it in evaluating an SCI entity's compliance with Regulation SCI. In particular, Rule 1005 should facilitate Commission examination of SCI entities by helping to reduce delays in obtaining relevant records during an examination. Therefore, as noted in the SCI Proposal, the Commission's ability to examine for, and enforce compliance with, Regulation SCI could be hampered if an SCI entity were not required to adequately provide accessibility to its records for the full proposed retention period.</P>
                    <P>Further, while many SCI events may occur, be discovered, and be resolved in a short time frame, there may be other SCI events that may not be discovered until months or years after their occurrences, or may take significant periods of time to fully resolve. In such cases, having an SCI entity's records available even after it has ceased to do business or be registered under the Exchange Act would be beneficial. Because SCI events have the potential to negatively impact trade execution, price discovery, liquidity, and investor participation, the Commission believes that its ability to oversee the securities markets could be undermined if it is unable to review records to determine the causes and consequences of one or more SCI events experienced by an SCI entity that deregisters or ceases to do business. This information should provide an additional tool to help the Commission reconstruct important market events and better understand how such events impacted trade execution, price discovery, liquidity, and investor participation.</P>
                    <HD SOURCE="HD3">b. Service Bureau—Rule 1007</HD>
                    <P>
                        Proposed Rule 1000(e) required that, if the records required to be filed or kept by an SCI entity under Regulation SCI were prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity ensure that the records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service and signed by a duly authorized person at such service bureau or other recordkeeping service. Further, the written undertaking was required to include an agreement by the service bureau designed to permit the Commission and its representatives to examine such records at any time or from time to time during business hours, and to promptly furnish to the Commission and its representatives true, correct, and current electronic files in a form acceptable to the Commission or its representatives or hard copies of any, all, or any part of such records, 
                        <PRTPAGE P="72357"/>
                        upon request, periodically, or continuously and, in any case, within the same time periods as would apply to the SCI entity for such records. Proposed Rule 1000(e) also provided that the preparation or maintenance of records by a service bureau or other recordkeeping service would not relieve an SCI entity from its obligation to prepare, maintain, and provide the Commission and its representatives with access to such records.
                    </P>
                    <P>
                        The Commission did not receive any comments on proposed Rule 1000(e) and is adopting Rule 1000(e) as proposed, but re-designated as Rule 1007. As noted in the SCI Proposal, Rule 1007 is substantively the same as the requirement applicable to broker-dealers under Rule 17a-4(i) of the Exchange Act.
                        <SU>1231</SU>
                        <FTREF/>
                         The Commission continues to believe that this requirement will help ensure the Commission's ability to obtain required records that are held by a third party who may not otherwise have an obligation to make such records available to the Commission. In addition, the Commission continues to believe that the requirement that SCI entities obtain from such third parties a written undertaking will also help ensure that such service bureau or other recordkeeping service is aware of its obligation with respect to records relating to Regulation SCI. The Commission believes that this requirement will help ensure that the Commission has prompt and efficient access to all required records, including those housed at a service bureau or any other recordkeeping service.
                        <SU>1232</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1231</SU>
                             17 CFR 240.17a-4(i). 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18129.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1232</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.17a-4(i) (records preserved or maintained by a service bureau).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Electronic Filing and Submission of Reports, Notifications, and Other Communications—Rule 1006</HD>
                    <P>Proposed Rule 1000(d) required that, except with respect to notifications to the Commission made pursuant to proposed Rule 1000(b)(4)(i) (Commission notification of certain SCI events) or oral notifications to the Commission made pursuant to proposed Rule 1000(b)(6)(ii) (Commission notification of certain material systems changes), any notification, review, description, analysis, or report to the Commission required under Regulation SCI be submitted electronically on Form SCI and include an electronic signature. Proposed Rule 1000(d) also required that the signatory to an electronically submitted Form SCI manually sign a signature page or document, in the manner prescribed by Form SCI, authenticating, acknowledging, or otherwise adopting his or her signature that appears in typed form within the electronic filing. This document would be required to be executed before or at the time Form SCI is electronically submitted and would be required to be retained by the SCI entity in accordance with the recordkeeping requirements of Regulation SCI. The Commission is adopting Rule 1000(d) substantially as proposed, as discussed below, but re-designated as Rule 1006.</P>
                    <P>
                        One commenter supported the electronic submission of Form SCI.
                        <SU>1233</SU>
                        <FTREF/>
                         One commenter suggested that the Commission should make clear that Regulation SCI filings do not need to be made in a tagged data format such as XBRL, which could be costly.
                        <SU>1234</SU>
                        <FTREF/>
                         Another commenter stated that the electronic signature requirement was appropriate only if the final rule included a safe harbor for good faith reporting of SCI events.
                        <SU>1235</SU>
                        <FTREF/>
                         According to this commenter, the requirement that there be an electronic signature and a manual signature could put SCI entity personnel at risk if it is later determined that there were factual errors, omissions, or other flaws in the initial filing.
                        <SU>1236</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1233</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 25.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1234</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 4. 
                            <E T="03">See also</E>
                             FINRA Letter at 28.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1235</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1236</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the comments, the Commission is adopting Rule 1000(d) substantially as proposed, and with updated internal cross references to reflect revisions to other aspects of Regulation SCI, as adopted. Specifically, Rule 1006 provides that notifications made pursuant to Rule 1002(b)(1) (immediate Commission notification of SCI events) and updates made pursuant to Rule 1002(b)(3) (updates regarding SCI events) are not required to be filed on Form SCI.
                        <SU>1237</SU>
                        <FTREF/>
                         As noted in the SCI Proposal, Rule 1006 is intended to provide a uniform manner in which the Commission would receive—and SCI entities would provide—written notifications, reviews, descriptions, analyses, or reports made pursuant to Regulation SCI.
                        <SU>1238</SU>
                        <FTREF/>
                         Rule 1006 should therefore allow SCI entities to efficiently draft and submit the required reports, and for the Commission to efficiently review, analyze, and respond to the information provided.
                        <SU>1239</SU>
                        <FTREF/>
                         In addition, the Commission believes that filing Form SCI in an electronic format would be less burdensome and more efficient for SCI entities and the Commission than mailing and filing paper forms.
                        <SU>1240</SU>
                        <FTREF/>
                         Further, after considering comments regarding the burden of submitting Form SCI in a tagged data format such as XBRL, the Commission is not requiring the use of XBRL formatting for Form SCI. Rather, certain fields in Sections I-III of Form SCI will require information to be provided by SCI entities in a format that will allow the Commission to gather information in a structured manner (
                        <E T="03">e.g.,</E>
                         the submission type and SCI event type in Section I), whereas the exhibits to Form SCI will allow SCI entities to provide narrative responses, such as through a text format. Further, the Commission also is specifying that documents filed through the EFFS system must be in a text-searchable format without the use of optical character recognition. If, however, a portion of a Form SCI submission (
                        <E T="03">e.g.,</E>
                         an image or diagram) cannot be made available in a text-searchable format, such portion may be submitted in a non-text-searchable format.
                        <SU>1241</SU>
                        <FTREF/>
                         The Commission believes that requiring documents to be submitted in a text-searchable format (with the limited exception noted) is necessary to allow Commission staff to efficiently review and analyze information provided by SCI entities. In particular, a text-searchable format allows Commission staff to better gather, analyze and use data submitted as exhibits, whereas a non-text-searchable format submission would require significantly more steps and labor to review and analyze data. The Commission notes that word processing and spreadsheet applications that are widely used by many businesses, including SCI entities, generate documents in this format.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1237</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events). Adopted Rule 1006 refers to an electronically “filed” Form SCI, rather than an electronically “submitted” Form SCI as proposed in Rule 1000(d)(1). This change clarifies that notices and reports required to be submitted under Regulation SCI are filings under the Exchange Act and Regulation SCI. 
                            <E T="03">See</E>
                             proposed and adopted 17 CFR 249.1900 (stating that Form SCI shall be used to “file” notices and reports as required by Regulation SCI). 
                            <E T="03">See also</E>
                             amended Rule 24b-2 (referring to material “filed” in electronic format on Form SCI).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1238</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18129-30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1239</SU>
                             
                            <E T="03">See id.</E>
                             at 18130.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1240</SU>
                             The Commission will implement Form SCI through the electronic form filing system (“EFFS”) currently used by SCI SROs to file Form 19b-4 filings. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 50486 (October 4, 2004), 69 FR 60287 (October 8, 2004) (adopting the EFFS for use in filing Form 19b-4). 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18130.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1241</SU>
                             
                            <E T="03">See</E>
                             General Instructions to Form SCI, Item A.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter stated that the electronic signature requirement was appropriate only if the 
                        <PRTPAGE P="72358"/>
                        final rule included a safe harbor for good faith reporting of SCI events. The Commission is adopting the electronic signature requirement as proposed. The Commission notes that, as discussed above in Section IV.B.3.c, immediate Commission notification following an SCI event and updates regarding the SCI event may be given orally; the 24-hour Commission notification is required to be made on a good faith, best efforts basis; and the final Commission notification is not required until the resolution of the SCI event and the completion of the SCI entity's investigation of the SCI event. The Commission also notes that the purpose of the electronic signature requirement on Form SCI is to ensure that the person submitting the form to the Commission has been properly authorized by the SCI entity to submit the form on its behalf.
                        <SU>1242</SU>
                        <FTREF/>
                         Therefore, the electronic signature requirement would not put SCI entity personnel at risk if the SCI entity later determines that there were factual errors, omissions, or other flaws in the initial filing. As such, the Commission does not agree with the comment that the electronic signature requirement was appropriate only if the final rule included a safe harbor for good faith reporting of SCI events.
                        <SU>1243</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1242</SU>
                             Additionally, similar to use of the EFFS in the context of electronic filing of Form 19b-4, by using a digital ID for each duly authorized signatory providing an electronic signature, both the Commission and an SCI entity may be assured of the authenticity and integrity of the electronic filing of Form SCI. 
                            <E T="03">See infra</E>
                             Section V.D.2.e (noting the necessity of completing a form to gain access to EFFS).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1243</SU>
                             The same rationale also applies to the requirement for manual signature in Rule 1006.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Amendment To Facilitate Electronic Filing Requirements</HD>
                    <P>
                        In addition, to permit implementation of Rule 1006,
                        <SU>1244</SU>
                        <FTREF/>
                         the Commission is adopting an amendment to Rule 24b-2 under the Exchange Act.
                        <SU>1245</SU>
                        <FTREF/>
                         Rule 24b-2 currently provides confidential treatment requests and the confidential portion of an electronic filing may be submitted in paper format only.
                        <SU>1246</SU>
                        <FTREF/>
                         The Commission is amending Rule 24b-2 by amending the rule's preliminary note, and paragraph (b) of the rule to clarify that under Rule 24b-2, confidential treatment requests and the confidential portion of an electronic filing may be submitted in paper format only, unless Rule 24b-2 provides otherwise. The Commission also is adding a new paragraph (g) to Rule 24b-2 to provide an electronic means by which an SCI entity may request confidential treatment of its filings on Form SCI. New paragraph (g) will provide that an SCI entity's electronic filings on Form SCI pursuant to Regulation SCI must include any information with respect to which confidential treatment is requested (“confidential portion”), and provide that, in lieu of the procedures described in Rule 24b-2b, an SCI entity may request confidential treatment of all information submitted on Form SCI by completing Section IV of Form SCI. The Commission's amendment provides an exception from Rule 24b-2's paper-only request for confidential treatment for all Form SCI filings, and specifically permits an SCI entity to electronically request confidential treatment of all information filed on Form SCI in accordance with Regulation SCI. The Commission believes that allowing for electronic submission of confidential treatment requests will reduce the burden on SCI entities by not requiring a separate paper submission, and provided the confidential treatment request is properly made, will expedite Commission review of the requests for confidential treatment, as all information submitted on Form SCI will be deemed to be the subject of the request for confidential treatment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1244</SU>
                             
                            <E T="03">See</E>
                             Rule 1006, 17 CFR 242.1006; 
                            <E T="03">see also</E>
                             General Instruction E to Form SCI (requiring Form SCI and exhibits to be filed electronically under Rule 1006).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1245</SU>
                             17 CFR 240.24b-2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1246</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.24b-2.
                        </P>
                    </FTNT>
                    <P>
                        If such a confidential treatment request is properly made, the Commission will keep the information collected pursuant to Form SCI confidential to the extent permitted by law.
                        <SU>1247</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1247</SU>
                             The Freedom of Information Act (“FOIA”) provides at least two pertinent exemptions under which the Commission has authority to withhold certain information. FOIA Exemption 4 provides an exemption for “trade secrets and commercial or financial information obtained from a person and privileged or confidential.” 5 U.S.C. 552(b)(4). FOIA Exemption 8 provides an exemption for matters that are “contained in or related to examination, operating, or condition reports prepared by, on behalf of, or for the use of an agency responsible for the regulation or supervision of financial institutions.” 5 U.S.C. 552(b)(8).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Access to the Systems of an SCI Entity</HD>
                    <P>
                        Proposed Rule 1000(f) would have required each SCI entity to provide Commission representatives reasonable access to its SCI systems and SCI security systems to assess the SCI entity's compliance with Regulation SCI.
                        <SU>1248</SU>
                        <FTREF/>
                         In the SCI Proposal, the Commission noted that the proposed rule would facilitate the access of representatives of the Commission to such systems of an SCI entity either remotely or on site, noting, for example, that with such access, Commission representatives could test an SCI entity's firewalls and vulnerability to intrusions.
                        <SU>1249</SU>
                        <FTREF/>
                         Further, the Commission noted that the proposed rule was intended to be consistent with the Commission's current authority with respect to access to records generally 
                        <SU>1250</SU>
                        <FTREF/>
                         and could help ensure that Commission representatives have ready access to the SCI systems and SCI security systems of SCI entities in order to evaluate an SCI entity's practices with regard to the requirements of Regulation SCI.
                        <SU>1251</SU>
                        <FTREF/>
                         As discussed below, the Commission has determined not to adopt the proposed requirement because it believes it can achieve the goal of the proposed rule through its existing recordkeeping requirements and examination authority, as well as through the new recordkeeping requirement in Rule 1005 of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1248</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(f) and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section III.D.3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1249</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18130.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1250</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18130 (citing Section 17(b) of the Exchange Act, as well as Sections 11A, 6(b)(1), 15A(b)(2), and 17A(b)(3)(A) of the Exchange Act).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1251</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18130.
                        </P>
                    </FTNT>
                    <P>
                        Many commenters criticized the SCI Proposal's discussion of the proposed access requirement as permitting unfettered access by third parties that could pose significant security risks to an SCI entity's systems.
                        <SU>1252</SU>
                        <FTREF/>
                         Potential issues identified by commenters included unauthorized access to confidential information,
                        <SU>1253</SU>
                        <FTREF/>
                         risk and damage to systems,
                        <SU>1254</SU>
                        <FTREF/>
                         and contractual issues with third party vendors.
                        <SU>1255</SU>
                        <FTREF/>
                         One commenter stated that the Commission should bear in mind that access to such highly sensitive environments of SCI entities carries a duty of care commensurate with the sensitivity of the access and information involved.
                        <SU>1256</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1252</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 34; BATS Letter at 15; ISE Letter at 10; MSRB Letter at 25-26; Omgeo Letter at 28-29; SIFMA Letter at 18-19; FIF Letter at 7; Fidelity Letter at 5-6; LiquidPoint Letter at 4; ITG Letter at 16; KCG Letter at 20-21; Joint SROs Letter at 17-18; OCC Letter at 20; UBS Letter at 5; Tellefsen Letter at 10; and FINRA Letter at 41.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1253</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 41; and Omgeo Letter at 29.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1254</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 29; and ITG Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1255</SU>
                             
                            <E T="03">See, e.g.,</E>
                             SIFMA Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1256</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 20.
                        </P>
                    </FTNT>
                    <P>
                        While several commenters advocated for the elimination of the proposed access provision,
                        <SU>1257</SU>
                        <FTREF/>
                         some commenters recommended ways to refine the proposed requirement while still achieving its goals.
                        <SU>1258</SU>
                        <FTREF/>
                         These 
                        <PRTPAGE P="72359"/>
                        suggestions included: Limiting the category of Commission staff to whom access could be provided; 
                        <SU>1259</SU>
                        <FTREF/>
                         providing the Commission with access to “configuration and information flows of the system, instead of direct access;” 
                        <SU>1260</SU>
                        <FTREF/>
                         providing the Commission with reports and metrics on systems vulnerabilities rather than direct access; 
                        <SU>1261</SU>
                        <FTREF/>
                         requiring only that SCI entities demonstrate for Commission staff their controls and safeguards and compliance with the rule; 
                        <SU>1262</SU>
                        <FTREF/>
                         mandating training of Commission staff and supervision of Commission staff access by SCI entity personnel; 
                        <SU>1263</SU>
                        <FTREF/>
                         and requiring that an SCI entity's staff conduct any tests while Commission staff observed, rather than providing Commission staff with direct access.
                        <SU>1264</SU>
                        <FTREF/>
                         One commenter also noted that the concept of reasonable access was vague.
                        <SU>1265</SU>
                        <FTREF/>
                         Other commenters asked that the Commission more clearly prescribe what would constitute “reasonable access.” 
                        <SU>1266</SU>
                        <FTREF/>
                         One commenter also recommended that SCI entities provide an individual contact for a designated Commission representative to communicate and meet with regarding an SCI entity's systems.
                        <SU>1267</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1257</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ITG Letter at 16; and CME Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1258</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 34; OCC Letter at 20; ISE Letter at 10; DTCC Letter at 14; CME Letter at 
                            <PRTPAGE/>
                            11; Omgeo Letter at 29; Joint SROs Letter at 18; and MSRB Letter at 26.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1259</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 34.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1260</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 34.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1261</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ISE Letter at 10; DTCC Letter at 14; OCC Letter at 20; and CME Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1262</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 28-29; and DTCC Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1263</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 26.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1264</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1265</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ITG Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1266</SU>
                             
                            <E T="03">See, e.g.,</E>
                             MSRB Letter at 26; Joint SROs Letter at 18; and FINRA Letter at 41.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1267</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 19.
                        </P>
                    </FTNT>
                    <P>
                        A few commenters also questioned whether the proposed access requirement is authorized by Section 17(b) or Section 11A of the Exchange Act, as stated in the SCI Proposal.
                        <SU>1268</SU>
                        <FTREF/>
                         Other commenters considered the proposed access requirement unnecessary and questioned the Commission's justification for needing this authority.
                        <SU>1269</SU>
                        <FTREF/>
                         Another commenter pointed out that this type of access is authorized by other sections of the Exchange Act and an additional provision in Regulation SCI is redundant.
                        <SU>1270</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1268</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 34; BATS Letter at 15; and CME Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1269</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 41; BATS Letter at 15; Omgeo Letter at 28-29; and Fidelity Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1270</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 18.
                        </P>
                    </FTNT>
                    <P>
                        After consideration of the views of commenters, the Commission has determined not to adopt the proposed reasonable access provision because it believes it can achieve its goals through existing recordkeeping requirements and its examination authority, as well as through the new recordkeeping requirement in Rule 1005 of Regulation SCI. As discussed in the SCI Proposal, the reasonable access provision was designed to help ensure that the Commission was able to evaluate an SCI entity's practices with regard to the requirements of proposed Regulation SCI.
                        <SU>1271</SU>
                        <FTREF/>
                         The Commission believes that it can adequately assess an SCI entity's compliance with Regulation SCI through its authority provided by existing provisions of the Exchange Act and rules thereunder, as well as through the additional recordkeeping provisions being adopted today in Rule 1005 of Regulation SCI, as described above. In this regard, as discussed above, Section 17(a) of the Exchange Act provides the Commission with the authority to adopt recordkeeping rules, and the breadth of Rule 17a-1 thereunder is such that it would require SCI SROs to make, keep, and preserve records relating to their compliance with Regulation SCI, including records produced by SCI systems and indirect SCI systems.
                        <SU>1272</SU>
                        <FTREF/>
                         Further, adopted Rule 1005 specifically imposes requirements on each SCI entity (other than SCI SROs) to, among other things: Make, keep, and preserve at least one copy of all documents relating to its compliance with Regulation SCI; keep all such documents for a period of not less than five years, the first two years in a place that is readily accessible to the Commission or its representatives for inspection and examination; and upon request of any representative of the Commission, promptly furnish to the possession of such representative copies of any documents required to be kept and preserved by it pursuant to Rules 1005(b)(1) and (2).
                        <SU>1273</SU>
                        <FTREF/>
                         The Commission also notes that Section 17(b) of the Exchange Act authorizes the Commission to conduct reasonable periodic, special, or other examinations of all records maintained by the entities described in Section 17(a).
                        <SU>1274</SU>
                        <FTREF/>
                         These examinations can be conducted “at any time, or from time to time,” as the Commission “deems necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of [the Exchange Act].” 
                        <SU>1275</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1271</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 
                            <E T="03">18130.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1272</SU>
                             
                            <E T="03">See supra</E>
                             note 1251 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1273</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.C.1 (discussing recordkeeping requirements of adopted Rule 1005). As noted above, the recordkeeping requirements also extend to records of third parties. Specifically, an SCI entity is responsible for producing to Commission representatives records required to be made, kept, and preserved under Regulation SCI, even if those records are maintained by third parties, and the SCI entity is responsible for ensuring that such third parties produce those requested documents, upon examination or other request. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1274</SU>
                             
                            <E T="03">See</E>
                             Section 17(b) of the Exchange Act, 15 U.S.C. 78q(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1275</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Taken together, the Commission believes that these provisions afford the Commission the authority and ability to assess SCI entities' compliance with the requirements of Regulation SCI, rendering the adoption of a reasonable access provision unnecessary. Pursuant to this authority, in some circumstances, the Commission's assessment of an SCI entity's compliance may require appropriate access to certain SCI systems in coordination with the relevant SCI entity. In particular, the Commission's ability to assess the accuracy and completeness of an SCI entity's records with regard to Regulation SCI, including the written policies and procedures established and maintained pursuant to Rule 1001 and the report of the SCI review prepared in accordance with Rule 1003(b), and to evaluate whether SCI entities are otherwise complying with Regulation SCI, may necessitate the observation of SCI systems and indirect SCI systems by Commission representatives.
                        <SU>1276</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1276</SU>
                             The Commission notes that, under the ARP Inspection Program, such access has been routinely requested by Commission staff and provided by ARP entities.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that such access would not require an SCI entity to agree to remote or direct access by Commission personnel to an SCI entity's systems, such as by permitting Commission staff to run tests or use system scanning tools on its SCI systems or indirect SCI systems. Rather, as suggested by some commenters, access would entail allowing Commission staff to observe the SCI entity's SCI systems and indirect SCI systems with appropriate safeguards, including through systems demonstrations for Commission staff performed by the SCI entity and running tests on an SCI system with Commission staff onsite to observe.
                        <SU>1277</SU>
                        <FTREF/>
                         The Commission believes that such access does not raise the potential security risks posed by unrestricted third party access to SCI systems.
                        <SU>1278</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1277</SU>
                             
                            <E T="03">See supra</E>
                             notes 1262 and 1264 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1278</SU>
                             The Commission believes that the elimination of the proposed reasonable access provision addresses the other comments on this provision.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Form SCI</HD>
                    <P>
                        Pursuant to proposed Rule 1000(d), subject to certain exceptions, notices, reports, and other information required 
                        <PRTPAGE P="72360"/>
                        to be provided to the Commission under Regulation SCI would have been required to be submitted electronically through the EFFS on proposed Form SCI.
                        <SU>1279</SU>
                        <FTREF/>
                         Proposed Form SCI included detailed instructions regarding the specific information that SCI entities would have been required to submit to the Commission. After careful consideration of comments, the Commission is adopting Form SCI with certain modifications, as further discussed below. These modifications to proposed Form SCI correspond to the changes to the Commission notification and reporting requirements as adopted, each of which is discussed in greater detail above.
                        <SU>1280</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1279</SU>
                             Proposed Rule 1000(d) provided exceptions for notifications under proposed Rule 1000(b)(4)(i) and oral notifications pursuant to proposed Rule 1000(b)(6)(ii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1280</SU>
                             
                            <E T="03">See supra</E>
                             Sections IV.B.3.c, IV.B.4, and IV.B.5 (discussing the reporting requirements of the adopted regulation). 
                            <E T="03">See also supra</E>
                             Section IV.B.6 (discussing the business continuity and disaster recovery plans testing requirement for SCI entity members or participants, and elimination of the proposed Commission notification requirement related to member or participation designations).
                        </P>
                    </FTNT>
                    <P>
                        Adopted Rule 1006 provides that, except with respect to notifications to the Commission made pursuant to Rule 1002(b)(1) or updates to the Commission made pursuant to Rule 1002(b)(3), all notifications, reviews, descriptions, analyses, or reports to the Commission required to be submitted under Regulation SCI must be filed electronically on Form SCI. Form SCI solicits information through a series of questions designed to elicit short-form answers, but also requires SCI entities to provide information and/or reports in narrative form by attaching specified exhibits. All filings on Form SCI require that an SCI entity identify itself and indicate the basis for submitting the form. Specifically, an SCI entity would indicate on the form the specific type of submission it is making: A notification regarding an SCI event pursuant to Rule 1002(b)(2); a final report or interim status report regarding an SCI event pursuant to Rule 1002(b)(4); a quarterly report on de minimis systems disruptions and de minimis systems intrusions pursuant to Rule 1002(b)(5)(ii); a quarterly report of material systems changes pursuant to Rule 1003(a)(1); a supplemental report of material system changes pursuant to Rule 1003(a)(2); or a submission of the report of an SCI review, together with any response by senior management, pursuant to Rule 1003(b)(3). In addition, Form SCI permits, but does not require, SCI entities to utilize the form to submit initial notifications of SCI events pursuant to Rule 1002(b)(1), as well as updates regarding SCI events pursuant to Rule 1002(b)(3). Moreover, if an SCI entity decides to withdraw a previously submitted Form SCI, it would complete page 1 of Form SCI and select the appropriate check box to indicate the withdrawal. A filing on Form SCI also requires that an SCI entity provide additional information on attached exhibits, as discussed below. Because Form SCI is a report that is required to be filed under the Exchange Act and Regulation SCI, it is unlawful for any person to willfully or knowingly make, or cause to be made, a false or misleading statement with respect to any material fact in Form SCI.
                        <SU>1281</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1281</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Section 32(a) of the Exchange Act, 15 U.S.C. 78ff(a).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters addressed the information required by Form SCI as well as the submission process for the form. One commenter asked a number of questions on how the submission process would work in practice, including: (i) Whether the form would be rejected by the Commission if information was missing; (ii) whether the Commission would deem it a failure to comply with Regulation SCI if a Form SCI is rejected for incompleteness and the SCI entity is unable to resubmit within the applicable reporting time frame; (iii) how SCI entities would update or correct information previously submitted on Form SCI; (iv) will the EFFS system be available for Form SCI submissions during non-business hours and whether there is an alternative means to submit notifications if the EFFS system is down or unavailable; (v) who at the Commission would be reviewing submissions and whether they would be familiar with technical jargon; and (vi) whether the SCI entities will be expected to attach documentation supporting the descriptions provided in the exhibits.
                        <SU>1282</SU>
                        <FTREF/>
                         The commenter also expressed several concerns, including: (i) The amount of time it would take SCI entities to master the new submission process for proposed Form SCI and suggested a delayed implementation or transition period; (ii) that the form could encourage SCI entities to guess where they are missing information if a form could be rejected for incomplete information; (iii) that a submission that needs to be updated or corrected would not be considered timely filed; (iv) that the updating procedure could become burdensome if the SCI entity needed to explain the reason for any changes to information previously provided; and (v) that submissions would be more burdensome if technical notifications and reports needed to be translated into plain English.
                        <SU>1283</SU>
                        <FTREF/>
                         Another commenter requested that the electronic filing system that the Commission puts in place to receive Form SCI submissions be made available on weekends and outside normal business hours.
                        <SU>1284</SU>
                        <FTREF/>
                         This commenter also suggested that the Commission remain open to changes to Form SCI as it and SCI entities gain experience with the use of Form SCI and that the Commission should work with SCI entities to test the electronic submission system to ensure its operational capability.
                        <SU>1285</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1282</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 28-30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1283</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1284</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 19, 25. 
                            <E T="03">See also</E>
                             FINRA Letter at 29 (questioning whether the EFFS system would be available during non-business hours for Form SCI submissions).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1285</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 25-26.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has considered these comments and has addressed many of the issues raised by commenters by revising the substantive requirements of adopted Rules 1002 and 1003, as well as making certain changes to the adopted form. With respect to a commenter's question regarding whether a Form SCI would be rejected if information was missing,
                        <SU>1286</SU>
                        <FTREF/>
                         as stated in the General Instructions for Form SCI, an SCI entity must provide all information required by the form, including the exhibits. The General Instructions for Form SCI also state that a filing that is incomplete or similarly deficient may be returned to the SCI entity, and any filing so returned will be deemed not to have been filed with the Commission.
                        <SU>1287</SU>
                        <FTREF/>
                         In response to the commenter who expressed concern that a submission that needed to be updated or corrected would not be considered timely filed, the Commission notes that an SCI entity is responsible for submitting a complete and correct Form SCI within the time period specified in the relevant provisions under Regulation SCI.
                        <SU>1288</SU>
                        <FTREF/>
                         At the same time, the Commission notes 
                        <PRTPAGE P="72361"/>
                        that, while the SCI event notification under Rule 1002(b)(2) is required to be provided within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that an SCI event occurred, information for such notifications is only required to be provided on a good faith, best efforts basis. For other types of notifications and reports required to be submitted on Form SCI, SCI entities have more time to prepare such submission, and to ensure that the information provided is complete and correct.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1286</SU>
                             
                            <E T="03">See supra</E>
                             note 1282 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1287</SU>
                             While the Commission has the ability to reject a Form SCI filing, the Commission notes that the Form SCI submission process is different from the Form 19b-4 filing process. Specifically, SCI entities file Form SCI to provide notification to the Commission regarding SCI events and material systems changes, and reports of SCI reviews. On the other hand, SROs file Form 19b-4 for immediately effective rule changes or to seek Commission approval of rule changes. Therefore, the process for rejecting a Form 19b-4 filing does not apply to Form SCI submissions.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1288</SU>
                             With respect to a commenter's concern that SCI entities may have to guess where information is missing if a form could be rejected for incomplete information, the Commission intends there to be communication between Commission staff and SCI entity personnel in instances where a Form SCI is rejected to discuss the information missing in the submission and anything else necessary to comply with the form requirements. 
                            <E T="03">See supra</E>
                             note 1283 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to a commenter's question regarding how SCI entities would update or correct information previously submitted on Form SCI, the Commission notes that the rules under Regulation SCI already provide for updates for many of the Form SCI submissions. Specifically, Rule 1002(b)(2) requires certain information to be submitted on a good faith, best efforts basis within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred. Rule 1002(b)(3) requires SCI entities to provide updates regarding SCI events until the SCI event is resolved and the SCI entity's investigation of the SCI event is closed.
                        <SU>1289</SU>
                        <FTREF/>
                         As such, SCI entities may use the updates under Rule 1002(b)(3) to correct or update previously submitted information. Also, Rule 1003(a)(2) requires SCI entities to submit supplemental reports to notify the Commission of any material error in or material omission from a previously submitted material systems change report.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1289</SU>
                             As discussed in detail in Section IV.B.3.c above, Rule 1002(b)(3) allows SCI entities to discuss the update with Commission staff orally, rather than by completing the form, although an SCI entity may use Form SCI if it chooses to do so. To the extent an SCI entity chooses to utilize the form for such updates, the written updates can facilitate the Commission's tracking and assessment of SCI events.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the Form SCI submissions where the rules do not specifically provide for updates (
                        <E T="03">i.e.,</E>
                         SCI event notifications under Rule 1002(b)(4), quarterly SCI event notifications under Rule 1002(b)(5), report of SCI reviews under Rule 1003(b)(3)), if an SCI entity discovers that a previously submitted Form SCI must be corrected or updated, the SCI entity should contact Commission staff as it corrects or updates the prior submission. In addition, an SCI entity will be able to withdraw and re-submit a previously submitted Form SCI.
                        <SU>1290</SU>
                        <FTREF/>
                         However, as noted above, an SCI entity is responsible for submitting a complete and correct Form SCI within the time period specified in the relevant provisions under Regulation SCI.
                        <SU>1291</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1290</SU>
                             
                            <E T="03">See</E>
                             General Instructions to Form SCI, Item F.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1291</SU>
                             As noted above, one commenter expressed concern that an updating procedure could become burdensome if the SCI entity needs to explain the reason for any changes to information previously provided. 
                            <E T="03">See supra</E>
                             note 1283 and accompanying text. The Commission notes that, with respect to rules under Regulation SCI that require updates, those rules specify the information that is required to be contained in an update, and do not require an explanation of the reason for the update. With respect to the Form SCI submissions where the rules do not specifically provide for updates, as noted above, the SCI entity can contact Commission staff as the SCI entity corrects or updates the prior submission.
                        </P>
                    </FTNT>
                    <P>
                        In addition, in response to comments,
                        <SU>1292</SU>
                        <FTREF/>
                         the Commission notes that Form SCI does not require SCI entities to attach documentation supporting the descriptions in the exhibits, although SCI entities will be able to do so if they so choose by attaching the documentation as part of the relevant exhibit. Moreover, in response to the commenter who asked who at the Commission would be reviewing submissions and whether they would be familiar with technical jargon, the Commission notes that appropriate Commission staff from different offices or divisions with the necessary expertise to understand the Form SCI submission will review it depending on the nature of the submission (
                        <E T="03">i.e.,</E>
                         legal or technical), and thus, it is not necessary for SCI entities to translate technical jargon into plain English.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1292</SU>
                             
                            <E T="03">See supra</E>
                             notes 1282-1283 and accompanying text.
                        </P>
                    </FTNT>
                    <P>In response to the commenter who expressed concern as to the amount of time it would take SCI entities to master the Form SCI submission process and suggested delayed implementation, the Commission believes that, by utilizing the EFFS system currently used by many SROs for Rule 19b-4 and Rule 19b-7 filings, it will allow for a quicker and smoother implementation of the Form SCI submission process for certain SCI entities, and allow the Commission to apply its experience with EFFS to facilitate the submissions of notifications and reports required by Regulation SCI. Nevertheless, the Commission notes that it is delaying the date for compliance with Regulation SCI, as discussed in Section IV.F below. The Commission does not expect that the Form SCI submission process will require substantial time for SCI entities to master and the delayed date for compliance with Regulation SCI provides SCI entities with more time to learn and adopt it.</P>
                    <P>
                        With respect to commenters' question regarding whether the EFFS system will be available during non-business hours and whether there is an alternative means to submit notifications if the EFFS system is down or unavailable,
                        <SU>1293</SU>
                        <FTREF/>
                         the Commission notes that, as is the case with Rule 19b-4 and Rule 19b-7 filings, EFFS is available 24 hours a day. If EFFS becomes unavailable for a period of time, the Commission recognizes that SCI entities will not be able to submit any required notifications during that time period, and the Commission would expect the SCI entities to file any required notifications promptly once it becomes available. In response to the commenter who suggested that the Commission remain open to changes to Form SCI and that the Commission work with SCI entities to test the electronic submission system to ensure its operational capability, the Commission expects, as it has done with the SRO rule filing process, to periodically evaluate the effectiveness of the submission process for Form SCI, as well as the form itself, and may consider improvements in the future as appropriate.
                        <SU>1294</SU>
                        <FTREF/>
                         The Commission also notes that it expects, prior to the compliance date, that its staff will provide materials to SCI entities regarding the operation of the electronic filing system to submit Forms SCI. Furthermore, the Commission will perform internal testing to help ensure the operational capability of EFFS prior to the compliance date.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1293</SU>
                             
                            <E T="03">See supra</E>
                             notes 1282, 1284 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1294</SU>
                             
                            <E T="03">See supra</E>
                             note 1285 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Notice of SCI Events Pursuant to Rule 1002(b)</HD>
                    <P>
                        Proposed Rule 1000(b)(4) would have required each SCI entity to submit certain information regarding SCI events to the Commission using proposed Form SCI.
                        <SU>1295</SU>
                        <FTREF/>
                         The Commission is adopting proposed Rule 1000(b)(4) as Rule 1002(b) with certain modifications, which are discussed above in Section IV.B.3.c.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1295</SU>
                             Proposed Rule 1000(d) provided an exception for notifications under proposed Rule 1000(b)(4)(i).
                        </P>
                    </FTNT>
                    <P>
                        With respect to Commission notifications under Rule 1002, adopted Form SCI requires an SCI entity to provide the following information in a short, standardized format: (i) Whether the Commission has previously been notified of the SCI event pursuant to Rule 1002(b)(1); (ii) the type of submission (
                        <E T="03">i.e.,</E>
                         an initial notification pursuant to Rule 1002(b)(1), a notification pursuant to Rule 1002(b)(2), an update pursuant to Rule 1002(b)(3), a final report pursuant to Rule 1002(b)(4), or an interim status report 
                        <PRTPAGE P="72362"/>
                        pursuant to Rule 1002(b)(4)); (iii) the type(s) of SCI event (
                        <E T="03">i.e.,</E>
                         systems compliance issue, systems disruption, or systems intrusion); 
                        <SU>1296</SU>
                        <FTREF/>
                         (iv) the date/time the SCI event occurred; (v) the duration of the SCI event; (vi) when responsible SCI personnel had a reasonable basis to conclude that an SCI event occurred; (vii) whether the SCI event has been resolved and, if so, the date/time of resolution; (viii) whether the SCI entity's investigation of the SCI event is closed and, if so, the date of closure; (ix) the estimated number of market participants potentially impacted by the SCI event; (x) whether the SCI event is a major SCI event; (xi) the types of systems impacted (
                        <E T="03">i.e.,</E>
                         trading, clearance and settlement, order routing, market data, market regulation, market surveillance, or indirect SCI systems) and the name of such system(s); and (xii) whether any critical SCI system(s) are impacted by the SCI event and, if so, the types of such critical SCI systems (
                        <E T="03">i.e.,</E>
                         systems that directly support functionality relating to: Clearance and settlement systems of clearing agencies; openings, reopenings, and closings on the primary listing market; trading halts; initial public offerings; the provision of consolidated market data; exclusively listed securities; or systems that provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets) and a description of such systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1296</SU>
                             Some SCI events may meet the definition of more than a single SCI event type, and the form permits SCI entities to check one, two, or all three SCI event types.
                        </P>
                    </FTNT>
                    <P>If an SCI entity chooses to utilize Form SCI to submit an initial notification required by Rule 1002(b)(1), an SCI entity will be able to submit a short description of the SCI event, and be allowed to attach documents regarding such SCI event as part of Exhibit 6 of Form SCI if the SCI entity chooses to do so.</P>
                    <P>For a notification required by Rule 1002(b)(2), in addition to providing the applicable standardized information on Form SCI as discussed above, an SCI entity is required to submit an Exhibit 1. An SCI entity is required to provide the following information on a good faith, best efforts basis in the Exhibit 1: (i) A description of the SCI event, including the system(s) affected; and (ii) to the extent available as of the time of notification, the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event.</P>
                    <P>If an SCI entity chooses to utilize Form SCI to submit an update required by Rule 1002(b)(3), an SCI entity will be able to submit a short description of the update, and be allowed to attach documents regarding such update as part of Exhibit 6 of Form SCI if the SCI entity chooses to do so.</P>
                    <P>
                        For a submission required by Rule 1002(b)(4), in addition to providing the applicable standardized information on Form SCI as discussed above, adopted Form SCI also requires an SCI entity to indicate if it is a final report or an interim status report and submit an Exhibit 2. If an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 calendar days of the occurrence of the SCI event, an SCI entity must file a final report under Rule 1002(b)(4)(i)(A) within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event. However, if an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 calendar days of the occurrence of the SCI event, an SCI entity must file an interim status report under Rule 1002(b)(4)(i)(B)(
                        <E T="03">1</E>
                        ) within 30 calendar days after the occurrence of the SCI event. For SCI events in which an interim status report is required to be filed, an SCI entity must file a final report under Rule 1002(b)(4)(i)(B)(
                        <E T="03">2</E>
                        ) within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event. For any submission required by Rule 1002(b)(4), an SCI entity is required to provide the following information in the Exhibit 2: (i) A detailed description of: The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event; (ii) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and (iii) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. As noted above, if an SCI entity submits an interim written notification under Rule 1000(b)(4)(i)(B), the SCI entity is required to provide the information specified in Exhibit 2, but only to the extent known at the time. The SCI entity is also required to subsequently submit a final report under Rule 1000(b)(4)(i)(B) and provide all the information specified in Exhibit 2.
                    </P>
                    <P>Rule 1002(b)(5) states that the Commission notification requirements under Rules 1002(b)(1)-(4) do not apply to any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. Rule 1002(b)(5)(i) instead requires that an SCI entity make, keep, and preserve records relating to all such SCI events and Rule 1002(b)(5)(ii) requires an SCI entity to submit to the Commission quarterly reports containing a summary description of such de minimis systems disruptions and de minimis systems intrusions. For a quarterly report required by Rule 1002(b)(5), an SCI entity is required to indicate the end date of the applicable calendar quarter for which the report is being submitted. The SCI entity is also required to submit an Exhibit 3, containing a summary description of such de minimis systems disruptions and de minimis systems intrusions, including the SCI systems and, for systems intrusions, the indirect SCI systems, affected by such de minimis systems disruptions and de minimis systems intrusions during the applicable calendar quarter.</P>
                    <HD SOURCE="HD3">2. Notices of Material Systems Changes Pursuant to Rule 1003(a)</HD>
                    <P>
                        Proposed Rule 1000(b)(6) would have required an SCI entity to provide advance Commission notifications of material systems changes. Proposed Rule 1000(b)(8)(ii) would have required an SCI entity to submit to the Commission semi-annual reports on material systems changes. As discussed in detail in Section IV.B.4 above, many commenters were critical of the proposed reporting framework with respect to material systems changes, including the 30-day advance notification procedure. After considering the views of commenters, the Commission is not adopting the 30-day advance notification requirement or the semi-annual reporting requirement 
                        <PRTPAGE P="72363"/>
                        for material systems changes. Rather, an SCI entity is required to submit quarterly reports for material systems changes under Rule 1003(a)(1). An SCI entity is also required under Rule 1003(a)(2) to promptly submit a supplemental report notifying the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a).
                    </P>
                    <P>
                        One commenter raised a concern that an advance notification could be rejected by the Commission for inadequate description and result in a delay to a planned systems change.
                        <SU>1297</SU>
                        <FTREF/>
                         As noted above in Section IV.B.4, the Commission is adopting a quarterly reporting system that does not require the advanced notification of individual planned material systems changes required by proposed Rule 1000(b)(6). The adopted framework is intended to keep the Commission and its staff apprised of systems changes at SCI entities while reducing the burdens related to notifying the Commission of such changes and allowing for the various types of development processes used by SCI entities (including agile development processes). Also, as noted above in Section IV.B.4, Regulation SCI does not provide for a new review or approval process for SCI entities' material systems changes. As such, Commission staff will not use material systems change reports to require any approval of prospective systems changes in advance of their implementation pursuant to any provision of Regulation SCI, or to delay implementation of material systems changes pursuant to any provision of Regulation SCI.
                        <SU>1298</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1297</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1298</SU>
                             At the same time, the Commission notes that the General Instructions for Form SCI state that a filing that is incomplete or similarly deficient may be returned to the SCI entity, and any filing so returned will be deemed not to have been filed with the Commission.
                        </P>
                    </FTNT>
                    <P>
                        For a notification required by Rule 1003(a) (including supplemental reports under Rule 1003(a)(2)), an SCI entity is required to indicate the end date of the applicable calendar quarter for which the report is being submitted and submit an Exhibit 4. For a notification required by Rule 1003(a)(1), Exhibit 4, is required to contain a description of completed, ongoing, and planned material changes to its SCI systems and the security of its indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion. For a notification required by Rule 1003(a)(2), Exhibit 4 is required to contain the supplemental report of a material error in or material omission from a report previously submitted under Rule 1003(a)(1).
                        <SU>1299</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1299</SU>
                             
                            <E T="03">See</E>
                             General Instructions to Form SCI, Item C.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Reports of SCI Reviews Pursuant to 1003(b)</HD>
                    <P>Proposed Rule 1000(b)(8)(i) would have required an SCI entity to submit to the Commission a report of the SCI review required by proposed Rule 1000(b)(7), together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity. As discussed above in Section IV.B.5, the Commission is adopting this Commission reporting requirement as proposed. There were no comments on proposed Form SCI with respect to reports of SCI reviews.</P>
                    <P>
                        For a notification required by Rule 1003(b), an SCI entity is required to indicate on Form SCI the date of completion of the SCI review and the date of submission of the SCI review to the SCI entity's senior management. An SCI entity is also required to submit an Exhibit 5, containing the report of the SCI review that was submitted to the SCI entity's senior management, along with any response to the report by senior management.
                        <SU>1300</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1300</SU>
                             As discussed in Section IV.B.5, the SCI review would contain: (1) A risk assessment with respect to SCI systems and indirect SCI systems of an SCI entity; and (2) an assessment of internal control design and effectiveness of SCI systems and indirect SCI systems to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Notification of Member or Participant Designation Standards and List of Designees</HD>
                    <P>Proposed Rule 1000(b)(9) would have required an SCI entity to notify the Commission of its members or participants that have been designated for business continuity and disaster recovery plans testing, as well as the standards for such designation. Proposed Rule 1000(b)(9) would have also required SCI entities to promptly update such notification after any changes to its list of designees or standards for designation. As discussed above in Section IV.B.6, the Commission is not adopting these Commission notification requirements.</P>
                    <HD SOURCE="HD3">5. Other Information and Electronic Signature</HD>
                    <P>Proposed Form SCI would have required an SCI entity to provide the Commission with contact information for the systems personnel, regulatory personnel, and senior officer responsible for addressing an SCI event, including the name, title, telephone number, and email address of such persons. Proposed Form SCI would also have given the SCI entity an option to provide contact information for an additional systems personnel and regulatory personnel. Finally, proposed Form SCI would have required an electronic signature to help ensure the authenticity of the Form SCI submission.</P>
                    <P>Adopted Form SCI more generally requires an SCI entity to provide contact information for a person who is prepared to respond to questions for a particular submission. Form SCI continues to require an electronic signature to help ensure the authenticity of the Form SCI submission. The Commission believes that these requirements will expedite communications between Commission staff and SCI entities, because they will help identify the person or persons responsible for communicating with Commission staff about an SCI event even though one or more other persons may be responsible for addressing and resolving the SCI event, and also help ensure that only authorized personnel at each SCI entity submit filings required by adopted Regulation SCI.</P>
                    <HD SOURCE="HD2">E. Other Comments Received</HD>
                    <HD SOURCE="HD3">1. Applying Regulation SCI to Security-Based Swap Data Repositories and Security-Based Swap Execution Facilities</HD>
                    <P>
                        As noted in the SCI Proposal, on July 21, 2010, the President signed the Dodd-Frank Act into law.
                        <SU>1301</SU>
                        <FTREF/>
                         The Dodd-Frank Act was enacted, among other things, to promote the financial stability of the United States by improving the accountability and transparency of the nation's financial system.
                        <SU>1302</SU>
                        <FTREF/>
                         Title VII of the Dodd-Frank Act provides the Commission and the CFTC with the authority to regulate over-the-counter derivatives.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1301</SU>
                             The Dodd-Frank Wall Street Reform and Consumer Protection Act (Pub. L. 111-203, H.R. 4173) (“Dodd-Frank Act”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1302</SU>
                             
                            <E T="03">See</E>
                             Dodd-Frank Act Preamble.
                        </P>
                    </FTNT>
                    <P>
                        In particular, as noted in the SCI Proposal, Section 763 of the Dodd-Frank Act amends the Exchange Act by adding new statutory provisions to govern the regulation of various entities, including security-based swap data repositories (“SB SDRs”) and security-based swap execution facilities (“SB SEFs”).
                        <SU>1303</SU>
                        <FTREF/>
                          
                        <PRTPAGE P="72364"/>
                        Under the authorities of Section 13(n) of the Exchange Act, applicable to SB SDRs, and Section 3D(d) of the Exchange Act, applicable to SB SEFs, the Commission proposed rules for these entities with regard to their automated systems' capacity, resiliency, and security.
                        <SU>1304</SU>
                        <FTREF/>
                         In the SB SDR Proposing Release and the SB SEF Proposing Release, respectively, the Commission proposed Rule 13n-6 and Rule 822 under the Exchange Act, which would set forth the requirements for these entities with regard to their automated systems' capacity, resiliency, and security. In each release, the Commission stated that it was proposing standards comparable to the standards applicable to SROs, including exchanges and clearing agencies, and other registrants, pursuant to the Commission's ARP standards.
                        <SU>1305</SU>
                        <FTREF/>
                         The SCI Proposal described in detail the SB SDR and SB SEF proposals relating to systems' capacity, resiliency, and security; the comments received on those proposals; and the differences between proposed Regulation SCI and those proposals.
                        <SU>1306</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1303</SU>
                             
                            <E T="03">See</E>
                             Dodd-Frank Act, Section 763 (adding Sections 13(n), 3C, and 3D of the Exchange Act). The Dodd-Frank Act also directs the Commission to harmonize to the extent possible Commission regulation of SB SDRs and SB SEFs with CFTC regulation of swap data repositories (“SDRs”) and swap execution facilities (“SEFs”) under the 
                            <PRTPAGE/>
                            CFTC's jurisdiction, an endeavor that Commission staff is undertaking as it seeks to move the SB SDR and SB SEF proposals toward adoption. 
                            <E T="03">See</E>
                             Dodd-Frank Act, Section 712 (directing the Commission, before commencing any rulemaking with regard to SB SDRs or SB SEFs, to consult and coordinate with the CFTC for purposes of assuring regulatory consistency and comparability to the extent possible).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1304</SU>
                             
                            <E T="03">See</E>
                             Securities Exchange Act Release Nos. 63347 (November 19, 2010), 75 FR 77306 (December 10, 2010) (proposing new Rule 13n-6 under the Exchange Act applicable to SB SDRs) (“SB SDR Proposing Release”); 63825 (February 2, 2011), 76 FR 10948 (February 28, 2011) (proposing new Rule 822 under the Exchange Act applicable to SB SEFs) (“SB SEF Proposing Release”). 
                            <E T="03">See also</E>
                             Dodd-Frank Act, Section 761(a) (adding Section 3(a)(75) of the Exchange Act) (defining the term “security-based swap data repository”), and Section 761(a) (adding Section 3(a)(77) of the Exchange Act) (defining the term “security-based swap execution facility”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1305</SU>
                             
                            <E T="03">See</E>
                             SB SDR Proposing Release, 
                            <E T="03">supra</E>
                             note 1304, at 77332 and SB SEF Proposing Release, 
                            <E T="03">supra</E>
                             note 1304, at 10987.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1306</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18133-34.
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission recognized that there could be differences between Regulation SCI, as adopted, and Rules 13n-6 and 822, if adopted. Therefore, the Commission sought comment on whether it should propose to apply the requirements of Regulation SCI, in whole or in part, to SB SDRs and/or SB SEFs.
                        <SU>1307</SU>
                        <FTREF/>
                         In addition, the Commission sought comment on what—if the Commission were to propose to apply some or all of the requirements of Regulation SCI to SB SDRs or SB SEFs—would be the most appropriate way to implement such requirements for SB SDRs and SB SEFs.
                        <SU>1308</SU>
                        <FTREF/>
                         However, the Commission also noted that, should the Commission decide to propose to apply the requirements of Regulation SCI to SB SDRs or SB SEFs, the Commission would issue a separate release discussing such a proposal.
                        <SU>1309</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1307</SU>
                             
                            <E T="03">See id.</E>
                             at 18134-37.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1308</SU>
                             
                            <E T="03">See id.</E>
                             at 18137-38. As noted in the SCI Proposal, although the Commission has issued a policy statement regarding the anticipated sequencing of the compliance dates of final rules to be adopted by the Commission for certain provisions of Title VII of the Dodd-Frank Act, the precise timing for adoption of or compliance with any final rules relating to SB SDRs or SB SEFs is not known at this time. 
                            <E T="03">See</E>
                             Securities Exchange Act Release No. 67177 (June 11, 2012), 77 FR 35625 (June 14, 2012) (Statement of General Policy on the Sequencing of the Compliance Dates for Final Rules Applicable to Security-Based Swaps Adopted Pursuant to the Securities Exchange Act of 1934 and the Dodd-Frank Wall Street Reform and Consumer Protection Act).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1309</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18134.
                        </P>
                    </FTNT>
                    <P>
                        One commenter supported the inclusion of SB SEFs and possibly SB SDRs under proposed Regulation SCI.
                        <SU>1310</SU>
                        <FTREF/>
                         Several commenters supported some form of harmonization, but were cognizant of the practical differences between options and equities, on the one hand, and derivatives, on the other.
                        <SU>1311</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1310</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1311</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 18-19; and NYC Bar Letter at 2-5. 
                            <E T="03">See also</E>
                             CoreOne Letter at 5-7.
                        </P>
                    </FTNT>
                    <P>
                        In the context of considering whether Regulation SCI should apply to SB SDRs or SB SEFs, one commenter supported principles-based rules relating to systems compliance and integrity, and generally believed that principles applicable to one type of system should be applicable to all types of systems.
                        <SU>1312</SU>
                        <FTREF/>
                         This commenter noted that the Commission should not promulgate principles-based rules that would apply different principles to different systems, unless such difference is clearly warranted by the facts and circumstances relating to and the purpose of a particular system.
                        <SU>1313</SU>
                        <FTREF/>
                         This commenter also commented that, because technology continues to evolve at a rapid pace and because specific and technical rules may create conflicting standards, any attempt to provide specific and technical rules should be avoided, unless the context clearly warrants such specific and technical rules.
                        <SU>1314</SU>
                        <FTREF/>
                         This commenter concluded that the similarities between certain SCI entities and SB SDRs and SB SEFs do not provide a clear justification for a different set of rules.
                        <SU>1315</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1312</SU>
                             
                            <E T="03">See</E>
                             NYC Bar Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1313</SU>
                             
                            <E T="03">See id.</E>
                             at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1314</SU>
                             
                            <E T="03">See id.</E>
                             at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1315</SU>
                             
                            <E T="03">See id.</E>
                             This commenter also specifically noted that important market systems should not have differing recovery requirements without a clear justification, particularly in light of a Congressional mandate in the Dodd-Frank Act to ensure regulatory consistency and comparability, to the extent possible. 
                            <E T="03">See</E>
                             NYC Bar Letter at 5.
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that SB SDRs should have standards that are consistent with, but not identical to, those of SCI entities.
                        <SU>1316</SU>
                        <FTREF/>
                         According to this commenter, the functions that SB SDRs perform are significantly different from those performed by SCI entities.
                        <SU>1317</SU>
                        <FTREF/>
                         However, this commenter supported applying to SB SDRs: Proposed Rule 1000(b)(1)(i)(A)-(E); 
                        <SU>1318</SU>
                        <FTREF/>
                         requirements relating to Commission notification of SCI events (by adopting the notification provisions described in proposed Rule 13n-6(3)); and requirements for business continuity planning and testing (but SB SDRs should not be required to test with other SB SDRs given the structure of the proposed SB SDR Regulations).
                        <SU>1319</SU>
                        <FTREF/>
                         Finally, rather than making Regulation SCI applicable to SB SDRs, this commenter recommended that these provisions be incorporated into Rule 13n-6.
                        <SU>1320</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1316</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1317</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1318</SU>
                             However, this commenter noted that specific industry standards should be adopted for SB SDRs, rather than adopting existing standards that were largely developed before repositories were developed and were not intended to cover these types of entities. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1319</SU>
                             
                            <E T="03">See id.</E>
                             at 18-19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1320</SU>
                             
                            <E T="03">See id.</E>
                             at 19.
                        </P>
                    </FTNT>
                    <P>The Commission appreciates the comments received on the potential application of Regulation SCI to SB SDRs and SB SEFs. As noted above, should the Commission decide to propose to apply the requirements of Regulation SCI to SB SDRs or SB SEFs, the Commission would issue a separate release discussing such a proposal and would take these comments into account.</P>
                    <HD SOURCE="HD3">2. Applying Regulation SCI to Broker-Dealers Other Than SCI ATSs and Other Types of Entities</HD>
                    <P>
                        Regulation SCI, as proposed and as adopted, would apply to national securities exchanges, registered securities associations, registered clearing agencies, the MSRB, SCI ATSs, plan processors, and exempt clearing agencies subject to ARP. It would not apply to other types of market participants, such as market makers or other broker-dealers. As noted in the SCI Proposal, recent events have highlighted the significance of systems integrity of a broader set of market participants than those included in the definition of SCI entity.
                        <SU>1321</SU>
                        <FTREF/>
                         Also, as 
                        <PRTPAGE P="72365"/>
                        noted in the SCI Proposal, some broker-dealers have grown in size and importance to the market in recent years.
                        <SU>1322</SU>
                        <FTREF/>
                         As such, the Commission recognized that systems disruptions, systems compliance issues, and systems intrusions at broker-dealers could pose a significant risk to the market.
                        <SU>1323</SU>
                        <FTREF/>
                         The Commission also noted that Rule 15c3-5 under the Exchange Act,
                        <SU>1324</SU>
                        <FTREF/>
                         which requires brokers or dealers with market access to implement risk management controls and supervisory procedures to limit risk, already seeks to address certain risks posed to the markets by broker-dealer systems.
                        <SU>1325</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1321</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18138, n. 334.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1322</SU>
                             
                            <E T="03">See id.</E>
                             at 18138, n. 335.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1323</SU>
                             
                            <E T="03">See id.</E>
                             at 18138.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1324</SU>
                             17 CFR 240.15c3-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1325</SU>
                             
                            <E T="03">See supra</E>
                             note 114 and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18138-39.
                        </P>
                    </FTNT>
                    <P>
                        The Commission did not propose to apply Regulation SCI to registered broker-dealers (other than SCI ATSs) or to other types of entities not covered by the definition of SCI entity. As noted in the SCI Proposal, if the Commission were to decide to propose to apply the requirements of Regulation SCI to such entities, the Commission would issue a separate release discussing such a proposal.
                        <SU>1326</SU>
                        <FTREF/>
                         Nevertheless, in the SCI Proposal, the Commission sought comment on whether such entities should be subject to Regulation SCI in whole or in part.
                        <SU>1327</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1326</SU>
                             
                            <E T="03">See id.</E>
                             at 18139.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1327</SU>
                             
                            <E T="03">See id.</E>
                             at 18139-41.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters stated that the Commission should expand the definition of SCI entity to include broker-dealers.
                        <SU>1328</SU>
                        <FTREF/>
                         One commenter stated that the goals of Regulation SCI could not be met without expanding the definition of SCI entity to include the following types of broker-dealers: Exchange market maker, OTC market maker, and any other broker or dealer that executes orders internally by trading as a principal or crossing orders as an agent.
                        <SU>1329</SU>
                        <FTREF/>
                         This commenter stated that these entities should be included because they play a critical role in the markets, handle market share that exceeds that of certain SCI ATSs, and, like exchanges and ATSs, rely heavily on sophisticated automated systems.
                        <SU>1330</SU>
                        <FTREF/>
                         Another commenter also believed that the objectives of Regulation SCI could more readily be achieved if the regulation also applied to market makers, high-frequency trading firms, and other broker-dealers because the activities of these types of entities could present systemic risks to the market.
                        <SU>1331</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1328</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 8-10; and Liquidnet Letter at 2-3. Another commenter expressed its view that inclusion of order routing systems within the definition of “SCI systems” puts SCI entities at a competitive disadvantage against broker-dealers that are not covered by Regulation SCI. 
                            <E T="03">See</E>
                             BATS Letter at 4. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             notes 48-50, 94-96, and 152 and accompanying text (discussing comments regarding broadening the coverage of “SCI entity” and “SCI ATS” and the effect of the adopted ATS thresholds on barriers to entry), and 
                            <E T="03">infra</E>
                             Section VI.C.1.c (discussing the effect of Regulation SCI on competition between SCI entities and non-SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1329</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1330</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1331</SU>
                             
                            <E T="03">See</E>
                             Liquidnet Letter at 2.
                        </P>
                    </FTNT>
                    <P>
                        In connection with questions in the SCI Proposal regarding the application of Regulation SCI to broker-dealers other than SCI ATSs, one commenter urged the Commission to broaden the definition of SCI entity to include any entity with direct electronic access to equity markets because the equity markets can be disrupted by a single server.
                        <SU>1332</SU>
                        <FTREF/>
                         Another commenter stated that all direct access proprietary trading market participants (including high frequency market participants) should be included as SCI entities because of their significant footprint in the markets, past incidents like Knight Capital Group's massive trading losses from a systems malfunction in August 2012,
                        <SU>1333</SU>
                        <FTREF/>
                         and flaws in the existing compliance controls and practices of such firms.
                        <SU>1334</SU>
                        <FTREF/>
                         One commenter stated that Regulation SCI should be extended to any trading platforms that transact significant volume, including systems that are not required to register as an ATS, because all executions are against the bids and offers of a single dealer.
                        <SU>1335</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1332</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 3. 
                            <E T="03">See also supra</E>
                             notes 212-213 (explaining that the Commission believes that many systems with direct market access are captured by the adopted definition but the Commission is not expanding the scope of Regulation SCI to include other broker-dealer entities and their systems at this time).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1333</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18090, n. 70 (discussing Knight's systems malfunction in August 2012).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1334</SU>
                             
                            <E T="03">See</E>
                             Leuchtkafer Letter at 1-7. 
                            <E T="03">See supra</E>
                             notes 124-126 and accompanying text (discussing the Commission's determination to not apply Regulation SCI to non-ATS broker-dealers at this time).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1335</SU>
                             
                            <E T="03">See</E>
                             BlackRock Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        A few commenters further argued that Rule 15c3-5 under the Exchange Act is not sufficient by itself and therefore some broker-dealers should be treated as SCI entities.
                        <SU>1336</SU>
                        <FTREF/>
                         One of these commenters stated that non-ATS broker-dealers should be treated as SCI entities because Rule 15c3-5, concerning the implementation of risk management and supervisory controls to limit risk associated with routing orders to exchanges or ATSs, does not address reliability or integrity of the systems that implement such controls.
                        <SU>1337</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1336</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 3 and NYSE Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1337</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        Many other commenters stated more generally that broker-dealers should not be captured by the definition of SCI entity.
                        <SU>1338</SU>
                        <FTREF/>
                         Several commenters stated that they do not support the expansion of Regulation SCI to all broker-dealers because broker-dealers generally perform functions that do not have any systemic impact on the operation of the national market system and are presently subject to numerous regulations that require the establishment of controls (such as the Market Access Rule, Rule 17a-3, and Rule 17a-4), making Regulation SCI duplicative and unduly burdensome.
                        <SU>1339</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1338</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 3; MFA Letter at 4-5; FIA PTG Letter at 5; FSI Letter at 3; WF Letter at 2; Fidelity Letter at 4; KCG Letter at 14-17; LiquidPoint Letter at 4; and FSR Letter at 2-3, n. 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1339</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 3; MFA Letter at 4-5; FIA PTG Letter at 5; WF Letter at 2; KCG Letter at 15-17; LiquidPoint Letter at 4; and FSR Letter at 2-3, n. 5.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that broker-dealers are currently subject to high standards of systems compliance and integrity by FINRA and state laws, and disciplinary actions for failure to maintain sufficient protection of customer data and supervisory policies.
                        <SU>1340</SU>
                        <FTREF/>
                         Moreover, this commenter noted that, if potential systems issues could be addressed by Regulation SCI as applied to SCI entities, there would be no need to apply Regulation SCI to broker-dealers conducting activities on behalf of retail clients.
                        <SU>1341</SU>
                        <FTREF/>
                         This commenter stated that additional regulation would only be warranted after a meticulous cost-benefit analysis and implementation of the additional regulation at the lowest cost to firms and investors.
                        <SU>1342</SU>
                        <FTREF/>
                         This commenter concluded that the inclusion of broker-dealers would raise investors' costs and is unnecessary.
                        <SU>1343</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1340</SU>
                             
                            <E T="03">See</E>
                             FSI Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1341</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1342</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1343</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Another commenter believed that non-SCI ATS broker-dealers should not be included in the definition of SCI entity because, despite the longstanding practice of retail brokers routing their customers' orders to market markers for execution, those market makers are not critical.
                        <SU>1344</SU>
                        <FTREF/>
                         Moreover, this commenter believed that FINRA's rules with respect to broker-dealers are more appropriate than the SCI Proposal, and FINRA rules hold broker-dealers accountable and do not shield them from liability.
                        <SU>1345</SU>
                        <FTREF/>
                         This commenter stated that the combination of Commission and FINRA rules on 
                        <PRTPAGE P="72366"/>
                        broker-dealers ensures that broker-dealers are sufficiently regulated, although this commenter stated that FINRA could provide additional guidance on its rules in light of the weaknesses revealed by Superstorm Sandy.
                        <SU>1346</SU>
                        <FTREF/>
                         Similarly, another commenter stated that broker-dealers should not be regulated under Regulation SCI because broker-dealer operational regulation has been overseen almost entirely by FINRA.
                        <SU>1347</SU>
                        <FTREF/>
                         Specifically, FINRA member broker-dealers are required to create and implement written supervisory procedures covering the operation of their business.
                        <SU>1348</SU>
                        <FTREF/>
                         According to this commenter, this process allows broker-dealers to devise procedures that keep them in-line with FINRA and Commission regulations, and allows FINRA to focus on bigger picture issues impacting the broker-dealer industry.
                        <SU>1349</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1344</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1345</SU>
                             
                            <E T="03">See id.</E>
                             at 14-15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1346</SU>
                             
                            <E T="03">See id.</E>
                             at 14-17.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1347</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1348</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1349</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        In addition, one commenter stated that the Commission should not propose a requirement that SCI SROs require their members to institute policies and procedures similar to those required under Regulation SCI.
                        <SU>1350</SU>
                        <FTREF/>
                         According to this commenter, SCI SROs already impose regulatory requirements addressing similar concerns as those that Regulation SCI is designed to address.
                        <SU>1351</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1350</SU>
                             
                            <E T="03">See</E>
                             WF Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1351</SU>
                             
                            <E T="03">See id.</E>
                             at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that the term SCI entity should not encompass clearing broker-dealers or transfer agents because they are not involved in “real-time” trading activities and therefore there would not be any material impact on critical market functions should their systems fail.
                        <SU>1352</SU>
                        <FTREF/>
                         Additionally, this commenter stated that because Regulation SCI “is designed to formalize the Commission's existing ARP Program,” and clearing broker-dealers and transfer agents do not participate in ARP, those entities should not be included within the scope of Regulation SCI.
                        <SU>1353</SU>
                        <FTREF/>
                         Another commenter echoed these positions with respect to transfer agents, and also stated that transfer agents should not be included within the definition of SCI entity because the majority of transfer agents do not have electronic connectivity to SCI entities.
                        <SU>1354</SU>
                        <FTREF/>
                         Additionally, this commenter stated that larger transfer agents are already required to have business continuity plans and written policies and procedures to ensure that their systems are robust and will function as intended.
                        <SU>1355</SU>
                        <FTREF/>
                         In determining whether to expand the scope of SCI entities, one commenter commented that the Commission should consider the role of an entity in the securities markets and the risks presented by that entity, and stated that transfer agents should not be covered because they raise fewer risks to the markets than the proposed SCI entities, as their systems do not directly support the functions intended to be targeted by the SCI Proposal.
                        <SU>1356</SU>
                        <FTREF/>
                         Another commenter similarly stated that transfer agents should not be covered because there is little chance that a problem with a transfer agent's operations would impact market activity.
                        <SU>1357</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1352</SU>
                             
                            <E T="03">See</E>
                             Fidelity Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1353</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1354</SU>
                             
                            <E T="03">See</E>
                             STA Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1355</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1356</SU>
                             
                            <E T="03">See</E>
                             ICI Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1357</SU>
                             
                            <E T="03">See</E>
                             Oppenheimer Letter at 2.
                        </P>
                    </FTNT>
                    <P>The Commission appreciates the comments received on the potential application of Regulation SCI to broker-dealers other than SCI ATSs and other types of entities. As noted above, should the Commission decide to propose to apply the requirements of Regulation SCI to these entities, the Commission would issue a separate release discussing such a proposal and would take these comments into account. </P>
                    <HD SOURCE="HD2">F. Effective Date and Compliance Dates </HD>
                    <P>
                        Several commenters provided recommendations for when the requirements of Regulation SCI should go into effect and/or when SCI entities should be required to comply with the various requirements of the regulation.
                        <SU>1358</SU>
                        <FTREF/>
                         Each commenter recommended allowing what they believed to be sufficient time for SCI entities to prepare for what they perceived as complex or substantial regulatory responsibilities.
                        <SU>1359</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1358</SU>
                             
                            <E T="03">See e.g.,</E>
                             FINRA Letter at 41-42; DTCC Letter at 3; OCC Letter at 2; MSRB Letter at 39-40; KCG Letter at 19; SIFMA Letter at 7; and OTC Markets Letter at 4, 22-23.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1359</SU>
                             
                            <E T="03">See e.g.,</E>
                             FINRA Letter at 41-42; DTCC Letter at 3; OCC Letter at 2; MSRB Letter at 39-40; KCG Letter at 19; SIFMA Letter at 7; and OTC Markets Letter at 4, 22-23.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters suggested that the implementation period should vary between those entities and/or systems currently subject to the ARP Inspection Program and those that are not.
                        <SU>1360</SU>
                        <FTREF/>
                         For example, one commenter suggested an implementation period of no less than two years for SCI systems that are subject to the ARP Inspection Program and three years for all other systems.
                        <SU>1361</SU>
                        <FTREF/>
                         Similarly, another commenter recommended that certain systems of non-ARP participants should be provided at least an additional one year transition period, after a six-month delayed effectiveness after final approval of Regulation SCI for SCI systems of current ARP participants that are trading, clearance and settlement, and order routing systems.
                        <SU>1362</SU>
                        <FTREF/>
                         Another commenter stated that systems currently covered by the ARP Inspection Program should be granted two years to phase-in the rule and that non-ARP systems would need a phase-in period of at least four years.
                        <SU>1363</SU>
                        <FTREF/>
                         One commenter also noted more generally that the time needed to meet the new requirements of Regulation SCI will vary by the type of SCI entity and the level of its current participation in the ARP Inspection Program.
                        <SU>1364</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1360</SU>
                             
                            <E T="03">See, e.g.,</E>
                             FINRA Letter at 41-42; DTCC Letter at 3; and OTC Markets Letter at 4, 22-23.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1361</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 41-42.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1362</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 39-40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1363</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 4, 22-23.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1364</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters requested a special phase-in period for ATSs. Specifically, two commenters suggested that ATSs should be given six months after meeting the given threshold in the definition of SCI ATS to come into compliance with Regulation SCI.
                        <SU>1365</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1365</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 19; and SIFMA Letter at 7. 
                            <E T="03">See also</E>
                             adopted Rule 1000 (definition of “SCI ATS”) and 
                            <E T="03">supra</E>
                             Section IV.A.1.b (discussing definition of “SCI ATS”).
                        </P>
                    </FTNT>
                    <P>
                        Other commenters provided detailed suggestions for a phase-in compliance timeline for the requirements of Regulation SCI.
                        <SU>1366</SU>
                        <FTREF/>
                         For example, one commenter suggested implementing the rule in three phases so that it would apply: (1) After initial six-month delayed effectiveness, to SCI systems of current ARP participants that are trading, clearance and settlement, and order routing systems, and after one additional year, to such systems of non-ARP participants (for at least one annual cycle); (2) to indirect SCI systems relating to the systems in phase one (for at least one annual cycle); and (3) to SCI systems that are market data, regulation and surveillance systems and related indirect SCI systems.
                        <SU>1367</SU>
                        <FTREF/>
                         Another commenter believed the rule should be phased-in over four stages, where each SCI entity would: (1) Review its SCI systems risk-based assessment with Commission staff; (2) review and update its policies and procedures to reasonably ensure compliance with Regulation SCI; (3) implement such policies and procedures; and (4) conduct an annual review.
                        <SU>1368</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1366</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 39-40; and OCC Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1367</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1368</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 3.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72367"/>
                    <P>
                        Other commenters recommended individual compliance deadlines for certain requirements of Regulation SCI.
                        <SU>1369</SU>
                        <FTREF/>
                         Specifically, two commenters suggested that phased-in compliance should be permitted for proposed Rule 1000(b)(9) addressing testing of SCI entity business continuity and disaster recovery plans by SCI entity members or participants.
                        <SU>1370</SU>
                        <FTREF/>
                         Specifically, one commenter believed that, if end-to-end business continuity and disaster recovery plans testing were to be required, it should be phased-in to allow SCI entities to conduct testing of specific SCI systems over time, rather than be required to conduct a full end-to-end test, which it stated cannot be done within a reasonable timeframe.
                        <SU>1371</SU>
                        <FTREF/>
                         The other commenter recommended a phased-in approach to implementation of broader BC/DR testing over a period of years.
                        <SU>1372</SU>
                        <FTREF/>
                         One commenter recommended that the Commission institute an implementation period for the Commission notification requirement under proposed Rule 1000(b)(4) to allow SCI entities to prepare for what the commenter believed to be an increase in the number of notifications that would be required.
                        <SU>1373</SU>
                        <FTREF/>
                         This commenter also noted generally that business continuity and end-to-end testing requirements,
                        <SU>1374</SU>
                        <FTREF/>
                         the two-hour recovery time objective,
                        <SU>1375</SU>
                        <FTREF/>
                         and adopting the required policies and procedures may take longer to comply with than other provisions of Regulation SCI.
                        <SU>1376</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1369</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 2-3, 11, and 18; and SIFMA Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1370</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1004 and 
                            <E T="03">supra</E>
                             Section IV.B.6 (discussing business continuity and disaster recovery plans testing requirements).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1371</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1372</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1373</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 11; 
                            <E T="03">see also</E>
                             adopted Rule 1002(b) and 
                            <E T="03">supra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement for SCI events). One commenter also expressed concern about SCI entities being able to effectively make submissions on Form SCI upon Regulation SCI becoming effective, and urged Commission staff to work with the SCI entities in the development, testing, and implementation of the Form SCI electronic submission system, including provision of any systems requirements (
                            <E T="03">e.g.,</E>
                             supported browsers, required certificates, or authentication protocols). 
                            <E T="03">See</E>
                             MSRB Letter at 25. Another commenter requested that the Commission provide SCI entities sufficient time to learn the new Form SCI submission process, and recommended that the Commission delay implementation of Form SCI until SCI entities and Commission staff have gained experience with the Regulation SCI reporting requirements. 
                            <E T="03">See</E>
                             FINRA Letter at 28. In the alternative, this commenter recommended that the Commission provide a transition period for SCI entities to establish their processes for submission of Form SCI. 
                            <E T="03">See</E>
                             FINRA Letter at 28.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1374</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1004 and 
                            <E T="03">supra</E>
                             Section IV.B.6 (discussing business continuity and disaster recovery plans testing requirements).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1375</SU>
                             
                            <E T="03">See</E>
                             adopted Rule 1001(a)(2)(v) and 
                            <E T="03">supra</E>
                             Section IV.B.1.b (discussing the policies and procedures requirement and the two-hour recovery time objective).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1376</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 2-3; 
                            <E T="03">see also</E>
                             adopted Rule 1001 and 
                            <E T="03">supra</E>
                             Sections IV.B.1-2 (discussing the policies and procedures requirement for operational capability and systems compliance).
                        </P>
                    </FTNT>
                    <P>
                        Regulation SCI will become effective 60 days after publication of the rules in the 
                        <E T="04">Federal Register</E>
                         (“Effective Date”). As proposed, SCI entities would have been required to meet the requirements of Regulation SCI on the Effective Date. However, after consideration of the views of commenters, the Commission has determined to adopt a compliance date for Regulation SCI of nine months after the Effective Date, except as described below with regard to: (1) ATSs newly meeting the thresholds in the definition of “SCI ATS;” and (2) the industry- or sector-wide coordinated testing requirement, which will have different compliance periods. The Commission believes that the importance of strengthening the technology infrastructure of key market participants, the potential significant risks posed by systems issues to the U.S. securities markets, and the significant number of recent systems issues at various trading venues, necessitates as prompt an implementation of the requirements of Regulation SCI by SCI entities as possible. At the same time, the Commission understands that SCI entities will need time to prepare for the obligations imposed by Regulation SCI and, accordingly, believes that this nine-month time frame provides SCI entities adequate time to meet the requirements of Regulation SCI. While certain commenters suggested longer compliance periods or phased-in compliance periods, the Commission understands that entities currently subject to the ARP Inspection Program may already comply with certain requirements of Regulation SCI. In addition, the Commission also believes that SCI entities that have not previously participated in the ARP Inspection Program may also currently operate in accordance with certain of the adopted requirements. For example, the Commission believes that most SCI entities generally have in place policies and procedures designed to ensure its systems' capacity, integrity, resiliency, availability, and security and that most SCI entities already take corrective actions in response to systems issues.
                    </P>
                    <P>
                        Further, the Commission notes that, as described above, it has further focused the scope of the requirements of Regulation SCI from the SCI Proposal and, thus, has lessened the potential burdens on SCI entities.
                        <SU>1377</SU>
                        <FTREF/>
                         Therefore, the Commission believes that many of the concerns expressed by commenters regarding the time that would be needed to prepare for the responsibilities imposed by Regulation SCI have been significantly mitigated or addressed by this overall refinement of the rules and obligations of SCI entities. For example, as discussed above, the Commission has further focused the definition of “SCI systems” and clarified the scope of “indirect SCI systems,” which will result in fewer systems being subject to the requirements of Regulation SCI.
                        <SU>1378</SU>
                        <FTREF/>
                         In addition, the Commission notification provision will require immediate Commission notice of fewer SCI events than as proposed as a result of the refining of several definitions and the adoption of an exception from the immediate reporting requirements for de minimis SCI events, which will instead be subject to recordkeeping requirements and/or a quarterly reporting obligation, as applicable.
                        <SU>1379</SU>
                        <FTREF/>
                         Further, the Commission has clarified that an SCI entity's policies and procedures relating to the capacity, integrity, resiliency, availability, and security of its SCI systems and indirect SCI systems can to be tailored to a particular SCI system's criticality and risk, contrary to the belief of some commenters that the rule required all systems to be held to the same standards.
                        <SU>1380</SU>
                        <FTREF/>
                         The Commission also notes that it expects, prior to the compliance date, that its staff will provide information to SCI entities regarding the operation of the electronic filing system to submit Forms SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1377</SU>
                             
                            <E T="03">See supra</E>
                             Section III (providing a summary of the key modifications from the SCI Proposal) and Section IV (providing a detailed discussion of changes from the SCI Proposal).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1378</SU>
                             
                            <E T="03">See supra</E>
                             Sections IV.A.2.b and IV.A.2.d (discussing the definitions of “SCI systems” and “indirect SCI systems”). The Commission notes that the refining of these definitions also reduces the need to phase-in compliance based on type of system as suggested by one commenter, because fewer systems overall will be subject to the regulation than proposed and many systems for which the commenter urged a delay in compliance will not be covered by the regulation, as adopted.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1379</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.c (discussing the Commission notification requirement). As discussed above, SCI entities will be required to make, keep, and preserve records relating to all de minimis SCI events and to report de minimis systems disruptions and de minimis systems intrusions quarterly.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1380</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.1 (discussing the requirement for policies and procedures to achieve capacity, integrity, resiliency, availability, and security).
                        </P>
                    </FTNT>
                    <P>
                        With regard to some commenters' suggestions that there should be different compliance periods for SCI entities currently subject to the ARP Inspection Program and those that do not currently participate in the ARP Inspection Program (or phased-in compliance based, in part, on this 
                        <PRTPAGE P="72368"/>
                        distinction), as noted above, the Commission believes that both categories of entities already have some level of processes or procedures in place that are in compliance with the requirements of Regulation SCI. Further, given the voluntary nature of the current ARP Inspection Program, the Commission believes that the extent of current compliance with the requirements of adopted Regulation SCI by entities subject to the ARP Inspection Program varies for different entities. In addition, as noted above, Regulation SCI has a broader scope than the current ARP Inspection Program and imposes mandatory requirements on entities subject to the rules, and accordingly will require all SCI entities (both ARP entities and non-ARP entities) to take steps, including implementing necessary systems changes, to meet the requirements of Regulation SCI. For these reasons, the Commission believes that it is appropriate to provide all SCI entities nine months to become compliant with the requirements of Regulation SCI.
                    </P>
                    <P>
                        With regard to two commenters' suggestions that the Commission should adopt specific phased-in compliance periods based on type of entity (
                        <E T="03">i.e.,</E>
                         ARP or non-ARP), type of system, or other factors, the Commission believes that such an approach is not necessary for the reasons stated above. Further, the Commission believes that having multiple phases of compliance would create unnecessary complexity and raise practical difficulties for implementation.
                    </P>
                    <P>
                        At the same time, the Commission believes that it is appropriate to provide additional compliance periods for limited aspects of Regulation SCI, as requested by some commenters. Specifically, the Commission believes that ATSs meeting the volume thresholds in the definition of “SCI ATS” for the first time should be provided an additional six months from the time that the ATS first meets the applicable thresholds to comply with the requirements of Regulation SCI.
                        <SU>1381</SU>
                        <FTREF/>
                         The Commission believes that this additional six-month period is appropriate and necessary to allow an SCI ATS the time needed to take steps to meet the requirements of the rules, rather than requiring compliance immediately upon meeting the volume thresholds. The Commission also believes that this additional compliance period should give a new ATS entrant the opportunity to initiate and develop its business by allowing additional time before a new ATS must incur the costs associated with compliance with Regulation SCI.
                        <SU>1382</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1381</SU>
                             
                            <E T="03">See supra</E>
                             note 1365 and accompanying text. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.A.1.b (discussing the definition of “SCI ATS,” including the applicable volume thresholds and the inclusion of a six-month compliance period within the definition). For example, if a new ATS begins operations in January 2016 and subsequently meets the volume thresholds in the definition of “SCI ATS” for four out of the six months ending December 31, 2016, it would have until June 30, 2017 to become compliant with the requirements of Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1382</SU>
                             
                            <E T="03">See supra</E>
                             note 152 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is also adopting a longer compliance period with regard to the industry- or sector-wide coordinated testing requirement in adopted Rule 1004(d).
                        <SU>1383</SU>
                        <FTREF/>
                         Specifically, SCI entities will have 21 months from the Effective Date to coordinate the testing of an SCI entity's business continuity and disaster recovery plans on an industry- or sector-wide basis with other SCI entities pursuant to adopted Rule 1004(d). Given that the compliance date for the other requirements of Regulation SCI is nine months from the Effective Date, this will provide SCI entities an additional year (12 months) beyond the compliance date for the other requirements of Regulation SCI (for a total of 21 months) to comply with Rule 1004(d). The Commission believes that this additional time period is appropriate in light of commenters' concerns regarding the complexity and logistical challenges posed by the requirement.
                        <SU>1384</SU>
                        <FTREF/>
                         The Commission expects SCI entities to work cooperatively to address these logistical hurdles and to carefully plan such testing, and believes that the additional time for compliance should help to ensure that such testing is implemented effectively.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1383</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.6.b.iv (discussing the coordinated testing requirement of adopted Rule 1004(d)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1384</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>If any provision of Regulation SCI, or the application thereof to any person or circumstance, is held to be invalid, such invalidity shall not affect other provisions or application of such provisions to other persons or circumstances that can be given effect without the invalid provision or application.</P>
                    <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>
                    <P>
                        Certain rules under Regulation SCI impose new “collection of information” requirements within the meaning of the Paperwork Reduction Act of 1995 (“PRA”).
                        <SU>1385</SU>
                        <FTREF/>
                         An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number. In accordance with 44 U.S.C. 3507 and 5 CFR 1320.11, the Commission submitted these collections of information to the Office of Management and Budget (“OMB”) for review. The title for the collection of information requirement is “Regulation Systems Compliance and Integrity.” The collection of information was assigned OMB Control No. 3235-0703.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1385</SU>
                             44 U.S.C. 3501 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission solicited comments on the collection of information burdens associated with Regulation SCI. In particular, the Commission asked whether commenters agree with the Commission's estimate of the number of respondents and the burden associated with compliance with Regulation SCI.
                        <SU>1386</SU>
                        <FTREF/>
                         In addition, the Commission asked whether SCI entities would outsource the work associated with compliance with Regulation SCI.
                        <SU>1387</SU>
                        <FTREF/>
                         Some commenters noted that the Commission underestimated the burdens that would be imposed by proposed Regulation SCI.
                        <SU>1388</SU>
                        <FTREF/>
                         As discussed above, the Commission received 60 comment letters on the proposal. Some of these comments relate directly or indirectly to the PRA. These comments are addressed below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1386</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18155.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1387</SU>
                             
                            <E T="03">See id.</E>
                             at 18154-55.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1388</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Joint SRO Letter at 18-19; CME Letter at 4-5; OCC Letter at 11-12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Summary of Collection of Information</HD>
                    <P>Regulation SCI includes four categories of obligations that require a collection of information within the meaning of the PRA. Specifically, an SCI entity is required to: (1) Establish specified written policies and procedures, and mandate participation by designated members or participants in certain testing of the SCI entity's business continuity and disaster recovery plans; (2) provide certain notifications, disseminate certain information, and create reports; (3) take corrective actions, and identify critical SCI systems, major SCI events, de minimis SCI events, and material systems changes; and (4) comply with recordkeeping requirements.</P>
                    <HD SOURCE="HD3">1. Requirements To Establish Written Policies and Procedures and Mandate Participation in Certain Testing</HD>
                    <P>
                        Rule 1001 requires SCI entities to establish policies and procedures with respect to various matters. Rule 1001(a) requires each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, 
                        <PRTPAGE P="72369"/>
                        integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. Rule 1001(a)(2) specifies that such policies and procedures are required to include, at a minimum: (i) The establishment of reasonable current and future technology infrastructure capacity planning estimates; (ii) periodic capacity stress tests of such systems to determine their ability to process transactions in an accurate, timely, and efficient manner; (iii) a program to review and keep current systems development and testing methodology for such systems; (iv) regular reviews and testing, as applicable, of such systems, including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters; (v) business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption; (vi) standards that result in such systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data; and (vii) monitoring of such systems to identify potential SCI events. Rule 1001(a)(3) requires each SCI entity to periodically review the effectiveness of the policies and procedures required by Rule 1001(a), and take prompt action to remedy deficiencies in such policies and procedures. Rule 1001(a)(4) states that an SCI entity's policies and procedures shall be deemed to be reasonably designed if they are consistent with current SCI industry standards, which are required to be comprised of information technology practices that are widely available to information technology professionals in the financial sector and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization, though compliance with current SCI industry standards is not the exclusive means to comply with the requirements of Rule 1001(a).
                    </P>
                    <P>Rule 1001(b)(1) requires each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the Act and rules and regulations thereunder and the entity's rules and governing documents, as applicable. Rule 1001(b)(2) specifies that such policies and procedures are required to include, at a minimum: (i) Testing of all SCI systems and any changes to SCI systems prior to implementation; (ii) a system of internal controls over changes to SCI systems; (iii) a plan for assessments of the functionality of SCI systems designed to detect systems compliance issues, including by responsible SCI personnel and by personnel familiar with applicable provisions of the Act and the rules and regulations thereunder and the SCI entity's rules and governing documents; and (iv) a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, regarding SCI systems design, changes, testing, and controls designed to detect and prevent systems compliance issues. Rule 1001(b)(3) requires each SCI entity to periodically review the effectiveness of the policies and procedures required by Rule 1001(b), and take prompt action to remedy deficiencies in such policies and procedures. Further, pursuant to Rule 1001(b)(4), personnel of an SCI entity is deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by an SCI entity of Rule 1001(b) if the person: (i) Has reasonably discharged the duties and obligations incumbent upon such person by the SCI entity's policies and procedures; and (ii) was without reasonable cause to believe that the policies and procedures relating to an SCI system for which such person was responsible, or had supervisory responsibility, were not established, maintained, or enforced in accordance with Rule 1001(b) in any material respect.</P>
                    <P>Rule 1001(c)(1) requires each SCI entity to establish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel, and escalation procedures to quickly inform responsible SCI personnel of potential SCI events. Rule 1001(c)(2) requires each SCI entity to periodically review the effectiveness of the policies and procedures required by Rule 1001(c)(1), and take prompt action to remedy deficiencies in such policies and procedures.</P>
                    <P>
                        Rule 1004 requires an SCI entity, with respect to its business continuity and disaster recovery plans, including its backup systems, to: (a) Establish standards for the designation of those members or participants that the SCI entity reasonably determines are, taken as a whole, the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of such plans; and (b) designate members or participants pursuant to such standards and require participation by such members or participants in scheduled functional and performance testing of the operation of such plans, in the manner and frequency as specified by the SCI entity, at least once every 12 months (
                        <E T="03">e.g.,</E>
                         for SCI SROs, by submitting proposed rule changes under Section 19(b) of the Exchange Act; for SCI ATSs, by revising membership or subscriber agreements and internal procedures; for plan processors, through an amendment to an SCI Plan under Rule 608 of Regulation NMS; and, for exempt clearing agencies subject to ARP, by revising participant agreements and internal procedures). Rule 1004(c) requires an SCI entity to coordinate such required testing on an industry- or sector-wide basis with other SCI entities.
                    </P>
                    <HD SOURCE="HD3">2. Notification, Dissemination, and Reporting Requirements for SCI Entities</HD>
                    <P>
                        Certain rules under Regulation SCI require SCI entities to notify or report information to the Commission, or disseminate information to their members or participants. Rules 1002 and 1003 each contain notification, dissemination, or reporting requirements.
                        <SU>1389</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1389</SU>
                             To access EFFS, the secure Commission Web site for filing of Form SCI, an SCI entity will submit to the Commission an External Application User Authentication Form (“EAUF”) to register each individual at the SCI entity who will access the EFFS system on behalf of the SCI entity. Upon receipt and verification of the information in the EAUF process, the Commission will issue each such person a User ID and Password to permit access to the Commission's secure Web site.
                        </P>
                    </FTNT>
                    <P>Rule 1002(b) requires Commission notification of SCI events. Rule 1002(b)(1) requires an SCI entity to immediately notify the Commission upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred. These notifications may be made orally or in writing.</P>
                    <P>
                        Rule 1002(b)(2) requires an SCI entity, within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, to submit a written notification to the Commission on Form SCI pertaining to such SCI event.
                        <SU>1390</SU>
                        <FTREF/>
                          
                        <PRTPAGE P="72370"/>
                        Rule 1002(b)(2) requires that this notification include: (i) A description of the SCI event, including the system(s) affected; and (ii) to the extent available as of the time of the notification, the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event, the potential impact of the SCI event on the market, a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event, the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved, and any other pertinent information known by the SCI entity about the SCI event.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1390</SU>
                             This notification is required to be submitted on a good faith, best efforts basis.
                        </P>
                    </FTNT>
                    <P>Rule 1002(b)(3) requires an SCI entity, until an SCI event is resolved and the SCI entity's investigation of the SCI event is closed, to provide updates pertaining to such SCI event to the Commission on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, to correct any materially incorrect information previously provided, or when new information is discovered (including but not limited to any of the information listed in Rule 1002(b)(2)(ii)). The updates under Rule 1002(b)(3) may be made orally or in writing.</P>
                    <P>Rule 1002(b)(4) states that, if an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 calendar days of the occurrence of the event, then within 5 business days after the resolution of the SCI event and closure of the investigation regarding the SCI event, the SCI entity is required to submit a final written notification to the Commission pertaining to the SCI event. This notification is required to include: (i) A detailed description of the SCI entity's assessment of the types and number of market participants affected by the SCI event, the SCI entity's assessment of the impact of the SCI event on the market, the steps that the SCI entity has taken, is taking, or plans to take with respect to the SCI event, the time the SCI event was resolved, the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event, and any other pertinent information known by the SCI entity about the SCI event; (ii) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and (iii) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. Rule 1002(b)(4)(iv) further states that, if an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 days of the occurrence of the SCI event, then the SCI entity is required to submit an interim written notification pertaining to such event within 30 calendar days after the occurrence of the event, containing the information required by Rule 1002(b)(4)(ii) to the extent known at that time. Within 5 business days after the resolution of such event and closure of the investigation, the SCI entity is required to submit a final written notification to the Commission, containing the information required by Rule 1002(b)(4)(ii).</P>
                    <P>Rule 1002(b)(5) states that the requirements of Rules 1002(b)(1)-(4) do not apply to de minimis SCI events. Instead, for these types of SCI events, an SCI entity is required to make, keep, and preserve records relating to these events, and submit to the Commission quarterly reports containing a summary description of de minimis systems disruptions and de minimis systems intrusions, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such systems disruptions and systems intrusions during the applicable calendar quarter.</P>
                    <P>Rule 1002(c) requires the dissemination of information regarding certain SCI events and specifies the nature and timing of such dissemination. Rule 1002(c)(1)(i) requires an SCI entity, promptly after any responsible SCI personnel has a reasonable basis to conclude that a systems disruption or systems compliance issue has occurred, to disseminate the following information about such SCI event: (A) The system(s) affected by the SCI event; and (B) a summary description of the SCI event. In addition, Rule 1002(c)(1)(ii) requires an SCI entity, when known, to further disseminate the following information: (A) A detailed description of the SCI event; (B) the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; and (C) a description of the progress of its corrective action for the SCI event and when the SCI event has been or is expected to be resolved. Rule 1002(c)(1)(iii) requires that an SCI entity provide regular updates of the information required to be disseminated under Rule 1002(c)(1)(i) and (ii).</P>
                    <P>
                        With respect to systems intrusions, Rule 1002(c)(2) states that, promptly after any responsible SCI personnel has a reasonable basis to conclude that a systems intrusion has occurred, an SCI entity is required to disseminate a summary description of the systems intrusion, including a description of the corrective action taken by the SCI entity and when the systems intrusion has been or is expected to be resolved, unless the SCI entity determines that dissemination of such information would likely compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and documents the reasons for such determination.
                        <SU>1391</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1391</SU>
                             Rule 1002(c)(3) provides that the information specified in Rules 1002(c)(1) and (2) is required to be disseminated to members or participants of the SCI entity that a responsible SCI personnel has reasonably estimated may have been affected by the SCI event, and promptly disseminated to any additional members or participants that any responsible SCI personnel subsequently reasonably estimates may have been affected by the SCI event. However, information regarding major SCI events must be disseminated to all members or participants of an SCI entity.
                        </P>
                    </FTNT>
                    <P>Rule 1002(c)(4) provides that the information dissemination requirement does not apply to SCI events to the extent they relate to market regulation or market surveillance systems, or to any de minimis SCI events.</P>
                    <P>Rule 1003(a)(1) requires an SCI entity, within 30 calendar days after the end of each calendar quarter, to submit to the Commission a report describing completed, ongoing, and planned material changes to its SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion. Rule 1003(a)(2) further requires an SCI entity to promptly submit a supplemental report to notify the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a).</P>
                    <P>
                        Rules 1003(b)(1) and (2) require an SCI entity to conduct periodic SCI reviews of its compliance with Regulation SCI,
                        <SU>1392</SU>
                        <FTREF/>
                         and to submit a report of the SCI review to senior management of the SCI entity for review no more than 30 calendar days after completion of such SCI review. Rule 1003(b)(3) also requires an SCI entity to submit to the Commission, and to the board of directors of the SCI entity or the equivalent of such board, a report of the SCI review, together with any response by senior management, within 
                        <PRTPAGE P="72371"/>
                        60 calendar days after its submission to senior management of the SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1392</SU>
                             SCI entities are required to conduct an SCI review not less than once each calendar year. However, under Rule 1003(b)(1)(i), penetration test reviews of the network, firewalls, and production systems are required to be conducted not less than once every three years. Under Rule 1003(b)(1)(ii), assessments of SCI systems directly supporting market regulation or market surveillance are required to be conducted at a frequency based on risk assessment, but not less than once every three years.
                        </P>
                    </FTNT>
                    <P>Rule 1006 requires any notifications to the Commission required to be submitted under Regulation SCI, except notifications pursuant to Rule 1002(b)(1) or 1002(b)(3), to be filed electronically on Form SCI, include all information as prescribed in Form SCI and the instructions thereto, and contain an electronic signature. In addition, pursuant to Rule 1006(b), the signatory to an electronically filed Form SCI is required to manually sign a signature page or document authenticating, acknowledging, or otherwise adopting his or her signature that appears in typed form within the electronic filing. Such document is required to be retained by the SCI entity in accordance with Rule 1005.</P>
                    <HD SOURCE="HD3">3. Requirements To Take Corrective Action and Identify Critical SCI Systems, Major SCI Events, De Minimis SCI Events, and Material Systems Changes</HD>
                    <P>Rule 1002(a) requires an SCI entity, upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, to begin to take appropriate corrective action, which is required to include, at a minimum, mitigating potential harm to investors and market integrity resulting from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable. The Commission believes that SCI entities are likely to work to develop a written process for ensuring that they are prepared to comply with the corrective action requirement and are likely to also periodically review this process.</P>
                    <P>
                        In connection with the reporting of material systems changes, Rule 1003(a)(1) requires an SCI entity to establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material. In addition, because the Commission notification and information dissemination requirements under Rules 1002(b) and (c), respectively, apply differently to SCI events depending on whether an event is a “major SCI event” or whether the event has no or a de minimis impact on the SCI entity's operations or on market participants, when an SCI event occurs, an SCI entity must determine whether an SCI event is a major SCI event or a de minimis SCI event. Moreover, because the business continuity and disaster recovery policies and procedures requirement under Rule 1001(a)(2)(v) imposes different resumption goals for critical SCI systems as compared to other SCI systems, an SCI entity must determine whether an SCI system is a critical SCI system.
                        <SU>1393</SU>
                        <FTREF/>
                         As such, SCI entities would likely work to develop a written process for ensuring that they are able to make timely and accurate determinations regarding the nature of an SCI system or SCI event, and periodically review this process.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1393</SU>
                             Also, pursuant to the definition of “major SCI event,” in determining whether an SCI event is a major SCI event, an SCI entity is required to consider whether an SCI event can have any impact on a critical SCI system. 
                            <E T="03">See</E>
                             Rule 1000.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Recordkeeping Requirements</HD>
                    <P>Rule 1005 sets forth recordkeeping requirements for SCI entities. Under Rule 1005(a), SCI SROs are required to make, keep, and preserve all documents relating to their compliance with Regulation SCI as prescribed in Rule 17a-1 under the Exchange Act. Under Rule 1005(b), each SCI entity that is not an SCI SRO is required to make, keep, and preserve at least one copy of all documents, including correspondence, memoranda, papers, books, notices, accounts, and other such records, relating to its compliance with Regulation SCI, including, but not limited to, records relating to any changes to its SCI systems and indirect SCI systems. Each SCI entity that is not an SCI SRO is required to keep all such documents for a period of not less than five years, the first two years in a place that is readily accessible to the Commission or its representatives for inspection and examination. Upon request of any representative of the Commission, such SCI entities would be required to promptly furnish to the possession of such representative copies of any documents required to be kept and preserved by it under Rules 1005(b)(1) and (2). Under Rule 1005(c), upon or immediately prior to ceasing to do business or ceasing to be registered under the Exchange Act, an SCI entity is required to take all necessary action to ensure that the records required to be made, kept, and preserved by Rule 1005 will be accessible to the Commission and its representatives in the manner required by Rule 1005 and for the remainder of the period required by Rule 1005.</P>
                    <P>In addition, Rule 1007 provides that, if the records required to be filed or kept by an SCI entity under Regulation SCI are prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity is required to ensure that the records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service and signed by a duly authorized person at such service bureau or other recordkeeping service.</P>
                    <HD SOURCE="HD2">B. Use of Information</HD>
                    <HD SOURCE="HD3">1. Requirements To Establish Written Policies and Procedures and Mandate Participation in Certain Testing</HD>
                    <P>The requirement that SCI entities establish policies and procedures under adopted Rule 1001(a) should advance the goal of improving Commission review and oversight of U.S. securities market infrastructure by requiring an SCI entity's policies and procedures to be reasonably designed to ensure its own operational capability, including the ability to maintain effective operations, minimize or eliminate the effect of performance degradations, and have sufficient backup and recovery capabilities. Because an SCI entity's own operational capability can have the potential to impact investors, the overall market, or the trading of individual securities, the Commission believes that these policies and procedures will help promote the maintenance of fair and orderly markets.</P>
                    <P>The Commission believes that Rule 1001(b), which requires each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the Exchange Act and the rules and regulations thereunder and the entity's rules and governing documents, as applicable, will help to prevent the occurrence of systems compliance issues. In addition, the Commission believes Rule 1001(b) will help to: Ensure that SCI SROs comply with Section 19(b)(1) of the Exchange Act; reinforce existing SRO rule filing processes to assist market participants and the public in understanding how the SCI systems of SCI SROs are intended to operate; and assist SCI SROs in meeting their obligations to file plan amendments to SCI Plans under Rule 608 of Regulation NMS. It should similarly help other SCI entities to achieve operational compliance with the Exchange Act, the rules and regulations thereunder, and their governing documents.</P>
                    <P>
                        The requirement to establish policies and procedures pursuant to Rule 1001(c) that include the designation and documentation of responsible SCI personnel should help make it clear to all employees of the SCI entity who the designated responsible SCI personnel are for purposes of the escalation procedures and so that Commission staff 
                        <PRTPAGE P="72372"/>
                        can easily identify such responsible SCI personnel in the course of its inspections and examinations and other interactions with SCI entities. The Commission also believes that escalation procedures to quickly inform responsible SCI personnel of potential SCI events will help ensure that the appropriate person(s) are provided notice of potential SCI events so that any appropriate actions can be taken in accordance with the requirements of Regulation SCI without unnecessary delay.
                    </P>
                    <P>The Commission believes that the requirement that SCI entities establish standards that require designated members or participants to participate in the testing of their business continuity and disaster recovery plans will help reduce the risks associated with an SCI entity's decision to activate its BC/DR plans and help to ensure that such plans operate as intended, if activated. The testing participation requirement should help an SCI entity to ensure that its efforts to develop effective BC/DR plans are not undermined by a lack of participation by members or participants that the SCI entity believes are necessary to the successful activation of such plans. This requirement should also assist the Commission in maintaining fair and orderly markets in a BC/DR scenario following a wide-scale disruption.</P>
                    <HD SOURCE="HD3">2. Notification, Dissemination, and Reporting Requirements for SCI Entities</HD>
                    <P>Adopted Rule 1002(b), including adopted Rules 1002(b)(1)-(3), will foster a system for comprehensive reporting of SCI events, which should enhance the Commission's review and oversight of U.S. securities market infrastructure and foster cooperation between the Commission and SCI entities in responding to SCI events. The Commission also believes that the aggregated data that will result from the reporting of SCI events will enhance its ability to comprehensively analyze the nature and types of various SCI events and identify more effectively areas of persistent or recurring problems across the systems of all SCI entities. The information in the final report required under Rule 1002(b)(4) should provide the Commission with a comprehensive analysis to more fully understand and assess the impact caused by the SCI event. The Commission expects that the quarterly reporting required by Rule 1002(b)(5) will better achieve the goal of keeping Commission staff informed regarding the nature and frequency of systems disruptions and systems intrusions that arise but are reasonably estimated by the SCI entity to have a de minimis impact on the entity's operations or on market participants. Further, submission and review of regular reports should facilitate Commission staff comparisons among SCI entities and thereby permit the Commission and its staff to have a more holistic view of the types of systems operations challenges that were posed to SCI entities in the aggregate.</P>
                    <P>Adopted Rule 1002(c) advances the Commission's goal of promoting fair and orderly markets by disseminating information about an SCI event to some or all of the SCI entity's members or participants, who can use such information to evaluate the event's impact on their trading and other activities and develop an appropriate response.</P>
                    <P>The quarterly material systems change reports required by Rule 1003(a) should permit the Commission and its staff to have up-to-date information regarding an SCI entity's systems development progress and plans, and help the Commission with its oversight of U.S. securities market infrastructure.</P>
                    <P>The SCI reviews under Rule 1003(b) should not only assist the Commission in improving its oversight of the technology infrastructure of SCI entities, but also each SCI entity in assessing the effectiveness of its information technology practices, helping to ensure compliance with the safeguards provided by the requirements of Regulation SCI, identifying potential areas of weakness that require additional or modified controls, and determining where to best devote resources.</P>
                    <P>Rule 1006 provides a uniform manner in which the Commission would receive—and SCI entities would provide—written notifications, reviews, descriptions, analyses, or reports made pursuant to Regulation SCI. The Commission believes that Rule 1006 therefore allows SCI entities to efficiently draft and submit the required reports, and for the Commission to efficiently review, analyze, and respond to the information provided.</P>
                    <P>As noted above, in order to access EFFS, an SCI entity will submit to the Commission an EAUF to register each individual at the SCI entity who access the EFFS system on behalf of the SCI entity. The information provided via EAUF will be used by the Commission to verify the identity of the individual submitting Form SCI on behalf of the SCI entity and provide such individual access to the EFFS.</P>
                    <HD SOURCE="HD3">3. Requirements To Take Corrective Action and Identify Critical SCI Systems, Major SCI Events, De Minimis SCI Events, and Material Systems Changes</HD>
                    <P>
                        The requirement that SCI entities begin to take appropriate corrective action upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, and the policies and procedures SCI entities would likely use to implement this requirement, should help facilitate SCI entities' responses to SCI events, including taking appropriate steps necessary to remedy the problem or problems causing such SCI event and mitigate the negative effects of the SCI event, if any, on market participants and the securities markets more broadly. The requirement that each SCI entity establish written criteria for identifying material systems changes should help the Commission ensure that it is kept apprised of the systems changes that SCI entities believe to be material and aid the Commission and its staff in understanding the operations and functionality of the systems of an SCI entity and any changes to such systems. The Commission expects that the application of different requirements (
                        <E T="03">e.g.,</E>
                         Commission notification requirements and information dissemination requirements) to critical SCI systems, major SCI events, and de minimis SCI events, and the policies and procedures required by SCI entities to make these determinations, will help to ensure that the Commission is kept apprised of SCI events, and that relevant market participants have basic information about SCI events so that those notified can better develop an appropriate response. These policies and procedures should also assist SCI entities in complying with the notification, dissemination and reporting requirements of Regulation SCI.
                    </P>
                    <HD SOURCE="HD3">4. Recordkeeping Requirements</HD>
                    <P>
                        Rule 1005 requires each SCI entity to make, keep, and preserve records relating to its compliance with Regulation SCI because such records should assist the Commission in understanding whether an SCI entity is meeting its obligations under Regulation SCI, assessing whether an SCI entity has appropriate policies and procedures with respect to its technology systems, helping to identify the causes and consequences of an SCI event, and understanding the types of material systems changes occurring at an SCI entity. The Commission expects that Rule 1005 will also facilitate the 
                        <PRTPAGE P="72373"/>
                        Commission's inspections and examinations of SCI entities and assist it in evaluating an SCI entity's compliance with Regulation SCI. Moreover, having an SCI entity's records available even after it has ceased to do business or to be registered under the Exchange Act should provide an additional tool to help the Commission to reconstruct important market events and better understand the impact of such events.
                    </P>
                    <P>Rule 1007 should help ensure the Commission's ability to obtain required records that are held by a third party who may not otherwise have an obligation to make such records available to the Commission.</P>
                    <HD SOURCE="HD2">C. Respondents</HD>
                    <P>
                        The “collection of information” requirements contained in Regulation SCI apply to SCI entities, as described below. Currently, there are 27 entities that would satisfy the definition of SCI SRO,
                        <SU>1394</SU>
                        <FTREF/>
                         14 entities that would satisfy the definition of SCI ATS,
                        <SU>1395</SU>
                        <FTREF/>
                         2 entities that would satisfy the definition of plan processor,
                        <SU>1396</SU>
                        <FTREF/>
                         and 1 entity that would meet the definition of exempt clearing agency subject to ARP.
                        <SU>1397</SU>
                        <FTREF/>
                         Accordingly, the Commission estimates that there are currently 44 entities that meet the definition of SCI entity and are subject to the collection of information requirements of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1394</SU>
                             
                            <E T="03">See supra</E>
                             notes 74-77 and accompanying text (listing 18 registered national securities exchanges, 7 registered clearing agencies, FINRA, and the MSRB). 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 80 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1395</SU>
                             
                            <E T="03">See supra</E>
                             notes 150 and 175 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1396</SU>
                             
                            <E T="03">See supra</E>
                             note 202 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1397</SU>
                             
                            <E T="03">See supra</E>
                             note 203 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Total Initial and Annual Reporting and Recordkeeping Burdens</HD>
                    <P>
                        The Commission notes that national securities exchanges, national securities associations, registered clearing agencies, plan processors, one ATS, and one exempt clearing agency currently participate in the ARP Inspection Program. Under the ARP Inspection Program, Commission staff conducts inspections of these entities, attends periodic technology briefings by staff of these entities, monitors planned significant systems changes, and responds to reports of systems failures, disruptions, and other systems problems of these entities.
                        <SU>1398</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1398</SU>
                             
                            <E T="03">See supra</E>
                             Section II.A.
                        </P>
                    </FTNT>
                    <P>
                        Under Regulation SCI, many of the principles of the ARP policy statements with which some SCI entities are familiar are codified. As such, current practices of these SCI entities already comply with certain requirements of Regulation SCI.
                        <SU>1399</SU>
                        <FTREF/>
                         However, because Regulation SCI has a broader scope than the current ARP Inspection Program and imposes mandatory recordkeeping obligations on SCI entities,
                        <SU>1400</SU>
                        <FTREF/>
                         the Commission believes Regulation SCI will impose paperwork burdens on all SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1399</SU>
                             In addition, some SCI entities already comply with certain requirements of Regulation SCI to some extent as a matter of prudent business practice or pursuant to other rules. For example, as noted above, FINRA Rule 4370 includes requirements for FINRA members related to business continuity plans. 
                            <E T="03">See</E>
                             supra note 115. In addition, NASD Rule 3010 and FINRA Rule 3130 include requirements for FINRA members related to procedures to achieve compliance with applicable securities laws and regulations and certain SRO rules. 
                            <E T="03">See</E>
                             supra note 115. Further, FINRA Rule 4530 includes reporting requirements related to certain compliance issues. 
                            <E T="03">See</E>
                             supra note 115. Compliance with existing requirements under FINRA rules could help SCI ATSs to comply with Regulation SCI. Therefore, the Commission acknowledges that SCI ATSs may experience a lower paperwork burden in complying with certain provisions of Regulation SCI than some other SCI entities. However, unlike SCI entities that participate in the ARP Inspection Program (where in many instances the Commission has estimated a 50% reduction in SCI entity staff compliance burden as compared to other SCI entities when estimating paperwork costs with regard to Regulation SCI requirements due to participation in the ARP inspection program), the Commission believes that any reduction in burden resulting from compliance with these FINRA and NASD rules is unlikely to be significant.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1400</SU>
                             As discussed more fully in 
                            <E T="03">supra</E>
                             Section IV.C.1, SCI SROs are already subject to existing recordkeeping and retention requirements under Rule 17a-1.
                        </P>
                    </FTNT>
                    <P>
                        The Commission's total burden estimates in this Paperwork Reduction Act section reflect the total burdens on all SCI entities, taking into account the extent to which some SCI entities already comply with some of the requirements of Regulation SCI. The Commission also notes that the burden estimates per SCI entity are intended to reflect the average paperwork burden for each SCI entity to comply with Regulation SCI. Therefore, some SCI entities may experience more burden than the Commission's estimates, while others may experience less. The Commission notes that the burden figures set forth in this section are the Commission's estimate of the paperwork burden for compliance with Regulation SCI based on a variety of sources, including Commission staff's experience with the current ARP Inspection Program, other similar estimated burdens for analogous rulemakings, and comments received on the burden estimates in the SCI Proposal.
                        <SU>1401</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1401</SU>
                             The Commission also notes that the allocation of burden hours between staff and managers of an SCI entity that are identified in this section is intended to reflect the Commission's estimate of the broad categories of SCI entity personnel who will be involved in compliance with Regulation SCI. The Commission recognizes that some SCI entities may have additional subcategories of staff or managers who will be involved in compliance with Regulation SCI (
                            <E T="03">e.g.,</E>
                             information security staff may be a subcategory of systems analysts), whereas other SCI entities may not have the specific categories of staff or managers that are identified in this section.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Requirements To Establish Written Policies and Procedures and Mandate Participation in Certain Testing</HD>
                    <P>The rules under Regulation SCI that would require an SCI entity to establish policies and procedures and to mandate member or participant participation in business continuity and disaster recovery plan testing are discussed more fully in Sections IV.B.1, IV.B.2, and IV.B.6 above.</P>
                    <HD SOURCE="HD3">a. Policies and Procedures</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that an SCI entity that has not previously participated in the ARP Inspection Program would require an average of 210 burden hours initially to develop and draft the policies and procedures required by proposed Rule 1000(b)(1) (except for the policies and procedures for standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data) 
                        <SU>1402</SU>
                        <FTREF/>
                         and 60 hours annually to review and update such policies and procedures.
                        <SU>1403</SU>
                        <FTREF/>
                         The Commission estimated that an SCI entity that currently participates in the ARP Inspection Program would require an average of 105 burden hours initially to develop and draft such policies and procedures 
                        <SU>1404</SU>
                        <FTREF/>
                         and 30 hours annually 
                        <PRTPAGE P="72374"/>
                        to review and update such policies and procedures.
                        <SU>1405</SU>
                        <FTREF/>
                         With respect to the requirement in proposed Rule 1000(b)(1) for policies and procedures that provide for standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data, the Commission estimated that each SCI entity would spend 130 hours annually.
                        <SU>1406</SU>
                        <FTREF/>
                         In the SCI Proposal, the Commission also estimated that all SCI entities would conduct most of the work associated with proposed Rule 1000(b)(1) internally.
                        <SU>1407</SU>
                        <FTREF/>
                         However, the Commission estimated that SCI entities would seek outside legal and/or consulting services in the initial preparation of the policies and procedures at an average cost of $20,000 per SCI entity.
                        <SU>1408</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1402</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18145. The 210 burden hours included 80 hours by a Compliance Manager (including senior management review), 80 hours by an Attorney, 25 hours by a Senior Systems Analyst, and 25 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                             at 18146. This estimate was based on Commission staff's experience with the ARP Inspection Program and the Commission's preliminary estimate in the SB SDR Proposing Release for a similar requirement. 
                            <E T="03">See id.</E>
                             at 18145, n. 365.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1403</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. The 60 burden hours included 30 hours by a Compliance Manager and 30 hours by an Attorney. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program and the Commission's preliminary estimate in the SB SDR Proposing Release for a similar requirement. 
                            <E T="03">See id.</E>
                             at 18146, n. 377.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1404</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18145. The 105 burden hours included 40 hours by a Compliance Manager (including senior management review), 40 hours by an Attorney, 12.5 hours by a Senior Systems Analyst, and 12.5 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                             at 18146. The Commission stated its belief that a fifty percent baseline for SCI entities that participate in the ARP Inspection Program is appropriate because, although these entities already have substantial 
                            <PRTPAGE/>
                            policies and procedures in place, the rule would require these entities to devote substantial time to review and revise their existing policies and procedures to ensure that they are sufficiently robust. 
                            <E T="03">See id.</E>
                             at 18145.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1405</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. The 30 burden hours included 15 hours by a Compliance Manager and 15 hours by an Attorney. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1406</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18145. The 130 burden hours included 30 hours by a Compliance Attorney and 100 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             at 18146. This estimate was based on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18145, n. 371. The Commission noted in the SCI Proposal that this proposed requirement was not addressed by the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18145.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1407</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18145.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1408</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        With respect to proposed Rule 1000(b)(2), the Commission estimated that each SCI entity would elect to comply with the proposed safe harbor provisions.
                        <SU>1409</SU>
                        <FTREF/>
                         The Commission estimated that each SCI entity would spend 180 hours initially to design the policies and procedures accordingly.
                        <SU>1410</SU>
                        <FTREF/>
                         The Commission estimated that each SCI SRO would spend approximately 120 hours annually to review and update such policies and procedures,
                        <SU>1411</SU>
                        <FTREF/>
                         and that each SCI entity that is not an SRO would spend approximately 60 hours to review and update such policies and procedures.
                        <SU>1412</SU>
                        <FTREF/>
                         In the SCI Proposal, the Commission also estimated that all SCI entities would conduct most of the work associated with proposed Rule 1000(b)(2) internally.
                        <SU>1413</SU>
                        <FTREF/>
                         However, the Commission estimated that SCI entities would seek outside legal and/or consulting services in the initial preparation of the policies and procedures at an average cost of $20,000 per SCI entity.
                        <SU>1414</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1409</SU>
                             
                            <E T="03">See id.</E>
                             at 18146, and proposed Rules 1000(b)(2)(ii) and (iii).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1410</SU>
                             
                            <E T="03">See id.</E>
                             at 18146. The 180 burden hours included 30 hours by a Compliance Attorney and 150 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program and OCIE examinations, which review policies and procedures of registered entities in conjunction with examinations of such entities for compliance with the federal securities laws. 
                            <E T="03">See id.</E>
                             at 18146, n. 383.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1411</SU>
                             
                            <E T="03">See id.</E>
                             at 18146. The 120 burden hours included 20 hours by a Compliance Attorney and 100 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18146, n. 384.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1412</SU>
                             
                            <E T="03">See id.</E>
                             at 18146. The 60 burden hours included 10 hours by a Compliance Attorney and 50 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1413</SU>
                             
                            <E T="03">See id.</E>
                             at 18145.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1414</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Several commenters noted that the Commission underestimated the paperwork burden of proposed Rules 1000(b)(1) and (b)(2). One commenter noted that the systems covered by proposed Rules 1000(b)(1) and (b)(2) are very complex and a first draft of the required policies and procedures would take far more than the estimated number of hours to complete and keep up-to-date.
                        <SU>1415</SU>
                        <FTREF/>
                         With respect to proposed Rule 1000(b)(2), this commenter stated that the breadth of the rule is extremely comprehensive because it requires policies and procedures that are designed to ensure that SCI systems “comply with the federal securities laws and rules and regulations thereunder” and operate “in the manner intended.” 
                        <SU>1416</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1415</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 31-32, 34. According to this commenter, the implementation of its current information security policy framework and related standards took approximately 18 months and over 1600 work hours to put in place. 
                            <E T="03">See id.</E>
                             This commenter noted that proposed Rule 1000(b)(1) would be far more labor and resource intensive because security is just one of the proposed seven areas of policy and standards development this new rule would require. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1416</SU>
                             
                            <E T="03">See id.</E>
                             at 34.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter noted that the hour burdens did not take into account the appropriate level of management review in connection with the development of the policies and procedures.
                        <SU>1417</SU>
                        <FTREF/>
                         This commenter also noted that policies and procedures developed to achieve compliance with Regulation SCI can potentially impact other areas of the SCI entity and other SCI entities, and therefore an SCI entity would broadly review the policies and procedures to ensure that they do not conflict with other policies, procedures, practices, and processes and revise the policies and procedures accordingly.
                        <SU>1418</SU>
                        <FTREF/>
                         Therefore, this commenter argued that the Commission did not include adequate estimates for the substantial amount of time required by senior management and others in the organization, as well as the persons identified in the SCI Proposal, in: Understanding the breadth and depth of the requirements established by proposed Regulation SCI; determining which systems of the SCI entity fall into the various categories of systems described in proposed Regulation SCI; assessing, growing and potentially reorganizing large portions of the SCI entity's workforce to align with the requirements of proposed Regulation SCI; and establishing and conducting extensive training curriculum to ensure appropriate personnel fully understand their new or changed duties; and any number of other collateral effects of the new requirements.
                        <SU>1419</SU>
                        <FTREF/>
                         This commenter suggested that a more accurate estimate of the paperwork burden from proposed Rule 1000(b)(1) would be three to four times the estimate in the SCI Proposal, and the allocation of the burden hours should be weighted more heavily toward more senior staff of the organization.
                        <SU>1420</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1417</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 28-29. This commenter stated that the Commission placed too much reliance on its experience with the ARP Inspection Program, which was “a voluntary program that did not create potential legal liabilities for non-compliance, and may not take into account the heightened need for high-level supervision that a rule-based requirement would entail.” 
                            <E T="03">See id.</E>
                             at 29. 
                            <E T="03">See also infra</E>
                             Sections IV.B.3.c and VI.C.2.b (discussing the Commission's view on the potential for liability resulting from requirements under Regulation SCI). 
                            <E T="03">See also</E>
                             Omgeo Letter at 32 (noting that the estimate of 210 hours for proposed Rule 1000(b)(1) is unrealistic because the estimate should include not only the drafting of the required policies and procedures, but also their review and approval by senior management) and 35 (noting that the burden estimate of proposed Rule 1000(b)(2) does not reflect the review and direction of senior managers); and CME Letter at 3, n. 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1418</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 29.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1419</SU>
                             
                            <E T="03">See id.</E>
                             at 30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1420</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated that the 50% baseline for SCI entities that are currently under the ARP Inspection Program does not account for the significant expansion of the requirements if the definition of SCI system is construed broadly, and as a result, the burden estimates may be too low.
                        <SU>1421</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1421</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 7.
                        </P>
                    </FTNT>
                    <P>
                        One commenter agreed with the Commission that ongoing paperwork burdens for compliance with proposed Rules 1000(b)(1) and (b)(2) should be lower than the initial burden.
                        <SU>1422</SU>
                        <FTREF/>
                         However, this commenter stated that the estimated ongoing burden is understated, but likely to a lesser extent than with respect to the initial burden.
                        <SU>1423</SU>
                        <FTREF/>
                         Another commenter also noted that, given the complexity of the 
                        <PRTPAGE P="72375"/>
                        underlying systems and the requirements of proposed Rule 1000(b)(1), significantly more effort and time will be required on an ongoing basis to comply with that rule.
                        <SU>1424</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1422</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 31.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1423</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1424</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 32, n. 63.
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that the establishment of the policies and procedures under proposed Rules 1000(b)(1) and (b)(2) would not be conducive to outsourcing, although an SCI entity might incur some cost for outside counsel for consultation purposes.
                        <SU>1425</SU>
                        <FTREF/>
                         On the other hand, another commenter argued that the Commission's burden estimate for proposed Rule 1000(b)(1) “is inaccurate because of its mistaken assumption that SCI entities would not seek guidance from outside consultants and attorneys.” 
                        <SU>1426</SU>
                        <FTREF/>
                         This commenter noted that, given the rates charged by large law firms and consulting firms, an estimate of approximately $100,000 for each exempt clearing agency subject to ARP is more realistic than the $20,000 estimated in the SCI Proposal.
                        <SU>1427</SU>
                        <FTREF/>
                         This commenter similarly noted that the burden estimate for proposed Rule 1000(b)(2) failed to account for the costs associated with using outside counsel or an outside consulting firm to help draft the policies and procedure.
                        <SU>1428</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1425</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 31.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1426</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 32.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1427</SU>
                             
                            <E T="03">See id.</E>
                             at 32, n. 64.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1428</SU>
                             
                            <E T="03">See id.</E>
                             at 35.
                        </P>
                    </FTNT>
                    <P>
                        As discussed in detail above in Sections IV.B.1 and IV.B.2, the Commission is adopting proposed Rules 1000(b)(1) and (b)(2) as Rules 1001(a) and (b), respectively, with certain modifications. As adopted, Rule 1001(a)(1), consistent with the proposal, requires each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. Adopted Rule 1001(a)(2), consistent with the proposal, provides the minimum required elements of such policies and procedures. Some of these elements were modified from the proposal,
                        <SU>1429</SU>
                        <FTREF/>
                         and one adopted element was not included in the proposal.
                        <SU>1430</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1429</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Rules 1001(a)(2)(i) (requiring policies and procedures with respect to the establishment of reasonable current and future “technological infrastructure capacity planning estimates” rather than simply “capacity planning estimates”); 1001(a)(2)(iv) (requiring policies and procedures with respect to “regular reviews and testing, as applicable,” of systems to identify vulnerabilities rather than “regular reviews and testing” of systems); and 1001(a)(2)(v) (requiring policies and procedures with respect to business continuity and disaster recovery plans that are “reasonably designed to achieve” next business day resumption of trading and two-hour resumption of “critical SCI systems” rather than “to ensure” next business day resumption of trading and two-hour resumption of “clearance and settlement services”). 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.B.1.b.ii (discussing modifications from the SCI Proposal in adopted Rule 1001(a)(2)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1430</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(a)(2)(vii) (requiring policies and procedures with respect to monitoring of systems to identify potential SCI events).
                        </P>
                    </FTNT>
                    <P>
                        As compared to proposed Rule 1000(b)(2), which required written policies and procedures reasonably designed to ensure that SCI systems operate “in the manner intended, including in a manner that complies with the federal securities laws,” adopted Rule 1001(b)(1) requires an SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the 
                        <E T="03">Exchange Act</E>
                         and the rules and regulations thereunder, and the entity's rules and governing documents, as applicable.
                        <SU>1431</SU>
                        <FTREF/>
                         Further, rather than adopting the proposed safe harbor for SCI entities, Rule 1001(b)(2) provides the minimum required elements of such policies and procedures. Some of these elements were modified from the proposed safe harbor elements,
                        <SU>1432</SU>
                        <FTREF/>
                         and one element of the proposed safe harbor is not included in Rule 1001(b)(2).
                        <SU>1433</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1431</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.2.a.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1432</SU>
                             
                            <E T="03">See</E>
                             Rules 1001(b)(2)(iii) (requiring policies and procedures with respect to “a plan for assessments” of systems compliance rather than both “ongoing monitoring” and “assessments” of systems compliance) and 1001(b)(2)(iv) (requiring policies and procedures with respect to “a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel” regarding SCI systems rather than “review by regulatory personnel of SCI systems”). 
                            <E T="03">See also supra</E>
                             Section IV.B.2.c (discussing modifications from the SCI Proposal in adopted Rule 1001(b)(2)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1433</SU>
                             
                            <E T="03">See</E>
                             proposed Rule 1000(b)(2)(ii)(A)(
                            <E T="03">2</E>
                            ) (periodic testing of all SCI systems and any changes to such systems after their implementation).
                        </P>
                    </FTNT>
                    <P>
                        With respect to the view of a commenter that the systems covered by proposed Rules 1000(b)(1) and (2) are very complex and that the Commission underestimated the burdens associated with completing and updating the required policies and procedures,
                        <SU>1434</SU>
                        <FTREF/>
                         the Commission believes that most, if not all, SCI entities already have some policies and procedures related to systems capacity, integrity, resiliency, availability, security, and compliance, although such policies and procedures differ in a variety of respects from the requirements under Regulation SCI. Also, in adopting Regulation SCI, the Commission has reduced the burdens for proposed Rules 1000(b)(1) and (2) from the SCI Proposal in a variety of ways, including by, for example: Refining the definition of SCI systems; more explicitly recognizing that some systems pose greater risk than others to the maintenance of fair and orderly markets and imposing obligations that allow for risk-based considerations; and providing that staff guidance on current SCI industry standards be characterized as providing examples of publications describing processes, guidelines, frameworks, or standards for an SCI entity to consider looking to in developing reasonable policies and procedures, rather than strictly as listing industry standards. At the same time, the Commission acknowledges commenters' feedback with respect to the burden of the rules and thus is doubling the burden estimates for the policies and procedures under Rules 1000(b)(1) and (2).
                        <SU>1435</SU>
                        <FTREF/>
                         The Commission notes that, as part of this approach, it doubled the ongoing burden estimates in part in response to comment stating that significantly more effort and time will be required on an ongoing basis to comply with proposed Rule 1000(b)(1).
                        <SU>1436</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1434</SU>
                             
                            <E T="03">See supra</E>
                             note 1415 and accompanying text. As noted above, one commenter stated that its current information security policy framework and related standards took over 1,600 hours to put in place, and that security is just one of the seven areas of policies and standards proposed to be required. 
                            <E T="03">See supra</E>
                             note 1415. The Commission notes that, to the extent an SCI entity already has adequate policies and procedures in place with respect to systems capacity, integrity, resiliency, availability, security, and compliance, Rules 1001(a) and (b) will not impose significant additional paperwork burden on the entity.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1435</SU>
                             In response to the commenter that suggested the initial burden for proposed Rule 1000(b)(1) would be three to four times that estimated in the SCI Proposal, the Commission believes that because it further focused the requirements associated with proposed Rules 1000(b)(1) and (2) in a variety of ways described above, resulting in reduced burden estimates as compared to the SCI Proposal, the commenter's estimate based on the proposal is too high. 
                            <E T="03">See supra</E>
                             note 1420. Based on Commission staff experience, the Commission believes it is more appropriate to double the estimated initial SCI entity staff burden and also add senior management time.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1436</SU>
                             
                            <E T="03">See supra</E>
                             note 1424.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, some commenters noted that the policies and procedures could potentially impact other areas of the SCI entity and other SCI entities, and therefore would result in more burden hours to ensure that the policies and procedures do not conflict with other policies, procedures, practices, and processes, and would require greater involvement of senior management and others in an SCI 
                        <PRTPAGE P="72376"/>
                        entity.
                        <SU>1437</SU>
                        <FTREF/>
                         Similarly, some commenters noted that the establishment, maintenance, and enforcement of the policies and procedures would involve senior management review.
                        <SU>1438</SU>
                        <FTREF/>
                         The Commission agrees with these comments and is adjusting the estimated paperwork burden. Specifically, in the SCI Proposal, the Commission included senior management review as part of its estimated burden hours for Compliance Managers in connection with the policies and procedures requirements under Rules 1001(a) and (b).
                        <SU>1439</SU>
                        <FTREF/>
                         However, in response to comments and based on Commission staff experience, the Commission is additionally including burden estimates for a Director of Compliance (10 hours initially, 5 hours annually) and Chief Compliance Officer 
                        <SU>1440</SU>
                        <FTREF/>
                         (20 hours initially, 10 hours annually) with respect to both Rules 1001(a) and (b).
                        <SU>1441</SU>
                        <FTREF/>
                         The Commission reiterates that these estimates are averages across all SCI entities—some SCI entities may spend more hours in connection with the establishment, maintenance, and enforcement of the policies and procedures than the Commission's estimates, while others may spend less.
                        <SU>1442</SU>
                        <FTREF/>
                         Each SCI entity is required to determine for itself what is required for its staff and senior managers to do in order for the SCI entity to comply with Rules 1001(a) and (b).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1437</SU>
                             
                            <E T="03">See supra</E>
                             notes 1418-1419 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1438</SU>
                             
                            <E T="03">See supra</E>
                             notes 1417, 1419, and 1420 and accompanying text. According to one commenter, the Commission's burden estimates for the policies and procedures did not account for the time required to determine which systems would fall into the various categories of systems. 
                            <E T="03">See supra</E>
                             note 1419 and accompanying text. The Commission disagrees with this view and notes that the burden of identifying various types of systems and events are discussed below in Section V.D.3. In addition, this commenter expressed concern that the Commission's estimates did not account for assessing, growing, and reorganizing an SCI entity's workforce; establishing and conducting training; and other collateral effects of the new requirements. 
                            <E T="03">See supra</E>
                             note 1419 and accompanying text. As discussed throughout this section, the Commission has increased the burden estimates for Rules 1001(a) and (b) in response to comments.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1439</SU>
                             
                            <E T="03">See supra</E>
                             note 1402.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1440</SU>
                             The Chief Compliance Officer burden estimates include the time spent by other senior officers, including Chief Information Officers and Chief Information Security Officers, as appropriate for a particular requirement under Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1441</SU>
                             In estimating the number of burden hours to be spent by senior management, the Commission is not making a distinction between SCI entities that currently participate in the ARP Inspection Program and SCI entities that do not. In contrast to the Commission's estimate with regard to non-senior staff of SCI entities that currently participate in the ARP Inspection Program, who the Commission believes could be subject to less burden in drafting the policies and procedures because these SCI entities already have certain policies and procedures in place, the Commission believes that all senior management, regardless of whether an SCI entity participates in the ARP Inspection Program, would require a similar number of hours to review such policies and procedures to ensure compliance with Regulation SCI.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1442</SU>
                             For example, some SCI entities have more complex systems than others, and current practices of some SCI entities already comply with certain requirements of Regulation SCI to some extent.
                        </P>
                    </FTNT>
                    <P>
                        After considering the views of commenters, and because Rule 1001(a) requires an additional element to be included in the policies and procedures (
                        <E T="03">i.e.,</E>
                         monitoring of systems to identify SCI events), the Commission estimates that an SCI entity that has not previously participated in the ARP Inspection Program would require an average of 534 burden hours initially to develop and draft the policies and procedures required by that rule (except for the policies and procedures for standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data, which is discussed below),
                        <SU>1443</SU>
                        <FTREF/>
                         or 7,476 hours for all such SCI entities.
                        <SU>1444</SU>
                        <FTREF/>
                         The Commission estimates that an SCI entity that has not previously participated in the ARP Inspection Program would require an average of 159 hours annually to review and update such policies and procedures,
                        <SU>1445</SU>
                        <FTREF/>
                         or 2,226 hours for all such SCI entities.
                        <SU>1446</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1443</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 210 hours × 2 = 420 hours. 420 hours ÷ 5 × 6 = 504 hours to establish policies and procedures that contain six elements, as opposed to the five in the SCI Proposal. The 504 burden hours include 192 hours by a Compliance Manager, 192 hours by an Attorney, 60 hours by a Senior Systems Analyst, and 60 hours by an Operations Specialist. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. As noted above, as compared to the proposal, the Commission is estimating an additional 20 hours by a Chief Compliance Officer and 10 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 504 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 534 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1444</SU>
                             As noted above, all of the national securities exchanges (18), national securities associations (1), registered clearing agencies (7), and plan processors (2) currently participate on a voluntary basis in the ARP Inspection Program. In addition, 1 ATS and 1 exempt clearing agency subject to ARP participate in the ARP Inspection Program, for a total of 30 SCI entities that currently participate in the ARP Inspection Program. Therefore, 14 SCI entities do not participate in the ARP Inspection Program. 534 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 7,476 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1445</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 60 hours × 2 = 120 hours. 120 hours ÷ 5 × 6 = 144 hours annually to review and update policies and procedures that contain six elements, as opposed to the five in the SCI Proposal. The 144 burden hours include 57 hours by a Compliance Manager, 57 hours by an Attorney, 15 hours by a Senior Systems Analyst, and 15 hours by an Operations Specialist. As compared to the proposal, the Commission is additionally allocating burden hours to Senior Systems Analysts and Operations Specialists. Also, as noted above, as compared to the proposal, the Commission is estimating an additional 10 hours by a Chief Compliance Officer and 5 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 144 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 159 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1446</SU>
                             159 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 2,226 hours. The Commission believes that the increases in the ongoing burden estimates for Rules 1001(a) and (b) are consistent with the comment that the Commission underestimated the ongoing burdens associated with proposed Rules 1000(b)(1) and (2), but to a lesser extent than with respect to the initial burden. 
                            <E T="03">See supra</E>
                             notes 1423-1424 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to SCI entities that currently participate in the ARP Inspection Program, the Commission continues to believe that a 50% percent baseline for these SCI entities in terms of staff burden hours is appropriate because although these entities already have substantial policies and procedures in place, the rule would require these entities to devote substantial time to review and revise their existing policies and procedures to ensure that they meet all of the rule requirements.
                        <SU>1447</SU>
                        <FTREF/>
                         However, the Commission does not believe that a 50% baseline would be appropriate for these SCI entities in terms of senior management review of the policies and procedures. Specifically, as noted above, Commission believes that, although these entities already have substantial policies and procedures in place, senior management of all SCI entities, regardless of whether an SCI entity currently participates in the ARP Inspection Program, would require a similar number of hours to review the SCI entity's policies and procedures to ensure compliance with the new requirements under Regulation SCI.
                        <SU>1448</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1447</SU>
                             With respect to a commenter's view that the 50% baseline does not account for the significant expansion of the requirements, the Commission notes that the 50% baseline merely indicates the difference between the level of burden imposed on SCI entities that participate in the ARP Inspection Program and SCI entities that do not. 
                            <E T="03">See supra</E>
                             note 1421 and accompanying text. As discussed above, the Commission has increased its burden estimates in response to comments.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1448</SU>
                             
                            <E T="03">See supra</E>
                             note 1441.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72377"/>
                    <P>
                        The Commission estimates that an SCI entity that currently participates in the ARP Inspection Program would require an average of 282 burden hours initially to develop and draft the policies and procedures required by Rule 1001(a) (except for the policies and procedures for standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data),
                        <SU>1449</SU>
                        <FTREF/>
                         or 8,460 hours for all such SCI entities.
                        <SU>1450</SU>
                        <FTREF/>
                         The Commission estimates that an SCI entity that currently participates in the ARP Inspection Program would require an average of 87 hours annually to review and update such policies and procedures,
                        <SU>1451</SU>
                        <FTREF/>
                         or 2,610 hours for all such SCI entities.
                        <SU>1452</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1449</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 105 hours × 2 = 210 hours. 210 hours ÷ 5 × 6 = 252 hours to establish policies and procedures that contain six elements, as opposed to the five in the SCI Proposal. The 252 burden hours include 96 hours by a Compliance Manager, 96 hours by an Attorney, 30 hours by a Senior Systems Analyst, and 30 hours by an Operations Specialist. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. As noted above, as compared to the proposal, the Commission is estimating an additional 20 hours by a Chief Compliance Officer and 10 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 252 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 282 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1450</SU>
                             282 hours × 30 SCI entities that participate in the ARP Inspection Program = 8,460 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1451</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 30 hours × 2 = 60 hours. 60 hours ÷ 5 × 6 = 72 hours to review and update policies and procedures that contain six elements, as opposed to the five in the SCI Proposal. The 72 burden hours include 28 hours by a Compliance Manager, 28 hours by an Attorney, 8 hours by a Senior Systems Analyst, and 8 hours by an Operations Specialist. As compared to the proposal, the Commission is additionally allocating burden hours to Senior Systems Analysts and Operations Specialists. Also, as noted above, as compared to the proposal, the Commission is estimating an additional 10 hours by a Chief Compliance Officer and 5 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 72 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 87 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1452</SU>
                             87 hours × 30 SCI entities that participate in the ARP Inspection Program = 2,610 hours.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the requirement in Rule 1001(a)(2)(vi) for policies and procedures that provide for standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data, the Commission estimates that each SCI entity would spend 160 hours initially,
                        <SU>1453</SU>
                        <FTREF/>
                         or 7,040 hours for all SCI entities.
                        <SU>1454</SU>
                        <FTREF/>
                         The Commission estimates that each SCI entity would spend 145 hours annually,
                        <SU>1455</SU>
                        <FTREF/>
                         or 6,380 hours annually for all SCI entities.
                        <SU>1456</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1453</SU>
                             This estimate includes 130 hours by staff of an SCI entity, as estimated in the SCI Proposal, and 30 hours by senior management. The 130 burden hours include 30 hours by a Compliance Attorney and 100 hours by a Senior Systems Analyst. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. As noted above, as compared to the proposal, the Commission is estimating an additional 20 hours by a Chief Compliance Officer and 10 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 130 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 160 hours. Unlike the burden estimates for complying with the rest of Rule 1001(a), the Commission does not believe it would be appropriate to double its proposed 130 hour staff burden estimate for Rule 1001(a)(2)(vi). Based on Commission staff experience, the Commission believes that these policies and procedures would not be so complex as to result in doubling the proposed burden estimate. The Commission also notes that the burden estimate for Rule 1001(a)(2)(vi) is already significantly higher than the estimated burden for the other individual policies and procedures required under Rule 1001(a)(2). In particular, the Commission estimates 160 hours for this one provision and 534 hours in total for the six other provisions of Rule 1001(a)(2) for non-ARP participants (which results in approximately 89 hours for each of those six other provisions).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1454</SU>
                             160 hours × 44 SCI entities = 7,040 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1455</SU>
                             This estimate includes 130 hours by staff of an SCI entity, as estimated in the SCI Proposal, and 15 hours by senior management. The 130 burden hours include 30 hours by a Compliance Attorney and 100 hours by a Senior Systems Analyst. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. 130 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 145 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1456</SU>
                             145 hours × 44 SCI entities = 6,380 hours.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter argued that, given the rates charged by large law firms and consulting firms, an estimate of $100,000 is more appropriate for the cost of outsourcing under proposed Rule 1000(b)(1).
                        <SU>1457</SU>
                        <FTREF/>
                         After considering the view of this commenter and because the Commission is increasing its estimated burden hours for compliance with Rule 1001(a), the Commission is similarly increasing its estimate of the outsourcing cost for complying with Rule 1001(a). In particular, because the Commission doubled the non-senior staff burden estimate for Rule 1001(a) in response to comments that the Commission underestimated the burden in the proposal, the Commission believes it is appropriate to similarly double its estimate of the outsourcing cost for complying with Rule 1001(a). As noted above in the context of the burden estimate for Rule 1001(a), the Commission believes that, by doubling its outsourcing cost estimate, the Commission has incorporated the views of commenters that the Commission underestimated the burden, and at the same time accounted for changes to the proposal that reduce the burden from the SCI Proposal. Further, the Commission acknowledges that some SCI entities may have more complex systems and policies and procedures, may outsource more of the work associated with the policies and procedures,
                        <SU>1458</SU>
                        <FTREF/>
                         or may outsource the work to more expensive law firms and consulting firms than others. Therefore, the Commission believes that while some SCI entities may incur more outsourcing cost than the Commission's estimate, other SCI entities may incur less than the Commission's estimate. The Commission does not believe that a commenter's $100,000 estimate is more appropriate given that there will be differences among SCI entities in the extent of outsourcing and in the rates of outside firms.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1457</SU>
                             
                            <E T="03">See supra</E>
                             note 1427 and accompanying text. This commenter also argued that the Commission mistakenly assumed that SCI entities would not seek guidance from outside consultants or attorneys. 
                            <E T="03">See supra</E>
                             note 1426 and accompanying text. However, the Commission did account for outsourcing cost in the SCI Proposal and does so here, as well.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1458</SU>
                             For example, smaller SCI entities may not have the same level of in-house expertise as larger SCI entities.
                        </P>
                    </FTNT>
                    <P>
                        Because Rule 1001(a) requires an additional element to be included in the policies and procedures as compared to proposed Rule 1000(b)(1) (
                        <E T="03">i.e.,</E>
                         monitoring of systems to identify SCI events), the Commission now estimates that on average, each SCI entity would seek outside legal and/or consulting services in the initial preparation of the policies and procedures at a cost of approximately $47,000,
                        <SU>1459</SU>
                        <FTREF/>
                         or $2,068,000 for all SCI entities.
                        <SU>1460</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1459</SU>
                             As noted above, the Commission is doubling its estimate of the outsourcing cost for SCI entities. $20,000 × 2 = $40,000. The Commission is also revising this cost estimate to reflect that Rule 1001(a) requires seven specific elements to be included in the policies and procedures, as opposed to the six in the proposed rule. $40,000 ÷ 6 × 7 = $46,667.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1460</SU>
                             $47,000 × 44 SCI entities = $2,068,000.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the view of a commenter that the Commission underestimated the paperwork burden under proposed Rule 1000(b)(2) because that rule is extremely extensive,
                        <SU>1461</SU>
                        <FTREF/>
                         the Commission notes that, as adopted, Rule 1001(b) requires policies and procedures to be reasonably designed to ensure, in part, that SCI systems “operate in a manner that complies with 
                        <PRTPAGE P="72378"/>
                        the Act and the rules and regulations thereunder.” As adopted, this rule no longer refers to compliance with “the federal securities laws and rules and regulations thereunder” and operation “in the manner intended.” Nevertheless, as noted above, after considering the views of commenters that the Commission underestimated the paperwork burden under proposed Rule 1000(b)(2), the Commission is doubling its estimates from the proposal (which were focused on the burden for SCI entity staff), and is increasing its estimates to account for senior management review of the policies and procedures.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1461</SU>
                             
                            <E T="03">See supra</E>
                             note 1416.
                        </P>
                    </FTNT>
                    <P>
                        The Commission now estimates that each SCI entity would spend 270 hours initially to design the systems compliance policies and procedures,
                        <SU>1462</SU>
                        <FTREF/>
                         or 11,880 hours for all SCI entities.
                        <SU>1463</SU>
                        <FTREF/>
                         The Commission estimates that each SCI SRO would spend approximately 175 hours annually to review and update such policies and procedures,
                        <SU>1464</SU>
                        <FTREF/>
                         or 4,725 hours for all SCI SROs.
                        <SU>1465</SU>
                        <FTREF/>
                         The Commission estimates that each SCI entity that is not an SRO would spend approximately 95 hours to review and update such policies and procedures,
                        <SU>1466</SU>
                        <FTREF/>
                         or 1,615 hours for all such SCI entities.
                        <SU>1467</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1462</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 180 hours × 2 = 360 hours. 360 hours ÷ 6 × 4 = 240 hours to establish policies and procedures that contain four elements at a minimum, as opposed to the six in the SCI Proposal. The 240 burden hours include 40 hours by a Compliance Attorney and 200 hours by a Senior Systems Analyst. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. As noted above, as compared to the proposal, the Commission is estimating an additional 20 hours by a Chief Compliance Officer and 10 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 240 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 270 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1463</SU>
                             270 hours × 44 SCI entities = 11,880 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1464</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 120 hours × 2 = 240 hours. 240 hours ÷ 6 × 4 = 160 hours to review and update policies and procedures that contain four elements at a minimum, as opposed to the six in the SCI Proposal. The 160 burden hours include 26 hours by a Compliance Attorney and 134 hours by a Senior Systems Analyst. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. As noted above, as compared to the proposal, the Commission is estimating an additional 10 hours by a Chief Compliance Officer and 5 hours by a Director of Compliance to reflect the views of commenters that compliance with the proposed policies and procedures requirements would require greater senior management involvement. 
                            <E T="03">See supra</E>
                             notes 1440-1441 and accompanying text. 160 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 175 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1465</SU>
                             175 hours × 27 SCI SROs = 4,725 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1466</SU>
                             As noted above, the Commission is doubling its estimate of the burden for staff of SCI entities. 60 hours × 2 = 120 hours. 120 hours ÷ 6 × 4 = 80 hours to review and update policies and procedures that contain four elements at a minimum, as opposed to the six in the SCI Proposal. The 80 burden hours include 14 hours by a Compliance Attorney and 66 hours by a Senior Systems Analyst. This burden hour allocation is based on the allocation in the SCI Proposal. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18146. 80 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 95 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1467</SU>
                             95 hours × 17 non-SRO SCI entities = 1,615 hours.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, similar to the burden estimates for proposed Rule 1000(b)(1), one commenter argued that the Commission underestimated the outsourcing cost under proposed Rule 1000(b)(2).
                        <SU>1468</SU>
                        <FTREF/>
                         Similar to the discussion above related to Rule 1001(a),
                        <SU>1469</SU>
                        <FTREF/>
                         after considering the view of this commenter and because the Commission is increasing its estimated burden hours for compliance with Rule 1001(b), the Commission is doubling its estimate of the outsourcing cost for complying with Rule 1001(b). The Commission now estimates that on average, each SCI entity would seek outside legal and/or consulting services in the initial preparation of the policies and procedures at a cost of approximately $27,000,
                        <SU>1470</SU>
                        <FTREF/>
                         or $1,188,000 for all SCI entities.
                        <SU>1471</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1468</SU>
                             
                            <E T="03">See supra</E>
                             note 1428 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1469</SU>
                             
                            <E T="03">See supra</E>
                             notes 1457-1458 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1470</SU>
                             As noted above, the Commission is doubling its estimate of the outsourcing cost for SCI entities. $20,000 × 2 = $40,000. The Commission is also revising this cost estimate to reflect that Rule 1001(b) will result in the inclusion of at least four elements in the policies and procedures, as opposed to the six in the proposed rule. $40,000 ÷ 6 × 4 = $26,667.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1471</SU>
                             $27,000 × 44 SCI entities = $1,188,000.
                        </P>
                    </FTNT>
                    <P>Adopted Rules 1001(a)(3) and (b)(3) explicitly require each SCI entity to periodically review the effectiveness of the policies and procedures required by Rules 1001(a) and (b), respectively, and to take prompt action to remedy deficiencies in such policies and procedures. The Commission notes that the paperwork burden related to the review of the policies and procedures, and remedying deficiencies in policies and procedures, is included in the estimated annual ongoing burden of Rules 1001(a) and (b).</P>
                    <P>
                        Rule 1001(c)(1), which was not included in the proposal, requires each SCI entity to establish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel,
                        <SU>1472</SU>
                        <FTREF/>
                         and escalation procedures to quickly inform responsible SCI personnel of potential SCI events. Like adopted Rules 1001(a)(3) and (b)(3), Rule 1001(c) requires each SCI entity periodically to review the effectiveness of these policies and procedures and to take prompt action to remedy deficiencies in policies and procedures. The Commission estimates that each SCI entity would require 114 hours initially to establish the criteria for identifying responsible SCI personnel and the escalation procedures,
                        <SU>1473</SU>
                        <FTREF/>
                         or 5,016 hours for all SCI entities.
                        <SU>1474</SU>
                        <FTREF/>
                         The Commission also estimates that each SCI entities would require 39 hours annually to review and update the criteria and the escalation procedures,
                        <SU>1475</SU>
                        <FTREF/>
                         or 1,716 hours for all 
                        <PRTPAGE P="72379"/>
                        SCI entities.
                        <SU>1476</SU>
                        <FTREF/>
                         The Commission believes that SCI entities will internally establish and maintain the policies and procedures required by Rule 1001(c) because these policies and procedures relate to internal personnel designations and internal processes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1472</SU>
                             The paperwork burden associated with the documentation of responsible SCI personnel is included in the Commission's estimate of the recordkeeping burden, as discussed in Section V.D.4 below.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1473</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and Rule 1001(c) both require policies and procedures or processes. Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the establishment of six policies and procedures at a minimum and Rule 1001(c) requires the establishment of two policies and procedures, the Commission estimates that the initial burden to draft the policies and procedures required by Rule 1001(c) is one-third of the initial burden to draft the policies and procedures required by Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). Further, the Commission believes that, even though Rule 1001(c) will impose paperwork burdens on SCI entities, most, if not all, SCI entities, regardless of whether they participate in the ARP Inspection Program, already have some processes in place for the designation of persons responsible for particular systems and escalation procedures. Therefore, the Commission believes it is appropriate to assume a 50% baseline for all SCI entities (as compared to the burden estimate for Rule 1001(a) for SCI entities that do not participate in the ARP Inspection Program) in terms of the staff burden for compliance with Rule 1001(c). 252 hours ÷ 3 = 84 hours. The 84 burden hours include 32 hours by a Compliance Manager, 32 hours by an Attorney, 10 hours by a Senior Systems Analyst, and 10 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1443. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures required by Rule 1001(c). 84 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 114 hours. 
                        </P>
                        <P>
                            The Commission notes that, in the SCI Proposal, it also estimated the burden hours for other policies and procedures based on its burden estimate under proposed Rule 1000(b)(1). 
                            <E T="03">See, e.g.,</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18152, n. 442. One commenter stated that it was appropriate to base the burden estimate for proposed Rule 1000(b)(3), which would likely result in SCI entities revising their policies, on the burden estimate under proposed Rule 1000(b)(1). 
                            <E T="03">See infra</E>
                             note 1700 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1474</SU>
                             114 hours × 44 SCI entities = 5,016 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1475</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 
                            <PRTPAGE/>
                            1001(a) and Rule 1001(c) both require policies and procedures or processes. Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the maintenance of six policies and procedures at a minimum and Rule 1001(c) requires the maintenance of two policies and procedures, the Commission estimates that the ongoing staff burden under Rule 1001(c) is one-third of the ongoing staff burden under Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). As noted above, the Commission believes it is appropriate to assume a 50% baseline for all SCI entities in terms of the staff burden for compliance with Rule 1001(c). 72 hours ÷ 3 = 24 hours. The 24 burden hours include 9.5 hours by a Compliance Manager, 9.5 hours by an Attorney, 2.5 hours by a Senior Systems Analyst, and 2.5 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1445. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures required by Rule 1001(c). 24 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 39 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1476</SU>
                             39 hours × 44 SCI entities = 1,716 hours.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Mandate Participation in Certain Testing</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity (other than plan processors) would spend approximately 130 hours initially to meet the requirements of proposed Rules 1000(b)(9)(i) and (ii) (
                        <E T="03">i.e.,</E>
                         the requirement to mandate participation by designated members or participants in testing and the requirement that an SCI entity coordinate required testing with other SCI entities).
                        <SU>1477</SU>
                        <FTREF/>
                         The 130-hour estimate included 35 hours to write a proposed rule, or revise a membership/subscriber agreement or participant agreement to establish the participation requirement for designated members or participants.
                        <SU>1478</SU>
                        <FTREF/>
                         It also included 95 hours of follow-up work (
                        <E T="03">e.g.,</E>
                         notice and schedule coordination) to ensure implementation.
                        <SU>1479</SU>
                        <FTREF/>
                         The Commission estimated that each SCI entity (other than plan processors) would spend approximately 95 hours annually to comply with proposed Rules 1000(b)(9)(i) and (ii).
                        <SU>1480</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1477</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18147.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1478</SU>
                             
                            <E T="03">See id.</E>
                             The 35 burden hours included 10 hours by a Compliance Manager, 15 hours by an Attorney, and 10 hours by a Compliance Clerk. 
                            <E T="03">See id.</E>
                             In establishing this estimate, the Commission considered its estimate of the burden for an SRO to file an average proposed rule change under Rule 19b-4. 
                            <E T="03">See id.</E>
                             at 18147, n. 389.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1479</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18147. The 95 burden hours included 10 hours by a Compliance Manager, 15 hours by an Attorney, and 70 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1480</SU>
                             
                            <E T="03">See id.</E>
                             The 95 burden hours included 10 hours by a Compliance Manager, 15 hours by an Attorney, and 70 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                             The Commission noted that, although the initial burden included 35 hours to write a proposed rule, revise an agreement, or amend an SCI Plan, the Commission did not believe the 35-hour burden would be applicable on an ongoing basis. 
                            <E T="03">See id.</E>
                             at 18147, n. 393.
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity (other than plan processors) would spend approximately 35 hours initially to meet the requirements of proposed Rule 1000(b)(9)(iii) (
                        <E T="03">i.e.,</E>
                         establishing standards for designating members or participants and filing such standards with the Commission, and determining, compiling, and submitting the list of designated members or participants).
                        <SU>1481</SU>
                        <FTREF/>
                         The Commission estimated that each SCI entity (other than plan processors) would spend approximately 3 hours annually to comply with proposed Rule 1000(b)(9)(iii) (
                        <E T="03">i.e.,</E>
                         to review the designation standards to ensure that they remain up-to-date and to prepare any necessary amendments, to review the list of designated members or participants, and to update prior Commission notifications with respect to standards for designation and the list of designees).
                        <SU>1482</SU>
                        <FTREF/>
                         The Commission also estimated that all SCI entities, other than plan processors, would conduct the work associated with proposed Rule 1000(b)(9) internally.
                        <SU>1483</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1481</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18148. The 35 burden hours included 10 hours by a Compliance Manager, 15 hours by an Attorney, and 10 hours by a Compliance Clerk. 
                            <E T="03">See id.</E>
                             In establishing this estimate, the Commission considered its estimate of the burden for an SRO to file an average proposed rule filing under Rule 19b-4. 
                            <E T="03">See id.</E>
                             at 18148, n. 397.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1482</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18148. The 3 burden hours included 1.5 hours by a Compliance Manager and 1.5 hours by an Attorney. 
                            <E T="03">See id.</E>
                             In establishing this estimate, the Commission has considered its estimate of the burden for an SRO to amend a Form 19b-4 rule filing. 
                            <E T="03">See id.</E>
                             at 18148, n. 401.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1483</SU>
                             
                            <E T="03">See id.</E>
                             at 18145.
                        </P>
                    </FTNT>
                    <P>
                        For plan processors, the Commission estimated that proposed Rules 1000(b)(9)(i) and (ii) would carry an initial cost of $52,000 per plan processor 
                        <SU>1484</SU>
                        <FTREF/>
                         and an annual cost of $38,000 per plan processor.
                        <SU>1485</SU>
                        <FTREF/>
                         The Commission also estimated that proposed Rule 1000(b)(9)(iii) would carry an initial cost of $14,000 per plan processor 
                        <SU>1486</SU>
                        <FTREF/>
                         and an annual cost of $1,200 per plan processor.
                        <SU>1487</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1484</SU>
                             130 hours × $400 per hour for outside legal service = $52,000. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18147.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1485</SU>
                             95 hours × $400 per hour for outside legal service = $38,000. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1486</SU>
                             35 hours × $400 per hour for outside legal service = $14,000. 
                            <E T="03">See id.</E>
                             at 18148.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1487</SU>
                             3 hours × $400 per hour for outside legal service = $1,200. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        With respect to the Commission's estimate of the burdens under proposed Rule 1000(b)(9), one commenter noted that the estimate was effectively limited to ministerial tasks of producing a rule filing and of undertaking follow-up work in connection with implementation and does not take into account significant activities relating to the SRO rule change process (
                        <E T="03">e.g.,</E>
                         board or directors briefing and deliberation, potential notice for comment, responses to comment letters received on such notice, responses to comment letters received by the Commission on a rule filing, etc.) and understates the activities necessary to implement testing with industry participants.
                        <SU>1488</SU>
                        <FTREF/>
                         Another commenter argued that it has contractual relationships with thousands of clients, and contract negotiations always require a great deal of time and commitment from its legal personnel.
                        <SU>1489</SU>
                        <FTREF/>
                         This commenter also noted that while a certain significant percentage of its clients may sign the contracts without any negotiation, many do not.
                        <SU>1490</SU>
                        <FTREF/>
                         According to this commenter, the requirements under proposed Rule 1000(b)(9) would create for it many thousands of burden hours because it would require the commenter to re-negotiate contracts with “the many thousands of clients it has already signed up.” 
                        <SU>1491</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1488</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 38.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1489</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 46. This commenter noted that its relationships with clients are often based on negotiated agreements and that clients do not automatically agree to all terms stated in the standard contract. 
                            <E T="03">See id.</E>
                             at 45.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1490</SU>
                             
                            <E T="03">See id.</E>
                             at 46.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1491</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that the requirements under proposed Rule 1000(b)(9) would not be conducive to outsourcing.
                        <SU>1492</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1492</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 38.
                        </P>
                    </FTNT>
                    <P>
                        As discussed in detail above in Section IV.B.6, the Commission is adopting proposed Rule 1000(b)(9) as Rule 1004, with certain modifications. Rule 1004 requires each SCI entity to establish standards for the designation of certain members or participants for business continuity and disaster recovery plan testing, to designate members or participants in accordance with these standards, to require participation by designated members or participants in such testing at least annually, and to coordinate such testing on an industry- or sector-wide basis with other SCI entities. However, 
                        <PRTPAGE P="72380"/>
                        adopted Rule 1004 does not require an SCI entity to notify and update the Commission of its designated members or participants and its standards for designation on Form SCI, as proposed.
                    </P>
                    <P>
                        Considering commenters' view that the Commission had underestimated the burden hours associated with proposed Rule 1000(b)(9), the Commission now estimates that the requirements under Rules 1004(a) (
                        <E T="03">i.e.,</E>
                         establishment of standards for the designation of members and participants) and (c) (
                        <E T="03">i.e.,</E>
                         coordination of testing on an industry- or sector-wide basis) will initially require 360 hours for each SCI entity that is not a plan processor (
                        <E T="03">e.g.,</E>
                         establishing designation criteria by writing a proposed rule; revising a membership/subscriber agreement or participant agreement; providing notice to members or participants; scheduling the coordinated testing),
                        <SU>1493</SU>
                        <FTREF/>
                         or 15,120 hours for all such SCI entities.
                        <SU>1494</SU>
                        <FTREF/>
                         Further, the Commission estimates that the requirements under Rules 1004(a) and (c) will require 135 hours annually for each SCI entity that is not a plan processor,
                        <SU>1495</SU>
                        <FTREF/>
                         or 5,670 hours for all such SCI entities.
                        <SU>1496</SU>
                        <FTREF/>
                         The Commission continues to believe that SCI entities (other than plan processors) would handle internally the work associated with the requirements of Rule 1004.
                        <SU>1497</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1493</SU>
                             This estimate includes 90 hours to comply with Rule 1004(a) and 270 hours to comply with Rule 1004(c). The 90 hours include 30 hours by an Attorney, 20 hours by a Compliance Manager, 10 hours by an Assistant General Counsel, 6 hours by a Chief Compliance Officer, 4 hours by a Director of Compliance, and 20 hours by a Senior Operations Manager. The Commission is substantially increasing the estimated burden over that estimated for proposed Rule 1000(b)(9)(i), and is estimating an additional 10 hours by an Assistant General Counsel, 6 hours by a Chief Compliance Officer, 4 hours by a Director of Compliance, and 20 hours by a Senior Operations Manager to reflect senior management review of the standards for designation. With respect to the comment that the estimates in the proposal did not take into account significant activities relating to the SRO rule change process, the Commission notes that the paperwork burden associated with SRO rule filings are included as part of the burden associated with Rule 19b-4. 
                            <E T="03">See supra</E>
                             note 1488 and accompanying text. The 270 hours include 30 hours by an Attorney, 20 hours by a Compliance Manager, 10 hours by an Assistant General Counsel, 20 hours by a Chief Compliance Officer, 10 hours by a Director of Compliance, 140 hours by an Operations Specialist, and 40 hours by a Senior Operations Manager. The Commission is substantially increasing the estimated burden over that estimated for proposed Rule 1000(b)(9)(ii), and is estimating an additional 10 hours by an Assistant General Counsel, 20 hours by a Chief Compliance Officer, 10 hours by a Director of Compliance, and 40 hours by a Senior Operations Manager, in response to the view of a commenter that the estimates in the SCI Proposal underestimated the activities necessary to implement testing with industry participants. 
                            <E T="03">See supra</E>
                             note 1488 and accompanying text. The estimate of 360 hours includes the burden for designating members or participants for testing, as required by Rule 1004(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1494</SU>
                             360 hours × 42 SCI entities other than plan processors = 15,120 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1495</SU>
                             As noted in the SCI Proposal, the Commission does not believe that there would be significant annual burden under Rule 1004(a), as the Commission believes that the designation standards will likely not change substantially on an annual basis. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18147, n. 393. The 135 hours include 15 hours by an Attorney, 10 hours by a Compliance Manager, 5 hours by an Assistant General Counsel, 10 hours by a Chief Compliance Officer, 5 hours by a Director of Compliance, 70 hours by an Operations Specialist, and 20 hours by a Senior Operations Manager. As compared to the estimated ongoing burden for proposed Rule 1000(b)(9)(ii), the Commission is estimating an additional 5 hours by an Assistant General Counsel, 10 hours by a Chief Compliance Officer, 5 hours by a Director of Compliance, and 20 hours by a Senior Operations Manager, consistent with the Commission's estimate for the initial burden for Rule 1004.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1496</SU>
                             135 hours × 42 SCI entities other than plan processors = 5,670 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1497</SU>
                             
                            <E T="03">See supra</E>
                             note 1492 (discussing a commenter's view that the requirements under proposed Rule 1000(b)(9) would not be conducive to outsourcing).
                        </P>
                    </FTNT>
                    <P>
                        With respect to a commenter's statement that it has contractual relationships with thousands of clients and that proposed Rule 1000(b)(9) would create many thousands of burden hours,
                        <SU>1498</SU>
                        <FTREF/>
                         the Commission notes that adoption of a more focused designation requirement is likely to result in a smaller number of SCI entity members or participants being designated for participation in testing as compared to the SCI Proposal. Specifically, as adopted, Rule 1004(a) requires an SCI entity to designate “members or participants that the SCI entity reasonably determines are, taken as a whole, the minimum necessary for the maintenance of fair and orderly markets” in the event of the activation of the business continuity and disaster recovery plans. On the other hand, proposed Rule 1000(b)(9) required participation by members or participants the SCI entity deemed necessary “for the maintenance of fair and orderly markets in the event of the activation of its business continuity and disaster recovery plans.” 
                        <SU>1499</SU>
                        <FTREF/>
                         The Commission believes that SCI entities have an incentive to limit the imposition of the cost and burden associated with testing to the minimum necessary to comply with the rule, and it also believes that, given the option, most SCI entities would, in the exercise of reasonable discretion, prefer to designate few members or participants to participate in testing, than to designate more. Thus, even if an SCI entity individually negotiates contract modifications with certain designated members or participants, the Commission believes that the burden would be substantially less than suggested by the commenter.
                        <SU>1500</SU>
                        <FTREF/>
                         Moreover, as noted above, taking into account commenters' view that the Commission underestimated the burden for proposed Rule 1000(b)(9), the Commission increased its estimate for initial burden hours from 130 hours for the proposed rule to 360 hours for adopted Rule 1004. The average burden estimate associated with Rule 1004 applies to SCI entities that would need to negotiate contract modifications with members or participants.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1498</SU>
                             
                            <E T="03">See supra</E>
                             notes 1489-1491 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1499</SU>
                             The Commission notes that, because Rule 1004 would not require all members or participants of an SCI entity to participate in business continuity and disaster recovery plan testing, Rule 1004 will not affect all of an SCI entity's contractual relationships with clients or members or participants. Further, the Commission notes that its estimated burden for compliance with Rule 1004 is intended to reflect the average burden for all SCI entities (other than plan processors).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1500</SU>
                             As discussed in the Economic Analysis, the Commission estimates that each SCI entity would designate an average of 40 members or participants to participate in the necessary testing. 
                            <E T="03">See infra</E>
                             note 2065. Therefore, an SCI entity will not be required to re-negotiate contracts with “the many thousands of clients it has already signed up.” 
                            <E T="03">See supra</E>
                             note 1491 and accompanying text. Moreover, this commenter recognized that a significant percentage of its clients may sign the contracts without any negotiation. 
                            <E T="03">See supra</E>
                             note 1491 and accompanying text. As a result, the Commission does not expect that an SCI entity will need to negotiate with all of the estimated 40 members or participants.
                        </P>
                    </FTNT>
                    <P>
                        Based on its experience with plan processors, the Commission continues to believe that plan processors will outsource the work related to compliance with Rule 1004. The Commission estimates that Rule 1004 will carry an initial cost of $144,000 per plan processor,
                        <SU>1501</SU>
                        <FTREF/>
                         or $288,000 for all plan processors.
                        <SU>1502</SU>
                        <FTREF/>
                         The Commission estimates that Rule 1004 will carry an annual cost of $54,000 per plan processor,
                        <SU>1503</SU>
                        <FTREF/>
                         or $108,000 for all plan processors.
                        <SU>1504</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1501</SU>
                             360 hours × $400 per hour for outside legal service = $144,000. This is based on an estimated $400 per hour cost for outside legal services. This is the same estimate used by the Commission for these services in the “Exemptions for Advisers to Venture Capital Funds, Private Fund Advisers with Less Than $150 Million Under Management, and Foreign Private Advisers” final rule: SEC Release No. IA-3222 (June 22, 2011); 76 FR 39646 (July 6, 2011).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1502</SU>
                             $144,000 × 2 plan processors = $288,000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1503</SU>
                             135 hours × $400 per hour for outside legal service = $54,000. The Commission increased from its estimate in the proposal the estimated hours for the outsourced work for plan processors to be equivalent to the number of burden hours it estimated for an SCI entity that is not a plan processor (
                            <E T="03">i.e.,</E>
                             increasing the initial burden estimate from 130 hours to 360 hours and the annual burden estimate from 95 to 135 hours).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1504</SU>
                             $54,000 × 2 plan processors = $108,000.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Notification, Dissemination, and Reporting Requirements for SCI Entities</HD>
                    <P>
                        The rules under Regulation SCI that would require an SCI entity to notify the 
                        <PRTPAGE P="72381"/>
                        Commission of SCI events, disseminate information regarding certain SCI events, and notify the Commission of certain systems changes are discussed more fully in Sections IV.B.3.c, IV.B.3.d, and IV.B.4 above.
                    </P>
                    <HD SOURCE="HD3">a. Commission Notification of SCI Events</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity would experience an average of 40 immediate notification SCI events 
                        <SU>1505</SU>
                        <FTREF/>
                         per year (
                        <E T="03">i.e.,</E>
                         40 notifications under proposed Rule 1000(b)(4)(i)), and that one-fourth of the notifications under proposed Rule 1000(b)(4)(i) would be in writing (
                        <E T="03">i.e.,</E>
                         10 written notifications and 30 oral notifications).
                        <SU>1506</SU>
                        <FTREF/>
                         The Commission estimated that each written notification would require 0.5 hours to prepare and submit to the Commission.
                        <SU>1507</SU>
                        <FTREF/>
                         The Commission also estimated that each SCI entity would experience an average of 65 SCI events each year and therefore would submit 65 Commission notifications each year under proposed Rule 1000(b)(4)(ii).
                        <SU>1508</SU>
                        <FTREF/>
                         The Commission estimated that each such notification would require an average of 20 burden hours.
                        <SU>1509</SU>
                        <FTREF/>
                         In addition, the Commission estimated that on average, each SCI entity would submit 5 updates per year under proposed Rule 1000(b)(4)(iii), and that each update would require an average of 3 burden hours.
                        <SU>1510</SU>
                        <FTREF/>
                         Finally, the Commission estimated that SCI entities would handle internally the work associated with the notification requirement under proposed Rule 1000(b)(4).
                        <SU>1511</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1505</SU>
                             Immediate notification SCI events included systems disruptions that an SCI entity reasonably estimated would have a material impact on its operations or on market participants, all systems compliance issues, and all systems intrusions.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1506</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18148.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1507</SU>
                             
                            <E T="03">See id.</E>
                             The 0.5 burden hour would be spent by an Attorney. 
                            <E T="03">See id.</E>
                             at 18149.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1508</SU>
                             
                            <E T="03">See id.</E>
                             at 18148-49.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1509</SU>
                             
                            <E T="03">See id.</E>
                             at 18149. The 20 burden hours included 10 hours by an Attorney and 10 hours by a Compliance Manager. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. In determining this estimate, the Commission also considered its estimate of the burden to complete a Form 19b-4 filing, although the Commission noted that, unlike a Form 19b-4 filing, the information contained in Form SCI would only be factual. 
                            <E T="03">See id.</E>
                             at 18149, n. 410.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1510</SU>
                             
                            <E T="03">See id.</E>
                             at 18149. The 3 burden hours included 1.5 hours by an Attorney and 1.5 hours by a Compliance Manager. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. In determining this estimate, the Commission also considered its estimate of the burden for an SRO to amend a Form 19b-4. 
                            <E T="03">See id.</E>
                             at 18149, n. 410.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1511</SU>
                             
                            <E T="03">See id.</E>
                             at 18148-49, n. 408, n. 411, and n. 413.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters stated that the Commission underestimated the number of SCI events.
                        <SU>1512</SU>
                        <FTREF/>
                         One commenter stated that, because the proposed definition of SCI event was broad and would include minor or immaterial events, it is likely that each SCI entity could have hundreds if not thousands of SCI events on an annual basis.
                        <SU>1513</SU>
                        <FTREF/>
                         Similarly, another commenter stated that each SCI entity could be required to report hundreds of systems disruption events each year, although the vast majority of such events would be virtually unnoticed by market participants.
                        <SU>1514</SU>
                        <FTREF/>
                         Another commenter stated that, based on its best reading of the more expansive definitions of disruptions and intrusions, a more accurate estimate could be between 200 to 500 events per year per exchange.
                        <SU>1515</SU>
                        <FTREF/>
                         Several commenters noted that the Commission significantly underestimated the number of updates that would be required under Rule 1000(b)(4)(iii).
                        <SU>1516</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1512</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 35; BATS Letter at 11; Joint SRO Letter at 18; OTC Markets Letter at 6; and NYSE Letter at 18. However, commenters did not specify estimates for the number of systems compliance issues an SCI entity would experience each year.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1513</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 35. According to this commenter, many of these SCI events would require written notification even though the vast majority of them would be minor and immaterial. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1514</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 11. This commenter also noted that the Commission did not break down the anticipated reportable events into systems disruptions, systems intrusions, and systems compliance issues. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1515</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 18. 
                            <E T="03">See also</E>
                             FINRA Letter at 18, n. 32 (stating that depending on the interpretation of what constitutes a systems intrusion, it would be required to notify the Commission either: Several times a day under the broadest interpretation; three or four times per month under a narrower interpretation; or one or two times per year if limited to intrusions where there is a material impact).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1516</SU>
                             
                            <E T="03">See</E>
                             Joint SRO Letter at 19; NYSE Letter at 24 (noting that it is not realistic, with respect to over 90% of SCI events, that all required activity is complete and reportable on Form SCI within 24 hours). 
                            <E T="03">See also</E>
                             FINRA Letter at 19 (noting that some complex outages can take up to several days to triage, isolate, and begin to resolve, and that based on its experience with ARP outage reporting, it can take several days to confirm the root cause of an outage and even longer to determine the appropriate resolution and how long it will take to complete).
                        </P>
                    </FTNT>
                    <P>
                        With respect to the Commission's estimate of the burden for Commission notification generally, one commenter noted that preparation of Form SCI will take a fair amount of time, not just to compile information about the SCI event, but also to review and edit the submission.
                        <SU>1517</SU>
                        <FTREF/>
                         According to this commenter, further impediments to timely reporting may arise where an issue requires cross-department coordination or coordination with a joint facility or RSA client.
                        <SU>1518</SU>
                        <FTREF/>
                         This commenter stated that the Commission notification process will take even more time where a third party's technical and data personnel are relied on to provide initial drafts or where an RSA client requests that it have the opportunity to review all written notices before they are submitted.
                        <SU>1519</SU>
                        <FTREF/>
                         Another commenter noted that senior management of SCI entities would want an SCI event to be investigated before it is reported to the Commission.
                        <SU>1520</SU>
                        <FTREF/>
                         This commenter also noted that any responsible Chief Administrative Officer, Chief Financial Officer, Chief Operations Officer, Chief Compliance Officer, Chief Information Security Officer, General Counsel, and compliance attorneys and officers would want to review any report on an SCI event prior to submission to the Commission.
                        <SU>1521</SU>
                        <FTREF/>
                         In addition, this commenter noted that the SCI entity would need to engage outside counsel and possibly other parties to review such reports.
                        <SU>1522</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1517</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 19. Similarly, another commenter noted that notifications to the Commission for SCI events and material systems changes would be considered a serious matter, and a diligent and properly considered notification would require the time and effort of numerous staff in different departments. 
                            <E T="03">See</E>
                             UBS Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1518</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1519</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1520</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 35.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1521</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1522</SU>
                             
                            <E T="03">See id.</E>
                             at 35-36. This commenter also noted that the Commission's estimated cost for consulting outside experts is too low. 
                            <E T="03">See id.</E>
                             at 35, n. 69.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the Commission's estimate of the burden for written Commission notification under proposed Rule 1000(b)(4)(i), one commenter noted that considerable amounts of activities may be necessary to gather the information needed, to have appropriate confirmations from persons with knowledge and authority with respect to the applicable SCI system, to provide for senior management review where appropriate, and to otherwise be in a position to draft the notification.
                        <SU>1523</SU>
                        <FTREF/>
                         Another commenter noted that Commission notification required by proposed Rule 1000(b)(4)(i) would require substantive input from personnel outside of the legal and compliance departments, including IT analysts and managers as well as impacted business analysts and managers.
                        <SU>1524</SU>
                        <FTREF/>
                         This commenter estimated that each notification under proposed Rule 1000(b)(4)(i) would require 12 hours.
                        <SU>1525</SU>
                        <FTREF/>
                         This commenter also noted that the Commission erroneously assumed that verbal notifications under proposed Rule 
                        <PRTPAGE P="72382"/>
                        1000(b)(4)(i) would not consume the time of any employee.
                        <SU>1526</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1523</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1524</SU>
                             
                            <E T="03">See</E>
                             UBS Letter at 6. This commenter expressed the same concern with respect to proposed Rule 1000(b)(4)(ii). 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1525</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1526</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        With respect to the estimated burden under proposed Rule 1000(b)(4)(ii), one commenter noted that the estimate did not take into account the considerable amounts of activities to be undertaken by other personnel, including persons with knowledge and authority with respect to the applicable SCI system and the SCI event as well as senior management where appropriate, in order to collect and assess the appropriate information and to properly inform the attorney and compliance manager of such information in order to allow them to produce an accurate notification in compliance with proposed Rule 1000(b)(4)(ii).
                        <SU>1527</SU>
                        <FTREF/>
                         This commenter had similar concerns with the burden estimates for proposed Rule 1000(b)(4)(iii).
                        <SU>1528</SU>
                        <FTREF/>
                         Another commenter noted that, with respect to proposed Rule 1000(b)(4)(ii), no provision was made for the time burden that would be placed on technology personnel in the notification process.
                        <SU>1529</SU>
                        <FTREF/>
                         Similarly, one commenter noted that the 20-hour burden estimate failed to take into account technology staff and business operations personnel who spend considerable time gathering facts and circumstances of a systems issue.
                        <SU>1530</SU>
                        <FTREF/>
                         Another commenter estimated that each report under proposed Rule 1000(b)(4)(ii) will require approximately 5 hours of senior management time (including review and discussions between the Chief Administrative Officer, the Chief Compliance Officer, the Chief Information Officer, the Chief Operating Officer, and the General Counsel).
                        <SU>1531</SU>
                        <FTREF/>
                         In addition, this commenter estimated that middle managers from its Compliance, Legal, Technology, Product, and Information Security functions would spend on average approximately 31 hours per report.
                        <SU>1532</SU>
                        <FTREF/>
                         Further, this commenter estimated that associates from Compliance, Legal, Technology, Product, and Information Security functions would spend approximately 53.5 hours per report.
                        <SU>1533</SU>
                        <FTREF/>
                         With respect to the burden estimates for proposed Rule 1000(b)(4)(iii), this commenter believed that proposed Rule 1000(b)(4)(iii) could conceivably require it to update the Commission approximately half of the time it files Form SCI.
                        <SU>1534</SU>
                        <FTREF/>
                         According to this commenter, each update would result in 1 hour of senior management time, 17 hours of middle management time, and 9 hours of associate time.
                        <SU>1535</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1527</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 33.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1528</SU>
                             
                            <E T="03">See id.</E>
                             at 33-34.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1529</SU>
                             
                            <E T="03">See</E>
                             Joint SRO Letter at 18. This commenter also opined that, in other sections, the Commission either incorrectly assumes that no legal or outside counsel would be used, or significantly underestimates the amount of legal or outside counsel expenses. 
                            <E T="03">See id.</E>
                             at 18-19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1530</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 12. 
                            <E T="03">See also</E>
                             NYSE Letter at 18 and 34 (stating that a significant number of full time staff, including legal, compliance, technical, and operations staff, would be required to comply with the Commission notification process under proposed Rule 1000(b)(4), and that no estimate is provided for a technology staff member under Rule 1000(b)(4)(ii)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1531</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 36.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1532</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1533</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1534</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1535</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated its belief that none of the activities arising under proposed Rule 1000(b)(4) would be conducive to outsourcing.
                        <SU>1536</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1536</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 34-35.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.3.c, the Commission is adopting the Commission notification requirements in Rule 1002(b), with certain modifications from the proposal. As adopted, the Commission notification requirements under Rules 1002(b)(1)-(4) do not apply to SCI events that had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants.
                        <SU>1537</SU>
                        <FTREF/>
                         Rather, each SCI entity is required to make, keep, and preserve records relating to all such SCI events, and submit quarterly reports to the Commission regarding such de minimis systems disruptions and de minimis systems intrusions.
                        <SU>1538</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1537</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1538</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Rule 1002(b)(1), similar to the proposal, requires immediate Commission notification upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred. Rule 1002(b)(2), similar to the proposal, requires a written Commission notification within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that the SCI event has occurred. Rule 1002(b)(2) also specifically states that the 24-hour report is required to be made on a good faith, best efforts basis. In addition, the information required to be disclosed to the Commission under Rule 1002(b)(2) is less comprehensive than as proposed.
                        <SU>1539</SU>
                        <FTREF/>
                         Rule 1002(b)(3), similar to the proposal, requires SCI entities to provide updates pertaining to an SCI event on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, until the event is resolved and the SCI entity's investigation of the event is closed. However, Rule 1002(b)(3), unlike the proposal, does not require these updates to be in writing. Finally, Rule 1002(b)(4) includes requirements for SCI entities to submit interim written notifications, as necessary, and final written notifications regarding SCI events.
                        <SU>1540</SU>
                        <FTREF/>
                         Specifically, if an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 calendar days of the occurrence of the SCI event, then within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event, the SCI entity is required to submit a final written notification. If an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 calendar days of the occurrence of the SCI event, then the SCI entity is required to submit an interim written notification within 30 calendar days after the occurrence of the SCI event. Within five business days after the resolution of such SCI event and closure of the investigation regarding such SCI event, the SCI entity is required to submit a final written notification.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1539</SU>
                             For example, an SCI entity is not required to provide the Commission a detailed description of the SCI event; a discussion of whether the SCI event is a dissemination SCI event; a description of the SCI entity's rules and/or governing documents, as applicable, which relate to the SCI event; or an analysis of parties that may have experienced a loss due to the SCI event.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1540</SU>
                             The written notification is required to include (i) a detailed description of: The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event; (ii) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and (iii) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. The information required to be included in the Rule 1002(b)(4) notifications is similar to the information required under proposed Rule 1000(b)(4)(iv)(A), which was related to the proposed 24-hour Commission notification.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, some commenters expressed their view that the Commission underestimated the number of SCI events because they considered the definition of SCI event to be broad and would include minor or immaterial events.
                        <SU>1541</SU>
                        <FTREF/>
                         These commenters estimated hundreds and even thousands of SCI events annually for each SCI entity, but noted that the majority of such events would have no 
                        <PRTPAGE P="72383"/>
                        effect on market participants.
                        <SU>1542</SU>
                        <FTREF/>
                         As discussed above in Section IV.B.3.c, the Commission notification requirements under adopted Rule 1002(b)(1)-(4) do not apply to any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants.
                        <SU>1543</SU>
                        <FTREF/>
                         Rather, each SCI entity would be required to keep records related to such events and submit quarterly reports that only contain a summary description of such de minimis systems disruptions and de minimis systems intrusions.
                        <SU>1544</SU>
                        <FTREF/>
                         Further, as noted above in Section IV.A, the Commission has refined the definition of SCI systems and SCI events in various respects.
                        <SU>1545</SU>
                        <FTREF/>
                         Therefore, the Commission does not believe that the number of SCI events subject to Rules 1002(b)(1)-(4) would be substantially higher than the Commission's estimate in the SCI Proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1541</SU>
                             
                            <E T="03">See supra</E>
                             notes 1513-1515 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1542</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1543</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(b)(5).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1544</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1545</SU>
                             
                            <E T="03">See</E>
                             Rule 1000 (defining “SCI systems” and “SCI event”).
                        </P>
                    </FTNT>
                    <P>
                        After considering the views of commenters and in light of the more focused scope of the immediate Commission notification requirement, the Commission now estimates that each SCI entity will experience an average of 45 SCI events each year that are not de minimis SCI events, resulting in 45 written notifications under Rule 1002(b)(2) and 45 written notifications under Rule 1002(b)(4). The estimated 45 SCI events comprise 24 systems disruptions, 20 systems compliance issues, and one systems intrusion. These estimates are derived in part from the number of systems incidents reported to the Commission under the ARP Inspection Program and the number of compliance-related issues reported to the Commission by SROs.
                        <SU>1546</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1546</SU>
                             The Commission notes that only one ATS currently participates in the ARP Inspection Program and other ATSs generally do not self-report system incidents to the Commission. At the same time, the Commission acknowledges that, to the extent that some ATSs have less complex systems or perform fewer functions than other SCI entities, it is possible that these ATSs will experience fewer SCI events per year than other SCI entities. Also, as discussed more fully below, many ATSs do not have rulebooks and thus may experience fewer systems compliance issues than other SCI entities. Nevertheless, the Commission believes that an average of 45 SCI events per year (excluding de minimis SCI events) is an appropriate average across all SCI entities, including ATSs.
                        </P>
                    </FTNT>
                    <P>
                        In particular, the Commission notes that approximately 360 ARP incidents were reported to the Commission in 2013 by 29 entities that participated in the ARP Inspection Program.
                        <SU>1547</SU>
                        <FTREF/>
                         Thus, on average, each entity reported approximately 12 incidents in 2013, although some entities reported fewer than 12 incidents, and some entities reported significantly more than 12 incidents (
                        <E T="03">i.e.,</E>
                         over 100). By defining “systems disruption” for purposes of Regulation SCI and requiring Commission notification of systems disruptions, the Commission expects that more incidents will be reported pursuant to Regulation SCI than pursuant to the voluntary ARP Inspection Program. Therefore, the Commission estimates that each SCI entity will report an average of 24 systems disruptions each year that are not de minimis systems disruptions, which is double the average number of systems incidents reported by each participant under the ARP Inspection Program in 2013.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1547</SU>
                             In the SCI Proposal, the Commission noted that each entity reported an average of approximately 6 incidents under the ARP Inspection Program in 2011, and estimated that there would be an average of 65 SCI event notices per year for each SCI entity. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18148.
                        </P>
                    </FTNT>
                    <P>
                        Further, based on notifications received by Commission staff regarding certain SROs, each of these SROs experienced an average of 17 systems compliance-related issues in 2013. The notifications received by Commission staff indicate that some SROs experienced fewer than 17 systems compliance-related issues, and others experienced more than 17. The Commission believes that very few, if any, of the notifications received in 2013 would qualify as de minimis systems compliance issues under Regulation SCI. By defining “systems compliance issue” for purposes of Regulation SCI and requiring Commission notification of systems compliance issues, the Commission expects that more issues will be reported pursuant to Regulation SCI than pursuant to self-reporting. Therefore, the Commission estimates that each SCI entity will experience an average of 20 systems compliance issues each year that are not de minimis systems compliance issues.
                        <SU>1548</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1548</SU>
                             The Commission acknowledges that SCI entities other than SCI SROs may experience fewer systems compliance issues than SCI SROs because they may not have rulebooks, and thus, one aspect of the definition of systems compliance issue would not apply to such SCI entities (
                            <E T="03">i.e.,</E>
                             operating in a manner that does not comply with the entity's rules).
                        </P>
                    </FTNT>
                    <P>
                        Based on the Commission's experience with the ARP Inspection Program, the Commission believes each SCI entity will experience on average less than one non-de minimis systems intrusion per year. However, for purposes of the PRA, the Commission estimates one non-de minimis systems intrusion per SCI entity per year.
                        <SU>1549</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1549</SU>
                             This estimate is lower than those provided by commenters (
                            <E T="03">see supra</E>
                             note 1515 and accompanying text) because the adopted definitions of SCI systems and indirect SCI systems have been refined from the proposal, and because de minimis systems intrusions are required to be reported in summary format on a quarterly basis.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the notification requirement under Rule 1002(b)(1), the Commission notes that the notification can be made orally or in writing. As with the SCI Proposal, the Commission estimates that one-fourth of the notifications under Rule 1002(b)(1) will be submitted in writing (
                        <E T="03">i.e.,</E>
                         approximately 11 events per year for each SCI entity),
                        <SU>1550</SU>
                        <FTREF/>
                         and three-fourths will be provided orally (
                        <E T="03">i.e.,</E>
                         approximately 34 events per year for each SCI entity).
                        <SU>1551</SU>
                        <FTREF/>
                         The Commission also estimates that each written notification under Rule 1002(b)(1) will require 2 hours 
                        <SU>1552</SU>
                        <FTREF/>
                         for each SCI entity.
                        <SU>1553</SU>
                        <FTREF/>
                         The Commission is not 
                        <PRTPAGE P="72384"/>
                        significantly increasing its burden estimate for proposed Rule 1000(b)(4)(i) because Rule 1002(b)(1) requires the immediate notification of SCI events and does not specify the minimum information that must be submitted to the Commission. The Commission believes that, for many SCI events, an SCI entity will simply notify the Commission that an SCI event has occurred, often in a single phone call, and may not provide the Commission with additional information because it is not yet available to the SCI entity. For these reasons, contrary to the view of some commenters,
                        <SU>1554</SU>
                        <FTREF/>
                         the Commission does not expect that the SCI entity will need to gather a considerable amount of information or significantly confer with interested parties across the entity. In particular, while the Commission estimates some burden for legal and technology personnel of SCI entities in complying with Rule 1002(b)(1), it does not believe that Rule 1002(b)(1) will result in significant burden for such personnel.
                        <SU>1555</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1550</SU>
                             45 SCI events ÷ 4 = 11.25 SCI events reported in writing. One commenter noted that most SCI entities would submit a writing to document that they had satisfied the notice requirement of proposed Rule 1000(b)(4)(i). 
                            <E T="03">See</E>
                             Omgeo Letter at 16. However, the Commission continues to estimate that one-fourth of the notifications under Rule 1002(b)(1) will be submitted in writing and that the rest will be provided orally. The Commission believes that it is less burdensome for an SCI entity to provide oral notification than to provide written notification and, given the requirement of Rule 1002(b)(2) to provide a written notification to the Commission within 24 hours, the Commission believes it is likely that most initial notifications submitted under Rule 1002(b)(1) would be done orally. Moreover, based on Commission staff experience, ARP participants generally provide initial notifications of systems issues orally.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1551</SU>
                             45 SCI events−11 SCI events reported in writing = 34 SCI events reported orally.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1552</SU>
                             The burden estimates for each rule under Regulation SCI that involves the filing of Form SCI include the burden associated with completing and electronically submitting Form SCI, and for manually signing a signature page or document, pursuant to the requirements of Rule 1006.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1553</SU>
                             The 2 hours include 0.5 hours by an Attorney, 0.5 hours by a Compliance Manager, 0.5 hours by a Senior Systems Analyst, and 0.5 hours by a Senior Business Analyst. As compared to the estimated burden for proposed Rule 1000(b)(4)(i), the Commission is estimating an additional 0.5 hours by Compliance Managers, 0.5 hours by Senior Systems Analysts, and 0.5 hours by Senior Business Analysts to reflect that legal personnel may need to confer with technology and business personnel before contacting the Commission regarding an SCI event, in response to the views of commenters. 
                            <E T="03">See supra</E>
                             notes 1523-1525 and accompanying text. The Commission notes that the General Counsel, Director of Compliance, Chief Compliance Officer, or other senior employees or officers of certain SCI entities may review Commission notifications under Rule 1002(b)(1) before they are submitted (orally or in writing) to the Commission. However, the Commission estimates that on average, the General Counsel, Director of Compliance, Chief Compliance Officer, or other senior employees or officers may spend a small amount of time reviewing each Rule 1002(b)(1) notification. Rather, they will spend more time reviewing the other notifications required by Rule 1002(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1554</SU>
                             
                            <E T="03">See supra</E>
                             notes 1523-1526 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1555</SU>
                             Given that there is not a minimum amount of information that must be submitted to the Commission, the Commission believes its estimated burden hours is more appropriate than the 12 hours suggested by a commenter. 
                            <E T="03">See supra</E>
                             note 1525 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission agrees with the view of a commenter that oral notifications would also result in burdens on an SCI entity,
                        <SU>1556</SU>
                        <FTREF/>
                         although it expects the burden for legal and compliance personnel to be lower than in the case of written notifications because they would not need to draft and review a written document for submission to the Commission. The Commission estimates that the burden for systems and business analysts would remain the same as for written notifications because the SCI entity will still need to gather the same type of information in order to prepare an oral notification. The Commission therefore estimates that each oral notification under Rule 1002(b)(1) will require 1.5 hours for each SCI entity.
                        <SU>1557</SU>
                        <FTREF/>
                         The Commission estimates that each SCI entity would require an average of 73 hours annually to comply with Rule 1002(b)(1),
                        <SU>1558</SU>
                        <FTREF/>
                         or 3,212 hours for all SCI entities.
                        <SU>1559</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1556</SU>
                             
                            <E T="03">See supra</E>
                             note 1526 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1557</SU>
                             The 1.5 hours include 0.25 hours by an Attorney, 0.25 hours by a Compliance Manager, 0.5 hours by a Senior Systems Analyst, and 0.5 hours by a Senior Business Analyst.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1558</SU>
                             11 written notifications each year × 2 hours per notification + 34 oral notifications each year × 1.5 hours per notification = 73 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1559</SU>
                             73 hours × 44 SCI entities = 3,212 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each written notification under Rule 1002(b)(2) will require 24 hours for each SCI entity.
                        <SU>1560</SU>
                        <FTREF/>
                         Contrary to the views of a commenter that each notification under proposed Rule 1000(b)(4)(ii) would require approximately 90 burden hours between senior management, middle managers, and associates from various functions (
                        <E T="03">e.g.,</E>
                         legal, compliance, technology),
                        <SU>1561</SU>
                        <FTREF/>
                         the Commission is not significantly increasing its estimate of the burden hours from its estimate for proposed Rule 1000(b)(4)(ii) because Rule 1002(b)(2) requires less information than proposed Rule 1000(b)(4)(ii), although the Commission has revised its estimated burden hours to account for the various functions and multiple levels of review suggested by the commenter.
                        <SU>1562</SU>
                        <FTREF/>
                         Also, because Rule 1002(b)(2) explicitly permits information to be submitted on a good faith, best efforts basis, the Commission believes that SCI entities will be able to expend less resources in reviewing each notification. Therefore, the Commission estimates that each SCI entity would require an average of 1,080 hours annually to comply with Rule 1002(b)(2),
                        <SU>1563</SU>
                        <FTREF/>
                         or 47,520 hours for all SCI entities.
                        <SU>1564</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1560</SU>
                             The 24 hours include 5 hours by an Attorney, 5 hours by a Compliance Manager, 6 hours by a Senior Systems Analyst, 1 hour by an Assistant General Counsel, 1 hour by a Chief Compliance Officer, and 6 hours by a Senior Business Analyst. Given the modifications from proposed Rule 1000(b)(4)(ii) identified below, the Commission estimates that legal and compliance personnel will have less work in drafting the written notifications under Rule 1002(b)(2), and accordingly reduced the burden hours for Attorneys and Compliance Managers from 10 to 5. Further, as compared to the estimated burden for proposed Rule 1000(b)(4)(ii), the Commission is estimating an additional 6 hours by a Senior Systems Analyst, 1 hour by an Assistant General Counsel, 1 hour by a Chief Compliance Officer, and 6 hours by a Senior Business Analyst to reflect that legal personnel may need to confer with technology and business personnel and senior management, as well as the multiple levels of review (
                            <E T="03">e.g.,</E>
                             attorney, compliance manager, chief compliance officer), before submitting a report regarding an SCI event, in response to the views of commenters. 
                            <E T="03">See supra</E>
                             notes 1520-1521, 1527, and 1529-1533 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1561</SU>
                             
                            <E T="03">See supra</E>
                             notes 1531-1533 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1562</SU>
                             
                            <E T="03">See supra</E>
                             notes 1539 and 1560.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1563</SU>
                             45 written notifications each year × 24 hours per notification = 1,080 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1564</SU>
                             1,080 hours × 44 SCI entities = 47,520 hours.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the number of updates required under Rule 1002(b)(3), the Commission estimates that each SCI entity will submit 6 written updates and 18 oral updates each year under that rule. These estimates are based on Commission staff's experience with the ARP Inspection Program, systems compliance-related issues at SROs, and views of commenters. Specifically, most of the systems incidents reported to the Commission in 2013 were reported as resolved within 24 hours. Further, as discussed above, de minimis SCI events are not subject to the update requirement under Rule 1002(b)(3). Moreover, the Commission believes that, for some SCI events, an SCI entity will not need to provide an update under Rule 1002(b)(3), because the SCI entity will be able to quickly submit a final report under Rule 1002(b)(4). However, after considering the views of a commenter that some complex outages can take up to several days to triage, isolate, and begin to resolve,
                        <SU>1565</SU>
                        <FTREF/>
                         and the views of another commenter that proposed Rule 1000(b)(4)(iii) could conceivably require it to update the Commission approximately half the time it files Form SCI,
                        <SU>1566</SU>
                        <FTREF/>
                         the Commission is increasing its estimate of the number of updates from 5 to 24.
                        <SU>1567</SU>
                        <FTREF/>
                         Because Rule 1002(b)(3) does not require SCI entities to submit updates in writing or on Form SCI, the Commission estimates that one-fourth of the updates will be submitted in writing, and three-fourths will be provided orally.
                        <SU>1568</SU>
                        <FTREF/>
                         Because the SCI entity will still need to gather the same type of information in order to prepare an oral or a written update, the Commission expects that the burden for systems and business analysts will be the same for either type of update. The Commission, however, expects that the burden for legal and compliance personnel would be less in the case of oral updates because in that case, an SCI entity would not need to draft and review a written document for submission to the Commission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1565</SU>
                             
                            <E T="03">See supra</E>
                             note 1516.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1566</SU>
                             
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 1534 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1567</SU>
                             The Commission's estimate of 24 updates is slightly above half of the 45 written notifications estimated for Rule 1002(b)(2). 
                            <E T="03">See supra</E>
                             note 1534 (stating that the rule could conceivably require the commenter to update the Commission approximately half of the time it files Form SCI).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1568</SU>
                             The Commission similarly estimated one-fourth written notifications and three-fourths oral notifications in the SCI Proposal for proposed Rule 1000(b)(4)(i). 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18148; 
                            <E T="03">see also</E>
                              
                            <E T="03">supra</E>
                             note 1550 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each written update under Rule 1002(b)(3) will require 6 hours 
                        <SU>1569</SU>
                        <FTREF/>
                         and each oral 
                        <PRTPAGE P="72385"/>
                        update will require 4.5 hours.
                        <SU>1570</SU>
                        <FTREF/>
                         The Commission is not significantly increasing its burden estimate from proposed Rule 1000(b)(4)(iii). The Commission believes that each update will likely only reflect some of the information listed under Rules 1002(b)(1) and (2) because certain information about SCI events may not yet be available at the time the SCI entity submits such update or may not need to be updated. Therefore, contrary to one commenter's view that each update would require 27 hours,
                        <SU>1571</SU>
                        <FTREF/>
                         the Commission does not believe that a Rule 1002(b)(3) update will require significantly more time than as estimated in the SCI Proposal. The Commission estimates that each SCI entity would require an average of 117 hours annually to comply with Rule 1002(b)(3),
                        <SU>1572</SU>
                        <FTREF/>
                         or 5,148 hours for all SCI entities.
                        <SU>1573</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1569</SU>
                             The 6 hours include 1.5 hours by an Attorney, 1.5 hours by a Compliance Manager, 1.5 hours by a Senior Systems Analyst, and 1.5 hours by a Senior Business Analyst. As compared to the estimated burden for proposed Rule 1000(b)(4)(iii), the Commission is estimating an additional 1.5 hours by a Senior Systems Analyst and 1.5 hours by a Senior Business Analyst to reflect that legal personnel may need to confer with technology and business personnel before contacting the Commission regarding an SCI event, in response to the view of a commenter. 
                            <E T="03">See supra</E>
                             note 1528 and accompanying text. The Commission notes that the General Counsel, Director of Compliance, Chief 
                            <PRTPAGE/>
                            Compliance Officer, or other senior employees or officers of certain SCI entities may review the updates under Rule 1002(b)(3) before they are submitted (orally or in writing) to the Commission. However, the Commission estimates that on average, the General Counsel, Director of Compliance, Chief Compliance Officer, or other senior employees or officers may spend a small amount of time reviewing each Rule 1002(b)(3) notification because it is not the final report to the Commission on an SCI event, and the SCI entity can subsequently submit additional updates. 
                            <E T="03">See supra</E>
                             note 1535 and accompanying text (noting a commenter's burden estimate for proposed Rule 1000(b)(4)(iii), which includes estimates for senior management review).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1570</SU>
                             The 4.5 hours include 0.75 hours by an Attorney, 0.75 hours by a Compliance Manager, 1.5 hours by a Senior Systems Analyst, and 1.5 hours by a Senior Business Analyst.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1571</SU>
                             
                            <E T="03">See supra</E>
                             note 1535 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1572</SU>
                             6 written updates each year × 6 hours per notification + 18 oral updates each year × 4.5 hours per notification = 117 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1573</SU>
                             117 hours × 44 SCI entities = 5,148 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that compliance with Rule 1002(b)(4) for a particular SCI event (which includes a final report under Rule 1002(b)(4)(i)(A) and, as applicable, an interim report under Rule 1002(b)(4)(i)(B)) will require 35 hours.
                        <SU>1574</SU>
                        <FTREF/>
                         The Commission notes that the information required to be provided under Rule 1002(b)(4) is similar to the information required to be provided in a notification submitted under proposed Rule 1000(b)(4)(ii). As noted above, in the SCI Proposal, the Commission estimated that each notification under proposed Rule 1000(b)(4)(ii) would require an average of 20 burden hours,
                        <SU>1575</SU>
                        <FTREF/>
                         and some commenters argued that the Commission underestimated this burden.
                        <SU>1576</SU>
                        <FTREF/>
                         The Commission is estimating a higher burden for Rule 1002(b)(4) as compared to proposed Rule 1000(b)(4)(ii) (
                        <E T="03">i.e.,</E>
                         35 hours as compared to 20 hours) because the reports under Rule 1002(b)(4) constitute final reports regarding SCI events, and SCI entities will likely confer with technology and business personnel and senior management to ensure that the information provided is accurate. For the same reason, and because Rule 1002(b)(4) (final report) requires more information than Rule 1002(b)(2), the Commission's burden estimate for Rule 1002(b)(4) is higher than the burden estimate for Rule 1002(b)(2) (
                        <E T="03">i.e.,</E>
                         35 hours as compared to 24 hours).
                        <SU>1577</SU>
                        <FTREF/>
                         Nevertheless, the Commission is not substantially increasing the burden estimate as compared to proposed Rule 1000(b)(4)(ii) or adopted Rule 1002(b)(2) because it recognizes that some of the information required by Rule 1002(b)(4) may already have been provided in a prior notification to the Commission and, thus, its burden has been included in the burden estimate for Rule 1002(b)(2). Therefore, the Commission estimates that each SCI entity would require an average of 1,575 hours annually to comply with Rule 1002(b)(4),
                        <SU>1578</SU>
                        <FTREF/>
                         or 69,300 hours for all SCI entities.
                        <SU>1579</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1574</SU>
                             The 35 hours include 8 hours by an Attorney, 8 hours by a Compliance Manager, 7 hours by a Senior Systems Analyst, 2 hours by an Assistant General Counsel, 1 hour by a General Counsel, 2 hours by a Chief Compliance Officer, and 7 hours by a Senior Business Analyst. As compared to proposed Rule 1000(b)(4)(ii), the Commission expects the legal and compliance personnel to have less work in drafting the written notifications under Rule 1002(b)(4) because some of the information required by Rule 1002(b)(4) may already have been provided in a prior notification to the Commission, and accordingly reduced the burden hours for Attorneys and Compliance Managers from 10 to 8. Further, as compared to the estimated burden for proposed Rule 1000(b)(4)(ii), the Commission is estimating an additional 7 hours by a Senior Systems Analyst, 2 hours by an Assistant General Counsel, 1 hour by a General Counsel, 2 hours by a Chief Compliance Officer, and 7 hours by a Senior Business Analyst to reflect that legal personnel may need to confer with technology and business personnel and senior management before submitting a final report regarding an SCI event.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1575</SU>
                             
                            <E T="03">See supra</E>
                             note 1509 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1576</SU>
                             
                            <E T="03">See supra</E>
                             notes 1527, 1529-1533 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1577</SU>
                             As compared to the Commission's burden estimate for Rule 1002(b)(2), the Commission is estimating an additional 3 hours by an Attorney, 3 hours by a Compliance Manager, 1 hour by a Senior Systems Analyst, 1 hour by an Assistant General Counsel, 1 hour by a General Counsel, 1 hour by a Chief Compliance Officer, and 1 hour by a Senior Business Analyst. The type of personnel involved in compliance with Rule 1002(b)(4) is the same as those involved in compliance with Rule 1002(b)(2), except for the addition of the General Counsel.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1578</SU>
                             45 written notifications each year × 35 hours per notification = 1,575 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1579</SU>
                             1,575 hours × 44 SCI entities = 69,300 hours. The Commission notes that this burden estimate includes the burden for submitting the one interim Commission notification required under Rule 1002(b)(4)(i)(B) (if necessary). In particular, the Commission notes that the interim notification requires SCI entities to include the same information as required to be included in a final notification under Rule 1002(b)(4)(i)(A), except that SCI entities are only required to provide the information to the extent known at the time of the interim notification. If an SCI entity submits an interim notification, it would also be required to submit a final notification, which is required to include all of the remaining information that was not provided in the interim notification. Because all SCI entities are required to provide the same amount of information in total for a particular SCI event under Rule 1002(b)(4), regardless of whether they submit an interim notification, the estimated burden for Rule 1002(b)(4) includes the burden for both the interim notification and the final notification related to a particular SCI event.
                        </P>
                    </FTNT>
                    <P>
                        Finally, the quarterly notification under Rule 1002(b)(5) is required only to include “a summary description” of the SCI events. The Commission's estimated burden reflects the Commission's belief that most, if not all, SCI entities already have some internal documentation of de minimis SCI events. Rule 1002(b)(5) would impose more burden on SCI entities if they do not already have such internal documentation. The Commission estimates that the initial and ongoing burden to comply with the quarterly report requirement would be 40 hours per report per SCI entity,
                        <SU>1580</SU>
                        <FTREF/>
                         or 160 hours annually per SCI entity,
                        <SU>1581</SU>
                        <FTREF/>
                         and 7,040 hours annually for all SCI entities.
                        <SU>1582</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1580</SU>
                             The 40 burdens hours include 7.5 hours by an Attorney, 7.5 hours by a Compliance Manager, 2 hours by a Chief Compliance Officer, 2 hours by an Assistant General Counsel, 1 hour by a General Counsel, 10 hours by a Senior Business Analyst, and 10 hours by a Senior Systems Analyst.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1581</SU>
                             40 hours × 4 reports each year = 160 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1582</SU>
                             160 hours × 44 SCI entities = 7,040 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that while SCI entities would handle internally most of the work associated with Rule 1002(b), SCI entities would seek outside legal advice in the preparation of certain Commission notifications, at an average annual cost of $45,000 per SCI entity,
                        <SU>1583</SU>
                        <FTREF/>
                         or $1,980,000 for all SCI entities.
                        <SU>1584</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1583</SU>
                             
                            <E T="03">See supra</E>
                             note 1522 and accompanying text (discussing the view of a commenter that SCI entities would need to engage outside parties to review the Commission notifications). 
                            <E T="03">But see supra</E>
                             note 1536 and accompanying text (discussing the view of a commenter that none of the activities arising under proposed Rule 1000(b)(4) would be conducive to outsourcing). The Commission's estimate represents an average of $1,000 of outsourced cost for each SCI event that is not a de minimis SCI event. The $1,000 estimate is consistent with the Commission's estimated outsourcing cost for each SCI event that is subject to the dissemination requirements under Rule 1002(c). 45 SCI events × $1,000 = $45,000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1584</SU>
                             $45,000 × 44 SCI entities = $1,980,000.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Dissemination of Information Regarding SCI Events</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity would experience an average of 14 
                        <PRTPAGE P="72386"/>
                        dissemination SCI events 
                        <SU>1585</SU>
                        <FTREF/>
                         each year that are not systems intrusions, resulting in an average of 14 information disseminations per year for each SCI entity under proposed Rule 1000(b)(5)(i).
                        <SU>1586</SU>
                        <FTREF/>
                         The Commission estimated that each information dissemination under proposed Rule 1000(b)(5)(i)(A) would require an average of 3 hours to prepare and make available to members or participants.
                        <SU>1587</SU>
                        <FTREF/>
                         The Commission estimated that each information update under proposed Rule 1000(b)(5)(i)(B) would require an average of 5 hours to prepare and make available to members or participants.
                        <SU>1588</SU>
                        <FTREF/>
                         The Commission also estimated that, on average, each SCI entity would provide one regular update per year per dissemination SCI event under proposed Rule 1000(b)(5)(i)(C).
                        <SU>1589</SU>
                        <FTREF/>
                         The Commission estimated that each regular update would require an average of 1 hour to prepare and make available to members or participants.
                        <SU>1590</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1585</SU>
                             Dissemination SCI events included systems compliance issues, systems intrusions, and systems disruptions that resulted, or the SCI entity reasonably estimates would result, in significant harm or loss to market participants.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1586</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18149.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1587</SU>
                             
                            <E T="03">See id.</E>
                             The 3 burden hours included 2.67 hours by an Attorney and 0.33 hours by a Webmaster. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18149, n. 416.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1588</SU>
                             
                            <E T="03">See id.</E>
                             at 18150. The 5 burden hours included 4.67 hours by an Attorney and 0.33 hours by a Webmaster. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18150, n. 420.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1589</SU>
                             
                            <E T="03">See id.</E>
                             at 18150.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1590</SU>
                             
                            <E T="03">See id.</E>
                             The 1 burden hour included 0.67 hours by an Attorney and 0.33 hours by a Webmaster. 
                            <E T="03">See id.</E>
                             This estimate was based on the estimated burden to complete and submit a written update for an SCI event on Form SCI and on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18150, n. 422 and n. 423.
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity would experience an average of 1 dissemination SCI event that is a systems intrusion each year, resulting in 1 information dissemination per year under proposed Rule 1000(b)(5)(ii). The Commission estimated that each information dissemination would require an average of 3 hours to prepare and make available to members or participants.
                        <SU>1591</SU>
                        <FTREF/>
                         This burden estimate included any burden for an SCI entity to document its reason for determining that dissemination of information regarding a systems intrusion would likely compromise the security of the SCI entity's SCI systems or SCI security systems, or an investigation of the systems intrusion.
                        <SU>1592</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1591</SU>
                             
                            <E T="03">See id.</E>
                             at 18150. The 3 burden hours included 2.67 hours by an Attorney and 0.33 hours by a Webmaster. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program, and the Commission's burden estimate for proposed Rule 1000(b)(5)(i)(A). 
                            <E T="03">See id.</E>
                             at 18150, n. 426.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1592</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission estimated that while SCI entities would internally handle most of work associated with compliance with proposed Rule 1000(b)(5), SCI entities would seek outside legal advice in the preparation of the disseminations at an average annual cost of $15,000 per SCI entity.
                        <SU>1593</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1593</SU>
                             
                            <E T="03">See id.</E>
                             at 18150-51.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the estimated burden under proposed Rule 1000(b)(5), one commenter noted that since most of the work entailed in producing a notification relating to a dissemination SCI event would occur in connection with the Commission notification requirements under proposed Rule 1000(b)(4), the Commission's estimate of the burden of proposed Rule 1000(b)(5) is fairly accurate.
                        <SU>1594</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1594</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 35.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter stated that the Commission underestimated the burden associated with information dissemination.
                        <SU>1595</SU>
                        <FTREF/>
                         In connection with expressing its concern that almost any minor or immaterial systems issue would fall under the proposed definition of SCI event, this commenter estimated that there would be at a minimum a ten-fold increase in reportable events from the 175 incidents in 2011 under the ARP Inspection Program.
                        <SU>1596</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1595</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 37. This commenter argued that the Commission mistakenly relied upon experience with the ARP Inspection Program as a basis for the estimates. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1596</SU>
                             
                            <E T="03">See id.</E>
                             at 37-38.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the estimated burden associated with information dissemination, this commenter argued that the Commission incorrectly assumed that such communications would be drafted only by a single attorney and a webmaster.
                        <SU>1597</SU>
                        <FTREF/>
                         This commenter believed that properly drafting such communications will require a concerted effort by a number of individuals, including subject matter experts and mid-level and senior managers.
                        <SU>1598</SU>
                        <FTREF/>
                         This commenter also noted that SCI entities would draft different dissemination notices designed to address the particular concerns of the different client segments it services (
                        <E T="03">e.g.,</E>
                         broker-dealers, custodian banks, investment managers, hedge funds).
                        <SU>1599</SU>
                        <FTREF/>
                         As such, this commenter estimated that proposed Rule 1000(b)(5)(i)(A) would result in a burden of approximately 30 hours to create the dissemination 
                        <SU>1600</SU>
                        <FTREF/>
                         and 100 hours to review.
                        <SU>1601</SU>
                        <FTREF/>
                         Further, this commenter disagreed that SCI entities are likely to handle internally most of the work associated with information dissemination.
                        <SU>1602</SU>
                        <FTREF/>
                         This commenter believed that, to the extent a dissemination SCI event raises the possibility of litigation or reputational damage for an SCI entity, the SCI entity will likely engage outside counsel to review the facts and prepare the required materials.
                        <SU>1603</SU>
                        <FTREF/>
                         This commenter also argued that the Commission's estimate did not take into account the burden associated with addressing responses from an SCI entity's participants, members, or clients, which, according to this commenter, would be hundreds of hours of SCI entity associate and management time.
                        <SU>1604</SU>
                        <FTREF/>
                         This commenter expressed similar concerns respect to the burden estimates for proposed Rules 1000(b)(5)(i)(B) and (C) and noted that each follow-up notice would impose a burden far greater than 5 hours.
                        <SU>1605</SU>
                        <FTREF/>
                         This commenter also noted that the Commission underestimated that each SCI entity would only have to provide one update each year under proposed Rule 1000(b)(5)(i)(C), and that each dissemination would only be prepared by an attorney and a webmaster.
                        <SU>1606</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1597</SU>
                             
                            <E T="03">See id.</E>
                             at 38.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1598</SU>
                             
                            <E T="03">See id.</E>
                             According to this commenter, subject matter experts would include associates from functions such as Technology, Client Support, Information Security, Legal, Compliance, Product Management, and Sales and Relationship Management. 
                            <E T="03">See id.</E>
                             at 38, n. 75.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1599</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 38.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1600</SU>
                             This commenter noted that major incidents would require far more resources. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1601</SU>
                             
                            <E T="03">See id.</E>
                             This commenter noted that the 100-hour estimate does not include any follow up communications. 
                            <E T="03">See id.</E>
                             at 38, n. 76.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1602</SU>
                             
                            <E T="03">See id.</E>
                             at 39. However, another commenter stated its belief that none of the activities arising under proposed Rule 1000(b)(5) would be conducive to outsourcing. 
                            <E T="03">See</E>
                             MSRB Letter at 34-35.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1603</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 39. This commenter also expressed concern that SCI entities would be forced to send their clients and participants a constant stream of communications detailing minor, inconsequential events that have no impact on them, which would cause reputational damage to SCI entities. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1604</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1605</SU>
                             
                            <E T="03">See id.</E>
                             at 40-41.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1606</SU>
                             
                            <E T="03">See id.</E>
                             at 41.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72387"/>
                    <P>
                        With respect to the burden estimates for proposed Rule 1000(b)(5)(ii), this commenter expressed similar concern, and noted that each dissemination under proposed Rule 1000(b)(5)(ii) would require hundreds of burden hours.
                        <SU>1607</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1607</SU>
                             
                            <E T="03">See id.</E>
                             at 41-42.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.3.d, the Commission is adopting the information dissemination requirements in Rule 1002(c), with certain modifications from the proposal. As adopted, an SCI entity is required to disseminate certain information to its members or participants that may have been affected by an SCI event.
                        <SU>1608</SU>
                        <FTREF/>
                         However, for major SCI events, an SCI entity must disseminate the required information to all of its member or participants.
                        <SU>1609</SU>
                        <FTREF/>
                         Rule 1002(c)(4) further provides that the information dissemination requirement does not apply to SCI events to the extent they relate to market regulation or market surveillance systems, or any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1608</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(c)(3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1609</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Similar to proposed Rule 1000(b)(5), adopted Rule 1002(c)(1) requires SCI entities to promptly disseminate certain information regarding systems disruptions and systems compliance issues, to further disseminate certain information when such information becomes known,
                        <SU>1610</SU>
                        <FTREF/>
                         and to provide regular updates of such information until the SCI event is resolved. In addition, similar to proposed Rule 1000(b)(5), adopted Rule 1002(c)(2) requires SCI entities to promptly disseminate certain information regarding systems intrusions,
                        <SU>1611</SU>
                        <FTREF/>
                         and provides an exception when the SCI entity determines that dissemination of such information would likely compromise the security of its SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and documents the reasons for such determination.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1610</SU>
                             The information required to be disseminated under Rule 1002(c)(1) remains unchanged from the proposal.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1611</SU>
                             The information required to be disseminated under Rule 1002(c)(2) remains unchanged from the proposal.
                        </P>
                    </FTNT>
                    <P>
                        With respect to a commenter's concern that because almost any minor or immaterial systems issue would fall under the proposed definition of SCI event, there would be at a minimum a ten-fold increase in reportable events as compared to the reported incidents under the ARP Inspection Program,
                        <SU>1612</SU>
                        <FTREF/>
                         as noted above, Rule 1002(c)(4) provides exceptions to certain SCI events from the information dissemination requirement. Specifically, SCI events that relate to market regulation or market surveillance systems and de minimis SCI events would not be subject to the information dissemination requirement.
                        <SU>1613</SU>
                        <FTREF/>
                         Further, as noted above in Section IV.A, the Commission has refined the definition of SCI systems and SCI event in various respects.
                        <SU>1614</SU>
                        <FTREF/>
                         Given these changes, the Commission believes that the commenter's suggestion that there would be at a minimum a ten-fold increase in reportable events as compared to the reported incidents under the ARP Inspection Program is not an appropriate estimate. The Commission now estimates that each SCI entity would disseminate information regarding 36 SCI events each year under Rule 1002(c),
                        <SU>1615</SU>
                        <FTREF/>
                         including 1 non-de minimis systems intrusion each year.
                        <SU>1616</SU>
                        <FTREF/>
                         Therefore, the Commission now estimates that each SCI entity would disseminate information regarding 35 SCI events each year under Rule 1002(c)(1)(i). The Commission estimates that each SCI entity would disseminate 3 updates for each such SCI event under Rules 1002(c)(1)(ii) and (iii),
                        <SU>1617</SU>
                        <FTREF/>
                         or 105 updates each year.
                        <SU>1618</SU>
                        <FTREF/>
                         Further, the Commission estimates that each SCI entity would disseminate information regarding 1 systems intrusion each year under Rule 1002(c)(2).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1612</SU>
                             
                            <E T="03">See supra</E>
                             note 1596 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1613</SU>
                             These exceptions should address a commenter's concern that proposed Rule 1000(b)(5) would result in SCI entities being forced to send their clients and participants a constant stream of communications detailing minor, inconsequential events that have no impact on them. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1614</SU>
                             
                            <E T="03">See</E>
                             Rule 1000 (defining “SCI systems” and “SCI event”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1615</SU>
                             As discussed above, the Commission estimates that each SCI entity will experience an average of 45 SCI events each year that are not de minimis SCI events. The Commission estimates that approximately one-fifth of these SCI events relate to market regulation and market surveillance systems. Therefore, the Commission estimates that the number of SCI events subject to the requirements of Rule 1002(c) would be 36 per year for each SCI entity (45 SCI events ÷ 5 × 4 = 36 SCI events).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1616</SU>
                             Based on Commission's experience with the ARP Inspection Program, the Commission believes each SCI entity will experience on average less than one non-de minimis systems intrusion per year. However, for purposes of the PRA, the Commission estimates one non-de minimis systems intrusion per SCI entity per year.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1617</SU>
                             The Commission notes that Rule 1002(c)(1)(ii) requires each SCI entity, when known, to promptly further disseminate for each SCI event three types of information: (A) A detailed description of the SCI event; (B) the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; and (C) a description of the progress of its corrective action for the SCI event and when the SCI event has been or is expected to be resolved. The Commission believes that one or more of these types of information may become known to an SCI entity at different times, and therefore the Commission estimates that each SCI entity will submit two updates per SCI event under Rule 1002(c)(1)(ii). Rule 1002(c)(1)(iii) requires each SCI entity to provide regular updates of any information required to be disseminated under Rules 1002(c)(1)(i) and (ii). The Commission estimates that each SCI entity will submit one regular update under Rule 1002(c)(1)(iii) before the SCI event is resolved. The Commission believes that the number of updates under Rules 1002(c)(1)(ii) and (iii) will vary depending on how quickly information is discovered and how quickly the SCI event is resolved, but believes that a total of three updates for the two provisions is an appropriate estimate.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1618</SU>
                             35 SCI events × 3 updates per SCI event = 105 updates.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each information dissemination under Rule 1002(c)(1)(i) will require 7 hours.
                        <SU>1619</SU>
                        <FTREF/>
                         The Commission is not significantly increasing its burden estimate from the proposal because the Commission believes that the information required to be disseminated under Rule 1002(c)(1)(i) would likely already be collected for Commission notification under Rule 1002(b)(1) or (2).
                        <SU>1620</SU>
                        <FTREF/>
                         Therefore, contrary to the view of a commenter,
                        <SU>1621</SU>
                        <FTREF/>
                         the Commission does not believe that Rule 1002(c)(1)(i) will result in significantly higher burden for 
                        <PRTPAGE P="72388"/>
                        SCI entities than as estimated in the proposal. With respect to the view of a commenter that SCI entities would create different dissemination notices designed to address the concerns of different client segments,
                        <SU>1622</SU>
                        <FTREF/>
                         the Commission notes that Rule 1002(c) only specifies the general information that must be disseminated and does not require that SCI entities provide different information to different clients, even though SCI entities can decide to tailor the information dissemination for their clients.
                        <SU>1623</SU>
                        <FTREF/>
                         Based on the foregoing, the Commission estimates that each SCI entity would require an average of 245 hours annually to comply with Rule 1002(c)(1)(i),
                        <SU>1624</SU>
                        <FTREF/>
                         or 10,780 hours for all SCI entities.
                        <SU>1625</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1619</SU>
                             The 7 hours include 2.67 hours by an Attorney, 1 hour by a Compliance Manager, 0.5 hours by a Chief Compliance Officer, 0.5 hours by a General Counsel, 0.5 hours by a Director of Compliance, 1 hour by a Senior Systems Analyst, 0.5 hours by a Corporate Communications Manager, and 0.33 hours by a Webmaster. As compared to the estimated burden for proposed Rule 1000(b)(5)(i)(A), the Commission is estimating an additional 1 hour by a Compliance Manager, 0.5 hours by a General Counsel, 0.5 hours by a Chief Compliance Officer, 0.5 hours by a Director of Compliance, 1 hour by a Senior Systems Analyst, and 0.5 hours by a Corporate Communications Manager to reflect the view of commenters that the preparation for information dissemination would require the involvement of subject matter experts and mid-level and senior managers. 
                            <E T="03">See supra</E>
                             notes 1597-1598 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1620</SU>
                             
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 1594 and accompanying text (discussing the view of a commenter that since most of the work entailed in producing a notification relating to a dissemination SCI event would occur in connection with the Commission notification requirements under proposed Rule 1000(b)(4), the Commission's estimate of the burden of proposed Rule 1000(b)(5) is fairly accurate).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1621</SU>
                             
                            <E T="03">See supra</E>
                             notes 1600-1601 and 1607 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1622</SU>
                             
                            <E T="03">See supra</E>
                             notes 1599-1601 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1623</SU>
                             This commenter also noted that the Commission did not take into account the burden associated with addressing responses from an SCI entity's participants, members, or clients. 
                            <E T="03">See supra</E>
                             note 1604 and accompanying text. The Commission believes that currently, SCI entities already notify affected members or participants of certain systems issues. The Commission also believes that information regarding many systems issues that fall under the definition of major SCI event is already made available to members or participants of an SCI entity, and often to the public through the press or otherwise. Therefore, the Commission does not believe that the burden to respond to members or participants will be significantly higher than SCI entities' current practices in the absence of Regulation SCI. The Commission also notes that Rule 1002(c) does not impose any requirements related to responding to inquiries about the information dissemination.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1624</SU>
                             35 information dissemination each year × 7 hours per dissemination = 245 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1625</SU>
                             245 hours × 44 SCI entities = 10,780 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each update under Rules 1002(c)(1)(ii) and (iii) will require 13 hours.
                        <SU>1626</SU>
                        <FTREF/>
                         The Commission is not significantly increasing its burden estimate for proposed Rules 1000(b)(5)(i)(B) and (C) because the Commission believes that the information required to be disseminated under Rules 1002(c)(1)(ii) and (iii) would likely already be collected for Commission notification under Rules 1002(b)(2)-(4).
                        <SU>1627</SU>
                        <FTREF/>
                         Therefore, contrary to the view of a commenter,
                        <SU>1628</SU>
                        <FTREF/>
                         the Commission does not believe that Rules 1002(c)(1)(ii) and (iii) will result in significantly higher burden for SCI entities than as estimated in the SCI Proposal. Based on the foregoing, the Commission estimates that each SCI entity would require an average of 1,365 hours annually to comply with Rules 1002(c)(1)(ii) and (iii),
                        <SU>1629</SU>
                        <FTREF/>
                         or 60,060 hours for all SCI entities.
                        <SU>1630</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1626</SU>
                             The 13 hours include 4.67 hours by an Attorney, 2 hours by a Compliance Manager, 1 hour by a Chief Compliance Officer, 1 hour by a General Counsel, 1 hour by a Director of Compliance, 2 hours by a Senior Systems Analyst, 1 hour by a Corporate Communications Manager, and 0.33 hours by a Webmaster. As compared to the estimated burden for proposed Rule 1000(b)(5)(i)(B), the Commission is estimating an additional 2 hours by a Compliance Manager, 1 hour by a General Counsel, 1 hour by a Chief Compliance Officer, 1 hour by a Director of Compliance, 2 hours by a Senior Systems Analyst, and 1 hour by a Corporate Communications Manager to reflect the view of commenters that the preparation for information dissemination would require the involvement of subject matter experts and mid-level and senior managers. 
                            <E T="03">See supra</E>
                             notes 1597-1598 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1627</SU>
                             
                            <E T="03">See supra</E>
                             notes 1594 and 1620 accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1628</SU>
                             
                            <E T="03">See supra</E>
                             notes 1605-1606 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1629</SU>
                             105 updates each year × 13 hours per update = 1,365 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1630</SU>
                             1,365 hours × 44 SCI entities = 60,060 hours.
                        </P>
                    </FTNT>
                    <P>
                        The information required to be disseminated under Rule 1002(c)(2) for systems intrusions is similar to the information required to be disseminated under Rule 1002(c)(1)(i) in that both provisions require the dissemination of a summary description of an SCI event. Therefore, the Commission is using the burden estimate for Rule 1002(c)(1)(i) as the basis for its estimate for Rule 1002(c)(2). However, the Commission believes that Rule 1002(c)(2) will impose more burden than Rule 1002(c)(1)(i) because it also requires that the SCI entity determine whether dissemination of information regarding a particular systems intrusion would compromise the security of its SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and if the SCI entity determines that it would, to document the reason for such determination.
                        <SU>1631</SU>
                        <FTREF/>
                         Therefore, the Commission estimates that each SCI entity will spend an average of 10 hours to comply with Rule 1002(c)(2),
                        <SU>1632</SU>
                        <FTREF/>
                         or 440 hours for all SCI entities.
                        <SU>1633</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1631</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(c)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1632</SU>
                             The 10 hours include 3.67 hours by an Attorney, 1.5 hours by a Compliance Manager, 0.75 hours by a Chief Compliance Officer, 0.75 hours by a General Counsel, 0.75 hours by a Director of Compliance, 1.5 hour by a Senior Systems Analyst, 0.75 hours by a Corporate Communications Manager, and 0.33 hours by a Webmaster. 
                            <E T="03">See supra</E>
                             note 1619. The burden estimate for Rule 1002(c)(2) is approximately one and a half times the Commission's burden estimate for Rule 1002(c)(1)(i). (7 hours × 1.5 = 10.5 hours.)
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1633</SU>
                             10 hours × 44 SCI entities = 440 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that while SCI entities would handle internally some or most the work associated with compliance with Rule 1002(c),
                        <SU>1634</SU>
                        <FTREF/>
                         SCI entities would seek outside legal advice in the preparation of the information dissemination, at an average annual cost of $36,000 per SCI entity,
                        <SU>1635</SU>
                        <FTREF/>
                         or $1,584,000 for all SCI entities.
                        <SU>1636</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1634</SU>
                             The Commission recognizes that some SCI entities, such as certain SCI SROs, may have the in-house expertise to complete the work associated with compliance with Rule 1002(c), while other SCI entities may not and would therefore need to outsource some of the work associated with compliance with Rule 1002(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1635</SU>
                             The Commission is increasing its estimate of the outsourcing cost for compliance with Rule 1002(c) from its estimate in the proposal because its estimate of the number of information dissemination is higher than the estimated number in the proposal (
                            <E T="03">i.e.,</E>
                             from 15 to 36). In the SCI Proposal, the Commission estimated an outsourcing cost of $15,000 for 15 SCI events, which results in an average cost of $1,000 per SCI event. The Commission is continuing to estimate an average cost of $1,000 per SCI event subject to information dissemination, but is increasing the total outsourcing cost to $36,000 based on the increase in the number of estimated SCI events to 36. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             notes 1602-1603 and accompanying text (discussing the view of a commenter that SCI entities will likely engage outside counsel to review the facts and prepare the required documents to the extent an SCI event raises the possibility of litigation or reputational damage). 
                            <E T="03">But see</E>
                              
                            <E T="03">supra</E>
                             note 1602 and accompanying text (discussing the view of a commenter that none of the activities arising under proposed Rule 1000(b)(5) would be conducive to outsourcing).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1636</SU>
                             $36,000 × 44 SCI entities = $1,584,000.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Notification of Material Systems Changes</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that each SCI entity would have an average of 60 planned material systems changes each year, resulting in 60 advance notifications per year.
                        <SU>1637</SU>
                        <FTREF/>
                         The Commission estimated that each notification would require 2 hours to prepare and submit.
                        <SU>1638</SU>
                        <FTREF/>
                         For SCI entities that currently participate in the ARP Inspection Program, the Commission estimated that these entities would start from a baseline of fifty percent.
                        <SU>1639</SU>
                        <FTREF/>
                         The Commission also estimated that the initial and ongoing burden to submit semi-annual reports to the Commission pursuant to proposed Rule 1000(b)(8)(ii) would be 60 hours per report for each SCI entity.
                        <SU>1640</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1637</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18151. This estimate included instances where the information previously provided to the Commission regarding any planned material systems change becomes inaccurate. 
                            <E T="03">See id.</E>
                             at 18151, n. 431.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1638</SU>
                             
                            <E T="03">See id.</E>
                             at 18151. The 2 burden hours included 0.33 hours by an Attorney and 1.67 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. In determining this estimate, the Commission also considered its burden estimate for the same reporting requirement that was proposed for SB SEFs. 
                            <E T="03">See id.</E>
                             at 18151, n. 432.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1639</SU>
                             
                            <E T="03">See id.</E>
                             at 18151.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1640</SU>
                             
                            <E T="03">See id.</E>
                             at 18152. The 60 burden hours included 10 hours by an Attorney and 50 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with the ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 18152, n. 440.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the estimated burden under proposed Rule 1000(b)(6), some commenters noted that the Commission underestimated the number of material systems changes.
                        <SU>1641</SU>
                        <FTREF/>
                         For example, one 
                        <PRTPAGE P="72389"/>
                        commenter stated that, based on the proposed definition of material systems changes, each SCI entity could be reporting 60 material systems changes each week.
                        <SU>1642</SU>
                        <FTREF/>
                         One commenter noted that the burden estimate was effectively limited to ministerial tasks of producing material systems change notifications and did not take into account activities necessary to gather the information needed, to have appropriate confirmations from persons with knowledge of the material systems change, to provide for senior management review where appropriate, and to otherwise be in a position to draft the notification.
                        <SU>1643</SU>
                        <FTREF/>
                         One commenter stated that the Commission's estimate of 2 hours for each material systems change notice is too low because describing systems changes “involves the work of a tech-writer, who needs to collaborate with multiple groups on a project team, including the project manager, application development team and the testing and implementation teams.” 
                        <SU>1644</SU>
                        <FTREF/>
                         Similarly, one commenter noted that material systems change notifications would require substantial review by IT management, relevant business supervisors, as well as compliance staff, which would increase the burden estimate at least three-fold.
                        <SU>1645</SU>
                        <FTREF/>
                         One commenter noted that, based on its experience under the ARP Inspection Program, each notice under proposed Rule 1000(b)(6) would require at least 62 hours.
                        <SU>1646</SU>
                        <FTREF/>
                         This commenter also opined that the Commission mistakenly assumed that only a senior systems analyst and an attorney would be involved in the drafting of the notice.
                        <SU>1647</SU>
                        <FTREF/>
                         According to this commenter, a number of subject matter experts would need to be involved in drafting and reviewing these notices (
                        <E T="03">i.e.,</E>
                         Project Management, Developments, Quality Assurance, Performance Testing, Systems Engineering, Systems Architecture, Capacity Planning, Information Security, Business Continuity, Disaster Recovery, Legal, and Compliance).
                        <SU>1648</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1641</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 14. 
                            <E T="03">See also</E>
                             NYSE Letter at 26 (stating that if “material” were interpreted broadly to cover any functional change to an SCI system, the number of material systems changes 
                            <PRTPAGE/>
                            could measure in the thousands); and OTC Markets Letter at 21 (stating that it estimated it had a minimum of 430 reportable changes to its production systems over a ten-month time frame based on the proposed notification standards for material systems changes).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1642</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1643</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 35.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1644</SU>
                             
                            <E T="03">See</E>
                             OCC Letter at 15. This commenter stated that a large amount of information needs to be assembled from different groups and consolidated into a single report, which would include, for example: (i) A high-level description of the functionality and configuration of the affected systems; (ii) a description of the systems development process; (iii) the relationship to other systems; (iv) changes to production schedules due to the planned system change; (v) any effects on capacity; (vi) a description of test results; (vii) a summary of test results; (viii) contingency protocols (
                            <E T="03">i.e.,</E>
                             fallback options and disaster recovery measures); (ix) vulnerability assessments and security measures; and (x) whether an SEC rule filing under Rule 19b-4 has been made in connection with the system change notification. 
                            <E T="03">See id.</E>
                             at 15-16. According to this commenter, unless the Commission intends for the scope of information provided with these notices to be limited to high level descriptions and generally less detailed, the preparation of material systems change notices generally requires considerably more time than estimated. 
                            <E T="03">See id.</E>
                             at 16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1645</SU>
                             
                            <E T="03">See</E>
                             UBS Letter at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1646</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 42.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1647</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1648</SU>
                             
                            <E T="03">See id.</E>
                             at 42-43.
                        </P>
                    </FTNT>
                    <P>
                        On the other hand, one commenter stated that the Commission's estimate of the burden of proposed rule 1000(b)(8)(ii) is fairly accurate.
                        <SU>1649</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1649</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 37.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated its belief that none of the activities arising under proposed Rules 1000(b)(6) and (b)(8) would be conducive to outsourcing.
                        <SU>1650</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1650</SU>
                             
                            <E T="03">See id.</E>
                             at 36-37.
                        </P>
                    </FTNT>
                    <P>As discussed in detail above in Section IV.B.4, the Commission is not adopting the requirement for SCI entities to provide 30-day advance notifications or semi-annual reports of material systems changes. Also as discussed in detail above in Section IV.B.4, the Commission is not adopting the proposed definition of material systems change. Adopted Rule 1003(a) requires each SCI entity to submit quarterly reports describing completed, ongoing, and planned material changes to its SCI systems and security of indirect SCI systems during the prior, current, and subsequent calendar quarters. Adopted Rule 1003(b) additionally requires each SCI entity to promptly submit a supplemental report notifying the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a).</P>
                    <P>
                        With respect to the comment that, based on the proposed definition of material systems change, each SCI entity could be reporting 60 material systems changes each week (rather than each year), the Commission notes that it has not adopted the proposed definition of material systems change.
                        <SU>1651</SU>
                        <FTREF/>
                         Rather, as discussed above in Section IV.B.4, Rule 1003(a)(1) requires each SCI entity to establish reasonable criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material. Because Rule 1003(a)(1) allows each SCI entity to identify material systems changes, it is responsive to commenters' concern that the proposed definition was too broad and would result in an excessive number of notifications, and to commenters' suggestion that the definition should be revised. In particular, an SCI entity will have reasonable discretion in establishing the written criteria in order to capture the systems changes that it believes are material. Relatedly, with respect to commenters who specifically discussed the 30-day advance Commission notification requirement for material systems changes,
                        <SU>1652</SU>
                        <FTREF/>
                         the Commission notes that it is not adopting a 30-day advance notification requirement for each material systems change and is instead adopting a quarterly reporting requirement. Therefore, the Commission does not believe that it is necessary to estimate the number of material systems changes that each SCI entity will experience each year in order to estimate the burden associated with Rule 1003(a).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1651</SU>
                             
                            <E T="03">See supra</E>
                             notes 1641-1642 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1652</SU>
                             
                            <E T="03">See supra</E>
                             notes 1643-1648 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.4, Rule 1003(a) requires quarterly reports on material systems changes and supplemental reports under certain circumstances. Specifically, the quarterly reports are required to include a description of the completed, ongoing, and planned material changes to SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion.
                        <SU>1653</SU>
                        <FTREF/>
                         The Commission notes that the quarterly reports under Rule 1003(a) are required to include similar information as the information required under proposed Rule 1000(b)(8)(ii).
                        <SU>1654</SU>
                        <FTREF/>
                          
                        <PRTPAGE P="72390"/>
                        However, because the Commission is not requiring 30-day advance notification of each material systems change, SCI entities may need to spend more time to gather the information required to be included in the quarterly reports and to prepare the quarterly reports than the burden estimated for proposed Rule 1000(b)(8)(ii).
                        <SU>1655</SU>
                        <FTREF/>
                         Therefore, the Commission estimates that the initial and ongoing burden to comply with the quarterly reporting requirement would be 125 hours per report per SCI entity,
                        <SU>1656</SU>
                        <FTREF/>
                         or 500 hours annually per SCI entity 
                        <SU>1657</SU>
                        <FTREF/>
                         and 22,000 hours annually for all SCI entities.
                        <SU>1658</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1653</SU>
                             Contrary to the views of a commenter, these quarterly reports are limited in scope and do not require a detailed description of each systems change that the SCI entity determines to be material. 
                            <E T="03">See supra</E>
                             note 1644 (discussing the concerns of a commenter that a large amount of information would need to be assembled and consolidated into a single report, and that unless the Commission intends for the scope of the information provided to be limited to high level descriptions and generally less detailed, the preparation of material systems change notices will require considerably more time than estimated). The Commission notes that it intends for the quarterly report to only require the information necessary to allow the Commission and its staff to gain a sufficient understanding of the relevant material systems changes, which would aid the Commission and its staff in understanding the operations and functionality of the systems of an SCI entity and changes to such systems. Specifically, Rule 1003(a)(1) requires the quarterly report to “describe” the material systems changes and gives each SCI entity reasonable flexibility in how to describe it.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1654</SU>
                             Proposed Rule 1000(b)(8)(ii) required semi-annual reports that include a summary description of the progress of any material systems changes during the six-month period ending on June 30 or 
                            <PRTPAGE/>
                            December 31, and the date, or expected date, of completion of implementation of such changes.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1655</SU>
                             At the same time, the Commission believes that most, if not all, SCI entities already have some internal procedures for documenting all systems changes.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1656</SU>
                             In the SCI Proposal, the Commission preliminarily estimated 60 hours per semi-annual report. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18152. The Commission believes that, although Rule 1003(a)(1) requires quarterly reports rather than semi-annual reports, the reporting burden should not be reduced because the quarterly reports would cover material systems changes during the prior, current, and subsequent calendar quarters. On the other hand, the proposed semi-annual reports would have only covered material systems changes during the previous 6 months. In addition, because the Commission is not requiring 30-day advance notification of each material systems change, SCI entities may need more time to gather the information required to be included in the quarterly reports and to prepare the quarterly reports. Therefore, the Commission believes that it is appropriate to increase by fifty percent its estimate for the proposed semi-annual reporting requirement and to add additional personnel in response to comment. 
                            <E T="03">But see</E>
                              
                            <E T="03">supra</E>
                             note 1649 and accompanying text (discussing a commenter's view that the Commission's estimate of the burden under proposed Rule 1000(b)(8)(ii) is fairly accurate). The 125 burdens hours include 7.5 hours by an Attorney, 7.5 hours by a Compliance Manager, 5 hours by a Chief Compliance Officer, 30 hours by a Senior Business Analyst, and 75 hours by a Senior Systems Analyst. In addition to adding fifty percent to the estimated burden for proposed Rule 1000(b)(8)(ii), the Commission is estimating an additional 7.5 hours by a Compliance Manager (and decreasing the proposed burden estimate for Attorney from 10 hours to 7.5 hours), 5 hours by a Chief Compliance Officer, and 30 hours by a Senior Business Analyst to address commenters' view that the estimates in the SCI Proposal did not take into account the activities to gather the information needed, to have appropriate confirmations from persons with knowledge of the material systems change, and to provide for senior management review where appropriate (even though some of these commenters commented on the burden estimate for proposed Rule 1000(b)(6) only). 
                            <E T="03">See supra</E>
                             notes 1643, 1645, 1647, and 1648 and accompanying text. The Commission notes that the inclusion of Senior Business Analyst and Senior Systems Analyst is intended to cover subject matter experts for material systems changes, as suggested by a commenter. 
                            <E T="03">See supra</E>
                             note 1648 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1657</SU>
                             125 hours × 4 reports each year = 500 hours. The Commission recognizes that, to the extent an SCI entity develops a template for quarterly material systems change reports, the burden associated with creating future quarterly reports may be reduced.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1658</SU>
                             500 hours × 44 SCI entities = 22,000 hours.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the requirement under Rule 1003(a)(2) for supplemental material systems change reports, for purposes of this PRA analysis, the Commission estimates that most quarterly reports will not contain material errors or material omissions. Therefore, the Commission estimates that each SCI entity will submit 2 supplemental reports each year under Rule 1003(a)(2), in order to account for the few instances where a quarterly report must be corrected. The Commission estimates that the initial and ongoing burden to comply with the supplemental reporting requirement would be 15 hours per report per SCI entity,
                        <SU>1659</SU>
                        <FTREF/>
                         or 30 hours annually per SCI entity 
                        <SU>1660</SU>
                        <FTREF/>
                         and 1,320 hours annually for all SCI entities.
                        <SU>1661</SU>
                        <FTREF/>
                         The Commission believes that SCI entities would handle internally the work associated with reports required under Rule 1003(a).
                        <SU>1662</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1659</SU>
                             The 15 burdens hours include 2 hours by an Attorney, 2 hours by a Compliance Manager, 1 hour by a Chief Compliance Officer, 3 hours by a Senior Business Analyst, and 7 hours by a Senior Systems Analyst. The Commission believes that the burden associated with supplemental material systems change reports will be substantially lower than the burden associated with quarterly material systems change reports, but the same type of personnel will be involved the supplemental report as the quarterly report.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1660</SU>
                             15 hours × 2 reports each year = 30 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1661</SU>
                             30 hours × 44 SCI entities = 1,320 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1662</SU>
                             See supra note 1650 and accompanying text,
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. SCI Review</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that the initial and ongoing burden of conducting an SCI review and submitting the SCI review to senior management for review would be approximately 625 hours for each SCI entity.
                        <SU>1663</SU>
                        <FTREF/>
                         The Commission also estimated that each SCI entity would spend 1 hour to submit the SCI review to the Commission pursuant to proposed Rule 1000(b)(8)(i).
                        <SU>1664</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1663</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18151. The 625 burden hours included 80 hours by an Attorney, 170 hours by a Manager Internal Auditor, and 375 hours by a Senior Systems Analyst. 
                            <E T="03">See id.</E>
                             This estimate was the Commission's preliminary best estimate and was based on Commission staff's experience with the ARP Inspection Program. This estimate was also the same as the Commission's burden estimate for internal audits of SB SEFs. 
                            <E T="03">See id.</E>
                             at 18151, n. 437.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1664</SU>
                             
                            <E T="03">See id.</E>
                             at 18151. The 1 burden hour would be spent by an Attorney. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        With respect to the burden associated with SCI reviews, one commenter stated that the Commission's estimate of the burden of proposed Rule 1000(b)(7) is fairly accurate.
                        <SU>1665</SU>
                        <FTREF/>
                         According to this commenter, although the burden estimate of proposed Rule 1000(b)(7) did not require the inclusion of senior management's response, the Commission's estimate is sufficient to cover the burden on senior management to produce such response.
                        <SU>1666</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1665</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 36.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1666</SU>
                             
                            <E T="03">See id.</E>
                             at 37.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter noted that the Commission's estimate of the burden associated with SCI review is too low and that the SCI review will require over 1,200 burden hours.
                        <SU>1667</SU>
                        <FTREF/>
                         In connection with advocating for a risk-based approach for SCI reviews, one commenter noted that if it were to attempt to conduct all of the market-related technology application reviews that it currently conducts over four years during one year (excluding regulatory technology applications such as those related to member regulation), it would require approximately 6,400 to 8,320 hours.
                        <SU>1668</SU>
                        <FTREF/>
                         According to this commenter, significantly more resources would be required to conduct SCI reviews if the definition of SCI systems includes non-market regulatory and surveillance systems, and development and testing systems.
                        <SU>1669</SU>
                        <FTREF/>
                         One commenter noted that significant portions of the SCI review could be outsourced and that the Commission's estimate for the overall cost of outsourcing is reasonable, although some of the assumed hourly rates used in the SCI Proposal appear to be too low in the context of the current market environment.
                        <SU>1670</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1667</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1668</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 40. According to this commenter, it currently spends approximately 160 hours for each review of a technology application in connection with its regulatory audits, and currently it reviews between 10 and 13 market-related technology applications annually. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1669</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1670</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 36.
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that the Commission's estimate did not take into account the additional work that would be required by many different SCI entity associates, including managers and subject matter experts, in order to satisfy the requirements of proposed Rule 1000(b)(7).
                        <SU>1671</SU>
                        <FTREF/>
                         This commenter stated that the Commission incorrectly assumed that only an attorney, manager internal audit, and systems analyst would be required to work on the SCI review.
                        <SU>1672</SU>
                        <FTREF/>
                         According to this commenter, subject matter expertise that would be needed to perform such a review includes Product Managers, Project Managers, Developers, Quality Assurance staff, Systems Engineers, Systems Architects, Capacity Planners, Information Security experts, Business Continuity and Disaster Recovery staff, Compliance staff, and management.
                        <SU>1673</SU>
                        <FTREF/>
                         This commenter estimated that the 
                        <PRTPAGE P="72391"/>
                        annual burden under proposed Rule 1000(b)(7) would be 4,670 hours.
                        <SU>1674</SU>
                        <FTREF/>
                         According to this commenter, if the Commission intended SCI entities to conduct a broader scope review beyond those now required by the ARP Inspection Program, then the annual burden would be 11,199 hours.
                        <SU>1675</SU>
                        <FTREF/>
                         With respect to the burden estimate for proposed Rule 1000(b)(8)(i), one commenter stated that the estimate did not address the burden on senior management for reading, analyzing, and perhaps responding to the SCI review.
                        <SU>1676</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1671</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 44.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1672</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1673</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1674</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1675</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1676</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.5, the Commission is adopting SCI review-related requirements in Rule 1003(b), with some modifications from the proposal. Specifically, Rule 1003(b)(1) requires each SCI entity to conduct an SCI review of its compliance with Regulation SCI not less than once each calendar year, with an exception for penetration test reviews, which are required to be conducted not less than once every three years.
                        <SU>1677</SU>
                        <FTREF/>
                         As adopted, Rule 1003(b)(1)(ii) provides an exception for assessments of SCI systems directly supporting market regulation or market surveillance, which are required to be reviewed at a frequency based on the risk assessment conducted as part of the SCI review, but in no case less than once every three years.
                        <SU>1678</SU>
                        <FTREF/>
                         Rules 1003(b)(2) and (3) require each SCI entity to submit a report of the SCI review to senior management no more than 30 calendar days after completion of the review, and to submit the report to the Commission and to the board of directors of the SCI entity or the equivalent of such board, together with any response by senior management, within 60 calendar days after its submission to senior management.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1677</SU>
                             As proposed, the rule would have required penetration test reviews of the SCI entity's network, firewalls and development, testing, and production systems. However, consistent with modifications to the definition of SCI systems, references to development and test systems have been deleted in adopted Rule 1003(b)(1)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1678</SU>
                             These exceptions, along with the exclusion of development and testing systems from the definition of SCI systems, would address, at least in part, some commenters' concern regarding the scope of the definition of SCI systems and consequently the burden of the SCI review requirement. 
                            <E T="03">See supra</E>
                             notes 1669 and 1675 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        After considering the views of commenters, the Commission is not significantly increasing the burden estimate for compliance with Rules 1003(b)(1) and (2) from its estimates in the SCI Proposal. In particular, one commenter noted that the Commission's burden estimate for proposed Rule 1000(b)(7) was fairly accurate.
                        <SU>1679</SU>
                        <FTREF/>
                         Further, while other commenters advocated higher burden estimates for the SCI review requirement,
                        <SU>1680</SU>
                        <FTREF/>
                         the Commission notes that it has refined the definition of SCI systems (
                        <E T="03">e.g.,</E>
                         by eliminating development and testing systems, and focusing on 
                        <E T="03">market</E>
                         regulation and 
                        <E T="03">market</E>
                         surveillance systems) and has incorporated a risk-based approach to the frequency of testing for market regulation and market surveillance systems. The Commission estimates that the initial and ongoing burden of conducting an SCI review and submitting the SCI review to senior management of the SCI entity for review would be approximately 690 hours for each SCI entity,
                        <SU>1681</SU>
                        <FTREF/>
                         and 30,360 hours annually for all SCI entities.
                        <SU>1682</SU>
                        <FTREF/>
                         The Commission estimates that while SCI entities would handle internally some or most of the work associated with compliance with Rule 1003(b),
                        <SU>1683</SU>
                        <FTREF/>
                         SCI entities would outsource some of the work associated with an SCI review, at an average annual cost of $50,000 per SCI entity,
                        <SU>1684</SU>
                        <FTREF/>
                         or $2,200,000 for all SCI entities.
                        <SU>1685</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1679</SU>
                             
                            <E T="03">See supra</E>
                             note 1665 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1680</SU>
                             
                            <E T="03">See supra</E>
                             notes 1667-1668 and 1675 and accompanying text. These commenters estimated a range of 1,200 to 8,320 burden hours. In response to the commenter that stated that it currently spends approximately 160 hours for each review of a technology application and it reviews between 10 and 13 market-related technology applications annually, the Commission notes that the burden estimates in this section only include the incremental burden associated with the rule above what the Commission estimates that SCI entities are already performing. To the extent an SCI entity already reviews certain of its systems, the additional burden imposed by Rule 1003(b) will be lower than for other SCI entities.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1681</SU>
                             The 690 hours include 80 hours by an Attorney, 35 hours by a Compliance Manager, 5 hours by a General Counsel, 20 hours by a Chief Compliance Officer, 5 hours by a Director of Compliance, 170 hours by a Manager Internal Audit, and 375 hours by a Senior Systems Analyst. As compared to the estimated burden for proposed Rule 1000(b)(7), the Commission is estimating an additional 35 hours by a Compliance Manager, 5 hours by a General Counsel, 20 hours by a Chief Compliance Officer, and 5 hours by a Director of Compliance, to reflect the view of commenters that managers would be involved in satisfying the requirements related to SCI review. 
                            <E T="03">See supra</E>
                             notes 1671-1675 and accompanying text. The Commission notes that the 20-hour burden estimate for the Chief Compliance Officer includes the time spent by other members of the senior management team (other than the General Counsel, who has a separate burden estimate). 
                            <E T="03">See supra</E>
                             Section IV.B.5 (discussing senior management involvement in compliance with Rule 1003(b)). The Commission notes that the inclusion of Manager Internal Audit and Senior Systems Analyst is intended to cover subject matter experts related to systems review (
                            <E T="03">e.g.,</E>
                             information security experts, systems engineers, quality assurance staff). 
                            <E T="03">See supra</E>
                             notes 1671-1675 and accompanying text. The Commission also believes that some SCI entities already conduct annual reviews of its systems, and therefore may incur less burden than other SCI entities in complying with Rule 1003(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1682</SU>
                             690 hours × 44 SCI entities = 30,360 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1683</SU>
                             As noted above, one commenter suggested that significant portions of the SCI review may be outsourced. This commenter also noted that the Commission's estimate of the overall cost of outsourcing is reasonable, although it believed some of the assumed hourly rates appear to be too low in the context of current market environment. 
                            <E T="03">See supra</E>
                             note 1670 and accompanying text. The Commission acknowledges that some SCI entities may outsource work related to SCI review to more expensive outside firms than others. On average, the Commission believes its hourly rate of $400 for outsourcing continues to be appropriate.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1684</SU>
                             125 hours × $400 = $50,000. The Commission believes that SCI entities may outsource some of the legal and audit work associated with an SCI review. In particular, the Commission estimates that, on average, an SCI entity will outsource 40 hours of legal work and 85 hours of audit work (or half of the hour burden estimates for Attorney and Manager Internal Audit). 
                            <E T="03">See supra</E>
                             note 1681.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1685</SU>
                             $50,000 × 44 SCI entities = $2,200,000.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the comment that the burden estimate for proposed Rule 1000(b)(8)(i) failed to account for the burden on senior management for reviewing and responding to the report of the SCI review,
                        <SU>1686</SU>
                        <FTREF/>
                         the Commission notes that proposed Rule 1000(b)(8)(i) and adopted Rule 1003(b)(3) do not require senior management to respond to the report of the SCI review. Rather, Rule 1003(b)(3) only requires an SCI entity to submit the already prepared report of the SCI review, and response by senior management if there was any, to the Commission and to the board of directors of the SCI entity or the equivalent of such board. Moreover, the Commission is including in its burden estimate for Rules 1003(b)(1) and (2) the burden for senior management review of the report for the SCI review. Therefore, with respect to Rule 1003(b)(3), the Commission estimates that each SCI entity would require 1 hour per year to submit the report of the SCI review and any response by senior management to the Commission and to the board of directors of the SCI entity or the equivalent of such board,
                        <SU>1687</SU>
                        <FTREF/>
                         for a 
                        <PRTPAGE P="72392"/>
                        burden of 44 hours for all SCI entities.
                        <SU>1688</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1686</SU>
                             
                            <E T="03">See supra</E>
                             notes 1666 and 1676 and accompanying text. One of these commenters, however, noted that the Commission's estimated burden for proposed Rule 1000(b)(7) is fairly accurate, even though it did not include senior management's response. 
                            <E T="03">See supra</E>
                             notes 1665-1666 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1687</SU>
                             The 1 hour would be spent by an Attorney. This estimate is unchanged from the burden estimate for proposed Rule 1000(b)(8)(i), which only required submission of the report and any response by senior management to the Commission. The Commission believes that the additional burden for submitting the same report and response to the SCI entity's board of directors or the equivalent of such board would be modest, and thus the estimate of one hour remains unchanged from the burden estimate for proposed Rule 1000(b)(8)(i), which required submission of the report and response by senior management only to the Commission.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1688</SU>
                             1 hour × 44 SCI entities = 44 hours.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">e. Access to EFFS</HD>
                    <P>
                        As noted above, to access EFFS, an SCI entity will submit to the Commission an EAUF to register each individual at the SCI entity who will access the EFFS system on behalf of the SCI entity. The Commission is including in its burden estimates the burden for completing the EAUF for each individual at an SCI entity that will request access to EFFS. The Commission estimates that initially, on average, two individuals at each SCI entity will request access to EFFS through the EAUF, and each EAUF would require 0.15 hours to complete and submit. Therefore, each SCI entity would initially require 0.3 hours to complete the requisite EAUFs,
                        <SU>1689</SU>
                        <FTREF/>
                         or approximately 13 hours for all SCI entities.
                        <SU>1690</SU>
                        <FTREF/>
                         The Commission also estimates that annually, on average, one individual at each SCI entity will request access to EFFS through EAUF.
                        <SU>1691</SU>
                        <FTREF/>
                         Therefore, the ongoing burden to complete the EAUF would be 0.15 hours annually for each SCI entity,
                        <SU>1692</SU>
                        <FTREF/>
                         or approximately 7 hours annually for all SCI entities.
                        <SU>1693</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1689</SU>
                             0.15 hours per EAUF × 2 individuals = 0.3 hours per SCI entity. These estimates are based on Commission staff's experience with EFFS and EAUFs pursuant to Rule 19b-4 under the Exchange Act. The 0.15 hours would be spent by an Attorney. The Commission acknowledges that an SCI SRO may initially submit fewer than two EAUFs because certain individuals at SCI SROs currently already have access to EFFS, whereas an SCI entity other than an SCI SRO may submit more than two EAUFs initially because it has not previously submitted filings through EFFS. Therefore, the Commission believes it is appropriate to estimate that, on average, each SCI entity will submit two EAUFs initially.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1690</SU>
                             0.30 hours × 44 SCI entities = 13.2 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1691</SU>
                             The Commission estimates that annually, on average, one individual at each SCI entity will request access to EFFS through EAUF to account for the possibility that an individual who previously had access to EFFS may no longer be designated as needing such access.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1692</SU>
                             0.15 hours per EAUF × 1 individual = 0.15 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1693</SU>
                             0.15 hours × 44 entities = 6.6 hours.
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission estimates that each SCI entity will designate two individuals to sign Form SCI each year. An individual signing a Form SCI must obtain a digital ID, at the cost of approximately $25 each year. Therefore, each SCI entity would require approximately $50 annually to obtain digital IDs for the individuals with access to EFFS for purposes of signing Form SCI,
                        <SU>1694</SU>
                        <FTREF/>
                         or approximately $2,200 for all SCI entities.
                        <SU>1695</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1694</SU>
                             $25 per digital ID × 2 individuals = $50 per SCI entity.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1695</SU>
                             $50 × 44 SCI entities = $2,200.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Requirements To Take Corrective Actions and Identify Critical SCI Systems, Major SCI Events, De Minimis SCI Events, and Material Systems Changes</HD>
                    <P>The rules under Regulation SCI that would result in SCI entities establishing additional processes for compliance are discussed more fully in Sections IV.A, IV.B.3.b, and IV.B.4 above.</P>
                    <HD SOURCE="HD3">a. Corrective Actions</HD>
                    <P>
                        In the SCI Proposal, the Commission noted that, although SCI entities already take corrective action in response to systems issues, proposed Rule 1000(b)(3) would likely result in SCI entities revising their policies regarding taking corrective actions.
                        <SU>1696</SU>
                        <FTREF/>
                         The Commission estimated that the initial burden would be 42 hours per SCI entity,
                        <SU>1697</SU>
                        <FTREF/>
                         and the ongoing burden would be 12 hours annually per SCI entity.
                        <SU>1698</SU>
                        <FTREF/>
                         The Commission estimated that SCI entities would establish the process for compliance with proposed Rule 1000(b)(3) internally.
                        <SU>1699</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1696</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18152.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1697</SU>
                             
                            <E T="03">See id.</E>
                             The 42 burden hours included 16 hours by a Compliance Manager, 16 hours by an Attorney, 5 hours by a Senior Systems Analyst, and 5 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                             This estimate was based on the Commission's burden estimate for proposed Rule 1000(b)(1). 
                            <E T="03">See id.</E>
                             at 18152, n. 442.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1698</SU>
                             
                            <E T="03">See id.</E>
                             at 18152. The 12 burden hours included 6 hours by a Compliance Manager and 6 hours by an Attorney. 
                            <E T="03">See id.</E>
                             This estimate was based on the Commission's burden estimate for proposed Rule 1000(b)(1). 
                            <E T="03">See id.</E>
                             at 18152, n. 443.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1699</SU>
                             
                            <E T="03">See id.</E>
                             at 18152, n. 442.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated its belief that basing the estimate for proposed Rule 1000(b)(3) on the percentage of the burden estimate under proposed Rule 1000(b)(1) is appropriate.
                        <SU>1700</SU>
                        <FTREF/>
                         This commenter also noted that while the taking of corrective action might be wholly or partially outsourced with regard to systems development activities, the establishment of policies and procedures with respect to corrective action would not be conducive to outsourcing.
                        <SU>1701</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1700</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 31-32.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1701</SU>
                             
                            <E T="03">See id.</E>
                             at 32.
                        </P>
                    </FTNT>
                    <P>
                        As discussed in detail above in Section IV.B.3.b, the Commission continues to require each SCI entity to begin to take appropriate corrective action in Rule 1002(a), but the corrective action requirement is triggered when any responsible SCI personnel has a reasonable basis to conclude that an SCI event has occurred.
                        <SU>1702</SU>
                        <FTREF/>
                         The Commission continues to believe that all SCI entities, regardless of whether they participate in the ARP Inspection Program, already take corrective action in response to systems issues and have some internal processes with respect to corrective action.
                        <SU>1703</SU>
                        <FTREF/>
                         The Commission also continues to believe that Rule 1002(a) will likely result in SCI entities revising their policies, which will help to ensure that their information technology staff has the ability to access systems in order to take appropriate corrective actions.
                        <SU>1704</SU>
                        <FTREF/>
                         The Commission therefore believes that Rule 1002(a) may impose a one-time implementation burden on SCI entities associated with developing such a process, and periodic burdens in reviewing that process. The Commission estimates that the initial burden to implement such a process would be 114 hours per SCI entity,
                        <SU>1705</SU>
                        <FTREF/>
                         or 5,016 hours for all SCI entities.
                        <SU>1706</SU>
                        <FTREF/>
                         The Commission also estimates that the ongoing burden to review such a process would be 39 hours annually per SCI entity,
                        <SU>1707</SU>
                        <FTREF/>
                         or 
                        <PRTPAGE P="72393"/>
                        1,716 hours annually for all SCI entities.
                        <SU>1708</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1702</SU>
                             
                            <E T="03">See</E>
                             Rule 1002(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1703</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18152.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1704</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1705</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and Rule 1002(a) both would result in policies and procedures or processes. As noted above, one commenter stated that basing the burden estimate for proposed Rule 1000(b)(3) on the burden estimate under proposed Rule 1000(b)(1) is appropriate. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text. Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the establishment of six policies and procedures at a minimum and Rule 1002(a) would result in the establishment of one set of policies and procedures, the Commission estimates that the initial staff burden to draft the policies and procedures for Rule 1002(a) is one-sixth of the initial staff burden to draft the policies and procedures required by Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 504 hours ÷ 6 = 84 hours. The 84 burden hours include 32 hours by a Compliance Manager, 32 hours by an Attorney, 10 hours by a Senior Systems Analyst, and 10 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1443. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures required by Rule 1002(a). 84 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 114 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1706</SU>
                             114 hours × 44 SCI entities = 5,016 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1707</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and 1002(a) both would result in policies and procedures or processes. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text (stating that basing the burden estimate for proposed Rule 1000(b)(3) on the burden estimate under proposed 1000(b)(1) is appropriate). Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the maintenance of six policies and procedures at a minimum and 1002(a) would result in the maintenance of one set of policies and procedures, the Commission estimates that the ongoing staff burden under 1002(a) is one-sixth of the ongoing staff burden under Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 144 hours ÷ 6 = 24 hours. The 24 burden hours include 9 hours by a Compliance Manager, 9 hours by an Attorney, 3 hours by a Senior Systems Analyst, and 3 hours by an Operations Specialist. This burden hour 
                            <PRTPAGE/>
                            allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1445. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures required by Rule 1002(a). 24 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 39 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1708</SU>
                             39 hours × 44 SCI entities = 1,716 hours.
                        </P>
                    </FTNT>
                    <P>
                        The Commission continues to believe that SCI entities will conduct internally most of the work related to their corrective action procedures. As noted by a commenter, the establishment of policies and procedures with respect to corrective action would not be conducive to outsourcing.
                        <SU>1709</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1709</SU>
                             
                            <E T="03">See supra</E>
                             note 1701 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Identification of Critical SCI Systems, Major SCI Events, De Minimis SCI Events, and Material Systems Changes</HD>
                    <P>
                        In the SCI Proposal, the Commission estimated that requirements under the proposal with respect to immediate notification SCI events and dissemination SCI events may impose burdens on SCI entities in developing and reviewing a process to ensure that they are able to quickly and correctly make a determination regarding the nature of an SCI event.
                        <SU>1710</SU>
                        <FTREF/>
                         For SCI entities that do not participate in the ARP Inspection Program, the Commission estimated that the initial burden would be 42 hours per SCI entity 
                        <SU>1711</SU>
                        <FTREF/>
                         and the ongoing burden would be 12 hours annually per SCI entity.
                        <SU>1712</SU>
                        <FTREF/>
                         For SCI entities that currently participate in the ARP Inspection Program, the Commission estimated that the initial burden would be 21 hours per SCI entity 
                        <SU>1713</SU>
                        <FTREF/>
                         and the ongoing burden would be 6 hours annually per SCI entity.
                        <SU>1714</SU>
                        <FTREF/>
                         The Commission believed that SCI entities would internally establish the process for determining whether an SCI event is an immediate notification SCI event or dissemination SCI event.
                        <SU>1715</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1710</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18152.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1711</SU>
                             
                            <E T="03">See id.</E>
                             at 18153. The 42 burden hours included 16 hours by a Compliance Manager, 16 hours by an Attorney, 5 hours by a Senior Systems Analyst, and 5 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                             This estimate was based on the Commission's burden estimate for proposed Rule 1000(b)(1). 
                            <E T="03">See id.</E>
                             at 18153, n. 448.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1712</SU>
                             
                            <E T="03">See id.</E>
                             at 18153. The 12 burden hours included 6 hours by a Compliance Manager and 6 hours by an Attorney. 
                            <E T="03">See id.</E>
                             This estimate was based on the Commission's burden estimate for proposed Rule 1000(b)(1). 
                            <E T="03">See id.</E>
                             at 18153, n. 452.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1713</SU>
                             
                            <E T="03">See id.</E>
                             at 18153. The 21 burden hours included 8 hours by a Compliance Manager, 8 hours by an Attorney, 2.5 hours by a Senior Systems Analyst, and 2.5 hours by an Operations Specialist. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1714</SU>
                             
                            <E T="03">See id.</E>
                             The 6 burden hours included 3 hours by a Compliance Manager and 3 hours by an Attorney. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1715</SU>
                             
                            <E T="03">See id.</E>
                             at 18153, n. 448, n. 450, n. 452, and n. 454.
                        </P>
                    </FTNT>
                    <P>
                        One commenter stated its belief that the Commission's burden estimate for policies and procedures to identify an SCI event as an immediate notification SCI event or dissemination SCI event was effectively limited to ministerial tasks of producing such policies and procedures in isolation from other organizational activities and needs, and took into account only minimal supervisory or decision-making activities, therefore significantly underestimated the total burden of compliance with this provision.
                        <SU>1716</SU>
                        <FTREF/>
                         This commenter urged the Commission to adjust the estimate in a manner similar to this commenter's suggestion with regard to proposed Rules 1000(b)(1) and (2).
                        <SU>1717</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1716</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 32.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1717</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.4, Rule 1003(a)(1) requires each SCI entity to establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material. As noted in the SCI Proposal, because the ARP Inspection Program already provides for the reporting “significant systems changes” to Commission staff, the Commission believes that, as compared to entities that do not participate in the ARP Inspection Program, entities that currently participate in the ARP Inspection Program would already have some internal processes for determining the significance of a systems issue or systems change. Therefore, the Commission continues to estimate a 50% baseline for the staff burden estimates for SCI entities that currently participate in the ARP Inspection Program.
                        <SU>1718</SU>
                        <FTREF/>
                         However, the Commission does not believe that a 50% baseline would be appropriate for these SCI entities in terms of senior management review. The Commission believes that, although these entities already have some internal processes for determining the significance of a systems change, their senior management would require the same number of hours as other SCI entities to review and ensure that the process is reasonable, as required by Rule 1003(a)(1). The Commission continues to believe that SCI entities will internally establish and maintain the policies and procedures required by Rule 1003(a)(1).
                    </P>
                    <FTNT>
                        <P>
                            <SU>1718</SU>
                             The 50% baseline for ARP participants is consistent with the baseline for the Rule 1001(a) burden estimates.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each SCI entity that does not participate in the ARP Inspection Program would require 114 hours initially to establish the criteria for identifying material systems changes,
                        <SU>1719</SU>
                        <FTREF/>
                         or 1,596 hours for all such SCI entities.
                        <SU>1720</SU>
                        <FTREF/>
                         The Commission also estimates that each SCI entity that does not participate in the ARP Inspection Program would require 39 hours annually to review and update the criteria for identifying material systems changes,
                        <SU>1721</SU>
                        <FTREF/>
                         or 546 hours for all such SCI entities.
                        <SU>1722</SU>
                        <FTREF/>
                         The Commission estimates that each SCI entity that currently participates in the 
                        <PRTPAGE P="72394"/>
                        ARP Inspection Program would require 72 hours initially to establish the criteria for identifying material systems changes,
                        <SU>1723</SU>
                        <FTREF/>
                         or 2,160 hours for all such SCI entities.
                        <SU>1724</SU>
                        <FTREF/>
                         The Commission also estimates that each SCI entity that currently participates in the ARP Inspection Program would require 27 hours annually to review and update the criteria,
                        <SU>1725</SU>
                        <FTREF/>
                         or 810 hours for all such SCI entities.
                        <SU>1726</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1719</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and Rule 1003(a)(1) both require policies and procedures or processes. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text (stating, in the context of proposed Rule 1000(b)(3), that basing the burden estimate for a set of policies and procedures or processes on the burden estimate under proposed 1000(b)(1) is appropriate). Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the establishment of six policies and procedures at a minimum and Rule 1003(a)(1) requires the establishment of one set of criteria, the Commission estimates that the initial staff burden to draft the criteria required by Rule 1003(a)(1) is one-sixth of the initial staff burden to draft the policies and procedures required by Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 504 hours ÷ 6 = 84 hours. The 84 burden hours include 32 hours by a Compliance Manager, 32 hours by an Attorney, 10 hours by a Senior Systems Analyst, and 10 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1443. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures required by Rule 1003(a)(1). 84 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 114 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1720</SU>
                             114 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 1,596 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1721</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and Rule 1003(a)(1) both require policies and procedures or processes. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text (stating, in the context of proposed Rule 1000(b)(3), that basing the burden estimate for a set of policies and procedures or processes on the burden estimate under proposed 1000(b)(1) is appropriate). Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the maintenance of six policies and procedures at a minimum and Rule 1003(a)(1) requires the maintenance of one set of criteria, the Commission estimates that the ongoing staff burden under 1003(a)(1) is one-sixth of the ongoing staff burden under Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 144 hours ÷ 6 = 24 hours. The 24 burden hours include 9 hours by a Compliance Manager, 9 hours by an Attorney, 3 hours by a Senior Systems Analyst, and 3 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1445. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures required by Rule 1003(a)(1). 24 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 39 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1722</SU>
                             39 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 546 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1723</SU>
                             84 hours ÷ 2 = 42 hours. The 42 burden hours include 16 hours by a Compliance Manager, 16 hours by an Attorney, 5 hours by a Senior Systems Analyst, and 5 hours by an Operations Specialist. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures required by Rule 1003(a)(1). 42 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 72 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1724</SU>
                             72 hours × 30 SCI entities that participate in the ARP Inspection Program = 2,160 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1725</SU>
                             24 hours ÷ 2 = 12 hours. The 12 burden hours include 4.5 hours by a Compliance Manager, 4.5 hours by an Attorney, 1.5 hours by a Senior Systems Analyst, and 1.5 hours by an Operations Specialist. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures required by Rule 1003(a)(1). 12 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 27 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1726</SU>
                             27 hours × 30 SCI entities that participate in the ARP Inspection Program = 810 hours.
                        </P>
                    </FTNT>
                    <P>As adopted, Regulation SCI requires SCI entities to identify certain types of events, systems, and changes. Specifically, Rule 1000 defines “critical SCI systems” as any SCI systems of, or operated by or on behalf of, an SCI entity that: (1) Directly support functionality relating to (i) clearance and settlement systems of clearing agencies; (ii) openings, reopenings, and closings on the primary listing market; (iii) trading halts; (iv) initial public offerings; (v) the provision of consolidated market data; or (vi) exclusively-listed securities; or (2) provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets. Rule 1000 defines “major SCI event” as an SCI event that has had, or the SCI entity reasonably estimates would have any impact on a critical SCI system or a significant impact on the SCI entity's operations or on market participants. Because Rule 1001(a)(2)(v) requires business continuity and disaster recovery plans that are reasonably designed to achieve two-hour resumption of critical SCI systems following a wide-scale disruption, each SCI entity needs to identify its critical SCI systems. In addition, each SCI entity needs to identify its critical SCI systems because the definition of major SCI event includes an SCI event that has had, or the SCI entity reasonably estimates would have, any impact on a critical SCI system. Further, when an SCI event occurs, an SCI entity needs to determine whether the event is a major SCI event, because Rule 1002(c)(3) requires an SCI entity to disseminate information regarding major SCI events to all of its member or participants. In addition, Rules 1002(b) and (c) provide certain exceptions from the Commission notification and information dissemination requirements for any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. Therefore, when SCI events occur, an SCI entity needs to determine whether they are de minimis SCI events.</P>
                    <P>
                        The Commission believes that the identification of critical SCI systems, major SCI events, and de minimis SCI events will impose an initial one-time implementation burden on SCI entities in developing processes to quickly and correctly identify the nature of a system or event.
                        <SU>1727</SU>
                        <FTREF/>
                         The identification of these systems and events may also impose periodic burdens on SCI entities in reviewing and updating the processes. As noted in the SCI Proposal, because the ARP Inspection Program already provides for the reporting “significant systems changes” and “significant systems outages” to Commission staff, the Commission believes that, as compared to entities that do not participate in the ARP Inspection Program, entities that currently participate in the ARP Inspection Program would already have some internal processes for determining the significance of a systems issue or systems change. Therefore, the Commission estimates a 50% baseline for the staff burden for SCI entities that currently participate in the ARP Inspection Program.
                        <SU>1728</SU>
                        <FTREF/>
                         However, the Commission does not believe that a 50% baseline would be appropriate for these SCI entities in terms of senior management review. The Commission believes that SCI entities will internally establish and maintain the policies and procedures regarding the identification of critical SCI systems, major SCI events, and de minimis SCI events.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1727</SU>
                             The Commission's approach with respect to SCI events and SCI systems is responsive to some commenters' suggestion for a risk-based regime. 
                            <E T="03">See, e.g.,</E>
                              
                            <E T="03">supra</E>
                             notes 784-789 and accompanying text (discussing commenters' suggestions for revising the Commission reporting requirement).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1728</SU>
                             The 50% baseline for ARP participants is consistent with the baseline for the Rule 1001(a) burden estimates.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that each SCI entity that does not participate in the ARP Inspection Program would require 198 hours initially to establish the criteria for identifying certain systems and events,
                        <SU>1729</SU>
                        <FTREF/>
                         or 2,772 hours for all such SCI entities.
                        <SU>1730</SU>
                        <FTREF/>
                         The Commission also estimates that each SCI entity that does not participate in the ARP Inspection Program would require 63 hours annually to review and update such criteria,
                        <SU>1731</SU>
                        <FTREF/>
                         or 882 hours 
                        <PRTPAGE P="72395"/>
                        for all such SCI entities.
                        <SU>1732</SU>
                        <FTREF/>
                         The Commission estimates that each SCI entity that currently participates in the ARP Inspection Program would require 114 hours initially to establish the criteria for identifying certain systems and events,
                        <SU>1733</SU>
                        <FTREF/>
                         or 3,420 hours for all such SCI entities.
                        <SU>1734</SU>
                        <FTREF/>
                         The Commission also estimates that each SCI entity that currently participates in the ARP Inspection Program would require 39 hours annually to review and update such criteria,
                        <SU>1735</SU>
                        <FTREF/>
                         or 1,170 hours for all such SCI entities.
                        <SU>1736</SU>
                        <FTREF/>
                         The Commission believes that the revised burden estimates for establishing policies and procedures to identify certain systems and events are responsive to a commenter's concern that the estimate in the SCI Proposal only included ministerial tasks and minimal supervisory activities.
                        <SU>1737</SU>
                        <FTREF/>
                         Specifically, the Commission increased from the proposal the estimated burden hours for the personnel involved in establishing such policies and procedures, and included senior level review by adding burden estimates for the Chief Compliance Officer and Director of Compliance. Moreover, because these revised burden estimates are based on the revised burden estimates for Rule 1001(a), these estimates are responsive to a commenter's suggestion that they be revised in a manner similar to its suggestions with respect to proposed Rules 1000(b)(1) and (2).
                        <SU>1738</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1729</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and the identification of certain systems and events both would result in policies and procedures or processes. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text (stating, in the context of proposed Rule 1000(b)(3), that basing the burden estimate for a set of policies and procedures or processes on the burden estimate under proposed 1000(b)(1) is appropriate). Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the establishment of six policies and procedures at a minimum and the identification of certain systems and events could result in the establishment of two policies and procedures (
                            <E T="03">i.e.,</E>
                             one for systems and one for events), the Commission estimates that the initial staff burden to draft the policies and procedures to identify certain systems and events is one-third of the initial staff burden to draft the policies and procedures required by Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 504 hours ÷ 3 = 168 hours. The 168 burden hours include 64 hours by a Compliance Manager, 64 hours by an Attorney, 20 hours by a Senior Systems Analyst, and 20 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1443. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures to identify certain systems and events. 168 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 198 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1730</SU>
                             198 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 2,772 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1731</SU>
                             This estimate is based on the Commission's burden estimate for Rule 1001(a), because Rule 1001(a) and the identification of certain systems and events both would result in policies and procedures or processes. 
                            <E T="03">See supra</E>
                             note 1700 and accompanying text (stating, in the context of proposed Rule 1000(b)(3), that basing the burden estimate for a set of policies and procedures or processes on the burden estimate under proposed 1000(b)(1) is appropriate). Because Rule 1001(a) (excluding Rule 1001(a)(2)(vi)) requires the maintenance of six policies and procedures at a minimum and the identification of certain systems and events could result in the maintenance of two policies and procedures, the Commission estimates that the ongoing staff burden to draft the policies and procedures to identify certain systems and events is one-third of the ongoing staff burden under Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 144 hours ÷ 3 = 48 hours. The 48 burden hours include 18 hours by a Compliance Manager, 18 hours by an Attorney, 6 hours by a Senior Systems Analyst, and 6 hours by an Operations Specialist. This burden hour allocation is based on the allocation for Rule 1001(a) (excluding Rule 1001(a)(2)(vi)). 
                            <E T="03">See supra</E>
                             note 1445. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures for identifying certain 
                            <PRTPAGE/>
                            systems and events. 48 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 63 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1732</SU>
                             63 hours × 14 SCI entities that do not participate in the ARP Inspection Program = 882 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1733</SU>
                             168 hours ÷ 2 = 84 hours. The 84 burden hours include 32 hours by a Compliance Manager, 32 hours by an Attorney, 10 hours by a Senior Systems Analyst, and 10 hours by an Operations Specialist. The Commission also estimates that a Chief Compliance Officer will spend 20 hours and a Director of Compliance will spend 10 hours reviewing the policies and procedures for identifying certain systems and events. 84 hours + Chief Compliance Officer at 20 hours + Director of Compliance at 10 hours = 114 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1734</SU>
                             114 hours × 30 SCI entities that participate in the ARP Inspection Program = 3,420 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1735</SU>
                             48 hours ÷ 2 = 24 hours. The 24 burden hours include 9 hours by a Compliance Manager, 9 hours by an Attorney, 3 hours by a Senior Systems Analyst, and 3 hours by an Operations Specialist. The Commission also estimates that a Chief Compliance Officer will spend 10 hours and a Director of Compliance will spend 5 hours reviewing the policies and procedures for identifying certain systems and events. 24 hours + Chief Compliance Officer at 10 hours + Director of Compliance at 5 hours = 39 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1736</SU>
                             39 hours × 30 SCI entities that participate in the ARP Inspection Program = 1,170 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1737</SU>
                             
                            <E T="03">See supra</E>
                             note 1716 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1738</SU>
                             
                            <E T="03">See supra</E>
                             note 1717 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Recordkeeping Requirements</HD>
                    <P>
                        In the SCI Proposal, the Commission noted that it is not proposing a new recordkeeping requirement for SCI SROs because the documents relating to compliance with proposed Regulation SCI are subject to their existing recordkeeping and retention requirements under Rule 17a-1 under the Act.
                        <SU>1739</SU>
                        <FTREF/>
                         The Commission therefore noted its belief that the proposed recordkeeping requirements would not result in any burden that is not already accounted for in the Commission's burden estimates for Rule 17a-1.
                        <SU>1740</SU>
                        <FTREF/>
                         With respect to SCI entities other than SCI SROs, the Commission estimated that the initial and ongoing burdens to make, keep, and preserve records relating to compliance with proposed Regulation SCI would be approximately 25 hours annually per SCI entity.
                        <SU>1741</SU>
                        <FTREF/>
                         The Commission also estimated that each SCI entity other than an SCI SRO would incur a one-time burden to set up or modify an existing recordkeeping system to comply with the proposed recordkeeping requirements.
                        <SU>1742</SU>
                        <FTREF/>
                         Specifically, the Commission estimated that for each SCI entity other than an SCI SRO, setting up or modifying a recordkeeping system would create an initial burden of 170 hours and $900 in information technology costs for purchasing recordkeeping software.
                        <SU>1743</SU>
                        <FTREF/>
                         Further, the Commission noted its belief that proposed Rule 1000(c)(3), which would require an SCI entity, upon or immediately prior to ceasing to do business or ceasing to be registered under the Exchange Act, to take all necessary action to ensure that the records required to be made, kept, and preserved by Rules 1000(c)(1) and (2) remain accessible to the Commission and its representatives in the manner and for the remainder of the period required by Rule 1000(c), would not result in any additional paperwork burden that is not already accounted for in the Commission's burden estimates for proposed Rules 1000(c)(1) and (2).
                        <SU>1744</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1739</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18153.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1740</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1741</SU>
                             
                            <E T="03">See id.</E>
                             at 18154. The 25 burden hours would be spent by a Compliance Clerk. 
                            <E T="03">See id.</E>
                             This estimate was based on Commission staff's experience with examinations of registered entities, the Commission's estimated burden for an SRO to comply with Rule 17a-1, and the Commission's estimated burden for a SB SEF to keep and preserve documents made or received in the conduct of its business. 
                            <E T="03">See id.</E>
                             at 18154, n. 458.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1742</SU>
                             
                            <E T="03">See id.</E>
                             at 18154.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1743</SU>
                             
                            <E T="03">See id.</E>
                             These estimates were based on the Commission's experience with examinations of registered entities and the Commission's estimated burden for an SB SEF to keep and preserve documents made or received in the conduct of its business. 
                            <E T="03">See id.</E>
                             at 18154, n. 460.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1744</SU>
                             
                            <E T="03">See id.</E>
                             at 18154.
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that while proposed Rule 1000(c) does not create new recordkeeping requirements for SCI SROs, the number of records to be retained by an SRO would increase due to proposed Regulation SCI.
                        <SU>1745</SU>
                        <FTREF/>
                         This commenter stated that such additional recordkeeping is not costless and should be considered by the Commission.
                        <SU>1746</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1745</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 39.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1746</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>As discussed in detail above in Section IV.C.1.a, the Commission is adopting the recordkeeping requirements substantially as proposed. The Commission notes that the burden associated with creating such records, as required of all SCI entities, including SCI SROs, by Regulation SCI, are discussed and accounted for throughout this Section V.</P>
                    <P>
                        With respect to SCI SROs, the breadth of Rule 17a-1 under the Exchange Act 
                        <SU>1747</SU>
                        <FTREF/>
                         is such that it requires SCI SROs to make, keep, and preserve records relating to their compliance with Regulation SCI.
                        <SU>1748</SU>
                        <FTREF/>
                         SCI entities that participate in the ARP Inspection Program (nearly all of whom are SCI SROs) do generally keep and preserve the types of records that are subject to the requirements of Rule 1005. However, because Regulation SCI imposes new requirements on SROs, as noted by a commenter, the number of records to be retained by an SRO may increase.
                        <SU>1749</SU>
                        <FTREF/>
                         The Commission believes that existing recordkeeping systems and processes of SCI SROs will be used to retain the records required to be created pursuant to Regulation SCI. As a result, the Commission believes that the burden associated with retaining these additional records is an incrementally small increase in the burden currently incurred by SROs to retain records as required by Rule 17a-1 and that the burden associated with retaining records related to Regulation SCI is already accounted for in the 
                        <PRTPAGE P="72396"/>
                        Commission's burden estimates for Rule 17a-1.
                        <SU>1750</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1747</SU>
                             “Every national securities exchange, national securities association, registered clearing agency and the Municipal Securities Rulemaking Board shall keep and preserve at least one copy of all documents, including all correspondence, memoranda, papers, books, notices, accounts, and other such records as shall be made or received by it in the course of its business as such and in the conduct of its self-regulatory activity.” Exchange Act Rule 17a-1(a), 17 CFR 240.17a-1(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1748</SU>
                             
                            <E T="03">See also</E>
                             Rule 1005(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1749</SU>
                             
                            <E T="03">See supra</E>
                             notes 1745-1746 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1750</SU>
                             
                            <E T="03">See</E>
                             Supporting Statement for the Paperwork Reduction Act Information Collection Submissions for Rule 17a-1, available at: 
                            <E T="03">http://www.reginfo.gov.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission continues to believe that for SCI entities other than SCI SROs, the initial and ongoing burden to make, keep, and preserve records relating to compliance with Regulation SCI, as required by Rule 1005(b), would be approximately 25 hours annually per SCI entity that is not an SCI SRO.
                        <SU>1751</SU>
                        <FTREF/>
                         Therefore, the Commission estimates a total annual burden of 425 hours for all such SCI entities.
                        <SU>1752</SU>
                        <FTREF/>
                         The Commission also continues to estimate that each SCI entity other than an SCI SRO would incur a one-time burden to set up or modify an existing recordkeeping system to comply with Rule 1005. Specifically, the Commission estimates that, for each SCI entity other than an SCI SRO, setting up or modifying a recordkeeping system would create an initial burden of 170 hours and $900 in information technology costs for purchasing software.
                        <SU>1753</SU>
                        <FTREF/>
                         Therefore, the Commission estimates a total initial burden of 3,315 hours 
                        <SU>1754</SU>
                        <FTREF/>
                         and a total initial cost of $15,300 for all such SCI entities.
                        <SU>1755</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1751</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18154, n. 458.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1752</SU>
                             25 hours × 17 non-SRO SCI entities = 425 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1753</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18154, n. 460. The Commission believes that this burden estimate includes the burden imposed by Rule 1007. Specifically, Rule 1007 provides that, if the records required to be filed or kept by an SCI entity under Regulation SCI are prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity would be required to ensure that the records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service, which is signed by a duly authorized person at such service bureau or other recordkeeping service.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1754</SU>
                             (170 hours + 25 hours) × 17 non-SRO SCI entities = 3,315 hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1755</SU>
                             $900 × 17 non-SRO SCI entities = $15,300.
                        </P>
                    </FTNT>
                    <P>
                        Finally, the Commission continues to believe that Rule 1005(c), which requires an SCI entity, upon or immediate prior to ceasing to do business or ceasing to be registered under the Exchange Act, to take all necessary action to ensure that the records required to be made, kept, and preserved by Rule 1005 remain accessible to the Commission and its representatives in the manner and for the remainder of the period required by Rule 1005, would not result in any additional paperwork burden that is not already accounted for in the Commission's burden estimates for Rule 1005(b).
                        <SU>1756</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1756</SU>
                             The Commission believes that SCI entities will comply with Rule 1005(c) by, for example, a contractual arrangement with a recordkeeping service.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">5. Total Paperwork Burden Under Regulation SCI</HD>
                    <P>
                        Based on the foregoing, the Commission estimates that the total one-time initial burden for all SCI entities to comply with Regulation SCI would be 330,508 hours 
                        <SU>1757</SU>
                        <FTREF/>
                         and the total one-time initial cost would be approximately $9.3 million.
                        <SU>1758</SU>
                        <FTREF/>
                         The Commission estimates that the total annual ongoing burden for all SCI entities to comply with Regulation SCI would be 287,722 hours 
                        <SU>1759</SU>
                        <FTREF/>
                         and the total annual ongoing cost would be approximately $5.9 million.
                        <SU>1760</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1757</SU>
                             330,508 hours = 54,992 hours (policies and procedures, mandate participation in certain testing) + 257,237 (notification, dissemination, reporting) + 14,964 hours (corrective action, identification of certain systems and events, identification of material systems changes) + 3,315 hours (recordkeeping).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1758</SU>
                             $9,325,500 = $3,544,000 (policies and procedures, mandate participation in certain testing) + $5,766,200 (notification, dissemination, reporting) + $15,300 (recordkeeping).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1759</SU>
                             287,722 hours = 24,942 hours (policies and procedures, mandate participation in certain testing) + 257,231 (notification, dissemination, reporting) + 5,124 hours (corrective action, identification of certain systems and events, identification of material systems changes) + 425 hours (recordkeeping).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1760</SU>
                             $5,874,200 = $108,000 (mandate participation in certain testing) + $5,766,200 (notification, dissemination, reporting). One commenter noted that majority of the estimated paperwork burden in the SCI Proposal relate to notifications of SCI events, rather than the writing and maintenance of the policies and procedures. 
                            <E T="03">See</E>
                             NYSE Letter at 18. This commenter noted that creating and maintaining reasonable policies and procedure to seek to ensure that important market systems have adequate levels of capacity, integrity, resiliency, availability, and security should be the main focus of the regulation, not the reporting provisions. 
                            <E T="03">See</E>
                             NYSE Letter at 18. The Commission notes that the burden estimates in this section relate solely to the paperwork burden of compliance with Regulation SCI. The Commission discusses other costs associated with compliance with Regulation SCI in the Economic Analysis section below.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">E. Collection of Information Is Mandatory</HD>
                    <P>All collections of information pursuant to Regulation SCI is a mandatory collection of information.</P>
                    <HD SOURCE="HD2">F. Confidentiality</HD>
                    <P>
                        The Commission expects that the written policies and procedures, processes, criteria, standards, or other written documents developed or revised by SCI entities pursuant to Regulation SCI will be retained by SCI entities in accordance with, and for the periods specified in Exchange Act Rule 17a-1 and Rule 1005, as applicable. Should such documents be made available for examination or inspection by the Commission and its representatives, they would be kept confidential subject to the provisions of applicable law.
                        <SU>1761</SU>
                        <FTREF/>
                         In addition, the information submitted to the Commission pursuant to Regulation SCI that is filed on Form SCI, as required by Rule 1006, will be treated as confidential, subject to applicable law, including amended Rule 24b-2.
                        <SU>1762</SU>
                        <FTREF/>
                         The information disseminated by SCI entities pursuant to Rule 1002(c) under Regulation SCI to their members or participants will not be confidential.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1761</SU>
                             
                            <E T="03">See, e.g.,</E>
                             15 U.S.C. 78x (governing the public availability of information obtained by the Commission); 5 U.S.C. 552 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1762</SU>
                             
                            <E T="03">See, e.g.,</E>
                             15 U.S.C. 78x (governing the public availability of information obtained by the Commission); 5 U.S.C. 552 
                            <E T="03">et seq. See also supra</E>
                             Section IV.C.2 (discussing confidentiality treatment for Form SCI filings).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">G. Reduced Burden From Amendment of Rule 301(b)(6) (OMB Control Number 3235-0509)</HD>
                    <P>
                        Adopted Regulation SCI amends Rule 301(b)(6) of Regulation ATS.
                        <SU>1763</SU>
                        <FTREF/>
                         Amendment of Rule 301(b)(6) would eliminate certain collection of information requirements within the meaning of the PRA, which the Commission had submitted to OMB in accordance with 44 U.S.C. 3507 and 5 CFR 1320.11 and OMB had approved. The approved collection of information is titled “Rule 301: Requirements for Alternative Trading Systems and Form ATS; ATS-R,” and the OMB control number for this collection of information is 3235-0509.
                        <SU>1764</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1763</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6). 
                            <E T="03">See also</E>
                             Securities Exchange Act Release No. 40760 (December 8, 1998), 63 FR 70844 (December 22, 1998) (“ATS Release”). In the SCI Proposal, the Commission proposed that Regulation SCI would replace and supersede Rule 301(b)(6) in its entirety. As discussed above, the Commission is now amending Rule 301(b)(6) to remove paragraphs (i)(A) and (i)(B) so that Rule 301(b)(6) will no longer apply to ATSs that trade NMS stocks and non-NMS stocks. However, as described above, the Commission has determined to exclude ATSs that trade only municipal securities or corporate debt securities from the scope of Regulation SCI, and such ATSs will remain subject to the requirements of Rule 301(b)(6) if they meet the volume thresholds therein. The Commission estimates that no ATS that trade only municipal securities or corporate debt securities currently meet the thresholds of Rule 301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1764</SU>
                             
                            <E T="03">See</E>
                             Rule 301: Requirements for Alternative Trading Systems and Form ATS; ATS-R, OMB Control No: 3235-0509 (Rule 301 supporting statement), available at: 
                            <E T="03">http://www.reginfo.gov.</E>
                             This approval has an expiration date of April 30, 2017.
                        </P>
                    </FTNT>
                    <P>
                        Some of the information collection burdens imposed by Regulation ATS would be reduced by the amendment of Rule 301(b)(6). Specifically, the paperwork burdens that would be eliminated by the amendment of Rule 
                        <PRTPAGE P="72397"/>
                        301(b)(6) would be: (i) Burdens on ATSs that trade NMS stocks and non-NMS stocks associated with the requirement to make records relating to any steps taken to comply with systems capacity, integrity and security requirements under Rule 301(b)(6) (estimated to be 20 hours); 
                        <SU>1765</SU>
                        <FTREF/>
                         and (ii) burdens on ATSs that trade NMS stocks and non-NMS stocks associated with the requirement to provide notices to the Commission to report systems outages (estimated to be 2.5 hours).
                        <SU>1766</SU>
                        <FTREF/>
                         The Commission received no comments regarding the reduced paperwork burdens from the proposal to repeal Rule 301(b)(6) of Regulation ATS.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1765</SU>
                             The Commission estimated that two alternative trading systems that register as broker-dealers and comply with Regulation ATS would trigger this requirement, and that the average compliance burden for each response would be 10 hours of in-house professional work at $379 per hour. Thus, the total compliance burden per year was estimated to be 20 hours (2 respondents × 10 hours = 20 hours). 
                            <E T="03">See</E>
                             Rule 301: Requirements for Alternative Trading Systems OMB Control No: 3235-0509 (Rule 301 supporting statement), available at: 
                            <E T="03">http://www.reginfo.gov.</E>
                             As discussed above, the Commission is amending Rule 301(b)(6) so that it will no longer apply to ATSs that trade NMS stocks and non-NMS stocks. ATSs that trade only municipal securities or corporate debt securities will remain subject to the requirements of Rule 301(b)(6), but the Commission estimates that no such ATS currently meets the thresholds of Rule 301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1766</SU>
                             The Commission estimated that two alternative trading systems that register as broker-dealers and comply with Regulation ATS would meet the volume thresholds that trigger systems outage notice obligations approximately 5 times a year, and that the average compliance burden for each response would be .25 hours of in-house professional work at $379 per hour. Thus, the total compliance burden per year was estimated to be 2.5 hours (2 respondents × 5 responses each × .25 hours = 2.5 hours). 
                            <E T="03">See id.</E>
                             As discussed above, the Commission is amending Rule 301(b)(6) so that it will no longer apply to ATSs that trade NMS stocks and non-NMS stocks. ATSs that trade only municipal securities or corporate debt securities will remain subject to the requirements of Rule 301(b)(6), but the Commission estimates that no such ATS currently meets the thresholds of Rule 301(b)(6).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">VI. Economic Analysis</HD>
                    <HD SOURCE="HD2">A. Overview</HD>
                    <P>
                        The Commission is sensitive to the economic effects, including the costs and benefits, of its rules. When engaging in rulemaking pursuant to the Exchange Act that requires the Commission to consider or determine whether an action is necessary or appropriate in the public interest, Section 3(f) of the Exchange Act requires the Commission to consider, in addition to the protection of investors, whether the action will promote efficiency, competition, and capital formation.
                        <SU>1767</SU>
                        <FTREF/>
                         In addition, Section 23(a)(2) of the Exchange Act requires the Commission in making rules pursuant to the Exchange Act to consider the impact any such rule would have on competition. The Exchange Act prohibits the Commission from adopting any rule that would impose a burden on competition not necessary or appropriate in furtherance of the purposes of the Exchange Act.
                        <SU>1768</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1767</SU>
                             15 U.S.C. 78c(f).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1768</SU>
                             15 U.S.C. 78w(a)(2).
                        </P>
                    </FTNT>
                    <P>In the SCI Proposal, the Commission solicited comment on the economic effects of the proposed rules, including any effects that the proposed rules may have on efficiency, competition, and capital formation. The Commission also solicited comment on its representation of current practices and its characterization of the relevant markets in which SCI entities participate. In addition, the Commission solicited comment on reasonable alternatives to the proposed rules and their economic effects. The Commission encouraged commenters to identify, discuss, analyze, and supply relevant data, information, or statistics regarding any economic effects.</P>
                    <P>
                        The Commission received many comment letters that addressed the Commission's economic analysis of the proposed rules.
                        <SU>1769</SU>
                        <FTREF/>
                         As described further below, some commenters stated that the Commission underestimated the costs (including, for example, the proposed rules' potential to impact innovation and create barriers to entry) of compliance with Regulation SCI.
                        <SU>1770</SU>
                        <FTREF/>
                         Other commenters believed that the costs are justified by the benefits of the rules.
                        <SU>1771</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1769</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Tellefsen Letter; Angel Letter; MSRB Letter; OCC Letter; BIDS Letter; ISE Letter; Leuchtkafer Letter; Better Markets Letter; CAST Letter; FINRA Letter; CISQ Letter; Fidelity Letter; CME Letter; Omgeo Letter; Lauer Letter; SIFMA Letter; SunGard Letter; NYSE Letter; BATS Letter; FIA PTG Letter; ITG Letter; KCG Letter; UBS Letter; Joint SROs Letter; and TMC Letter.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1770</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 2-3; NYSE Letter at 2; UBS Letter at 5; and Omgeo Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1771</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Lauer Letter at 7 (commenting that cost burden should not be an appropriate reason to omit an SCI entity and that, if the burden to ensure secure, stable systems is too high for an entity, that entity should not be allowed to be in a position to impact the market); and Better Markets Letter at 9-12 (commenting that the Commission's preeminent duty when promulgating rules is to protect investors and the public interest, and these goals should not be subordinate to industry concerns over the cost of regulation).
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section I, a confluence of factors has contributed to the Commission's determination that it is necessary and appropriate at this time to address the technological vulnerabilities, and improve Commission oversight, of the core technology of key U.S. securities markets entities, including national securities exchanges and associations, significant ATSs, clearing agencies, and plan processors. These considerations include: The evolution of the markets to become significantly more dependent on sophisticated, complex, and interconnected technology; the current successes and limitations of the ARP Inspection Program; the significant number of, and lessons learned from, recent systems issues at exchanges and other trading venues,
                        <SU>1772</SU>
                        <FTREF/>
                         including increased concerns over “single points of failure” in the securities markets; and the views of a wide variety of commenters received in response to the SCI Proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1772</SU>
                             
                            <E T="03">See supra</E>
                             note 15 and accompanying text.
                        </P>
                    </FTNT>
                    <P>Regulation SCI codifies, updates, and expands the existing ARP Inspection Program in an effort to further the goals of the national market system. Regulation SCI is intended to help to ensure the capacity, integrity, resiliency, availability, and security of the automated systems of entities important to the functioning of the U.S. securities markets. Regulation SCI is also intended to strengthen the U.S. securities market infrastructure and improve the resilience of the U.S. securities markets when technological issues arise. Moreover, Regulation SCI is intended to reinforce the requirement that SCI entities operate their systems in compliance with the Exchange Act and the rules and regulations thereunder.</P>
                    <P>
                        As adopted, Regulation SCI will apply to SCI SROs (including national securities exchanges,
                        <SU>1773</SU>
                        <FTREF/>
                         national securities associations,
                        <SU>1774</SU>
                        <FTREF/>
                         registered clearing agencies, and the MSRB), SCI ATSs, plan processors, and certain exempt clearing agencies.
                        <SU>1775</SU>
                        <FTREF/>
                         As such, Regulation SCI covers the trading of NMS stocks, OTC equities, and listed options. As discussed below, Regulation SCI also will impact multiple markets for services, including the markets for trading services, listing services, regulation and surveillance services, clearance and settlement services, and market data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1773</SU>
                             Regulation SCI will not apply to an exchange that lists or trades security futures products that is notice-registered with the Commission as a national securities exchange pursuant to Section 6(g) of the Exchange Act, including security futures exchanges. 
                            <E T="03">See supra</E>
                             note 78 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1774</SU>
                             Regulation SCI will not apply to limited purpose national securities associations registered with the Commission pursuant to Section 15A(k) of the Exchange Act. 
                            <E T="03">See supra</E>
                             note 78 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1775</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1 (discussing the definition of SCI entities).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Economic Baseline</HD>
                    <P>
                        The Commission recognizes that any economic effects, including costs and benefits and effects on efficiency, competition, and capital formation, 
                        <PRTPAGE P="72398"/>
                        should be compared to a baseline that accounts for current practices. The description of current practices below is based, among other things, on the Commission's understanding of the current practices under the ARP Inspection Program (including current practices influenced by staff guidance related to the ARP Inspection Program), the requirements under Regulation ATS, rules of SROs, information provided by commenters, and current practices and staff guidance related to systems compliance-related issues.
                    </P>
                    <P>
                        As noted above, all active registered clearing agencies, all registered national securities exchanges, FINRA, two plan processors, one ATS, and one exempt clearing agency currently participate in the ARP Inspection Program. Under the ARP Policy Statements and through the ARP Inspection Program, these entities, among other things, are expected to establish current and future capacity estimates; conduct capacity stress tests; and conduct annual reviews that cover significant elements of the operations of the automation process, including the capacity planning and testing process, contingency planning, systems development methodology, and vulnerability assessments. When conducting an ARP inspection, Commission staff also evaluates whether an ARP entity's controls over its information technology resources in nine general areas, or information technology “domains,” is consistent with ARP and industry guidelines.
                        <SU>1776</SU>
                        <FTREF/>
                         The ARP Policy Statements and staff letters also address, among other things, the reporting of certain systems changes, intrusions, and outages, and the need to comply with relevant laws and rules.
                        <SU>1777</SU>
                        <FTREF/>
                         Many participants in the ARP Inspection Program have developed current practices that to some extent overlap with the requirements of Regulation SCI. These practices are discussed in more detail throughout this economic analysis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1776</SU>
                             
                            <E T="03">See supra</E>
                             Section II.A (discussing the ARP Policy Statements and Commission staff letters).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1777</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The ARP Policy Statements and the ARP Inspection Program address systems that directly support trading, clearance and settlement, order routing, and market data, which are a subset of the systems covered by Regulation SCI.
                        <SU>1778</SU>
                        <FTREF/>
                         Additionally, Commission staff currently inspects all the categories of systems that are included in the adopted definition of “SCI systems” to varying degrees.
                        <SU>1779</SU>
                        <FTREF/>
                         In general, the Commission believes that, to varying degrees, entities participating in the ARP Inspection Program establish current and future capacity estimates, conduct periodic capacity stress tests, and conduct an annual independent assessment of whether their automated systems can perform adequately at their estimated capacity levels and whether these systems have adequate protection against threats.
                        <SU>1780</SU>
                        <FTREF/>
                         Additionally, entities participating in the ARP Inspection Program provide to the Commission and its staff reports relating to system changes and reviews, as well as information regarding systems outages.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1778</SU>
                             
                            <E T="03">See infra</E>
                             note 1900 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1779</SU>
                             Commission staff inspects systems that are not directly related to trading, clearance and settlement, order routing, or market data if staff detects red flags. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18158.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1780</SU>
                             
                            <E T="03">See</E>
                             ARP I Release and ARP II Release, 
                            <E T="03">supra</E>
                             note 1.
                        </P>
                    </FTNT>
                    <P>
                        In addition, as discussed above, pursuant to Rule 301(b)(6) of Regulation ATS, certain aspects of the ARP Policy Statements apply to ATSs that meet the thresholds set forth in that rule.
                        <SU>1781</SU>
                        <FTREF/>
                         Currently, the Commission believes that only one ATS meets such thresholds and, thus, is required by Commission rule to implement systems safeguard measures. There is also one ATS that voluntarily participates in the ARP Inspection Program. Rule 301(b)(6) of Regulation ATS includes requirements that are similar to the requirements underlying the policies and procedures required by Rule 1001(a)(2) of Regulation SCI. Specifically, Rule 301(b)(6) under Regulation ATS requires relevant ATSs to establish certain capacity estimates, conduct periodic capacity stress tests of critical systems, develop and implement reasonable procedures to review and keep current systems development and testing methodology, review the vulnerability of their systems and data center computer operations to specified threats, establish adequate contingency and disaster recovery plans, conduct an independent review of its systems controls annually for ensuring that Rules 301(b)(6)(ii)(A)-(E) are met and conduct a review by senior management of a report of the independent review, and promptly notify the Commission of certain systems outages and systems changes. Rule 301(b)(6) of Regulation ATS, however, applies only to systems that support order entry, order routing, order execution, transaction reporting, and trade comparison,
                        <SU>1782</SU>
                        <FTREF/>
                         which is more targeted than the adopted definition of “SCI system.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>1781</SU>
                             Specifically, Rule 301(b)(6) of Regulation ATS applies to ATSs that, during at least four of the preceding six months, had: (A) With respect to any NMS stock, 20 percent or more of the average daily volume reported by an effective transaction reporting plan; (B) with respect to equity securities that are not NMS stocks and for which transactions are reported to a self-regulatory organization, 20 percent or more of the average daily volume as calculated by the self-regulatory organization to which such transactions are reported; (C) with respect to municipal securities, 20 percent or more of the average daily volume traded in the United States; or (D) with respect to corporate debt securities, 20 percent or more of the average daily volume traded in the United States. 
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6)(i).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1782</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6)(ii).
                        </P>
                    </FTNT>
                    <P>
                        The Commission recognizes that market participants that do not participate in the ARP Inspection Program and are not subject to Regulation ATS also take measures consistent with certain aspects of Regulation SCI to avoid systems disruptions, compliance issues, and intrusions. For example, the Commission believes that many market participants document systems events as prudent and standard business practice, even when the entity is not an ARP participant or does not report the incident as an ARP participant. Additionally, commenters provided information about their practices for maintaining suitable levels of systems capacity, integrity, resiliency, availability, and security. As discussed in Section IV.B.1, the Commission understands that some SCI entities are already following technology standards such as ISO 27000 and COBIT.
                        <SU>1783</SU>
                        <FTREF/>
                         One commenter also stated that NFPA-1600 or BS 25999 was useful for contingency planning.
                        <SU>1784</SU>
                        <FTREF/>
                         Commenters also provided less specific information on current practices that allow the Commission to gauge current practices. For example, one commenter stated that SCI entities commonly review a variety of different standards for frameworks or best practices, and then adopt a derivative of multiple standards, customizing them for the systems at issue.
                        <SU>1785</SU>
                        <FTREF/>
                         In addition, another commenter stated that the financial services industry currently uses processes for software development that are more “nimble” than the frameworks listed in Table A, such as the NIST publication under the Systems Development Methodology domain.
                        <SU>1786</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1783</SU>
                             
                            <E T="03">See</E>
                             text accompanying 
                            <E T="03">supra</E>
                             note 606.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1784</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1785</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1786</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 6-7 (commenting that the NIST publication reflects a burdensome staged process to software development that favors the “waterfall methodology” over “agile” software development).
                        </P>
                    </FTNT>
                    <P>
                        FINRA members, including ATSs, are also subject to FINRA rules that are generally related to certain aspects of Regulation SCI.
                        <SU>1787</SU>
                        <FTREF/>
                         For example, NASD 
                        <PRTPAGE P="72399"/>
                        Rule 3010(b)(1) requires a member to establish, maintain, and enforce written procedures to supervise the types of business in which it engages and to supervise the activities of registered representatives, registered principals, and other associated persons that are reasonably designed to achieve compliance with applicable securities laws and regulations. However, this NASD rule does not specifically address compliance of the 
                        <E T="03">systems</E>
                         of FINRA members and does not cover more broadly policies and procedures relating to operational capability. Additionally, FINRA Rule 3130 requires a member's chief compliance officer to certify that the member has in place written policies and procedures reasonably designed to achieve compliance with applicable FINRA rules, MSRB rules, and federal securities laws and regulations. Again, this FINRA rule does not specifically address compliance of the 
                        <E T="03">systems</E>
                         of FINRA members and does not cover more broadly policies and procedures relating to operational capability. Further, FINRA Rule 4530 imposes a reporting regime for, among other things, compliance issues and other events where a member has concluded or should have reasonably concluded that a violation of securities or other enumerated law, rule, or regulation of any domestic or foreign regulatory body or SRO has occurred. However, the reporting requirements of FINRA Rule 4530 are different in several respects from the Commission notification requirements under Regulation SCI relating to systems compliance issues (
                        <E T="03">e.g.,</E>
                         scope, timing, content, the recipient of the reports) and would not cover reporting of systems disruptions or systems intrusions that did not also involve a violation of a securities law, rule, or regulation. In addition, FINRA Rule 4370 generally requires that a member maintain a written continuity plan identifying procedures relating to an emergency or significant business disruption. However, as compared to adopted Rules 1001(a)(2)(v) and 1004, this FINRA rule does not include a requirement that the business continuity and disaster recovery plans be reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption, nor does it require the functional and performance testing and coordination of industry or sector-testing of such plans.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1787</SU>
                             
                            <E T="03">See supra</E>
                             note 115. As noted above, although these rules have some broad relation to certain 
                            <PRTPAGE/>
                            aspects of Regulation SCI, the Commission is not persuaded that the rules, even when taken together, are an appropriate substitute for the comprehensive approach in Regulation SCI with respect to technology systems and system issues. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Commenters addressed the Commission's consideration of current practices under the ARP Inspection Program as part of the baseline. According to a commenter, the ARP Inspection Program was implemented many years ago in a series of policy statements setting out guidance for voluntary compliance, and was supplemented with informal Commission staff guidance over the years, in many cases before the relevant systems existed.
                        <SU>1788</SU>
                        <FTREF/>
                         This commenter also noted that Regulation SCI is a mandatory regulation with a more expansive nature, differentiating the proposed regulation from the voluntary, targeted scope of the ARP Inspection Program.
                        <SU>1789</SU>
                        <FTREF/>
                         Some commenters believed that the Commission performed the economic analysis from a faulty premise by assuming that SCI entities that participate in the ARP Inspection Program have been in compliance with the voluntary standards and that the cost of compliance with Regulation SCI would merely be incremental as compared with the current baseline cost of voluntary compliance with the ARP regime.
                        <SU>1790</SU>
                        <FTREF/>
                         One commenter noted that there is no publicly available information on voluntary compliance under the ARP Inspection Program, and the Commission should calculate the actual cost based on its knowledge of the extent to which SCI entities currently participating in the ARP Inspection Program are actually in compliance with ARP, rather than simply assuming full compliance.
                        <SU>1791</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1788</SU>
                             
                            <E T="03">See</E>
                             NYSE Letter at 2, 6-7. This commenter noted that the ARP Inspection Program was never subject to Commission rulemaking, including notice and public comment, and a cost-benefit analysis. 
                            <E T="03">See id.</E>
                             at 6. This commenter further stated that if the Commission were to move forward with Regulation SCI, it should first engage in a detailed public analysis of the costs and benefits of the existing ARP Inspection Program. 
                            <E T="03">See id.</E>
                             at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1789</SU>
                             
                            <E T="03">See id.</E>
                             at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1790</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 11; and Joint SROs Letter at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1791</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 11.
                        </P>
                    </FTNT>
                    <P>In response to these comments, the Commission believes that current practices under the ARP Inspection Program continue to be relevant in an economic assessment of Regulation SCI and the current baseline. In particular, as described in more detail throughout the economic analysis, based on comments and staff experience, the Commission believes that ARP entities have developed practices that to some extent overlap with the requirements of Regulation SCI. Accordingly, the Commission believes that, for some entities, the economic effects associated with compliance with Regulation SCI will be less significant as these entities will need to make incremental adjustments to their current practices to comply with many of the requirements.</P>
                    <P>
                        The Commission recognizes that there is no publicly available information on voluntary compliance under the ARP Inspection Program. At the same time, the Commission and its staff have overseen the ARP Inspection Program for over two decades and notes that participants in the ARP Inspection Program generally follow the ARP Policy Statements. The Commission also notes that, in the ARP II Release, it stated that Commission staff and the SROs have discussed the independent review process, “taking into account that the SROs already engage in testing and quality assurance reviews of new or modified systems, and that there are other significant controls in place to prevent, detect or correct problems in such areas as capacity planning, testing, systems development, vulnerability and contingency planning.” 
                        <SU>1792</SU>
                        <FTREF/>
                         The Commission is not assuming in the economic analysis that each SCI entity is fully in compliance with the ARP Inspection Program. Rather, the Commission's and its staff's experience informs the Commission's view regarding the range of existing practices of SCI entities. The Commission recognizes that some participants in the ARP Inspection Program may also have adopted practices that are not precisely in line with the standards articulated in the ARP Policy Statements and other Commission policy statements. As discussed throughout this economic analysis, the Commission has considered what the economic effects, including the costs and benefits of complying with Regulation SCI, will be for those entities that may not have practices consistent with the standards articulated in the ARP Policy Statements. For example, some SRO backup facilities may be less geographically dispersed from the primary facilities than articulated in the 2003 BCP Policy Statement.
                        <SU>1793</SU>
                        <FTREF/>
                         Further, some SROs may report systems issues or changes to the Commission in a manner different from what is articulated in the ARP Policy Statements and Commission staff letters. Instead of assuming full compliance with the ARP Inspection Program, throughout the economic analysis the Commission notes that some SCI entities that participate in the ARP Inspection Program have current 
                        <PRTPAGE P="72400"/>
                        practices that already satisfy some of the requirements of Regulation SCI and considers the details of those current practices when assessing the economic effects of the rules.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1792</SU>
                             
                            <E T="03">See</E>
                             ARP II, 
                            <E T="03">supra</E>
                             note 1, at 22491.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1793</SU>
                             
                            <E T="03">See</E>
                             2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56658.
                        </P>
                    </FTNT>
                    <P>Finally, in using the ARP Inspection Program as a component of the baseline, the Commission also recognizes that Regulation SCI is more expansive than the ARP Inspection Program and has taken this fact into consideration throughout the economic analysis. For example, among other things, Regulation SCI includes more expansive requirements compared to the ARP Inspection Program for the establishment of policies and procedures regarding systems capacity, integrity, resiliency, availability, security, and compliance; and annual business continuity and disaster recovery plans testing. In addition, the Commission is aware that more entities will be subject to Regulation SCI than are currently participating in the ARP Inspection Program, including a higher number of ATSs. The Commission has considered these differences in the economic analysis.</P>
                    <P>
                        The sections below describe in more detail the Commission's understanding of current practices related to areas covered by Regulation SCI, as informed by its experience with the ARP Inspection Program, the OCIE examination program, as well as by commenters. In particular, the sections below provide an overview of the frequency and the types of systems issues addressed by Regulation SCI (
                        <E T="03">i.e.,</E>
                         systems disruptions, systems intrusions, and systems compliance issues) and current practices related to these events, as well as current practices related to business continuity and disaster recovery, and material systems changes notifications. Additionally, the sections below include a summary of the current competitive landscape in various markets for services related to Regulation SCI and why the markets for these services do not provide an adequate competitive incentive to prevent the occurrence of these market events and reduce the duration and severity when they occur.
                        <SU>1794</SU>
                        <FTREF/>
                         Details regarding the baseline for certain specific current practices relevant to specific provisions of Regulation SCI are discussed throughout the consideration of costs and benefits and the effect on efficiency, competition, and capital formation below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1794</SU>
                             Throughout this Economic Analysis, the general concept of a reduction of SCI events may refer to fewer events, shorter duration of events, and/or less severe events.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. SCI Events</HD>
                    <HD SOURCE="HD3">a. Systems Disruptions and Intrusions</HD>
                    <P>Currently, market participants use an array of preventive and corrective measures to avoid systems disruptions and to restore systems when disruptions occur, including escalation procedures to notify management of disruptions. The range of preventive and corrective measures varies among market participants and SCI entities, and also differs among the systems employed by SCI entities. For instance, clearing systems and order matching engines generally are given higher priority by SCI entities than other SCI entity systems.</P>
                    <P>
                        Also, as noted by a commenter, exchanges, member firms, and ATSs conduct regular and ad hoc testing of mission critical systems for the introduction of new software releases, new features and functions, and systems upgrades, among other things.
                        <SU>1795</SU>
                        <FTREF/>
                         This commenter also noted that the internal IT staff of exchanges, ATSs, trading platform providers, and clearing houses conduct regular systems testing, regression testing, stress testing, and failover testing to ensure the availability, capacity, resilience, and readiness of newly introduced systems, applications, products, and system functions.
                        <SU>1796</SU>
                        <FTREF/>
                         However, industry practices are not codified as requirements for SCI entities and systems, except as may be the case in an entity's rulebook or subscriber agreement.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1795</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1796</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>Market participants also employ a wide variety of measures to prevent and respond to systems intrusions, including escalation procedures to notify management of intrusions. Generally, market participants use measures such as firewalls to prevent systems intrusions, and use detection software to identify systems intrusions. Once an intrusion has been identified, the affected systems typically would be isolated and quarantined, and forensics would be performed.</P>
                    <P>
                        While there have been instances in which SCI entities revealed systems issues (including disruptions and intrusions) to their members or participants and to the public in the past,
                        <SU>1797</SU>
                        <FTREF/>
                         there currently is no requirement applicable to SCI entities that includes the level of specificity in Regulation SCI for dissemination of information regarding systems disruptions and systems intrusions, as those terms are defined in Regulation SCI, to affected members or participants or to all members or participants of an SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1797</SU>
                             One instance of a publicly reported systems intrusion at an SCI entity occurred in February 2011, when NASDAQ OMX Group, Inc. revealed that hackers had penetrated certain of its computer networks, though Nasdaq reported that at no point did this intrusion compromise Nasdaq's trading systems. 
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18089. One commenter also stated that when systems issues arise that impact subscriber access, functionality, or security, each potential SCI entity informs its subscribers of the problem and the expected solution, and generally follows with a post mortem. According to this commenter, some entities provide this notice pursuant to a contract or general agreement with subscribers, while others do so in order to maintain and grow their subscriber base. 
                            <E T="03">See</E>
                             OTC Markets Letter at 19. 
                            <E T="03">See also supra</E>
                             Section II.B (describing recent events involving systems-related issues, which have been made public).
                        </P>
                    </FTNT>
                    <P>
                        In 2013, entities that participated in the ARP Inspection Program, including at least one of each type of such participants (
                        <E T="03">i.e.,</E>
                         national securities exchange, national securities association, registered clearing agency, plan processor, ATS, and exempt clearing agency), reported a total of approximately 357 systems disruptions to the Commission.
                        <SU>1798</SU>
                        <FTREF/>
                         These incidents had durations ranging from under one hour to well over several hours, with most incidents having a duration of less than three hours.
                        <SU>1799</SU>
                        <FTREF/>
                         The Commission has also tracked the percentage of market outages at SROs and electronic communications networks, which were self-reported to the Commission or identified by Commission staff, that were corrected within targeted timeframes. Specifically, in fiscal year 2013, 80% of outages were resolved within 2 hours, 86% were resolved within 4 hours, and 98% were resolved within 24 hours.
                        <SU>1800</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1798</SU>
                             One commenter believes that ATSs have not contributed to the recent major systems issues that have impacted the market. 
                            <E T="03">See</E>
                             ITG letter at 4. However, as the Commission has noted, FINRA halted trading for over 3
                            <FR>1/2</FR>
                             hours in all OTC equity securities due to a lack of availability of quotation information resulting from a connectivity issue experienced by OTC Markets Group Inc.'s OTC Link ATS. 
                            <E T="03">See supra</E>
                             note 33 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1799</SU>
                             The Commission acknowledges that the number of systems incidents reported to the Commission by entities that participated in the ARP Inspection Program represents the lower end of expected SCI events under Regulation SCI because the definition of “SCI event” is broader than the types of events covered by the current ARP Inspection Program. 
                            <E T="03">See supra</E>
                             Section V.D.2.a.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1800</SU>
                             
                            <E T="03">See</E>
                             U.S. Securities and Exchange Commission FY 2015 Annual Performance Plan, at 26 (March 7, 2014), available at: 
                            <E T="03">http://www.sec.gov/about/reports/secfy15congbudgjust.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Systems Compliance Issues</HD>
                    <P>
                        Currently, systems compliance issues are not covered by the ARP Inspection Program. However, the Commission notes that all SROs are required to comply with the Exchange Act, the rules 
                        <PRTPAGE P="72401"/>
                        and regulations thereunder, and their own rules and governing documents, as applicable,
                        <SU>1801</SU>
                        <FTREF/>
                         and securities information processors and ATSs are subject to similar requirements.
                        <SU>1802</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1801</SU>
                             
                            <E T="03">See, e.g.,</E>
                             15 U.S.C. 78s(g) (requiring each SRO to comply with the Exchange Act, the rules and regulations thereunder, and its own rules).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1802</SU>
                             
                            <E T="03">See, e.g.,</E>
                             15 U.S.C. 78k-1(b)(6); 15 U.S.C. 78k-1(c)(1); and FINRA Rule 3130. Moreover, ATSs are registered broker-dealers and may be subject to Commission sanctions if they fail to comply with relevant federal securities laws and rules and regulations thereunder.
                        </P>
                    </FTNT>
                    <P>
                        Further, SROs currently take steps to ensure that their systems' operations are consistent with the federal securities laws and rules and their own rules, and some SROs notify Commission staff of certain systems compliance issues.
                        <SU>1803</SU>
                        <FTREF/>
                         In particular, the Commission understands that SCI SROs generally have procedures to escalate a compliance issue upon discovery, to include legal and compliance personnel in the review of systems changes, and to periodically review rulebooks. However, although some SCI entities currently notify the Commission of certain systems compliance issues, the Commission does not receive comprehensive data regarding such issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1803</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18087, n. 36. As part of the Commission's oversight of SROs, OCIE reviews systems compliance issues reported to Commission staff.
                        </P>
                    </FTNT>
                    <P>
                        Similar to systems disruptions and systems intrusions, while there have been instances in which SCI entities revealed systems compliance-related issues to their members or participants and to the public in the past,
                        <SU>1804</SU>
                        <FTREF/>
                         there currently is no requirement applicable to SCI entities that includes the level of specificity in Regulation SCI for dissemination of information regarding systems compliance issues, as that term is defined in Regulation SCI, to affected members or participants, or to all members or participants of an SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1804</SU>
                             
                            <E T="03">See supra</E>
                             Section II.B (describing recent events involving systems-related issues, which have been made public).
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, based on Commission staff's experience with SROs and the rule filing process, the Commission estimated that there are likely approximately seven systems compliance issues per SCI entity per year. No commenter provided additional information regarding the frequency of systems compliance issues. However, Commission staff received notifications indicating that certain SROs experienced an average of 17 systems compliance-related issues in 2013. The Commission believes that its staff received notification of a larger number of systems compliance issues in 2013 for a variety of reasons, including the proposal of Regulation SCI, recent Commission enforcement actions relating to systems compliance issues, as well as related press reports, all of which the Commission believes increased attention on systems compliance issues.
                        <SU>1805</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1805</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Business Continuity and Disaster Recovery</HD>
                    <P>
                        The Commission recognizes that SCI entities already have business continuity and disaster recovery plans. For example, nearly all national securities exchanges already have backup facilities that do not rely on the same infrastructure components as those used by their primary facility.
                        <SU>1806</SU>
                        <FTREF/>
                         Additionally, most participants in the ARP Inspection Program have strived to adhere to the recovery timeframes in the Interagency White Paper and the 2003 BCP Policy Statement.
                        <SU>1807</SU>
                        <FTREF/>
                         Some SCI entities also already require some of their members or participants to connect to their backup systems.
                        <SU>1808</SU>
                        <FTREF/>
                         Further, some SCI entities already provide their members or participants with the opportunity to test the SCI entity's business continuity and disaster recovery plans, including its backup systems.
                        <SU>1809</SU>
                        <FTREF/>
                         However, because participation in BC/DR testing, including backup systems, is not always required by SCI entities, the Commission understands that not all market participants participate in testing.
                        <SU>1810</SU>
                        <FTREF/>
                         In addition, based on the discussions between Commission staff and market participants in the months following Superstorm Sandy, the Commission understands that many market participants had previously engaged in connectivity testing with backup facilities, and yet remained uncomfortable about switching to the use of backup facilities in advance of the storm.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1806</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CBOE Regulatory Circular RG14-001 (Back-Up Data Center Test on January 25, 2014).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1807</SU>
                             
                            <E T="03">See supra</E>
                             note 504 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1808</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CBOE Regulatory Circular RG13-110 (Connectivity to the CBOE Back-Up Data Center). 
                            <E T="03">See also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at n. 641.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1809</SU>
                             For example, SIFMA organizes industry-wide business continuity tests. 
                            <E T="03">See</E>
                             Industry Testing, 
                            <E T="03">http://www.sifma.org/services/bcp/industry-testing/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1810</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Angel Letter at 9-10.
                        </P>
                    </FTNT>
                    <P>
                        Commenters also provided information regarding current practices surrounding business continuity and disaster recovery. One commenter noted that the major equity and options exchanges and numerous ATSs already regularly augment IT testing with other business continuity management exercises (
                        <E T="03">e.g.,</E>
                         they conduct annual business continuity and disaster recovery plan updates, building evacuation drills, and business disruption scenario planning workshops).
                        <SU>1811</SU>
                        <FTREF/>
                         This commenter also noted that all of the U.S. exchanges and clearinghouses have participated in the planning and execution of the annual disaster recovery test initiative conducted and coordinated by the FIA and SIFMA.
                        <SU>1812</SU>
                        <FTREF/>
                         This commenter noted that, in 2012, for example, the annual FIA industry test involved 18 exchanges and clearinghouses, 68 futures commission merchants, and 46 trading participant firms.
                        <SU>1813</SU>
                        <FTREF/>
                         This commenter also noted that the exchanges reported that the firms engaged in testing represented approximately 80% of their clearing members and that these firms reflected approximately 85% of the exchanges' 2012 volumes.
                        <SU>1814</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1811</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1812</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1813</SU>
                             
                            <E T="03">See id.</E>
                             at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1814</SU>
                             
                            <E T="03">See id. See also</E>
                             CME Letter at 12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Material Systems Changes Notifications</HD>
                    <P>
                        Many entities that participate in the ARP Inspection Program already voluntarily provide material systems change notifications to the Commission on an annual and ad hoc basis. In particular, the ARP II Release stated that SROs should notify Commission staff of significant additions, deletions, or other changes to their automated systems.
                        <SU>1815</SU>
                        <FTREF/>
                         Moreover, in the 2001 Staff ARP Interpretive Letter, Commission staff provided guidance to ARP entities on how they should report planned systems changes to the Commission.
                        <SU>1816</SU>
                        <FTREF/>
                         In addition, Rule 301(b)(6) under Regulation ATS requires that ATSs that meet the thresholds in that rule notify Commission staff of significant systems changes,
                        <SU>1817</SU>
                        <FTREF/>
                         and Rule 301(b)(2) under Regulation ATS requires each ATS that is subject to Rule 301, regardless of activity level, to file an amendment on Form ATS at least 20 days prior to implementing a material change to the operation of the ATS.
                        <SU>1818</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1815</SU>
                             
                            <E T="03">See</E>
                             ARP II Release, 
                            <E T="03">supra</E>
                             note 1, at 22491.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1816</SU>
                             
                            <E T="03">See supra</E>
                             note 21 and accompanying text. The 2001 Staff ARP Interpretive Letter provided guidance on what Commission staff considers significant systems changes to include.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1817</SU>
                             17 CFR 242.301(b)(6)(ii)(G).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1818</SU>
                             17 CFR 242.301(b)(2)(ii) (requiring an amendment to Form ATS not solely for material systems changes, but also for any material change to the operation of an ATS).
                        </P>
                    </FTNT>
                    <PRTPAGE P="72402"/>
                    <HD SOURCE="HD3">4. Potential for Market Solutions</HD>
                    <P>
                        The current competitive landscape in various markets for services related to Regulation SCI affect current incentives to prevent the occurrence of SCI events in these markets.
                        <SU>1819</SU>
                        <FTREF/>
                         The Commission outlined and examined this competitive landscape and potential for market solutions to reduce SCI events and their shortcomings in the SCI Proposal.
                        <SU>1820</SU>
                        <FTREF/>
                         In particular, the Commission evaluated current limitations to competition and potential market solutions in the markets for trading services, listing services, regulatory services, clearance and settlement services, and market data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1819</SU>
                             This section evaluates competition as it currently exists. The Commission analyzes the economic effects of Regulation SCI, including potential effects on competition, in Section VI.C.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1820</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18159-61.
                        </P>
                    </FTNT>
                    <P>
                        The discussion below responds to comments received regarding the Commission's discussion of the potential for market solutions in the markets for trading services and market data. The Commission did not receive specific comments regarding its analysis of the markets for listing services, regulatory services, and clearance and settlement services. Therefore, the Commission believes that its analysis of these markets in the SCI Proposal continues to apply. Specifically, the Commission believes that, while the market for listing services provides some discipline, it has limitations related to a disconnect between trading location and listing market (
                        <E T="03">i.e.,</E>
                         while a company can be listed on a certain exchange, trading does not necessarily occur on that exchange), to switching costs if an issuer wishes to change its listing exchange, and to market power deriving from the “prestige” of a listing exchange.
                        <SU>1821</SU>
                        <FTREF/>
                         Further, the Commission believes that the market for regulatory and surveillance services is concentrated in a few competitors and that the market for clearance and settlement services is currently characterized by specialization and limited competition.
                        <SU>1822</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1821</SU>
                             
                            <E T="03">See id.</E>
                             at 18160.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1822</SU>
                             
                            <E T="03">See id.</E>
                             at 18160-61.
                        </P>
                    </FTNT>
                    <P>
                        The Commission has considered the views of commenters and the Commission's analysis of markets not addressed by commenters, and continues to believe that market forces alone are insufficient to significantly reduce SCI events in the markets that it evaluated and that a regulatory solution is needed. In particular, the Commission continues to believe that SCI entities do not fully internalize the costs associated with systems issues, SCI events pose significant negative externalities on the market—
                        <E T="03">i.e.,</E>
                         systems issues have ramifications on the securities markets beyond the impact on the entity responsible for the systems issues—and, as discussed above, significant technology issues continue to occur in the absence of regulation.
                    </P>
                    <P>
                        Some commenters broadly addressed the potential for market solutions evaluated in the SCI Proposal. According to one commenter, SCI entities (
                        <E T="03">e.g.,</E>
                         ATSs) are highly motivated to provide uninterrupted order matching services for economic reasons.
                        <SU>1823</SU>
                        <FTREF/>
                         On the other hand, another commenter noted that, as indicated by the 2008 financial crisis and the technology incidents over the past few years, market participants do not have the right economic incentives to protect themselves.
                        <SU>1824</SU>
                        <FTREF/>
                         Another commenter stated that, in the past, “disruptive or deviant behavior in the markets was disciplined not just by regulators but also by trading crowds,” but anonymity and fully automated price/time matching made it impossible for the trading crowd to attribute and sanction disruptive behavior.
                        <SU>1825</SU>
                        <FTREF/>
                         This commenter also noted that market incentives can drive the industry in the opposite direction (
                        <E T="03">i.e.,</E>
                         short-term market incentives can drive the industry to minimize risk controls).
                        <SU>1826</SU>
                        <FTREF/>
                         According to this commenter, the only practical source of discipline left is government regulation.
                        <SU>1827</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1823</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 4 (stating also that sponsors of ATSs have a “compelling business incentive to avoid systems issues”). 
                            <E T="03">See also</E>
                             Angel Letter at 5-6 (commenting that firms have sufficient motivation to take every precaution against catastrophic failures, although the interaction between firms may result in a catastrophic event).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1824</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1825</SU>
                             
                            <E T="03">See</E>
                             Leuchtkafer Letter at 1-2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1826</SU>
                             
                            <E T="03">See id.</E>
                             at 6. This commenter stated that it is far cheaper for firms to implement new trading strategies “in a matter of minutes” than it is for them to rigorously test a new strategy before deployment, and that it is more profitable for firms to skimp on risk controls because controls take time. 
                            <E T="03">See id.</E>
                             Further, this commenter noted that the exchanges know, or should know, who “misbehaves,” but they are tangled in mixed incentives of their own, dependent on firms for the next quarter's profits and, at the same time, expected to moderate the firms' behavior. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1827</SU>
                             
                            <E T="03">See id.</E>
                             at 6-7.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that all SCI entities have some incentives to maintain robust systems in order to maximize long-term revenue. However, as evidenced by the various systems issues that have occurred prior to and since publication of the SCI Proposal, economic motivations alone have not been sufficient to significantly reduce systems issues.
                        <SU>1828</SU>
                        <FTREF/>
                         In addition, although SCI entities may suffer an economic and reputational burden if a systems issue becomes apparent to the trading community or the public, the Commission believes that SCI entities are not sufficiently incentivized to improve the robustness of these systems to prevent systems issues, as described in more detail below.
                        <SU>1829</SU>
                        <FTREF/>
                         Further, SCI entities may fail to internalize the risk of catastrophic failure associated with systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1828</SU>
                             
                            <E T="03">See supra</E>
                             Section II.B (discussing recent events involving systems-related issues).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1829</SU>
                             As noted above, the Commission acknowledges that the nature of technology and the level of sophistication and automation of current market systems prevent any measure, regulatory or otherwise, from completely eliminating all systems disruptions, intrusions, or other systems issues. 
                            <E T="03">See supra</E>
                             Section III.
                        </P>
                    </FTNT>
                    <P>As noted above, systems issues have ramifications on the securities markets beyond the impact on the entity responsible for or experiencing the systems issues (an “economic externality”). That is, a systems issue not only affects the entity responsible for the issue, but also directly affects other entities that use that entity. Often, when an SCI entity experiences a systems issue, all market participants that use that entity incur costs. For example, if market data systems fail, it affects anyone requiring such market data to make informed decisions. Also, when a matching engine fails, securities cannot be traded via that functionality. As discussed in greater detail below, the failure of a trading system not only forces the venue to forgo revenue, but also can diminish trading in financial instruments during the disruption. Additionally, the failure of a trading system can impose costs on market participants that have optimized their strategy so that trading costs are minimized. If the strategy of these market participants assumes that all trading venues are fully operational, then the failure of a trading system could impose additional transaction costs. The Commission believes that, in part because the costs of such externalities are not fully borne by SCI entities in the form of lost business, market forces alone are insufficient to significantly reduce SCI events.</P>
                    <HD SOURCE="HD3">Market for Trading Services</HD>
                    <P>
                        In the proposing release, the Commission identified many competitors in the market for trading services, including equities exchanges, options exchanges, ATSs, OTC market makers, and broker-dealers.
                        <SU>1830</SU>
                        <FTREF/>
                         Competitors for listed-equity (NMS) 
                        <PRTPAGE P="72403"/>
                        trading services include 11 national securities exchanges, none having an overall market share of 20 percent,
                        <SU>1831</SU>
                        <FTREF/>
                         44 ATSs, which account for 18% of dollar volume, and several hundred OTC market makers and broker-dealers, which account for 15.8% of dollar volume.
                        <SU>1832</SU>
                        <FTREF/>
                         In the SCI Proposal, the Commission recognized that all providers of trading services compete and have incentives to avoid systems disruptions, systems compliance issues, and systems intrusions because, for example, brokers and other entities will be inclined to route orders away from trading venues that have frequent systems problems. However, the Commission noted several limitations on competition, including market participants misjudging the quality of trading services because of incomplete information regarding SCI events and the limited number of competitors (in some cases only one competitor) that may offer trading services in a particular product.
                        <SU>1833</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1830</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18159.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1831</SU>
                             
                            <E T="03">See supra</E>
                             note 106 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1832</SU>
                             Calculated by Commission staff using market volume statistics reported by BATS and data from Form ATS-R for the second quarter of 2014. 
                            <E T="03">See supra</E>
                             notes 106 and 150. In 2012, 255 OTC market makers and broker-dealers accounted for 17% of volume. 
                            <E T="03">See</E>
                             DERA staff white papers, “Alternative Trading Systems: Description of ATS Trading in National Market System Stocks” by Laura Tuttle (
                            <E T="03">http://www.sec.gov/marketstructure/research/alternative-trading-systems-march-2014.pdf</E>
                            ) and “OTC Trading: Description of Non-ATS OTC Trading in National Market System Stocks” by Laura Tuttle (
                            <E T="03">http://www.sec.gov/marketstructure/research/otc_trading_march_2014.pdf</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1833</SU>
                             For example, a number of listed options and NMS stocks trade on only one venue.
                        </P>
                    </FTNT>
                    <P>
                        With respect to the market for trading services, one commenter stated that the current competitive market for trading services provides sufficient redundancies that make a disruption at any particular service provider minor.
                        <SU>1834</SU>
                        <FTREF/>
                         Another commenter noted that exchanges compete vigorously with one another and against broker-dealer execution platforms and cannot afford to develop a reputation for technology problems.
                        <SU>1835</SU>
                        <FTREF/>
                         This commenter also noted that the incidence of self-help declarations 
                        <SU>1836</SU>
                        <FTREF/>
                         has been reduced, which reflects technology enhancements by exchanges that are a direct result of the competitive environment in which exchanges operate.
                        <SU>1837</SU>
                        <FTREF/>
                         Similarly, another commenter stated that, apart from any regulatory standards, no organization has a greater stake in assuring the effective operation of its systems than the owners and operators of the entities that participate in the market structure.
                        <SU>1838</SU>
                        <FTREF/>
                         Moreover, one commenter stated that ATSs already have incentives to avoid any systems disruptions for competitive reasons and also perform numerous tests and employ best practices.
                        <SU>1839</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1834</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 6-8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1835</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1836</SU>
                             Rule 611(b) under Regulation NMS provides a number of exceptions from the general requirement to prevent trade-throughs of protected quotations. In particular, Rule 611(b)(1) provides the “self-help” exception, which applies when the “transaction that constituted the trade-through was effected when the trading center displaying the protected quotation that was traded through was experiencing a failure, material delay, or malfunction of its systems or equipment.” 
                            <E T="03">See</E>
                             17 CFR 242.611(b)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1837</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1838</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1839</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 4.
                        </P>
                    </FTNT>
                    <P>
                        Again, the Commission acknowledges that all providers of trading services compete and have some incentives to avoid systems issues. However, the Commission continues to believe that there are limits to the extent to which competition mitigates systems problems associated with trading services because providers of trading services compete on a variety of measures—for example, providing the best prices, deep quotes, and fast executions—not just the quality of their systems. As a result, an issue with trading systems might not significantly harm the SCI entity that experienced the issue. Additionally, competition in the market for trading services may also not sufficiently mitigate the occurrence and effects of SCI events because market participants may lack information about SCI events. The Commission believes that it is important for affected SCI entity members or participants and, in some cases, all members or participants of an SCI entity, to know about SCI events at a particular service provider.
                        <SU>1840</SU>
                        <FTREF/>
                         Moreover, even in markets where significant competition exists—such as the market for trading NMS securities, which has many competitors including exchanges and ATSs—entities that experience significant outages may temporarily lose market share, but may quickly regain the lost market share.
                        <SU>1841</SU>
                        <FTREF/>
                         The Commission believes that this further suggests that competition alone will not significantly reduce systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1840</SU>
                             
                            <E T="03">See supra</E>
                             Section VI.B.1 (discussing current practices of SCI entities regarding dissemination of information on systems-related issues).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1841</SU>
                             For example, on November 12, 2012, the NYSE experienced a failure in a matching engine that forced it to stop trading 216 stocks. 
                            <E T="03">See</E>
                             NYSE Market Status Alert, 
                            <E T="03">http://markets.nyx.com/nyse/market-status/view/11558.</E>
                             The NYSE lost market share on the day of the outage but regained its market share the next day. 
                            <E T="03">See generally http://www.batstrading.com/market_summary/</E>
                             (compiling data on market share).
                        </P>
                    </FTNT>
                    <P>
                        In addition, some entities that face little competition in one security may impose significant externalities on the market with little competitive recourse. For example, even though there may be multiple trading venues for the majority of securities, trading service providers may have limited means to transact in particular securities (
                        <E T="03">e.g.,</E>
                         certain index options exclusively traded on one options exchange) and thus, if systems issues persist at certain venues, brokers, investors, and other entities will not be able to trade the security until the venue that lists the security recovers. In this particular case, not only does the venue lose revenue from forgone volume, but market participants also incur costs because they are not able to trade the security. As a result, the Commission believes that competition alone in the market for trading services is not sufficient to reduce SCI events at entities providing these services.
                    </P>
                    <P>
                        As mentioned by one commenter,
                        <SU>1842</SU>
                        <FTREF/>
                         competitive forces among trading venues may also lead to “underinvestment and cutting corners.” For example, the incentive to migrate software from testing to the production environment to improve trading services (and thereby the entity's profitability) may promote an environment where software that has not been adequately tested is launched into production, thus increasing the potential for systems issues to develop.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1842</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 4 (stating that “[e]very firm in every industry is constantly balancing the cost of safety with scarcity of resources . . . [and t]he Commission's job in this regard is to compel these firms to act in their own long-term interests, and the interests of the public at-large, rather than any short-term interests that may be better served by underinvestment and cutting corners”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Market for Market Data</HD>
                    <P>
                        One commenter stated that Regulation SCI, as applied to market data, is unnecessary and will have “zero benefits” because the revenue from the sale of market data is an important revenue source for an SRO.
                        <SU>1843</SU>
                        <FTREF/>
                         Therefore, according to this commenter, SROs already have the right incentives to successfully collect, process, and disseminate market data.
                        <SU>1844</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1843</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 18-19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1844</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As noted above, the Commission has, on numerous occasions, emphasized the importance of market data, including the consolidated data feed.
                        <SU>1845</SU>
                        <FTREF/>
                         The Commission believes that consolidated market data is an important part of the investment and trading process as it helps market participants to make well-informed investment and trading decisions, and also helps investors to monitor the quality of execution of orders by their brokers. In addition, 
                        <PRTPAGE P="72404"/>
                        exchanges rely on accurate consolidated market data for many of their real-time functions. Even though demand is great, a total of only two SIPs collect, process, and distribute consolidated market data in NMS securities, and only a single SIP collects, processes, and distributes consolidated market data for any given security. Further, other providers of market data in markets other than NMS securities (
                        <E T="03">e.g.,</E>
                         municipal securities) may also be the sole providers of their data. Therefore, the Commission believes that the market data consolidators are not subject to significant competitive market forces. Further, because the demand for market data from the SIPs is inelastic,
                        <SU>1846</SU>
                        <FTREF/>
                         there is little incentive to improve reliability as few alternatives exist. Thus, the Commission believes that competition alone is not sufficient to reduce SCI events for market data consolidators. Because an SCI event in connection with market data can significantly disrupt markets, the Commission believes that regulation is needed and, as discussed below, will provide significant benefits.
                        <SU>1847</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1845</SU>
                             
                            <E T="03">See supra</E>
                             note 249 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1846</SU>
                             Demand is inelastic when demand does not diminish as price increases.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1847</SU>
                             For example, as discussed above, on August 22, 2013, Nasdaq halted trading in all Nasdaq-listed securities for more than three hours after the Nasdaq SIP, the single source of consolidated market data for Nasdaq-listed securities, became unable to process quotes from exchanges for dissemination to the public. 
                            <E T="03">See supra</E>
                             note 32 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Consideration of Costs and Benefits and the Effect on Efficiency, Competition, and Capital Formation</HD>
                    <HD SOURCE="HD3">1. Broad Economic Considerations</HD>
                    <P>The Commission has considered the economic effects of Regulation SCI as a whole as well as the specific effect of each rule. This section provides an overview of the broad economic considerations relevant to Regulation SCI and the economic effects, including the costs, benefits, and effects on efficiency, competition, and capital formation that are attributable to Regulation SCI as a whole. Additional economic effects, including benefits and costs, related to specific requirements in Regulation SCI and reasonable alternatives are discussed in Section VI.C.2 below.</P>
                    <P>The Commission has attempted, where possible, to quantify the benefits and costs anticipated to flow from Regulation SCI. The Commission notes, however, that many of the costs and benefits of Regulation SCI are difficult to quantify with any degree of certainty, especially as the current practices of market participants vary and are expected to evolve and adapt to changes in technology and market developments. For example, in some cases, quantification depends heavily on factors outside of the control of the Commission, particularly because Regulation SCI provides flexibility to an SCI entity to tailor its policies and procedures to the nature of its business, technology, and the relative criticality of each of its SCI systems. Additionally, in some cases, the Commission is unable to quantify the benefits and costs associated with Regulation SCI because the Commission lacks the information necessary to provide a reasonable estimate. For example, the Commission does not have sufficient information upon which to base an estimate of all costs associated with the various specific systems changes that may be required as the result of Regulation SCI. Accordingly, much of the discussion of economic effects is qualitative in nature but, again, where possible, the Commission has provided quantified information.</P>
                    <HD SOURCE="HD3">a. Benefits</HD>
                    <P>
                        The Commission believes that the adoption of, and compliance by SCI entities with Regulation SCI, will further the goals of the national market system as a result of each SCI entity establishing, maintaining, and enforcing written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. In this respect, Regulation SCI will promote the capacity, integrity, resiliency, availability, and security of the automated systems of entities important to the functioning of the U.S. securities markets, as well as reinforce the requirement that such systems operate in compliance with the Exchange Act and rules and regulations thereunder, thus strengthening the infrastructure of the U.S. securities markets and improving their resilience when technological issues arise. Regulation SCI also establishes an updated and formalized regulatory framework, thereby helping to ensure more effective Commission oversight of such systems. Although the Commission acknowledges that Regulation SCI likely will not eliminate all systems issues, the Commission believes that Regulation SCI will change and strengthen the practices of SCI entities, and should result in a number of benefits, including those summarized below.
                        <SU>1848</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1848</SU>
                             As noted above, in the SCI Proposal, the Commission encouraged commenters to identify, discuss, analyze, and supply relevant data, information, or statistics regarding benefits. The Commission notes that it is unable to quantify the benefits associated with Regulation SCI as a whole because quantitative data regarding each of the benefits is not readily available to the Commission, and commenters did not provide sufficient quantitative data to allow the Commission to do so.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that adopting Regulation SCI will result in fewer market disruptions due to systems issues, which could lead to fewer interruptions in the price discovery process 
                        <SU>1849</SU>
                        <FTREF/>
                         and liquidity flows and, thus, may result in fewer periods with pricing inefficiencies. Specifically, the Commission believes that Regulation SCI would improve systems up-time for SCI entities and also would promote more robust systems that directly support execution facilities, order matching, and the dissemination of market data. Systems issues that directly inhibit execution facilities, order matching, and dissemination of market data could cause slow executions and result in delaying the incorporation of information into prices, and thus could harm price efficiency and price discovery. System issues could also result in unfilled orders, depriving traders of an execution. The Commission believes that Regulation SCI would reduce the frequency, severity, and duration of such effects resulting from systems issues. Moreover, decreasing the number of trading interruptions could improve price discovery and liquidity because interruptions in trading interfere with the process in which relevant information gets incorporated into security prices and, thus, temporarily disrupt liquidity flows and lower the quality of the price discovery process. Further, because interruptions in liquidity flows and the price discovery process in one security can affect securities trading in other markets, reducing trading interruptions could have broad effects. For example, an interruption in the market for securities that underlie derivative securities (
                        <E T="03">e.g.,</E>
                         index options and futures) would harm the price discovery process for those products and potentially restrict liquidity flows between the stock market and the derivative markets.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1849</SU>
                             The price discovery process involves trading—buyers and sellers arriving at a transaction price for a specific asset at a given time. Thus, generally, any trading interruptions would interfere with the price discovery process.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also believes that Regulation SCI has the potential to reduce widespread SCI events. Given 
                        <PRTPAGE P="72405"/>
                        the speed and interconnected nature of the U.S. securities markets, a seemingly minor systems problem at a single entity can quickly create losses and liability for market participants, and spread rapidly across the national market system, potentially creating widespread damage and harm to market participants, including investors. By reducing systems issues, Regulation SCI also has the potential to decrease the risk of these catastrophic events.
                    </P>
                    <P>In addition, other benefits may derive from the additional information provided to the Commission and to members or participants of an SCI entity resulting from Regulation SCI. In particular, the information provided to the Commission should enhance the Commission's review and oversight of U.S. securities market infrastructure and foster cooperation between the Commission and SCI entities in responding to SCI events. Also, as noted in Section IV.B.3.c, the Commission believes that the aggregated data that will result from the reporting of SCI events will enhance its ability to comprehensively analyze the nature and types of various SCI events and identify more effectively areas of persistent or recurring problems across the systems of all SCI entities. Moreover, as discussed in Section IV.A.3, the Commission notification requirements for SCI events will help to focus the Commission's and SCI entities' resources on the more significant SCI events, as the Commission has determined to distinguish the timing of its receipt of information regarding SCI events based on their impact, with SCI events estimated to have a greater impact being subject to “immediate” Commission notification, and SCI events having no or a de minimis impact being subject to recordkeeping obligations, and for de minimis systems disruptions and de minimis systems intrusions, a quarterly summary notification. Moreover, the increased dissemination of information about SCI events to SCI entity members or participants could reduce search costs for market participants when they are gathering information to make a decision with respect to the use of an entity's services. As discussed more thoroughly below, by lowering search costs, the information dissemination requirement could provide SCI entities additional competitive incentives to ensure and maintain robust policies and procedures to promote systems capacity, integrity, resiliency, availability, security and compliance.</P>
                    <P>
                        Some commenters addressed how the availability of Commission resources may affect the benefits and costs of Regulation SCI. One commenter argued that Regulation SCI would result in misallocation of Commission resources.
                        <SU>1850</SU>
                        <FTREF/>
                         This commenter stated that it is likely that Regulation SCI would not reduce in a material manner the occurrence of systems issues at SCI entities, and Commission staff resources would be better devoted to working with the industry to develop best practices (not legal requirements) for all regulated entities in the areas of systems capacity, security, and integrity.
                        <SU>1851</SU>
                        <FTREF/>
                         Similarly, one commenter noted that unless the Commission and Congress devote sufficient resources to hiring enough skilled technical staff, Regulation SCI will devolve into a paperwork exercise with little added benefit to the markets.
                        <SU>1852</SU>
                        <FTREF/>
                         Another commenter stated that there is insufficient evidence regarding the resources and capacity of Commission staff to assess and analyze the data required to be provided under Regulation SCI.
                        <SU>1853</SU>
                        <FTREF/>
                         This commenter urged the Commission to consider its resources as the Commission accommodates new initiatives.
                        <SU>1854</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1850</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 6-7. This commenter noted that Commission staff resources used to oversee Regulation SCI compliance would dwarf those used for the ARP Inspection Program and that Commission staff would have to analyze and act upon notifications from SCI entities, including systems change notifications. 
                            <E T="03">See id.</E>
                             This commenter also noted that substantial examination resources from the Commission and FINRA would be assigned to Regulation SCI oversight. 
                            <E T="03">See id.</E>
                             Similarly, another commenter noted that proposed Regulation SCI would result in a dramatic increase in the number of Commission notifications and would require substantial resources for Commission staff to process them in a responsible fashion. 
                            <E T="03">See</E>
                             Omgeo Letter at 8, n. 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1851</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1852</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1853</SU>
                             
                            <E T="03">See</E>
                             SunGard Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1854</SU>
                             
                            <E T="03">See id.</E>
                             at 5.
                        </P>
                    </FTNT>
                    <P>As described throughout this release, the Commission believes that Regulation SCI will have significant benefits and that a regulatory solution is necessary because market forces alone are insufficient to significantly reduce SCI events in the relevant markets. The Commission has significant experience with the ARP Inspection Program, and thus has developed expertise in this area that it will apply to implementing and monitoring compliance with Regulation SCI. In light of this experience, the Commission believes that it can devote sufficient resources to carry out its obligations associated with Regulation SCI so that the benefits of Regulation SCI can be realized.</P>
                    <HD SOURCE="HD3">b. Costs</HD>
                    <P>Some of the costs associated with Regulation SCI are compliance costs. Compliance costs include, for example, documentation and mandatory reporting and dissemination of SCI events, and reports that include material systems changes. SCI entities will also incur costs in complying with the SCI review requirement, as well as in implementing the policies and procedures related to systems capacity, integrity, resiliency, availability, security, and compliance. Moreover, SCI entities will incur costs related to recordkeeping. Additional costs will also result from member/participant participation in the testing of SCI entity business continuity and disaster recovery plans. Also, market participants (including institutional and retail investors) in the securities markets may face increased transaction costs from SCI entities, to the extent that increased compliance costs are passed on to market participants.</P>
                    <P>
                        Many, but not all, of the quantifiable costs of Regulation SCI involve a collection of information, and these costs and burdens are discussed in the Paperwork Reduction Act section of this release.
                        <SU>1855</SU>
                        <FTREF/>
                         When the PRA burdens are monetized, the estimated paperwork related compliance burdens for SCI entities as a result of Regulation SCI total approximately $117 million initially and approximately $100 million annually.
                        <SU>1856</SU>
                        <FTREF/>
                         The Commission notes that the monetized PRA burdens have increased from those contained in the SCI Proposal. Although many of the adopted rules are more targeted and impose fewer requirements on SCI entities than the proposed rules, the monetized PRA burdens have changed in part due to modifications made to the PRA estimates as a result of recommendations from commenters, revisions to the rule text, and the revised estimate of the number of SCI events, which resulted from incorporating the Commission's review of the number of systems compliance-related issues and ARP incidents reported to Commission staff in 2013.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1855</SU>
                             
                            <E T="03">See supra</E>
                             Section V. The Commission provides below quantified estimates of other costs imposed by Regulation SCI beyond the PRA burdens, to the extent the Commission can quantify such costs.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1856</SU>
                             The monetized PRA cost reflects the paperwork cost estimated for all of Regulation SCI, as discussed in Section V.
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission has quantified non-paperwork related costs for SCI entities that total between approximately $14 million 
                        <SU>1857</SU>
                        <FTREF/>
                         and $106 million 
                        <SU>1858</SU>
                        <FTREF/>
                         in initial costs and between 
                        <PRTPAGE P="72406"/>
                        $9 million 
                        <SU>1859</SU>
                        <FTREF/>
                         and $70 million 
                        <SU>1860</SU>
                        <FTREF/>
                         in annual ongoing costs. In addition to the costs to SCI entities, the Commission also estimates the total connectivity costs to members or participants of SCI entities associated with the testing of business continuity and disaster recovery plans to be $18 million annually.
                        <SU>1861</SU>
                        <FTREF/>
                         Thus, the Commission estimates total quantified costs for SCI entities and members or participants of SCI entities to be between approximately $149 million 
                        <SU>1862</SU>
                        <FTREF/>
                         and $241 million 
                        <SU>1863</SU>
                        <FTREF/>
                         in initial costs and between $127 million 
                        <SU>1864</SU>
                        <FTREF/>
                         and $188 million 
                        <SU>1865</SU>
                        <FTREF/>
                         in annual ongoing costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1857</SU>
                             
                            <E T="03">See infra</E>
                             note 1943 (estimating cost for complying with the policies and procedures required by Rules 1001(a) and (b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1858</SU>
                             
                            <E T="03">See infra</E>
                             note 1944 (estimating cost for complying with the policies and procedures required by Rules 1001(a) and (b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1859</SU>
                             
                            <E T="03">See infra</E>
                             note 1945 (estimating cost for complying with the policies and procedures required by Rule 1001(a) and (b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1860</SU>
                             
                            <E T="03">See infra</E>
                             note 1946 (estimating cost for complying with the policies and procedures required by Rule 1001(a) and (b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1861</SU>
                             
                            <E T="03">See infra</E>
                             note 2065.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1862</SU>
                             $149 million = $117 million (PRA cost) + $14 million (other costs for SCI entities) + $18 million (connectivity costs for members or participants of SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1863</SU>
                             $241 million = $117 million (PRA cost) + $106 million (other costs for SCI entities) + $18 million (connectivity costs for members or participants of SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1864</SU>
                             $127 million = $100 million (PRA cost) + $9 million (other costs for SCI entities) + $18 million (connectivity costs for members or participants of SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1865</SU>
                             $188 million = $100 million (PRA cost) + $70 million (other costs for SCI entities) + $18 million (connectivity costs for members or participants of SCI entities).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters provided broad comments regarding the costs of proposed Regulation SCI.
                        <SU>1866</SU>
                        <FTREF/>
                         According to one commenter, Regulation SCI as proposed is “too universal in its application, too ambitious in its scope and too costly in its implementation to achieve the hoped for reduction in risk to the markets without simultaneously diminishing other important SEC accomplishments, such as increased competition, improved innovation, increased consumer choice, lower barriers to entry into the industry and reduced transaction costs to the customer.” 
                        <SU>1867</SU>
                        <FTREF/>
                         Another commenter noted that proposed Regulation SCI would impose an unreasonably burdensome technology and controls standard on automated systems of SCI entities, which could lead to allocative inefficiencies in the marketplace and therefore have a stifling effect on innovation in the U.S. equity markets.
                        <SU>1868</SU>
                        <FTREF/>
                         Another commenter stated that the ultimate result of proposed Regulation SCI will be to limit or suppress the execution choice of buy-side investors, meaning investors will have less ability to effectively manage their trading strategies and diminished opportunities to seek better execution, lower transaction costs, and achieve price improvement and investment performance.
                        <SU>1869</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1866</SU>
                             One commenter provided “conservative and preliminary” estimates for the cost of compliance with Regulation SCI. 
                            <E T="03">See</E>
                             FINRA Letter at 42-43. This commenter estimated that its one-time cost to comply with Regulation SCI would be between approximately $1.1 million and $1.3 million, and its ongoing annual costs would be between approximately $4.5 million and $5.5 million, if Regulation SCI is adopted as proposed (
                            <E T="03">e.g.,</E>
                             if SCI systems is defined to apply to non-market regulatory and surveillance systems, and development and testing environments). 
                            <E T="03">See id.</E>
                             at 42. As discussed above, the definition of SCI systems does not include non-market regulation and non-market surveillance systems, or development and testing systems. Therefore, the Commission believes these estimates are too high. This commenter estimated that, under a narrower Regulation SCI (
                            <E T="03">e.g.,</E>
                             if non-market systems and development and testing environments are excluded from the definition of SCI systems), its one-time compliance costs would be between approximately $675,000 and $825,000 and its annual costs would be between approximately $2.2 million and $2.6 million. 
                            <E T="03">See id.</E>
                             This commenter also stated that, monetizing its hour estimates for annual SCI reviews, its compliance costs would increase by between approximately $600,000 and $900,000, and higher if more systems than currently in scope under ARP would be subject to annual SCI reviews. 
                            <E T="03">See id.</E>
                             at 42. The Commission notes that, other than the costs for SCI reviews, these estimates do not distinguish paperwork costs from non-paperwork costs. If the commenter's estimates are intended to include all costs for compliance with Regulation SCI, these estimates are close to or within the Commission's estimated total quantified cost ranges for SCI entities. 
                            <E T="03">See supra</E>
                             notes 1862-1865 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1867</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1868</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1869</SU>
                             
                            <E T="03">See</E>
                             UBS Letter at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        As discussed throughout this release, the Commission believes that Regulation SCI will change and strengthen the practices of SCI entities, and should result in a number of benefits. Further, the Commission believes that these benefits should result without diminishing the Commission's accomplishments in other areas, stifling innovation, or suppressing the execution choice of investors. In particular, although costs associated with Regulation SCI could adversely impact competition and increase barriers to entry, the Commission believes that the adverse effect on competition and heightened barriers for SCI entities that provide venues for trading, including ATSs and exchanges, would be mitigated and therefore the Commission does not expect that investor choice on trading venues would be significantly limited.
                        <SU>1870</SU>
                        <FTREF/>
                         The Commission also believes that any such effects would be warranted in light of the expected benefits of Regulation SCI. Additionally, as discussed below, the dissemination of information regarding certain major SCI events to all members or participants of an SCI entity can promote competitive incentives to prevent systems issues. The Commission also believes that the reduction in systems issues resulting from Regulation SCI could result in fewer interruptions in the price discovery process and liquidity flows and thus result in fewer periods with pricing inefficiencies. Furthermore, Regulation SCI could improve system uptime for SCI entities, and therefore reduce latency as market participants will not be forced to reroute orders or change execution strategies associated with situations in which an SCI entity is not operational.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1870</SU>
                             
                            <E T="03">See infra</E>
                             Section VI.C.1.c (addressing potential effects on efficiency, competition, and capital formation, including effects on other SCI entities).
                        </P>
                    </FTNT>
                    <P>
                        Moreover, the Commission notes that it has revised the proposed rules after considering the comments received. The Commission believes that many of the revisions to the proposed rules would reduce burdens on SCI entities and significantly address commenters' concerns regarding potential negative effects on allocative inefficiency and innovation. For example, because the Commission is adopting a quarterly reporting requirement for material systems changes instead of the proposed 30-day advance notification requirement, adopted Regulation SCI would impose lower burdens on SCI entities compared to the proposal and allow SCI entities more flexibility when they implement material systems changes.
                        <SU>1871</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1871</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.4.b.i.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Effects on Efficiency, Competition, and Capital Formation</HD>
                    <P>Along with the effects on efficiency, competition, and capital formation discussed below with regard to specific provisions of Regulation SCI, the Commission believes that Regulation SCI as a whole could affect efficiency, competition, and capital formation in several ways.</P>
                    <P>
                        By increasing the robustness of SCI systems and indirect SCI systems of SCI entities, Regulation SCI may improve efficiency—in particular, price efficiency—and the improvement in pricing efficiency could promote capital formation. In particular, as discussed in VI.C.1, disruptions to SCI systems and the resulting trading interruptions can degrade pricing efficiency, price discovery, and liquidity. Regulation SCI may reduce the frequency, severity, and duration of market disruptions (
                        <E T="03">e.g.,</E>
                         trading interruptions) that may otherwise prevent market participants from impounding information into security prices through market activity (
                        <E T="03">e.g.,</E>
                         order submission) and, thus, 
                        <PRTPAGE P="72407"/>
                        improve price efficiency in the markets. Such disruptions also impose liquidity costs and harm the price discovery process. The quality of the price discovery process has important implications for efficiency and capital formation, as prices that accurately convey information about fundamental value improve the efficiency with which capital is allocated across projects and firms.
                    </P>
                    <P>
                        The Commission also believes that Regulation SCI could affect competition in several ways. The Commission believes that the existing competition among the markets has not sufficiently mitigated the occurrence of SCI events.
                        <SU>1872</SU>
                        <FTREF/>
                         Regulation SCI requires SCI entities to disseminate information regarding certain SCI events to affected members or participants or to all members or participants of an SCI entity. As discussed more thoroughly in Section VI.C.2.b.iv below, the Commission believes that requiring the dissemination of information regarding certain SCI events could further incentivize SCI entities to maintain more robust SCI systems and indirect SCI systems and would enhance competition among SCI entities with respect to the maintenance of robust SCI systems and indirect SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1872</SU>
                             
                            <E T="03">See supra</E>
                             Section VI.B.4.
                        </P>
                    </FTNT>
                    <P>
                        Additionally, the Commission believes that Regulation SCI may have an impact on competition among SCI entities, in part because the compliance costs of Regulation SCI will be different among SCI entities. Specifically, some SCI entities already satisfy some of the requirements of Regulation SCI because those provisions codify certain aspects of the ARP Policy Statements. The Commission believes that these current ARP participants will incur direct compliance costs that are incremental relative to the current cost of participating in the ARP Inspection Program and current practices outside of the scope of ARP. But Regulation SCI also applies to some entities that currently do not participate in the ARP Inspection Program such as the MSRB and most SCI ATSs. These SCI entities may incur higher initial compliance costs, compared to current ARP participants, in modifying their current practices to comply with Regulation SCI.
                        <SU>1873</SU>
                        <FTREF/>
                         To the extent that SCI entities with different initial compliance costs compete, Regulation SCI could alter the competitive relationship and give SCI entities that are currently in compliance with certain provisions of Regulation SCI a competitive advantage.
                        <SU>1874</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1873</SU>
                             The Commission notes that the SCI entities incurring the lower initial compliance costs previously incurred such costs to participate in the ARP Inspection Program.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1874</SU>
                             However, given the voluntary nature of the current ARP Inspection Program, the extent of current compliance with the requirements of adopted Regulation SCI by entities subject to the ARP Inspection Program varies.
                        </P>
                    </FTNT>
                    <P>In addition to competition among SCI entities, the compliance costs imposed by Regulation SCI could have an effect on competition between SCI entities and non-SCI entities in the markets for trading services. Specifically, in part because non-SCI entities do not have to incur the compliance costs associated with Regulation SCI, these entities may have a competitive advantage in the markets for trading services over SCI entities that they compete with. The adverse competitive effects, however, are likely to be minor when considering only ATSs because an SCI ATS is likely to be larger and have more of an established customer base than other ATSs. The Commission recognizes that broker-dealers also compete with SCI entities in the market for trading services and that some broker-dealers are larger than some ATSs and exchanges. However, broker-dealers cannot offer the same services as ATSs or exchanges without becoming ATSs or exchanges.</P>
                    <P>
                        The costs imposed by Regulation SCI could also affect barriers to entry for new ATSs and exchanges and, thus, could adversely affect competition.
                        <SU>1875</SU>
                        <FTREF/>
                         Specifically, the Commission acknowledges that Regulation SCI will increase the costs for those that meet the definition of SCI entity. This will increase the expected costs of market entrants who expect to eventually be SCI entities. If an increase in these costs reduces the number of potential new entrants, the potential competition from new entrants will be lower.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1875</SU>
                             While Regulation SCI could also increase start-up costs for SIPs and registered clearing agencies, SIPs provide exclusive services and registered clearing agencies are currently characterized by specialization and limited competition. Clearing and settlement services exhibit high barriers to entry and economies of scale. 
                            <E T="03">See</E>
                             Clearing Agency Standards Release, 
                            <E T="03">supra</E>
                             note 76, at 66263 and 66265.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, however, the Commission believes that the heightened barriers to entry for ATSs would be mitigated to some degree because the compliance period would provide a new ATS entrant the opportunity to initiate and develop its business before the ATS would need to comply with Regulation SCI.
                        <SU>1876</SU>
                        <FTREF/>
                         In particular, the Commission believes that few new ATSs would likely initially meet the threshold to be covered under Regulation SCI and a new ATS could trade for at least three months (
                        <E T="03">i.e.,</E>
                         less than four of the preceding six months) and conduct such trading at any level without being subject to Regulation SCI. The Commission also notes that ATSs meeting the volume thresholds in the definition of “SCI ATS” for the first time will also be provided six months from the time that the ATS first meets the applicable thresholds to comply with the requirements of Regulation SCI.
                        <SU>1877</SU>
                        <FTREF/>
                         This compliance period should also provide such ATSs with time to plan on how they would meet the requirements of Regulation SCI, and could also potentially allow SCI ATSs to become more equipped to bear the cost of Regulation SCI once compliance is required, and thus not significantly discourage new ATSs from entering the market and growing. For newly registered exchanges, the Commission believes the costs associated with Regulation SCI would not represent a significant increased barrier to entry, as the costs would represent a small portion of total costs associated with creating and registering an exchange.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1876</SU>
                             
                            <E T="03">See supra</E>
                             note 152.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1877</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.F (discussing effective date and compliance dates for Regulation SCI).
                        </P>
                    </FTNT>
                    <P>
                        The compliance costs associated with participating in business continuity and disaster recovery plan testing may affect competition among members or participants of SCI entities and also could raise barriers to entry for new members or participants. In particular, Regulation SCI imposes compliance costs on certain members or participants of SCI entities that are designated to participate in business continuity and disaster recovery plans testing. Because some members or participants may incur compliance costs associated with Rule 1004 and others may not, it could negatively impact the ability for some to compete and could raise barriers to entry. As discussed more thoroughly in Section VI.C.2.b.vii below, the Commission expects the compliance costs associated with the business continuity and disaster recovery plans testing requirements in Rule 1004 to be limited for larger members or participants who already maintain connections to backup facilities, including for testing purposes, than for smaller members or participants. Furthermore, the Commission believes that new members or participants are less likely to be designated immediately to participate in business continuity and disaster recovery plan testing than existing significant members or participants because new members may not initially satisfy the SCI entity's designation standards as they establish their businesses. Thus, the Commission 
                        <PRTPAGE P="72408"/>
                        believes the adverse effect on competition may be mitigated to some extent as the most likely members or participants to be designated for testing are those comprising the largest market share as ranked by volume by the SCI entity, and that these firms will have more limited compliance costs.
                        <SU>1878</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1878</SU>
                             The Commission also notes that SCI entities have an incentive to limit the imposition of the cost and burden associated with testing to the minimum necessary to comply with Rule 1004, and that, given the option, most SCI entities would, in the exercise of reasonable discretion, prefer to designate fewer members or participants to participate in testing, than to designate more. 
                            <E T="03">See supra</E>
                             Section IV.B.6.b.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Analysis of Final Rules</HD>
                    <HD SOURCE="HD3">a. Definitions—Rule 1000</HD>
                    <P>In general, the definitions in Rule 1000 either clarify a provision or circumscribe the scope of a provision in Regulation SCI. Therefore, many of the costs and benefits associated with the impacts of the definitions are incorporated in the discussion of the substantive requirements of Regulation SCI. This section contains a discussion of the economic effects of the scope of Regulation SCI resulting from the definitions adopted by the Commission.</P>
                    <HD SOURCE="HD3">i. SCI Entities</HD>
                    <P>
                        The Commission estimates that the definition of SCI entity in Rule 1000 currently covers 44 entities. This includes 30 current participants in the ARP Inspection Program (
                        <E T="03">i.e.,</E>
                         18 registered national securities exchanges, seven registered clearing agencies, FINRA, two plan processors, one ATS trading NMS stocks, and one exempt clearing agency). The definition of SCI entity also includes one ATS that currently exceeds the relevant threshold in Rule 301(b)(6)(i) of Regulation ATS and is subject to the systems safeguard requirements of Regulation ATS. In addition to these entities, the definition of SCI entity includes the MSRB and an estimated 12 additional SCI ATSs.
                    </P>
                    <P>Generally, by including certain entities that do not currently participate in the ARP Inspection Program or meet the current threshold for the systems safeguard requirements of Regulation ATS in the definition of SCI entity, the Commission believes that Regulation SCI will not only enhance systems resiliency at such entities, but also reduce the potential for incidents at these entities to have broader, disruptive effects across the securities markets more generally on other SCI entities, and attendant costs to investors. Although the Commission believes that the requirements of Regulation SCI will reduce the impact of SCI events, the Commission is unable to quantify the economic effects of the reduction because the degree to which adherence to the requirements of Regulation SCI will reduce the impact of SCI events is unknown.</P>
                    <P>As discussed throughout the economic analysis, the Commission also expects that SCI entities will incur costs for complying with the requirements of Regulation SCI and that these costs could affect the competitiveness of entities incurring such costs. For example, the section summarizing the effects of Regulation SCI on efficiency, competition, and capital formation, Section VI.C.1.c, discusses several ways that Regulation SCI might affect the competitiveness of SCI entities, including the competitiveness of SCI entities versus non-SCI entities, the relative initial competitiveness of SCI entities needing to make more changes to comply with Regulation SCI, and barriers to entry for SCI entities.</P>
                    <P>
                        As discussed in detail in Section IV.A.1, many commenters addressed the scope of the definition of SCI entity. Many of these comments related to the inclusion of certain ATSs in the definition.
                        <SU>1879</SU>
                        <FTREF/>
                         Commenters presented mixed views on the inclusion of ATSs, with some commenters believing that all ATSs should be covered by Regulation SCI,
                        <SU>1880</SU>
                        <FTREF/>
                         and other commenters arguing that no ATSs should be covered by Regulation SCI.
                        <SU>1881</SU>
                        <FTREF/>
                         The commenters who supported including all ATSs in the scope of the definition of SCI entity argued that any ATS can impact the market and one of these commenters also stated that any participant on any ATS can have disproportionate impact on the market.
                        <SU>1882</SU>
                        <FTREF/>
                         One of the main points of commenters that suggested no ATSs should be covered was that ATSs are redundant of exchanges and other ATSs and that, in case an ATS fails, other ATSs or exchanges can service investors and absorb trading volume.
                        <SU>1883</SU>
                        <FTREF/>
                         Additionally, some commenters suggested applying higher thresholds in the definition of SCI ATS such that fewer ATSs would be covered under Regulation SCI.
                        <SU>1884</SU>
                        <FTREF/>
                         Many of these commenters who advocated for applying higher thresholds in the definition of SCI ATS stated that the inclusion of smaller ATSs in the definition of SCI ATS does not justify what they believed to be the significant compliance costs imposed by Regulation SCI.
                        <SU>1885</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1879</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1.b.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1880</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 8-10; and Lauer Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1881</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 3; ITG Letter at 2-4; and OTC Markets Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1882</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NYSE Letter at 8-10; and Lauer Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1883</SU>
                             
                            <E T="03">See, e.g.,</E>
                             BIDS Letter at 7-8; and ITG Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1884</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Direct Edge Letter at 2; ITG Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1885</SU>
                             
                            <E T="03">See, e.g.,</E>
                             ITG Letter at 9-10.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that certain ATSs should be required to comply with rules regarding systems capacity, integrity, resiliency, availability, security, and compliance. ATSs now collectively represent a significant source of liquidity for NMS stocks.
                        <SU>1886</SU>
                        <FTREF/>
                         Given this level of activity on ATSs, coupled with the increasingly inter-connected and complex nature of the markets and heavy reliance on automated systems, the Commission recognizes that a systems issue even at one ATS could result in a market-wide impact. Further, some ATSs execute a larger portion of consolidated volume than smaller exchanges. In this respect, an outage at one or more of these ATSs, which serve as markets to bring buyers and sellers together in the national market system, could disrupt the entire market and could pose even greater risks to the market as a whole than certain smaller exchanges. Accordingly, the Commission believes that the exclusion of all ATSs from the definition of SCI entity would significantly reduce the benefits of Regulation SCI discussed in Section VI.C.1. On the other hand, the Commission believes that including all ATSs in the definition of SCI entity would heighten barriers to entry and restrict competition in the markets for trading services and, thus, could stifle innovations. As discussed in Section IV.A.1.b, the Commission believes that the adopted thresholds for SCI ATSs result in the inclusion of ATSs that can play a significant role in the securities markets and, given their heavy reliance on automated systems, have the potential to impact investors, the overall market, and the trading of individual securities should an SCI event occur. With respect to comments calling for higher or lower volume thresholds, the Commission believes that higher thresholds would increase the risk of significant market disruptions due to SCI events relative to the adopted thresholds and lower thresholds would serve to increase barriers to entry. In setting the levels in the thresholds for SCI ATS, the Commission has considered the trade-offs between barriers to entry and the risk of significant market disruptions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1886</SU>
                             
                            <E T="03">See supra</E>
                             note 148 and accompanying text. 
                            <E T="03">See also</E>
                             text accompanying 
                            <E T="03">supra</E>
                             note 1832.
                        </P>
                    </FTNT>
                    <P>
                        In adopting the thresholds in the definition of SCI ATS, the Commission also considered alternative thresholds, 
                        <PRTPAGE P="72409"/>
                        including the threshold used in Regulation ATS. The adopted thresholds in the definition of SCI ATS differ from the thresholds that subject an ATS to the systems safeguard requirements under Rule 301(b)(6) of Regulation ATS in several ways.
                        <SU>1887</SU>
                        <FTREF/>
                         First, for ATSs that trade NMS stocks or non-NMS stocks, the adopted thresholds are based on dollar trading volume instead of share trading volume. The Commission believes that the application of dollar trading volume thresholds better reflects the potential economic impact of a systems issue at a significant ATS as it more accurately measures the value of trading activity compared to a threshold based on share trading volume.
                        <SU>1888</SU>
                        <FTREF/>
                         Second, the adopted volume thresholds for NMS stocks and non-NMS stocks are lower than the volume thresholds in Rule 301(b)(6) of Regulation ATS. As discussed in IV.A.1.b, securities trading has evolved significantly since the adoption of Regulation ATS; today, trading activity in stocks is more dispersed among a larger number of trading venues. Because trading activity in stocks is now dispersed among a larger number of trading venues and markets today are so inter-connected and complex, the Commission believes that the application of lower volume thresholds would more effectively capture multiple sources of potential systems issues that could significantly disrupt the market for a single security or for the market as a whole. Third, with respect to ATSs that trade NMS stocks, the Commission is adopting the two-fold dollar volume thresholds in the first prong—a single NMS stock threshold and an all NMS stocks threshold. The Commission believes that such thresholds would appropriately account for the significance of an ATS in both overall trading of NMS stocks and for a single NMS stock.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1887</SU>
                             
                            <E T="03">See also supra</E>
                             Section IV.A.1.b.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1888</SU>
                             
                            <E T="03">See</E>
                             text accompanying 
                            <E T="03">supra</E>
                             note 161; 
                            <E T="03">see also</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18094 (stating that the use of dollar thresholds may better reflect the economic impact of trading activity).
                        </P>
                    </FTNT>
                    <P>
                        With regard to commenters that stated no ATSs should be covered because ATSs are redundant of exchanges and other ATS, the Commission acknowledges that, to some extent, certain services provided by any trading venue, including exchanges and ATSs, are redundant in the sense that these facilities execute and process trades. However, the Commission notes that each ATS provides different services in terms of, among other things, order types, matching rules, and the speed of execution to meet investors' specific needs. If an ATS outage interferes with the supply of certain services that investors demand, it would impose costs on investors. For example, market participants may program their routing algorithms assuming that all market centers are operational. If one of those venues is not available, rerouting order flow may increase costs to the market participant seeking execution as time required for executing orders may increase, order fill rates may decrease, and slippage 
                        <SU>1889</SU>
                        <FTREF/>
                         may also increase, which would further increase transaction costs.
                        <SU>1890</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1889</SU>
                             Slippage refers to the difference between the expected price of a trade and the actual trade price due to the passage of time.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1890</SU>
                             
                            <E T="03">See supra</E>
                             Section VI.B.4 for a discussion of why market incentives do not seem to reduce these costs.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also received comments regarding the inclusion of fixed-income ATSs. One commenter suggested the use of par value traded rather than volume.
                        <SU>1891</SU>
                        <FTREF/>
                         Further, in noting that fixed-income ATSs should not be subject to Regulation SCI, this commenter noted that retail fixed-income ATSs operate on a vastly different scale than institutional equity markets.
                        <SU>1892</SU>
                        <FTREF/>
                         According to this commenter, the costs of compliance for a retail fixed-income ATS would be several orders of magnitude higher than for an exchange in the equity market, and would overwhelm revenues for retail fixed-income ATSs.
                        <SU>1893</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1891</SU>
                             
                            <E T="03">See</E>
                             TMC Letter at 1-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1892</SU>
                             
                            <E T="03">See id.</E>
                             at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1893</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The Commission, after considering the views of commenters, has determined to exclude ATSs that trade only municipal securities or corporate debt securities from the definition of SCI ATS at this time.
                        <SU>1894</SU>
                        <FTREF/>
                         Accordingly, such fixed-income ATSs will not be subject to the requirements of Regulation SCI. Rather, fixed-income ATSs will continue to be subject to the existing requirements in Rule 301(b)(6) of Regulation ATS regarding systems capacity, integrity and security if they meet the twenty percent threshold for municipal securities or corporate debt securities provided by that rule.
                        <SU>1895</SU>
                        <FTREF/>
                         Because no such ATS is subject to Regulation SCI at this time, it is possible that the municipal security and corporate debt markets may be affected by SCI events that otherwise may have been prevented with more robust systems that would result from Regulation SCI. However, the Commission believes that this loss in potential benefit relative to the proposed approach would be minimal as fixed-income securities trading is generally significantly less automated than trading in equities.
                        <SU>1896</SU>
                        <FTREF/>
                         Further, as commenters pointed out, the cost of the requirements of Regulation SCI could be significant for fixed-income ATSs relative to their size, scope of operations, and more limited potential for systems risk. Therefore, lowering the current threshold applicable to fixed-income ATSs in Regulation ATS and subjecting such ATSs to the requirements of Regulation SCI could have potentially discouraged the growth of automation that could benefit investors in these markets. However, as the Commission monitors the evolution of automation in this market, the Commission may reconsider the benefits and costs of extending the requirements of Regulation SCI to fixed-income ATSs in the future.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1894</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.1.b.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1895</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1896</SU>
                             The Commission notes that the corporate debt and municipal securities markets are primarily voice markets with little automation. 
                            <E T="03">See also supra</E>
                             note 185 (discussing the view of commenters that the inclusion of fixed-income ATSs and/or the adoption of the proposed thresholds would impose unduly high costs on these entities given their size, scope of operations, lack of automation, low speed, and resulting low potential to pose risk to systems).
                        </P>
                    </FTNT>
                    <P>
                        The adopted definition of SCI SRO includes all national securities exchanges regardless of their volume share. The Commission received one comment letter stating that the rule should also include volume thresholds for exchanges.
                        <SU>1897</SU>
                        <FTREF/>
                         The Commission is not persuaded that applying a volume threshold is appropriate for SCI SROs that are exchanges, but instead believes that Regulation SCI should cover all exchanges. In particular, the Commission recognizes that all exchanges play an important role in the securities markets. As discussed above in Section IV.A.1.a, all stock exchanges are subject to a variety of specific public obligations under the Exchange Act, including the requirements of Regulation NMS which, among other things, designates the best bid or offer of such exchanges to be protected quotations. Accordingly, every exchange may have a protected quotation that can obligate market participants to send orders to that exchange if such exchange is displaying the best bid or offer. Among other reasons, given that market participants may be required to send orders to any one of the exchanges at any given time if such exchange is displaying the best bid or offer, the Commission believes that it is important that the safeguards of Regulation SCI apply equally to all exchanges irrespective of trading volume. As 
                        <PRTPAGE P="72410"/>
                        market participants may be required to send orders to the exchange displaying the best prices, systems issues at such exchange could force market participants to re-route their orders and, thus, could increase execution time and slippage, imposing additional transaction costs to investors.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1897</SU>
                             
                            <E T="03">See supra</E>
                             note 81 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        With respect to options exchanges, the Commission additionally believes that it would be inappropriate to exclude them from the definition of SCI SRO because technology risks are equally applicable to such exchanges, as evidenced by recent technology incidents affecting the options markets.
                        <SU>1898</SU>
                        <FTREF/>
                         While there are many options that trade on multiple venues, systems issues resulting in trading disruptions at an options exchange could lower the quality of pricing efficiency and disrupt the price discovery process for singly-listed options (
                        <E T="03">e.g.,</E>
                         certain index options only trade on one options exchange). As such, systems issues at options exchanges can pose significant risks to the markets, and the Commission believes that the inclusion of options exchanges within the scope of Regulation SCI is necessary to achieve the goals of Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1898</SU>
                             
                            <E T="03">See supra</E>
                             note 84.
                        </P>
                    </FTNT>
                    <P>The definition of SCI entity also includes the MSRB. The Commission believes that the inclusion of the MSRB as an SCI entity will provide several significant benefits. In particular, the MSRB collects and consolidates municipal securities data and makes it available to market participants. The Commission believes that any event that could affect the market data collected and consolidated by the MSRB could significantly disrupt the municipal bond market. Also, the municipal securities data collected by the MSRB is provided to FINRA and made available to the Commission and the bank regulators, and serves as a key resource for monitoring the municipal bond market. Therefore, the inclusion of the MSRB will help ensure the robustness of the MSRB's systems and reduce the likelihood of systems issues that could harm investors in the municipal bond market.</P>
                    <P>
                        As discussed above in Section IV.A.1, several commenters advocated the adoption of a “risk-based” approach in the definition of SCI entity based on the criticality of the functions performed.
                        <SU>1899</SU>
                        <FTREF/>
                         In effect, these commenters suggested that the Commission apply provisions of Regulation SCI based on the entity's risk to the operations of the U.S. securities markets based on the entity's functional role in the market (
                        <E T="03">e.g.,</E>
                         a primary listing market, the sole venue of the security, a monopoly or utility type role with no redundancy). The Commission has considered these factors in developing the definition of SCI entity and believes that the adopted definition, in part, captures the intent of the commenters' suggestions in that it includes entities in the definition that play a significant role in the securities markets. In particular, as discussed in Section IV.A.1.a in detail, the Commission included all exchanges in the definition of SCI SRO because exchanges play a significant role in the functioning of securities markets. With respect to the comments that suggested including only those entities that are essential to continuous market-wide operation, the Commission believes that the specific criteria suggested by commenters, in effect, could lead to the exclusion of significant ATSs. As discussed above, the Commission continues to believe that significant ATSs that trade NMS and non-NMS stocks should be included in Regulation SCI. ATSs collectively represent a significant source of liquidity for stocks. Furthermore, as today's markets are increasingly inter-connected and complex with heavy reliance on automated systems, the Commission recognizes that a systems issue at an ATS could result in a market-wide impact. Consequently, the Commission believes that re-defining SCI entities according to commenters' “risk-based” approach could exclude certain entities that the Commission believes have the potential to pose significant risks to the securities markets should an SCI event occur, and thus limit the potential benefits from Regulation SCI, which are discussed throughout this economic analysis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1899</SU>
                             
                            <E T="03">See supra</E>
                             notes 53-57 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. SCI Systems</HD>
                    <P>
                        Regulation SCI expands on current practice, and applies to a broader range of systems than the current ARP Inspection Program. In particular, the ARP Policy Statements are focused on specific types of automated systems.
                        <SU>1900</SU>
                        <FTREF/>
                         The ARP Policy Statements and the ARP Inspection Program address systems that directly support trading, clearance and settlement, order routing, and market data. The definition of “SCI systems” would include these systems, as well as those that directly support market regulation and market surveillance, systems that serve an essential function for investor protection and market integrity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1900</SU>
                             
                            <E T="03">See supra</E>
                             Section II.A and Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at Section I.A (discussing in more detail the ARP Policy Statements and the ARP Inspection Program). According to the ARP I Release, the term “automated systems” or “automated trading systems” means computer systems for listed and OTC equities, as well as options, that electronically route orders to applicable market makers and systems that electronically route and execute orders, including the data networks that feed the systems. These terms also encompass systems that disseminate transaction and quotation information and conduct trade comparisons prior to settlement, including the associated communication networks. 
                            <E T="03">See</E>
                             ARP I Release, 
                            <E T="03">supra</E>
                             note 1, at 48706, n. 21.
                        </P>
                    </FTNT>
                    <P>The inclusion of market regulation and market surveillance systems under Regulation SCI could reduce systems compliance issues that result from disruptions in systems that support market regulation and market surveillance. The Commission believes that including market regulation and market surveillance systems under the definition of SCI systems should help ensure the robustness of the systems used by SCI entities to monitor compliance with relevant laws, rules, and their own rules, and detect any violations of such laws or rules by members or participants. The reduction in market regulation and market surveillance systems issues could help ensure investor protection and preserve market integrity.</P>
                    <P>
                        The Commission also believes that the inclusion of market data systems in the definition of SCI systems will benefit the market. Currently, SIAC, Nasdaq, and the MSRB 
                        <SU>1901</SU>
                        <FTREF/>
                         process, collect, and disseminate market data on equities, options, and municipal securities to investors. While SIAC and Nasdaq are part of the ARP Inspection Program, the MSRB is not. The Commission believes that consolidated market data is an important part of the investing and trading process as it helps market participants to make well-informed investment and trading decisions, and also helps investors to monitor the quality of execution of orders by their brokers. Thus, any SCI events that affect market data processed, collected, and disseminated by the MSRB could reduce 
                        <PRTPAGE P="72411"/>
                        pricing efficiency and, consequently, could significantly disrupt the municipal bond market. Further, with respect to NMS securities, the Commission understands that many trading algorithms make trading decisions based primarily on market data and rely on that data being current and accurate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1901</SU>
                             As discussed above, in 2008, the Commission amended Rule 15c2-12 to designate the MSRB as the single centralized disclosure repository for continuing municipal securities disclosure. In 2009, the MSRB established EMMA, which serves as the official repository of municipal securities disclosure and provides the public with free access to relevant municipal securities data, and is the central database for information about municipal securities offerings, issuers, and obligors. Additionally, the MSRB's RTRS, with limited exceptions, requires municipal bond dealers to submit transaction data to the MSRB within 15 minutes of trade execution, and such near real-time post-trade transaction data can be accessed through the MSRB's EMMA Web site. 
                            <E T="03">See supra</E>
                             note 77. The MSRB is an SCI entity by virtue of being an SRO, rather than a plan processor.
                        </P>
                    </FTNT>
                    <P>In addition, as noted in Section IV.A.2.b, market data as used in the definition of “SCI systems” does not refer exclusively to consolidated market data, but also includes proprietary market data generated by SCI entities as well. The Commission notes that proprietary market data is widely used and relied upon by a broad array of market participants, including institutional investors, to make trading decisions. Therefore, if a proprietary market data feed became unavailable or otherwise unreliable, it could interfere with market participants making trading decisions and impose additional transaction costs on market participants.</P>
                    <P>
                        The Commission has limited information on the extent to which the ARP Policy Statements guide ARP participants' practices with respect to their proprietary market data systems because this information is not reported to the Commission. To the extent that the ARP Policy Statements guide ARP participants with respect to certain of their proprietary market data systems, the potential benefits from including proprietary market data systems in Regulation SCI could be incremental given current practice. The Commission also notes that entities have competitive incentives to limit the number of systems issues with their proprietary market data systems, as those SCI entities with minimum latency and the most robust proprietary market data systems may attract more trading volume. While proprietary market data systems have experienced systems issues, because these issues are not reported to the Commission, the Commission has limited information on the frequency and severity of such systems issues and, in addition, does not have information about how proprietary market data systems issues affect the demand to subscribe to a particular proprietary market data feed. Although the Commission is unable to estimate the benefits and costs of subjecting proprietary market data systems to Regulation SCI, the Commission believes that if a proprietary market data feed became unavailable or otherwise unreliable, it could have a significant impact on the trading of the securities to which it pertains, and could interfere with the maintenance of fair and orderly markets.
                        <SU>1902</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1902</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b.
                        </P>
                    </FTNT>
                    <P>To the extent that proprietary market data systems and consolidated market data systems share common infrastructure, the compliance costs associated with proprietary market data systems could be incremental to those costs associated with consolidated market data systems. In addition, to the extent the ARP Policy Statements guide ARP participants with respect to their proprietary market data systems, the initial compliance costs associated with proprietary market data systems will be lower for these participants with respect to the relevant proprietary market data systems.</P>
                    <P>
                        As adopted, a subset of SCI systems are defined as critical SCI systems. Critical SCI systems are defined as SCI systems of, or operated by or on behalf of, an SCI entity that directly support functionality relating to clearance and settlement systems of clearing agencies; openings, reopenings, and closings on the primary listing exchange; trading halts; initial public offerings; the provision of consolidated market data; and exclusively listed securities.
                        <SU>1903</SU>
                        <FTREF/>
                         In addition, critical SCI systems include systems that provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent, and without which there would be a material impact on fair and orderly markets.
                        <SU>1904</SU>
                        <FTREF/>
                         Critical SCI systems include systems that represent potential “single points of failure” in the securities markets—if they were to experience systems issues, the Commission believes they would be the most likely to have a widespread and significant impact on the U.S. securities markets. Critical SCI systems are subject to certain heightened resilience and information dissemination requirements under Regulation SCI. In addition, because an SCI entity may tailor its policies and procedures based on the relative criticality of a given system to the SCI entity and to the securities markets generally, an SCI entity may subject its critical SCI systems to higher standards than other SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1903</SU>
                             
                            <E T="03">See</E>
                             Rule 1000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1904</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>By adopting a defined term “critical SCI systems” (which is not defined for purposes of the ARP Inspection Program or Regulation ATS), along with the heightened requirements associated with critical SCI systems, the Commission expects fewer disruptions in critical SCI systems, and therefore fewer SCI events involving potential “single points of failure” that could cause wide-scale disruptions across the securities markets. As explained in Section VI.C.1, this could reduce the likelihood and duration of systems issues, thereby helping to avoid pricing inefficiencies and reduce interruptions in liquidity flow, which may occur during times when systems disruptions can make systems unavailable or unreliable.</P>
                    <P>The Commission also notes that, by distinguishing critical SCI systems from other SCI systems, and because an SCI entity may tailor its policies and procedures based on the relative criticality of a given system to the SCI entity and to the securities markets generally, an SCI entity may subject its critical SCI systems to higher standards than other SCI systems. In addition, critical SCI systems are subject to a goal of two-hour recovery following a wide-scale disruption, and a requirement for information dissemination to all members or participants of an SCI entity in the case of an SCI event impacting critical SCI systems (unless the SCI event qualifies as a de minimis SCI event). As result, the designation of critical SCI systems may result in additional costs as compared to the proposal. However, by distinguishing critical systems, Regulation SCI is consistent with a risk-based approach that targets areas that would generate the most benefits.</P>
                    <P>
                        Regulation SCI defines “indirect SCI systems” 
                        <SU>1905</SU>
                        <FTREF/>
                         to mean any systems of, or operated by or on behalf of, an SCI entity that, if breached, would be reasonably likely to pose a security threat to SCI systems.
                        <SU>1906</SU>
                        <FTREF/>
                         As discussed above in Section IV.A.2.d, the adopted definition excludes systems that are effectively physically or logically separated from SCI systems because the Commission believes that the benefit of including systems that can effectively be “walled off” may be limited, as “walled off” systems are less likely to serve as potential vulnerable entry points to SCI systems in the event of a security 
                        <PRTPAGE P="72412"/>
                        breach.
                        <SU>1907</SU>
                        <FTREF/>
                         Regulation SCI will expressly impose new requirements on systems that fall within the definition of “indirect SCI systems” (which is not defined for purposes of the ARP Inspection Program or Regulation ATS). These new requirements for indirect SCI systems should help ensure the robustness and resiliency of SCI systems by reducing the occurrence of security-related issues at SCI systems. Moreover, the application of Regulation SCI to indirect SCI systems could encourage SCI entities to isolate certain non-SCI systems from SCI systems (thereby removing these non-SCI systems from the scope of indirect SCI systems), which would decrease the risk that non-SCI systems provide vulnerable points of entry into SCI systems and cause security-related issues at SCI systems. The reduction in security-related SCI systems issues could lead to fewer interruptions in the price discovery process and liquidity flows and thus result in fewer periods with pricing inefficiencies as discussed in Section VI.C.1.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1905</SU>
                             As discussed in Section IV.A.2.d, “SCI security systems” have been renamed “indirect SCI systems” and its definition has been revised in response to commenters who expressed concern about the breadth of the proposed definition. Because the definition of indirect SCI systems has been refined from the proposal, the compliance costs associated with indirect SCI systems (discussed below) would be lower relative to the compliance costs associated with the proposed rules.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1906</SU>
                             As proposed, “SCI security systems” means any systems that share network resources with SCI systems that, if breached, would be reasonably likely to pose a security threat to SCI systems.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1907</SU>
                             Some SCI entities currently employ a wide variety of means to separate their systems, including logical and physical separation.
                        </P>
                    </FTNT>
                    <P>
                        Regulation SCI specifies the obligations SCI entities would have with respect to SCI systems and indirect SCI systems. As mentioned above, the definition of SCI systems includes more systems than the ARP Inspection Program traditionally covered, and “indirect SCI systems” is not defined for purposes of the ARP Inspection Program or Regulation ATS. Because Regulation SCI applies to SCI systems and indirect SCI systems, SCI entities will incur compliance costs, discussed in detail further below in Section VI.C.2, which include, among other things, costs associated with policies and procedures related to such systems. Furthermore, as mentioned above, the definition of SCI systems includes systems that directly support trading, clearance and settlement, order routing, and market data, which are covered by the ARP Inspection Program. Accordingly, the Commission believes that initial compliance costs associated with SCI systems will be higher for SCI entities that are not currently participating in the ARP Inspection Program (
                        <E T="03">e.g.,</E>
                         some SCI ATSs) as compared to ARP Inspection Program participants that have established practices consistent with the ARP Policy Statements. Although the Commission believes that some SCI ATSs will generally incur higher initial compliance costs associated with the requirements of Rule 1001 compared to other SCI entities that are current participants in the ARP Inspection Program, the difference in initial compliance costs could be limited because, as currently constituted, relative to the systems of SCI SROs, the systems of SCI ATSs generally would not fall within the category of critical SCI systems, and thus such SCI ATSs would not be subject to the more stringent requirements that would be applicable to the critical SCI systems of other SCI entities. Further, as discussed in Section VI.C.1, the Commission believes that Regulation SCI could have an impact on competition among SCI entities in part because the initial compliance costs associated with SCI systems and indirect SCI systems will vary across SCI entities.
                    </P>
                    <P>
                        In the SCI Proposal, the Commission defined SCI systems more broadly than it has in the adopted rule. Specifically, the proposed definition of SCI systems would have included all regulation and surveillance systems, as well as development and testing systems. As discussed above in Section IV.A.2.b, after considering, among other things, the views of commenters that the definition of SCI systems was overbroad and, thus, could cover nearly all systems of an SCI entity, the Commission refined the definition of SCI systems.
                        <SU>1908</SU>
                        <FTREF/>
                         Specifically, the scope of adopted Regulation SCI does not cover member regulation or member surveillance systems such as those, for example, relating to member registration, capital requirements, or dispute resolution, because issues relating to such systems are unlikely to have the same level of impact on the maintenance of fair and orderly markets or an SCI entity's operational capability as those systems identified in the definition of SCI systems. Consequently, the Commission does not believe that the exclusion of member regulation and member surveillance systems will significantly reduce the benefits of Regulations SCI discussed in Section VI.C.1. Furthermore, the Commission believes that the exclusion of member regulation and member surveillance systems from the adopted definition of SCI systems will substantially reduce the costs of compliance with Regulation SCI relative to the proposal because it reduces the potential number of SCI events that would be subject to the Commission notification requirements compared to the proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1908</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the definition of SCI systems).
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.A.2.b, many commenters also opposed the inclusion of development and testing systems in the definition of SCI system, stating that issues in development and testing systems would have little or no impact on the operations of SCI entities.
                        <SU>1909</SU>
                        <FTREF/>
                         The Commission agrees that issues with development and testing systems generally have less of an impact on the SCI entity's operations than production systems that directly support trading, clearance and settlements, order routing, market data, market regulation, and market surveillance. In response to comment letters, the adopted definition of SCI systems is limited to systems that directly support trading, clearance and settlement, order routing, market data, market regulation, and market surveillance, and does not include development and testing systems. Consequently, the requirements of Regulation SCI that are triggered by the definition of SCI systems do not apply to development and testing systems. However, the Commission recognizes that there would be benefits from maintaining robust development and testing systems because these systems are important in ensuring the reliability and resiliency of systems of SCI entities. As discussed in Section IV.A.2.b, in order to have policies and procedures reasonably designed to ensure capacity, integrity, resiliency, availability, and security for SCI systems (and indirect SCI systems, as applicable) in accordance with adopted Rule 1001(a), an SCI entity will be required to have policies and procedures that include a program to review and keep current systems development and testing methodology for such systems.
                        <SU>1910</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1909</SU>
                             
                            <E T="03">See supra</E>
                             note 234 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1910</SU>
                             Further, as discussed above, the definition of SCI review and the corresponding requirement for an annual SCI review require an assessment of internal control design and effectiveness, which includes development processes. In addition, if development and testing systems are not appropriately walled off from production systems, such systems could be captured under the definition of indirect SCI systems and be subject to the requirements of Regulation SCI.
                        </P>
                    </FTNT>
                    <P>
                        A few commenters advocated that SCI entities should be permitted to conduct their own risk-based assessment in determining the scope of SCI systems.
                        <SU>1911</SU>
                        <FTREF/>
                         As discussed in Section IV.A.2.b, rather than limiting the definition of SCI systems to systems that pose a greater risk to the markets in the event of a systems issue or that are of paramount importance to the functioning of the U.S. securities market, the Commission is subjecting those systems that meet the definition of “critical SCI systems” to certain heightened requirements under 
                        <PRTPAGE P="72413"/>
                        Regulation SCI. The Commission continues to believe that any systems issues involving systems that directly support one of the six functions (trading, clearance and settlement, order routing, market data, market regulation, or market surveillance) listed in the definition of SCI systems could also cause significant market disruptions and, thus, including such systems and imposing heightened requirements on a subset of such systems—critical SCI systems—should help realize the benefits of Regulation SCI discussed in Section VI.C.1.a.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1911</SU>
                             
                            <E T="03">See</E>
                             DTCC Letter at 3-5; Omgeo Letter at 5-6; and OCC Letter at 3-4.
                        </P>
                    </FTNT>
                    <P>As discussed above in Section IV.A.2.b, the definition of SCI systems includes any system that is operated by a third-party on behalf of an SCI entity and directly supports one of the six key functions (trading, clearance and settlement, order routing, market data, market regulation, or market surveillance) listed in the definition of SCI systems. The Commission understands that many SCI entities and many SROs, in particular, rely heavily on outsourcing to help test, operate, and run various systems in their daily operations and that they outsource networks, data center operations, and many of the products and systems that support their trading and/or clearing systems. The Commission also notes that its staff already discusses with ARP entities their use of certain third-party systems as necessary under the ARP Inspection Program. Because of this reliance on outsourcing to third party systems, the Commission believes that including any system that directly supports one of the six functions listed in the definition of SCI system, regardless of whether it is operated by the SCI entity directly or by a third party, is important in reducing systems issues and, thus, promoting pricing efficiency and price discovery process.</P>
                    <P>
                        Several commenters stated that the definition of SCI systems should not include systems operated on behalf of an SCI entity by a third-party.
                        <SU>1912</SU>
                        <FTREF/>
                         These commenters expressed concerns about potential difficulties with meeting the requirements of Regulation SCI with regard to third-party systems.
                        <SU>1913</SU>
                        <FTREF/>
                         Another commenter questioned whether the Commission considered the costs and benefits of including third-party systems within the definition.
                        <SU>1914</SU>
                        <FTREF/>
                         This commenter also noted that the inclusion of third-party systems may force SCI entities to insource functions that are more efficiently performed by vendors, and the cost of insourcing will be passed along to members and market participants and may degrade competition.
                        <SU>1915</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1912</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 5-6; and BATS Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1913</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Omgeo Letter at 5-6; and BATS Letter at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1914</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1915</SU>
                             
                            <E T="03">See id.</E>
                             at 5.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, the Commission believes that, among other reasons, allowing systems operated on behalf of an SCI entity by a third-party to be excluded from the requirements of Regulation SCI would reduce the effectiveness of the regulation in promoting the national market system by ensuring the capacity, integrity, resiliency, availability, and security of those systems important to the functioning of the U.S. securities markets.
                        <SU>1916</SU>
                        <FTREF/>
                         The Commission acknowledges that ensuring compliance of systems operated by a third-party with Regulation SCI may be more costly than ensuring compliance of internal systems with Regulation SCI because of search costs associated with employing adequate third-party systems or services and the additional communication needed with the third-party service provider. The Commission acknowledges that higher compliance costs associated with managing third-party systems could be passed on to market participants.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1916</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.b (discussing the definition of “SCI systems”).
                        </P>
                    </FTNT>
                    <P>Moreover, the Commission recognizes that the inclusion of systems operated by a third-party on behalf of an SCI entity in the scope of SCI systems may in certain cases make it more difficult for an SCI entity to utilize third parties because the SCI entity is required to ensure that SCI systems and indirect SCI systems operated on its behalf by a third party are operated in compliance with Regulation SCI. In particular, the SCI entity might not be able to ensure that systems operated by certain third parties are in compliance with Regulation SCI and therefore might not be able to utilize such third-party service providers. Limitations on the choice of third-party systems could lower the quality of employable third-party systems because the employable third-party systems may not be best suited for the SCI entity or be the best available of its type. At this time, however, it is difficult to estimate the extent to which inclusion of systems operated by third parties on behalf of an SCI entity in the definition of SCI systems will alter outsourcing arrangements in a manner that would result in reducing an SCI entity's ability to maintain its operational capability and promote the maintenance of fair and orderly markets. While the Commission understands that SROs outsource some systems, the Commission lacks sufficient information regarding the specific contractual relationships between SCI entities and third-party service providers.</P>
                    <P>Furthermore, if—due to limited options on employable third-parties—an SCI entity decides to insource systems that could be more cost-effectively provided by third parties with relevant expertise, the quality of such systems may be adversely affected, while the cost to the SCI entity may be increased. As such, Regulation SCI could impose higher costs on SCI entities that are currently more dependent on third-party systems for their operations than SCI entities that primarily employ their own systems and therefore could potentially have adverse effects on competition among SCI entities. In addition, the requirements of Regulation SCI could force some third-party vendors out of the market for SCI systems or indirect SCI systems. In this respect, Regulation SCI could negatively impact such vendors and reduce the ability for some third-party vendors to compete in the market for SCI systems and indirect SCI systems, with attendant costs to SCI entities. However, Regulation SCI, over time, could result in quality improvements for systems or services provided by such third-party vendors as vendors that primarily provide services to SCI entities may compete in part on the quality of their systems in light of the requirements of Regulation SCI.</P>
                    <HD SOURCE="HD3">iii. SCI Events</HD>
                    <P>Rule 1000 defines SCI events to include systems disruptions, systems compliance issues, and systems intrusions. Further, for purposes of the information dissemination requirement under Rule 1002(c), the Commission defines the new term, major SCI event, to mean an SCI event that has had, or the SCI entity reasonably estimates would have, any impact on a critical SCI system, or a significant impact on the SCI entity's operations or on market participants. As discussed further below, Regulation SCI requires SCI entities to take appropriate corrective actions in response to SCI events (Rule 1002(a)), notify the Commission of SCI events (Rule 1002(b)), and disseminate information regarding certain major SCI events to all members or participants of an SCI entity and certain other SCI events to affected members or participants (Rule 1002(c)).</P>
                    <P>
                        Prior to the adoption of Regulation SCI, “systems disruption” was not defined by Commission rule. Rather, in the 2001 Staff ARP Interpretive Letter, Commission staff provided guidance on 
                        <PRTPAGE P="72414"/>
                        examples of significant systems outages that should be reported to Commission staff.
                        <SU>1917</SU>
                        <FTREF/>
                         The Commission understands that ARP participants currently exercise a level of discretion in determining what systems issues constitute significant systems outages.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1917</SU>
                             
                            <E T="03">See</E>
                             2001 Staff ARP Interpretive Letter, 
                            <E T="03">supra</E>
                             note 21.
                        </P>
                    </FTNT>
                    <P>As adopted, “systems disruption” is defined to mean an event in an SCI entity's SCI systems that disrupts, or significantly degrades, the normal operation of an SCI system. The Commission believes the revised definition sets forth a standard that SCI entities can apply in a wide variety of circumstances to determine in their discretion whether a systems issue should be appropriately categorized as a systems disruption. The adopted definition of systems disruption potentially covers types of events that were not articulated as part of Commission staff guidance regarding significant systems outages, and at the same time potentially excludes types of systems events that were articulated as part of such guidance. The Commission, however, believes that the adopted definition of systems disruptions would more appropriately capture material or significant systems issues than the 2001 Staff ARP Interpretive Letter. Accordingly, the inclusion of systems disruptions in the definition of SCI event, along with the requirements of taking timely corrective actions, Commission notification, information dissemination, and recordkeeping on these systems issues, should help effectively reduce the severity and duration of events that harm pricing efficiency, price discovery, and liquidity and help Commission oversight of the securities markets. The Commission also acknowledges that SCI entities will incur some costs to determine whether a systems disruption has occurred. The Commission notes that these costs should be lower compared to the proposed definition, in part, because the adopted definition of systems disruption sets forth a standard that permits SCI entities to more effectively identify such systems issues.</P>
                    <P>As discussed in Section IV.A.3.a, after considering the views of commenters that the proposed definition of systems disruption was too prescriptive, insufficiently flexible, and should be limited to material systems disruptions, the Commission has taken a different approach. Instead of the proposed seven-prong prescriptive definition representing the effects caused by a disruption of an SCI entity's systems, the adopted definition focuses on whether a system is halted or degraded in a manner that is outside of its normal operation. The proposed definition had the potential to incorporate certain types of minor events that should more appropriately fall outside the purview of the regulation. Similarly, the prescriptive approach of the proposed definition also had the potential to exclude certain types of events that were significant enough to warrant inclusion, but may otherwise have gone unreported because they were not one of the seven enumerated types of systems malfunctions.</P>
                    <P>Currently, “systems intrusion” is not defined by Commission rule or Commission staff guidance. The Commission believes that regulated entities exercise a level of discretion in determining what systems intrusions to report to Commission staff. By adopting a definition of systems intrusion, the Commission is specifying the criteria for SCI entities to use to identify systems intrusions that would be subject to Regulation SCI. The definition of systems intrusion covers successful unauthorized entry to SCI systems and indirect SCI systems. Unauthorized access, destruction, and manipulation of SCI systems and indirect SCI systems could adversely affect the markets and market participants because intruders could force systems to operate in unintended ways that could create significant disruptions in securities markets. Therefore, the inclusion of systems intrusions in the definition of SCI events can help reduce the risk of such adverse effects. The Commission believes that the inclusion of systems intrusion in the definition of SCI event should help ensure consistent compliance with the requirements of taking timely corrective actions, Commission notification, information dissemination, and recordkeeping and, thus, should help realize the benefits of those requirements discussed in sections below. The Commission also acknowledges that SCI entities will incur some costs to determine whether a systems intrusion has occurred.</P>
                    <P>
                        Currently, “systems compliance issue” is also not defined by Commission rule or Commission staff guidance and the Commission believes that regulated entities exercise a level of discretion in determining what systems compliance-related issues to report to Commission staff. While the ARP Policy Statements do not address systems compliance issues, some SCI entities notify the Commission of certain systems compliance-related issues.
                        <SU>1918</SU>
                        <FTREF/>
                         As noted above, however, the Commission does not receive comprehensive data regarding such issues. By adopting a definition of systems compliance issue, the Commission is specifying the criteria for SCI entities to use to identify systems compliance issues that would be subject to Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1918</SU>
                             
                            <E T="03">See supra</E>
                             note 1803 and accompanying text. As part of the Commission's oversight of SROs, OCIE reviews systems compliance issues reported to Commission staff.
                        </P>
                    </FTNT>
                    <P>
                        By defining SCI events to include systems compliance issues, the Commission believes Regulation SCI should further assist the Commission in its oversight of SCI entities and in the protection of investors. Specifically, the Commission believes that inclusion of systems compliance issues in the definition of SCI event and the resulting applicability of the Commission reporting, information dissemination, and recordkeeping requirements are important to help ensure that SCI systems are operated by SCI entities in compliance with the Exchange Act, rules thereunder, and their own rules and governing documents.
                        <SU>1919</SU>
                        <FTREF/>
                         In addition, the Commission believes that, as part of its oversight of the securities markets, it should learn of a non-de minimis systems compliance issue immediately upon an SCI entity having a reasonable basis to conclude that such a systems compliance issue has occurred so that the Commission may consider whether there has been any resulting harm to investors or market participants. The Commission also acknowledges that SCI entities could incur some costs to determine whether a systems compliance issue has occurred.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1919</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.3.b.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that it has refined the definition of systems compliance issue as compared to the proposal by replacing the phrase “federal securities laws” with “the Act.” 
                        <SU>1920</SU>
                        <FTREF/>
                         Accordingly, the number of systems compliance issues subject to Regulation SCI could be no greater and possibly lower than if the Commission adopted the definition of systems compliance issue as proposed and there could be a corresponding reduction in benefits, compared to the proposal, as a result of adopting a targeted definition.
                        <SU>1921</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1920</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1921</SU>
                             For example, the adopted definition of systems compliance issue makes explicit that the requirements of Regulation SCI do not apply to any obligations that an SCI entity has under the Securities Act of 1933.
                        </P>
                    </FTNT>
                    <P>
                        Regulation SCI also defines “major SCI event.” The addition of the definition of major SCI event allows the requirement for dissemination of 
                        <PRTPAGE P="72415"/>
                        information to all members or participants of an SCI entity to be consistent with a tiered, risk-based approach. As discussed in Section VI.C.2.b.iv below and in Section VI.C.1 above, dissemination of information regarding SCI events to all members or participants of an SCI entity can result in benefits and affect competitive incentives to prevent systems issues. The Commission acknowledges, however, that the benefits of information dissemination to all members or participants of an SCI entity would not be realized if SCI entities were required to disseminate too many events, creating confusion about which events are meaningful, or if SCI entities were required to disseminate too few events. The definition of major SCI events provides a targeted approach to determining which events are appropriately disseminated to all members or participants of an SCI entity. The Commission also acknowledges that, as discussed in Section VI.C.2.b.iv below, SCI entities would incur compliance costs associated with developing a process for determining major SCI events and de minimis SCI events.
                    </P>
                    <P>
                        SCI entities will incur compliance costs with regard to the requirements of Regulation SCI. As noted above, the definition of SCI event includes systems disruptions and systems intrusions, terms that are not defined under the ARP Inspection Program, but which are contemplated by the ARP Inspection Program's attention to systems failures, disruptions, and other systems problems, including systems vulnerability.
                        <SU>1922</SU>
                        <FTREF/>
                         To this extent, the initial compliance costs associated with SCI events may be higher for SCI entities that are not currently participating in the ARP Inspection Program than for those currently participating in the ARP Inspection Program. Similarly, the initial compliance costs associated with SCI events will be higher for SCI entities that do not currently self-report systems compliance-related issues to the Commission than those that do. As discussed in Section VI.C.1, the Commission believes that Regulation SCI will have an impact on competition among SCI entities because the initial compliance costs stemming from the definition of SCI events will be different among SCI entities. However, all SCI entities, regardless of current participation in the ARP Inspection Program or self-reporting of systems compliance-related issues, could incur costs associated with the inclusion of major SCI events as a definition.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1922</SU>
                             
                            <E T="03">See supra</E>
                             Section II.A (discussing the ARP Inspection Program).
                        </P>
                    </FTNT>
                    <P>
                        As an alternative to the adopted definitions of SCI event, several commenters suggested that the definition of SCI event include a materiality threshold such that certain Regulation SCI requirements would apply only to events that exceed the threshold, as determined by the SCI entity.
                        <SU>1923</SU>
                        <FTREF/>
                         The Commission is not persuaded that incorporating a materiality threshold into the definition of SCI event would appropriately capture SCI events. Some systems issues, which may initially seem insignificant to an SCI entity, may later prove to be the source of significant systems issues at the SCI entity. Furthermore, there could be incidences in which systems issues cause minor disruptions for one particular SCI entity but result in significant disruptions for another SCI entity or market participant. Under the use of the suggested materiality threshold, such systems issues could be overlooked and timely corrective action may not be taken.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1923</SU>
                             
                            <E T="03">See supra</E>
                             note 334 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Requirements for SCI Entities—Rules 1001-1004</HD>
                    <HD SOURCE="HD3">i. Policies and Procedures—Rules 1001(a), (b), and (c)</HD>
                    <P>Rules 1001(a), (b), and (c) set forth requirements relating to the written policies and procedures that SCI entities are required to establish, maintain, and enforce. Rule 1001(a) requires an SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. Rule 1001(b) requires an SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the Exchange Act and the rules regulations thereunder and the entity's rules and governing documents, as applicable. Rule 1001(c) requires an SCI entity to establish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel, and escalation procedures to quickly inform responsible SCI personnel of potential SCI events. This section discusses the economic effects of requiring these policies and procedures, both individually and as a whole.</P>
                    <P>
                        The Commission believes the policies and procedures requirements as a whole should reduce the risk and incidences of SCI events because they are requirements under Commission rules rather than voluntary guidelines, and require SCI entities to establish, maintain, and enforce written policies and procedures related to capacity, integrity, resiliency, availability, security, compliance, responsible SCI personnel, and escalation. Also, policies and procedures requirements as a whole should reduce the risk and incidences of SCI events by imposing requirements on entities that are not currently participating in the ARP Inspection Program, and by covering areas not currently within the scope of the ARP Inspection Program, such as policies and procedures regarding systems compliance.
                        <SU>1924</SU>
                        <FTREF/>
                         The policies and procedures requirements in Regulation SCI should help ensure faster recoveries from systems disruptions, systems compliance issues, and systems intrusions. As discussed in Section VI.C.1, reducing the risk, incidence, and duration of SCI events could reduce interruptions in the price discovery process and liquidity flows and thus result in reduced periods with pricing inefficiencies.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1924</SU>
                             With respect to NASD and FINRA rules identified by commenters, although they have some broad relation to certain aspects of the policies and procedures provisions under Regulation SCI, the Commission is not persuaded that these rules, even when taken together, are an appropriate substitute for the comprehensive approach in Regulation SCI with respect to technology systems and system issues. 
                            <E T="03">See</E>
                             NASD Rule 3010(b)(1) and FINRA Rule 3130. 
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 115.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also recognizes that the policies and procedures requirements of Regulation SCI will impose certain costs. In general, the Commission believes that some SCI entities that participate in the ARP Inspection Program already comply with some of the requirements of Rule 1001 and thus would incur lower initial costs to comply with the requirements of Rule 1001 than SCI entities that do not participate in the ARP Inspection Program. Additionally, some SCI entities that currently participate in the ARP Inspection Program are large and have complex systems and, therefore, will incur more costs to comply with Rule 1001 than others. Furthermore, SCI entities that do not currently participate in the ARP Inspection Program will also face costs to comply with Rule 1001 if they do not already have policies and procedures similar to those required by 
                        <PRTPAGE P="72416"/>
                        Rule 1001. These costs are discussed further below.
                    </P>
                    <HD SOURCE="HD3">Quantifiable Costs</HD>
                    <P>
                        In the SCI Proposal, based on discussion with industry participants, the Commission estimated that, to comply with all requirements underlying the policies and procedures required by proposed Rules 1000(b)(1) and (2) other than paperwork burdens, on average, each SCI entity would incur an initial cost of between approximately $400,000 and $3 million.
                        <SU>1925</SU>
                        <FTREF/>
                         Based on this estimated range in costs, the Commission estimated that in the aggregate SCI entities would incur a total initial cost of between approximately $17.6 million 
                        <SU>1926</SU>
                        <FTREF/>
                         and $132 million 
                        <SU>1927</SU>
                        <FTREF/>
                         to comply with proposed Rules 1000(b)(1) and (2). In addition, the Commission estimated that, to comply with the policies and procedures required by proposed Rules 1000(b)(1) and (2), on average, each SCI entity would incur an ongoing annual cost of between approximately $267,000 
                        <SU>1928</SU>
                        <FTREF/>
                         and $2 million.
                        <SU>1929</SU>
                        <FTREF/>
                         Based on this estimated range, the Commission estimated that in the aggregate SCI entities would incur a total annual ongoing cost of between approximately $11.7 million 
                        <SU>1930</SU>
                        <FTREF/>
                         and $88 million.
                        <SU>1931</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1925</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18171. As explained in the SCI proposal, the Commission preliminarily estimated a range of cost for complying with the policies and procedures required by proposed Rules 1000(b)(1) and (2) because some SCI entities are already in compliance with some of these requirements and thus would likely need to incur less costs to comply with the rules. For example, the Commission believed that many SCI SROs (
                            <E T="03">e.g.,</E>
                             certain national securities exchanges and registered clearing agencies) already have or have begun implementation of business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse to ensure next business day resumption of trading and two-hour resumption of clearance and settlement services following a wide-scale disruption. 
                            <E T="03">See id.</E>
                             at 18171, n. 633.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1926</SU>
                             
                            <E T="03">See id.</E>
                             at 18171, n. 634.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1927</SU>
                             
                            <E T="03">See id.</E>
                             at 18171, n. 635.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1928</SU>
                             
                            <E T="03">See id.</E>
                             at 18172, n. 637.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1929</SU>
                             
                            <E T="03">See id.</E>
                             at 18172, n. 638.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1930</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1931</SU>
                             
                            <E T="03">See id.</E>
                             at 18172, n. 640.
                        </P>
                    </FTNT>
                    <P>
                        One commenter noted that the Commission did not provide sufficient discussion of the basis for the cost estimates for complying with the policies and procedures required by proposed Rules 1000(b)(1) and (2).
                        <SU>1932</SU>
                        <FTREF/>
                         However, this commenter was cautiously confident that its initial cost for full implementation of proposed Rules 1000(b)(1) and (2) would not exceed $3 million plus four times the estimated burden under the Paperwork Reduction Act analysis, although the commenter believed that such cost would not be less than half of such $3 million plus at least three times the Paperwork Reduction Act estimate.
                        <SU>1933</SU>
                        <FTREF/>
                         This commenter further noted that the approach taken by the Commission in the proposal with regard to federal securities law liabilities and the safe harbors likely will result in increased insurance costs for SCI entities and higher salaries for employees.
                        <SU>1934</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1932</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1933</SU>
                             
                            <E T="03">See id.</E>
                             at 31. According to this commenter, if as a result of the restrictive listing of industry standards in Table A, it determines that it should adhere to one of the listed standards rather than the standards to which it currently adheres, its cost of compliance with proposed Rule 1000(b)(1) would be considerably increased and its total cost for compliance with proposed Rules 1000(b)(1) and (2) would likely be at or near $3 million plus four times the estimated burden under the Paperwork Reduction Act analysis. 
                            <E T="03">See id.</E>
                             As noted above in Section IV.B.1.b.iii, the Commission believes that staff guidance should be characterized as listing examples of publications describing processes, guidelines, frameworks, and/or standards for an SCI entity to consider looking to in developing reasonable policies and procedures, rather than strictly as listing examples of “standards.” As such, nothing that the staff may include in its guidance precludes an SCI entity from adhering to standards such as ISO 27000, COBIT, or others referenced by commenters to the extent they result in policies and procedures that comply with the requirements of Rule 1001(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1934</SU>
                             
                            <E T="03">See id.</E>
                             The commenter did not provide an estimate of the anticipated increased insurance costs for SCI entities and higher salaries for employees. The Commission acknowledges that SCI entities may incur increased insurance and personnel costs because of the potential additional liability associated with Regulation SCI, although the Commission is unable to estimate these costs given it lacks specific information regarding current personnel and insurance costs and the amount of any potential increases associated with changes in liability. The Commission also notes that many entities that fall within the definition of SCI entity could already be subject to liability for systems issues and thus may already largely be incurring these insurance and personnel costs.
                        </P>
                    </FTNT>
                    <P>
                        Another commenter noted that, without further clarification, the broad scope of the policies and procedures requirement under Regulation SCI could be burdensome, in terms of the cost of developing and implementing new (or enhancing existing) policies and procedures, and in terms of complying and documenting compliance under such policies and procedures.
                        <SU>1935</SU>
                        <FTREF/>
                         According to this commenter, these requirements could significantly increase technology project costs (
                        <E T="03">e.g.,</E>
                         for testing, monitoring, and compliance staff) and would significantly prolong the systems development lifecycle and time to market.
                        <SU>1936</SU>
                        <FTREF/>
                         With respect to the Commission's cost estimate for proposed Rules 1000(b)(1) and (2), another commenter noted that the Commission's estimates do not adequately account for the opportunity costs of delays in systems innovation.
                        <SU>1937</SU>
                        <FTREF/>
                         This commenter stated that the Commission did not address the significant costs of complying with the requirements concerning the capacity, integrity, resiliency, availability, and security of systems.
                        <SU>1938</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1935</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 32. The estimated burden associated with the development and maintenance of policies and procedures is discussed in the Paperwork Reduction Act section above. 
                            <E T="03">See supra</E>
                             Section V.D.1.a.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1936</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 32.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1937</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 7. This commenter also noted that the estimates do not adequately account for the monitoring and notification costs that would be engendered by the proposal. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1938</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        After considering the views of these commenters and in light of the changes to the proposed rules, the Commission now estimates that, to comply with all requirements underlying the policies and procedures required by Rules 1001(a) and (b),
                        <SU>1939</SU>
                        <FTREF/>
                         other than paperwork burdens, on average, each SCI entity will incur an initial cost of between approximately $320,000 and $2.4 million and an ongoing annual cost of between approximately $213,600 and $1.6 million.
                        <SU>1940</SU>
                        <FTREF/>
                         The Commission notes that it has reduced the cost for complying with the policies and procedures required by Rules 1001(a) and (b) in a variety of ways, including by, for example: Refining the definition of SCI systems; more explicitly allowing SCI entities to tailor policies and procedures consistent with a risk-based approach; having separate staff guidance on current SCI industry standards rather than Commission guidance through proposed Table A, with staff guidance characterized as listing examples of publications describing processes, guidelines, frameworks, and/or standards for an SCI entity to consider looking to in developing reasonable policies and procedures, rather than strictly as listing examples of 
                        <PRTPAGE P="72417"/>
                        “standards;” and focusing compliance on the Exchange Act rather than federal securities laws generally.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1939</SU>
                             These include, for example, establishing current and future capacity planning estimates, capacity stress testing, reviewing and keeping current systems development and testing methodology, regular reviews and testing to detect vulnerabilities, testing of all SCI systems and changes to SCI systems prior to implementation, implementing a system of internal controls, implementing a plan for assessments of the functionality of SCI systems, implementing a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, designed to detect and prevent systems compliance issues, and hiring additional staff.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1940</SU>
                             The Commission estimates an average range of cost for complying with the policies and procedures required by Rules 1001(a) and (b) because some SCI entities are already in compliance with some of these requirements. The Commission recognizes that, for SCI entities that do not currently comply with the policies and procedures required by Rules 1001(a) and (b), their cost of compliance may, depending on their nature, size, technology, business model, and other aspects of their business, be at the upper end of the estimated average cost range.
                        </P>
                    </FTNT>
                    <P>
                        At the same time, the Commission acknowledges that other aspects of the compliance costs could potentially be higher for the adopted rules than the proposed rules. For example, the requirement for a goal of two-hour resumption for all critical SCI systems (rather than only clearance and settlement systems) could increase compliance costs for SCI entities with critical SCI systems as compared to the proposal. However, as discussed above, the Commission has specified that the stated recovery timeframes in Regulation SCI are goals, rather than inflexible requirements.
                        <SU>1941</SU>
                        <FTREF/>
                         In addition, for some SCI entities that would have chosen to not use the proposed SCI entity safe harbor, the Commission's adoption of non-exhaustive, general minimum elements for systems compliance policies and procedures in Rule 1001(b)(2) could increase compliance costs as compared to the proposal. Based on the foregoing, the Commission believes that it is reasonable to revise the estimate to reflect the more targeted scope and increased flexibility of the adopted regulation, as compared to the proposal, in combination with potential increased costs associated with compliance with Rules 1001(a)(2)(v) and 1001(b)(2), and new costs associated with compliance with Rule 1001(a)(2)(vii).
                        <SU>1942</SU>
                        <FTREF/>
                         Therefore, the Commission believes that on balance overall, the costs will be reduced, and in its best judgment, each SCI entity is likely to incur an initial cost of between approximately $320,000 and $2.4 million and an ongoing annual cost of between approximately $213,600 and $1.6 million for complying with the policies and procedures required by Rules 1001(a) and (b). However, the Commission acknowledges that its cost estimates reflect a high degree of uncertainty. As noted above, the compliance costs of Rule 1001 may depend on the complexity of SCI entities' systems (
                        <E T="03">e.g.,</E>
                         the compliance costs will be higher for SCI entities with more complex systems). The initial compliance costs associated with Rule 1001 may also vary across SCI entities depending on the degree of current practices' compliance with the requirements of Rule 1001. Because it is difficult to gauge the precise degree of current compliance for each SCI entity in estimating potential costs with respect to Rule 1001 at this time, the Commission is estimating a range of compliance costs above.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1941</SU>
                             
                            <E T="03">See supra</E>
                             note 504 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1942</SU>
                             Rule 1001s(a)(2)(v), 1001(a)(2)(vii), and 1001(b)(2) are discussed further below.
                        </P>
                    </FTNT>
                    <P>
                        The Commission estimates that, in the aggregate, SCI entities will incur a total initial cost of between approximately $14 million 
                        <SU>1943</SU>
                        <FTREF/>
                         and $106 million 
                        <SU>1944</SU>
                        <FTREF/>
                         to comply with the policies and procedures required by Rules 1001(a) and (b). In addition, the Commission estimates that, in the aggregate, SCI entities will incur total annual ongoing cost of between approximately $9 million 
                        <SU>1945</SU>
                        <FTREF/>
                         and $70 million.
                        <SU>1946</SU>
                        <FTREF/>
                         These cost estimates are intended to cover the cost of complying with all substantive requirements under Rules 1001(a) and (b) other than paperwork related burdens.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1943</SU>
                             $320,000 × 44 SCI entities = $14.1 million.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1944</SU>
                             $2.4 million × 44 SCI entities = $105.6 million.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1945</SU>
                             $213,600 × 44 SCI entities = $9.4 million.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1946</SU>
                             $1.6 million × 44 SCI entities = $70.4 million.
                        </P>
                    </FTNT>
                    <P>
                        The Commission acknowledges that, for SCI entities, the requirements of Rules 1001(a) and (b) could increase technology project costs, prolong the systems development lifecycle and time to market, and result in opportunity costs because of potential delays in systems innovation.
                        <SU>1947</SU>
                        <FTREF/>
                         On the other hand, as discussed throughout this release, the Commission believes that entities that are important to the functioning of the U.S. securities markets should be required to have policies and procedures reasonably designed to ensure systems capacity, integrity, resiliency, availability, security, and compliance. Further, as discussed above in Sections IV.B.1 and IV.B.2, the Commission has focused the scope of Rules 1001(a) and (b) as compared to the SCI Proposal. Moreover, in tandem with the adoption of a definition of critical SCI systems, the Commission is making more clear that Rule 1001(a) permits SCI entities to tailor policies and procedures consistent with a risk-based approach. With respect to Rule 1001(b), the Commission is adopting non-exhaustive, general minimum elements that an SCI entity must include in its systems compliance policies and procedures.
                        <SU>1948</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1947</SU>
                             
                            <E T="03">See supra</E>
                             note 1936 and accompanying text (discussing a commenter's view regarding the potential economic effects of the policies and procedures requirements).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1948</SU>
                             
                            <E T="03">See supra</E>
                             note 1935 and accompanying text (discussing a commenter's views that, without clarification, the policies and procedures requirement under Regulation SCI could be burdensome).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Benefits and Qualitative Costs</HD>
                    <HD SOURCE="HD3">Capacity, Integrity, Resiliency, Availability, and Security</HD>
                    <P>
                        Rule 1001(a)(1) requires that each SCI entity establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets. Rule 1001(a)(2)(i)-(iv) provides that an SCI entity's policies and procedures under Rule 1001(a) must include, at a minimum: (i) The establishment of reasonable current and future technological infrastructure capacity planning estimates; (ii) periodic capacity stress tests of systems to determine their ability to process transactions in an accurate, timely, and efficient manner; (iii) a program to review and keep current systems development and testing methodology of such systems; and (iv) regular reviews and testing, as applicable, of systems, including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters.
                        <SU>1949</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1949</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(a)(2) and 
                            <E T="03">supra</E>
                             Section IV.B.1.
                        </P>
                    </FTNT>
                    <P>
                        Rules 1001(a)(1) and (2)(i)-(iv) codify and expand certain provisions of the ARP Policy Statements. They also expand on the requirements under Rule 301(b)(6) of Regulation ATS for ATSs that trade NMS stocks and non-NMS stocks. In particular, under the ARP Policy Statements and through the ARP Inspection Program, ARP participants, among other things, are expected to establish current and future capacity estimates; conduct capacity stress tests; and conduct annual reviews that cover significant elements of the operations of the automation process, including the capacity planning and testing process, contingency planning, systems development methodology, and vulnerability assessments. Further, Rule 301(b)(6) requires certain ATSs, with respect to those systems that support order entry, order routing, order execution, transaction reporting, and trade comparison, to establish certain capacity estimates, conduct periodic capacity stress tests of critical systems, develop and implement reasonable procedures to review and keep current systems development and testing methodology, review the vulnerability of their systems and data center computer operations to specified threats, establish adequate contingency and disaster recovery plans, conduct an independent review of their systems controls annually for ensuring that Rule 301(b)(6)(ii)(A)-(E) are met and conduct a review by senior management of a report of the independent review, and 
                        <PRTPAGE P="72418"/>
                        promptly notify the Commission of certain systems outages and systems changes.
                        <SU>1950</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1950</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.301(b)(6)(ii).
                        </P>
                    </FTNT>
                    <P>
                        As mentioned above, Rules 1001(a)(1) and (2)(i)-(iv) codify certain aspects of the ARP Policy Statements. For SCI entities that are current participants in the ARP Inspection Program, codifying these aspects into requirements to establish policies and procedures should help ensure more robust systems that help realize the benefits of Regulation SCI discussed in Section VI.C.1.
                        <SU>1951</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1951</SU>
                             Likewise, the relocation and modification of certain requirements in Rule 301(b)(6) of Regulation ATS applicable to significant-volume ATSs that trade NMS stocks and non-NMS stocks will help ensure that SCI ATSs create and maintain policies and procedures to support robust systems. 
                            <E T="03">See supra</E>
                             note 2 and accompanying text (noting that Regulation SCI, in addition to codifying the ARP Policy Statements, also supersedes and replaces aspects of those policy statements codified in Rule 301(b)(6) under the Exchange Act for significant-volume ATSs that trade NMS stocks and non-NMS stocks).
                        </P>
                    </FTNT>
                    <P>In addition to the effects of the codification of aspects of the ARP Inspection Program, the Commission believes that the rules would further reduce the risk and incidences of systems issues affecting the markets by imposing requirements on entities that are not currently participating in the ARP Inspection Program, and by covering systems and events not currently within the scope of the ARP Inspection Program. For example, Rules 1001(a)(2)(i)-(iv) will help maintain robust systems at SCI entities that currently do not have the policies and procedures in place required by the rule. In particular, the Commission believes that, taken together, Rules 1001(a)(2)(i)-(iv) will benefit the securities markets by leading to the establishment, maintenance, and enforcement of policies and procedures that will reduce the risks and incidences of systems disruptions and systems intrusions. As noted above in Section VI.C.1, a reduction in the risk and incidences of systems issues could reduce interruptions in the price discovery process and liquidity flows.</P>
                    <P>
                        Because current ARP participants will change their current practices to comply with Rules 1001(a)(2)(i)-(iv), the Commission recognizes that these entities will incur compliance costs that are incremental relative to the current compliance costs of the ARP Inspection Program.
                        <SU>1952</SU>
                        <FTREF/>
                         Furthermore, SCI entities that are not currently participating in the ARP Inspection Program may incur higher initial compliance costs to meet the requirements of Rules 1001(a)(2)(i)-(iv), compared to SCI entities that are current participants of the ARP Inspection Program. The paperwork burdens are discussed in Section V, and other costs are included as part of the quantified costs estimated above related to all requirements associated with Rules 1001(a) and (b) other than paperwork burdens.
                        <SU>1953</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1952</SU>
                             
                            <E T="03">See supra</E>
                             Section VI.B (discussing current practices of SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1953</SU>
                             
                            <E T="03">See supra</E>
                             note 1940 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        A few commenters discussed in detail how setting forth policies and procedures with regard to systems development could yield benefits, such as efficient pricing of securities, to markets. One commenter noted that preventing defects from entering in software construction is the most cost effective approach to quality assurance.
                        <SU>1954</SU>
                        <FTREF/>
                         This commenter stated that it is ten times cheaper to find a defect in development than it is during systems testing, and it is one hundred times cheaper to fix a defect in development than in production (and this is not accounting for the impact on business).
                        <SU>1955</SU>
                        <FTREF/>
                         In addition, this commenter noted that software of higher quality is cheaper to maintain and easier to enhance, and that testing schedules for low quality, large software projects are two to three times longer and more than twice as costly as testing for high quality projects.
                        <SU>1956</SU>
                        <FTREF/>
                         According to information submitted by this commenter of large, mission critical systems across several industries, improving overall structural quality by 10 percent reduces “ticket volume” by over 30 percent.
                        <SU>1957</SU>
                        <FTREF/>
                         This commenter believed that this would be an inadvertent benefit of controlling integrity at the structural level that may even compensate for the cost of other aspects of Regulation SCI.
                        <SU>1958</SU>
                        <FTREF/>
                         Another commenter noted that the cost of a serious operational problem can rise to eight digits, and in extreme cases nine digits.
                        <SU>1959</SU>
                        <FTREF/>
                         This commenter noted that these costs are often shared with market participants beyond the owners of the disrupted systems.
                        <SU>1960</SU>
                        <FTREF/>
                         This commenter believed that the proposed Rule 1000(b)(1) requirements are reasonable and their cost can be balanced against the losses associated with the operational risks they address.
                        <SU>1961</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1954</SU>
                             
                            <E T="03">See</E>
                             CAST Letter at 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1955</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1956</SU>
                             
                            <E T="03">See id.</E>
                             (quoting Capers Jones and Olivier Bonsignour, 
                            <E T="03">The Economics of Software Quality</E>
                             (2012)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1957</SU>
                             
                            <E T="03">See id.</E>
                             at 10-11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1958</SU>
                             
                            <E T="03">See id.</E>
                             at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1959</SU>
                             
                            <E T="03">See</E>
                             CISQ Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1960</SU>
                             
                            <E T="03">See id.</E>
                             at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1961</SU>
                             
                            <E T="03">See id.</E>
                             at 2. 
                            <E T="03">See also</E>
                             CISQ2 Letter at 6 (stating, “[t]he cost of recent outages in SCI systems easily justifies the additional effort in quality assurance. However, empirical evidence from software industry improvement programs demonstrates that the additional time added into quality assurance is more than compensated for by a reduction in rework to produce [return on investments] of 5:1 or greater”).
                        </P>
                    </FTNT>
                    <P>
                        The Commission generally agrees with commenters that setting forth policies and procedures with regard to systems development could yield benefits to market participants and SCI entities, including a potential reduction in losses due to SCI events. Rule 1001(a)(2)(iii) requires SCI entities to establish a program to review and keep current systems development and testing methodology for SCI systems and, for purposes of security standards, indirect SCI systems. The Commission believes that development and testing systems are important in ensuring the reliability and resiliency of SCI systems. More reliable and resilient systems should help reduce the occurrences of SCI events and improve systems uptime for SCI entities, and thus possibly result in a reduction in losses due to SCI events. Furthermore, the Commission recognizes that the use of inadequately tested software in production could result in substantial losses to market participants if it does not function as intended. For instance, if software malfunctions, it may not route orders as intended and also could result in mispricing of securities. Additionally, if a system's capacity thresholds are improperly estimated, it may become congested, resulting in higher indirect transaction costs due to lower execution quality (
                        <E T="03">e.g.,</E>
                         decrease in order fill rates). The Commission believes that costs associated with Rule 1001(a)(2)(iii) are appropriate in light of the reduction in losses due to SCI events and other benefits discussed throughout this Economic Analysis.
                    </P>
                    <HD SOURCE="HD3">Business Continuity and Disaster Recovery Plans</HD>
                    <P>
                        Rule 1001(a)(2)(v) requires SCI entities' policies and procedures to set forth business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption.
                        <SU>1962</SU>
                        <FTREF/>
                         Therefore, as 
                        <PRTPAGE P="72419"/>
                        adopted, Rule 1001(a)(2)(v) puts an emphasis on trading and critical SCI systems with respect to resumption following a wide-scale disruption. As discussed above, the definition of critical SCI systems is intended to capture those systems that are critical to the operation of the securities markets, including systems that are potential single points of failure in the securities markets. The Commission understands that some SCI entities already have, to an extent, policies and procedures that are required by Rule 1001(a)(2)(v), while others would need to make more significant changes to their current practices.
                        <SU>1963</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1962</SU>
                             FINRA Rule 4370 generally requires that a FINRA member maintain a written continuity plan identifying procedures relating to an emergency or significant business disruption, which is akin to adopted Rule 1001(a)(2)(v) requiring policies and procedures for business continuity and disaster recovery plans. However, the FINRA rule does not include the requirement that the business continuity and disaster recovery plans be reasonably designed to achieve next business day 
                            <PRTPAGE/>
                            resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption, nor does it require the functional and performance testing and coordination of industry or sector-testing of such plans. 
                            <E T="03">See supra</E>
                             note 115.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1963</SU>
                             
                            <E T="03">See infra</E>
                             note 1973 and accompanying text (discussing the estimated range of cost per SCI entity to comply with the policies and procedures required by Rules 1001(a) and (b)).
                        </P>
                    </FTNT>
                    <P>Rule 1001(a), among other things, is expected to help ensure prompt resumption of all critical SCI systems, which in turn is expected to help minimize interruptions in trading and liquidity after a wide-scale disruption. In addition, in the case of a wide-scale disruption, multiple SCI entities may be affected by the same incident at the same time. Given that U.S. securities market infrastructure is concentrated in relatively few areas, such as New York City, New Jersey, and Chicago, maintaining backup and recovery capabilities that are geographically diverse could facilitate resumption in trading and critical SCI systems following wide-scale market disruptions. As discussed in detail in Section VI.C.1, the Commission expects the reduction in the occurrence of trading interruptions and the duration of trading interruptions would promote pricing efficiency, price discovery, and liquidity flows in markets.</P>
                    <P>
                        One commenter noted that the Commission's cost-benefit analysis in the SCI Proposal did not take into consideration the already existing industry excess capacity as backup.
                        <SU>1964</SU>
                        <FTREF/>
                         With respect to this commenter, the Commission understands, based on staff expertise, that systems are sized to adequately handle message traffic with excess capacity under normal conditions and in those situations that moderately exceed the norm. The Commission also understands, however, that exchanges periodically receive escalated levels of message traffic due to unanticipated events and must make real-time adjustments to manage the capacity of their systems, such as queuing and/or throttling. Therefore, the Commission is not persuaded that excess capacity is a reasonable alternative to backup systems because systems may reach their capacity periodically. Also, as noted above, in the case of a wide-scale disruption, multiple SCI entities may be affected by the same incident at the same time. Given that U.S. securities market infrastructure is concentrated in relatively few areas, maintaining backup and recovery capabilities that are geographically diverse could facilitate resumption in trading and critical SCI systems following wide-scale market disruptions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1964</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 14.
                        </P>
                    </FTNT>
                    <P>
                        The Commission also received comments regarding the costs of maintaining geographically diverse backup facilities under proposed Rule 1000(b)(1). One commenter stated that the Commission did not appropriately consider the costs and benefits of maintaining geographically diverse data centers to meet the next-day readiness requirement.
                        <SU>1965</SU>
                        <FTREF/>
                         This commenter believed that the cost of establishing and maintaining geographically diverse data centers alone will dwarf the estimated overall compliance cost of $400,000 to $3 million.
                        <SU>1966</SU>
                        <FTREF/>
                         This commenter estimated that the incremental all-in, five-year cost to it to relocate its backup site would be $17 million.
                        <SU>1967</SU>
                        <FTREF/>
                         This commenter noted that the geographically diverse backup center requirement could also result in costs on members and users of the SCI entity.
                        <SU>1968</SU>
                        <FTREF/>
                         Another commenter noted that it maintains robust redundant and backup systems that exceed regulatory requirements and provide adequate capacity, security, and resiliency for its trading operations; however, the manpower and financial capital required to maintain and staff a geographically diverse backup site would easily push its annual and recurring compliance cost beyond the higher estimates provided by the Commission.
                        <SU>1969</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1965</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 12. 
                            <E T="03">See also</E>
                             FIF Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1966</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1967</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1968</SU>
                             
                            <E T="03">See id.</E>
                             The cost to members or participants of SCI entities in connection with business continuity and disaster recovery plan testing is discussed in Section VI.C.2.b.vii below.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1969</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that the potential cost for maintaining geographically diverse backup and recovery capabilities is likely less than those estimated by commenters given the scope of the adopted rule. Specifically, because Rule 1001(a)(2)(v) does not require an SCI entity to require its members or participants to use an SCI entity's backup facility in the same way they use the primary facility (
                        <E T="03">i.e.,</E>
                         does not require members or participants to co-locate their systems at backup sites to replicate the speed and efficiency of the primary site), the requirement for geographically diverse backup systems does not mean that the backup systems are required to be identical (
                        <E T="03">e.g.,</E>
                         same speed and efficiency) to the primary facility. Nevertheless, the Commission believes it is critical that SCI entities and their designated members or participants be able to operate with the SCI entities' backup systems in the event of a wide-scale disruption. In addition, the Commission notes that Rule 1001(a) does not specify any particular minimum distance or geographic location that would be necessary to achieve geographic diversity, although the Commission believes that backup sites should not rely on the same infrastructure components, such as for transportation, telecommunications, water supply, and electric power. Further, Regulation SCI does not require an SCI entity to have a geographically diverse backup facility so distant from the primary facility that the SCI entity may not rely primarily on the same labor pool to staff both facilities if it believed it to be appropriate.
                    </P>
                    <P>
                        With respect to commenters who expressed concern regarding the potential cost for maintaining geographically diverse backup and recovery capabilities, the Commission cannot estimate with confidence the precise costs for the creation of a new, geographically diverse backup facility, given the wide range of message traffic that various exchanges, ATSs, and other entities receive and the reasonable flexibility in the design of the backup facility. Given that Rule 1001(a)(2)(v) does not require an SCI entity to require its members or participants to use an SCI entity's backup facility in the same way they use the primary facility, however, the Commission believes that the upper bound of building a new backup facility is equal to the cost of building a new primary facility. Given the Commission's response to commenters' concerns regarding the requirement to maintain geographically diverse backup and recovery capabilities, and the degree of flexibility within Regulation SCI to determine the precise nature and location of its backup site,
                        <SU>1970</SU>
                        <FTREF/>
                         the Commission believes that the commenter's estimate of $17 million over five years (or $3.4 million per 
                        <PRTPAGE P="72420"/>
                        year),
                        <SU>1971</SU>
                        <FTREF/>
                         is high. Based on the Commission's best judgment, including taking into account Commission staff experience with SCI entities that have invested in geographically diverse backup facilities in recent years, the Commission believes that the average cost is more likely to be approximately $1.5 million annually for an SCI entity (that does not already have geographically diverse backup facilities). Nevertheless, even were the costs to be at the upper amount suggested by the commenter, the Commission believes the costs are appropriate given that individual SCI entity resilience is fundamental to achieving the goal of improving U.S. securities market infrastructure resilience.
                        <SU>1972</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1970</SU>
                             
                            <E T="03">See supra</E>
                             notes 541-544 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1971</SU>
                             
                            <E T="03">See supra</E>
                             note 1967 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1972</SU>
                             
                            <E T="03">See supra</E>
                             notes 499-544 and accompanying text.
                        </P>
                    </FTNT>
                    <P>
                        The Commission recognizes that SCI entities may encounter significantly different costs in complying with the geographic diversity requirement underlying Rule 1001(a)(2)(v). As noted in Section VI.B.2, nearly all national securities exchanges already have backup facilities that do not rely on the same infrastructure components as those used by their primary facility. For those national securities exchanges that do not have such backup facilities, the cost to build such backup facilities will result in higher initial compliance costs than for national securities exchanges that do. For other SCI entities (
                        <E T="03">e.g.,</E>
                         some SCI ATSs), the compliance costs to meet the geographic diversity requirement would depend on the nature, size, technology, business model, and other aspects of their business.
                        <SU>1973</SU>
                        <FTREF/>
                         Because SCI entities may encounter significantly different costs in complying with the geographic diversity requirement, the Commission believes that the initial compliance costs could have impact on competition among SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1973</SU>
                             The Commission notes that its average estimated range of initial cost of approximately $320,000 to $2.4 million per SCI entity to comply with Rules 1001(a) and (b), other than paperwork burdens, includes the cost to build and maintain a geographically diverse backup facility. The Commission estimates that the costs for SCI entities that do not currently have a geographically diverse backup facility would be at the higher end of this range.
                        </P>
                    </FTNT>
                    <P>
                        The requirement to have policies and procedure to meet a goal of next day resumption in trading and two-hour resumption in critical SCI systems will impose compliance costs for SCI entities. The Interagency White Paper sets forth sound practices for core clearing and settlement organizations and firms that play significant roles in critical financial markets,
                        <SU>1974</SU>
                        <FTREF/>
                         and the 2003 BCP Policy Statement discusses the resumption of certain trading markets following a wide-scale disruption.
                        <SU>1975</SU>
                        <FTREF/>
                         As noted in Section VI.B.1, the Commission believes that SCI entities currently use an array of measures to restore systems when disruptions occur. However, the two-hour resumption goal for all critical SCI systems differs from the goals set forth in the Interagency White Paper insofar as the goal for Regulation SCI applies to critical SCI systems generally.
                        <SU>1976</SU>
                        <FTREF/>
                         To this extent, Rule 1001(a)(2)(v) would impose additional costs for SCI entities that currently have practices that are consistent with the Interagency White Paper for clearance and settlement systems but not all critical SCI systems. The next business day resumption goal for certain trading markets set forth in the 2003 BCP Policy Statement is consistent with the resumption goal for trading in Rule 1001(a)(2)(v). For some SCI entities that do not have policies and procedures with respect to critical SCI systems consistent with the Interagency White Paper and the 2003 BCP Policy Statement, the Commission believes that the initial compliance costs associated with establishing policies and procedures with respect to next day resumption in trading and two-hour resumption in all critical SCI systems would be larger than those that do. The costs associated with designing and modifying policies and procedures with respect to systems resumption requirements are included in the costs related to paperwork burdens in Section V. Furthermore, as discussed in Section VI.C.1, the Commission believes that the systems resumption requirements of Rule 1001(a)(2)(v) will have an impact on competition among SCI entities in part because the associated initial compliance costs will be different among SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1974</SU>
                             According to the Interagency White Paper, core clearing and settlement organizations should develop the capacity to recover and resume clearing and settlement activities within the business day on which the disruption occurs with the overall goal of achieving recovery and resumption within two hours after an event. 
                            <E T="03">See</E>
                             Interagency White Paper, 
                            <E T="03">supra</E>
                             note 504, at 17812.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1975</SU>
                             The 2003 BCP Policy Statement states that each SRO market and ECN should have a business continuity plan that anticipates the resumption of trading, in the securities traded by that market, no later than the next business day following a wide-scale disruption. 
                            <E T="03">See</E>
                             2003 BCP Policy Statement, 
                            <E T="03">supra</E>
                             note 504, at 56658.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1976</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.A.2.c (discussing the definition of critical SCI systems) and 
                            <E T="03">supra</E>
                             Section IV.B.1 (discussing the Commission's rationale for applying the two hour recovery goal to critical SCI systems generally instead of clearance and settlement services specifically).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Market Data</HD>
                    <P>
                        Rule 1001(a)(2)(vi) provides that an SCI entity's policies and procedures must include standards that result in systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data.
                        <SU>1977</SU>
                        <FTREF/>
                         Unlike the other provisions of Rule 1001(a)(2) discussed above, Rule 1001(a)(2)(vi) is not addressed in Regulation ATS or the ARP Policy Statements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1977</SU>
                             
                            <E T="03">See</E>
                             Rule 1001(a)(2) and 
                            <E T="03">supra</E>
                             Section IV.B.1.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that Rule 1001(a)(2)(vi) should help ensure that timely and accurate market data is available to all market participants. Given that market participants rely on consolidated market data in a variety of ways, including making markets, formulating trading algorithms, and placing orders, the Commission believes that this is an important benefit of Regulation SCI, although the Commission recognizes that SCI entities currently already take measures to facilitate the successful collection, processing, and dissemination of market data. As discussed in Section VI.C.1, the Commission believes that the further improvements in timeliness and accuracy of market data would help further ensure pricing efficiencies and uninterrupted liquidity flows in markets. As Rule 1001(a)(2)(vi) will be a new requirement for SCI entities, it will impose incremental compliance costs on SCI entities in setting aside additional resources to satisfy the requirements of the rule. These costs are included as part of the quantified costs estimated above related to all requirements underlying Rules 1001(a) and (b) other than paperwork burdens.
                        <SU>1978</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1978</SU>
                             
                            <E T="03">See supra</E>
                             note 1940 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Monitoring</HD>
                    <P>Rule 1001(a)(2)(vii) provides that an SCI entity's policies and procedures must include monitoring of systems to identify potential SCI events. Rule 1001(a)(2)(vii) imposes a new requirement that is not addressed in Regulation ATS or the ARP Policy Statements.</P>
                    <P>
                        The Commission believes that SCI entities, particularly those that participate in the ARP Inspection Program, already monitor their systems in order to identify potential systems issues. Nevertheless, by defining “SCI event” and requiring policies and procedures for monitoring systems to identify potential SCI events, the Commission believes that Rule 
                        <PRTPAGE P="72421"/>
                        1001(a)(2)(vii) should further help ensure that SCI entities identify potential SCI events, which could allow them to prevent some SCI events from occurring or to take timely appropriate corrective action after the occurrence of SCI events. As discussed above, the Commission believes the reduction in the occurrence of SCI events or the reduction in the duration of SCI events that disrupt markets would reduce pricing inefficiencies and promote price discovery and liquidity. Although the Commission believes that SCI entities already monitor their systems in order to identify potential systems issues, the Commission believes that SCI entities will have to allocate additional resources to comply with the requirements of Rule 1001(a)(2)(vii), including potentially hiring additional staff, and thus will incur costs. These costs are included as part of the quantified costs estimated above related to all requirements underlying Rules 1001(a) and (b) other than paperwork burdens.
                    </P>
                    <HD SOURCE="HD3">Current SCI Industry Standards</HD>
                    <P>
                        Rule 1001(a)(4) deems an SCI entity's policies and procedures under Rule 1001(a) to be reasonably designed if they are consistent with current SCI industry standards.
                        <SU>1979</SU>
                        <FTREF/>
                         However, Rule 1001(a)(4) specifically states that compliance with current SCI industry standards is not the exclusive means to comply with the requirements of Rule 1001(a). Therefore, as adopted, Rule 1001(a)(4) provides flexibility to allow each SCI entity to determine how to best meet the requirements in Rule 1001(a), taking into account, for example, its nature, size, technology, business model, and other aspects of its business. Thus, Rule 1001(a)(4) allows SCI entities to choose the technology standards that best fit with their business, promoting efficiency. Furthermore, as discussed in Section IV.B.1, staff guidance lists examples of publications describing processes, guidelines, frameworks, or standards for an SCI entity to consider looking to in developing reasonable policies and procedures under Rule 1001(a). The reference to the publications which the staff may include, and which the Commission believes should be general and flexible enough to be compatible with many widely-recognized technology standards, will help SCI entities to implement and comply with Regulation SCI.
                        <SU>1980</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1979</SU>
                             Current SCI industry standards are required to be comprised of information technology practices that are widely available to information technology professionals in the financial sector and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization. 
                            <E T="03">See</E>
                             Rule 1001(a)(4).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1980</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.1.b (discussing the role of staff guidance on current SCI industry standards).
                        </P>
                    </FTNT>
                    <P>
                        Some commenters expressed concern that SCI entities would closely adhere to the publications listed in Table A rather than take advantage of the flexibility built into the proposed rule out of concern that, if they did not, they would expose themselves to potential regulatory action for failure to comply with Regulation SCI.
                        <SU>1981</SU>
                        <FTREF/>
                         As discussed above in Section IV.B.1, Rule 1001(a) allows for flexibility in choosing standards or guidelines when an SCI entity is designing policies and procedures required by that rule. Moreover, the staff guidance lists examples of publications describing processes, guidelines, frameworks, or standards for an SCI entity to consider looking to in developing reasonable policies and procedures under Rule 1001(a). As noted in Section IV.B.1, the Commission understands that many SCI entities are already following other technology standards, such as ISO 27000 and COBIT. The staff guidance would not preclude SCI entities from adhering to standards such as ISO 27000, COBIT, or others, to the extent they result in policies and procedures that comply with the requirements of Rule 1001(a).
                        <SU>1982</SU>
                        <FTREF/>
                         Because there is no requirement for SCI entities to follow the publications listed as staff guidance, there is no separate compliance cost associated with the staff guidance in addition to the cost of complying with Rule 1001(a). As discussed throughout this section, the Commission recognizes that, in general, there will be costs associated with designing policies and procedures required by Rule 1001(a). Such costs to SCI entities that already set forth their policies and procedures based on industry standards, or that follow the publications listed in the staff guidance or comparable publications as a guide, would be minimal. On the other hand, other SCI entities that decide to modify their policies and procedures and those that do not have such policies and procedures in place may incur greater costs in designing policies and procedures required by Rule 1001(a). The costs associated with modifying and designing policies and procedures are included in the costs related to paperwork burdens in Section V.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1981</SU>
                             
                            <E T="03">See, e.g.,</E>
                             MSRB Letter at 11; Angel Letter at 8; BATS Letter at 6; and NYSE Letter at 20-21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1982</SU>
                             Likewise, the staff guidance would not preclude an SCI entity from adopting a derivative of multiple standards, and/or customizing one or more standards for the particular system at issue. In assessing whether an SCI entity's use of such an approach in designing its policies and policies and procedures would be “deemed” to be reasonably designed, the Commission's inquiry would be into whether its policies and procedures were consistent with standards meeting the criteria in adopted Rule 1001(a)(4).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Systems Compliance</HD>
                    <P>Rule 1001(b)(1) requires each SCI entity to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the Exchange Act and the rules and regulations thereunder, and the entity's rules and governing documents, as applicable. Rule 1001(b)(2)(i)-(iv) provides that an SCI entity's policies and procedures under Rule 1001(b)(1) must include, at a minimum: (i) Testing of all SCI systems and any changes to SCI systems prior to implementation; (ii) a system of internal controls over changes to SCI systems; (iii) a plan for assessments of the functionality of SCI systems designed to detect systems compliance issues, including by responsible SCI personnel and by personnel familiar with applicable provisions of the Act and the rules and regulations thereunder and the SCI entity's rules and governing documents; and (iv) a plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, regarding SCI systems design, changes, testing, and controls designed to detect and prevent systems compliance issues. The Commission recognizes that SCI entities currently take varying measures to ensure that their systems operate in a manner that complies with relevant laws and rules. These practices at SCI entities may include escalating a compliance issue upon discovery, including legal and compliance personnel in the review of systems changes, and periodically reviewing rulebooks.</P>
                    <P>
                        The Commission believes that Rule 1001(b) should help to ensure that SCI entities operate their SCI systems in compliance with the Exchange Act and relevant rules and should help to reduce the occurrence of systems compliance issues. For example, the tests under Rule 1001(b)(2)(i) should help SCI entities to identify potential compliance issues before new systems or systems changes are implemented; the internal controls under Rule 1001(b)(2)(ii) should help to ensure that SCI entities remain vigilant against compliance issues when changing their systems and resolve potential compliance issues before the changes are implemented; and the systems assessment plans under Rule 1001(b)(2)(iii) and the coordination 
                        <PRTPAGE P="72422"/>
                        and communication plans under Rule 1001(b)(2)(iv) should help technology, regulatory, and other relevant personnel (including responsible SCI personnel) of SCI entities to work together to prevent compliance issues, and to promptly identify and address compliance issues if they occur. To the extent that compliance with Rule 1001(b) reduces the occurrence of systems compliance issues, Rule 1001(b) should help ensure investor protection. Because SCI entities will need to allocate their resources towards establishing, maintaining, and enforcing policies and procedures with regard to systems compliance, Rule 1001(b) will impose compliance costs on SCI entities. These costs are included as part of the quantified costs estimated above related to all requirements underlying Rules 1001(a) and (b) other than paperwork burdens.
                        <SU>1983</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1983</SU>
                             
                            <E T="03">See supra</E>
                             note 1940 and accompanying text. However, the costs associated with establishing and maintaining policies and procedures are included in the costs related to paperwork burdens in Section V.
                        </P>
                    </FTNT>
                    <P>
                        One commenter suggested that the Commission follow the Federal Aviation Administration's and NASA's approach, where, according to this commenter, individuals are encouraged to report safety issues and penalties are waived where there is self-reporting.
                        <SU>1984</SU>
                        <FTREF/>
                         As discussed above in Section IV.B.2.b, the Commission is not persuaded that it would be appropriate to provide a safe harbor for all problems that are self-reported by SCI entities and individuals because the Commission is not persuaded that the suggested self-report safe harbor will effectively further the intent of Regulation SCI.
                        <SU>1985</SU>
                        <FTREF/>
                         The extent to which regulators' reporting rules offer safe harbor protection is determined by particular circumstances and regulatory objectives. For purposes of Regulation SCI, a blanket safe harbor provision of the type proposed by the commenter would reduce incentives for SCI entities to take the proactive actions required to ensure the compliance of their SCI systems and, thus, could undermine the benefits of Regulation SCI discussed in Section IV.C.1.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1984</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 3-4. This commenter also stated that, in the SCI Proposal, the Commission did not analyze how other government regulatory agencies in the U.S. and elsewhere address technology risks (
                            <E T="03">e.g.,</E>
                             in the aviation, nuclear power, electricity, telecommunications, medical, and banking sectors). 
                            <E T="03">See</E>
                             Angel Letter at 3 and 15. The Commission notes that, in considering the adoption of Regulation SCI, it has considered some of the current practices in other industries, such as those discussed by panelists at the Technology Roundtable (
                            <E T="03">e.g.,</E>
                             aviation, nuclear power). 
                            <E T="03">See supra</E>
                             note 15 and Transcript of the Technology Roundtable, at 42-45.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1985</SU>
                             The Commission notes that, in addition to dealing with a different problem in different industries, the “waiving of penalties” cited by the commenter has limitations (
                            <E T="03">e.g.,</E>
                             the ASRS system cited by the comment suspends safe harbor protection for repeat violators and does not offer safe harbor for certain types of violations). Safe harbor protection for self-reporters may be appropriate in some circumstances. However, the Commission believes that in the specific context of Regulation SCI, such safe harbor protections would not further the intent of the regulation.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Responsible SCI Personnel</HD>
                    <P>Rule 1001(c) requires an SCI entity to establish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel, and escalation procedures to quickly inform responsible SCI personnel of potential SCI events. Rule 1001(c) imposes a requirement that is not addressed in Regulation ATS or the ARP Policy Statements.</P>
                    <P>The Commission believes that requiring policies and procedures to identify and designate responsible SCI personnel and to establish escalation procedures to quickly inform responsible SCI personnel of potential SCI events should help to effectively alert responsible SCI personnel of potential SCI events, in order for such personnel to determine whether an SCI event has occurred so that any appropriate actions can be taken in accordance with the requirements of Regulation SCI without unnecessary delay. As such, Rule 1001(c) should help reduce the duration of SCI events as SCI entities should become aware of potential SCI events and take appropriate corrective actions more quickly. The reduction in the duration of SCI events would benefit markets as it would promote pricing efficiency and price discovery as discussed in Section VI.C.1.</P>
                    <P>
                        The Commission believes that the costs associated with Rule 1001(c) are attributed to paperwork burdens, which are discussed in Section V.D.1.a above.
                        <SU>1986</SU>
                        <FTREF/>
                         The Commission does not believe that Rule 1001(c) will impose significant other costs on SCI entities because these entities already identify and designate responsible SCI personnel and have escalation procedures.
                        <SU>1987</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1986</SU>
                             When monetized, the paperwork burden would result in approximately $1.7 million initially and $611,000 annually for all SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1987</SU>
                             As noted above, several commenters emphasized the importance of escalation procedures at SCI entities, pursuant to which technology staff or junior employees could assess a systems problem and escalate the issue up the chain of command to management as well as legal and/or compliance personnel. 
                            <E T="03">See supra</E>
                             note 740 and accompanying text.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Periodic Review</HD>
                    <P>Rules 1001(a)(3), (b)(3), and (c)(2) require each SCI entity to periodically review the effectiveness of the policies and procedures required under Rules 1001(a), (b), and (c), respectively, and to take prompt action to remedy deficiencies in such policies and procedures. Regulation ATS and the ARP Policy Statements do not explicitly address the periodic review of policies and procedures and remediation of deficient policies and procedures.</P>
                    <P>
                        The Commission believes that requiring periodic review of the policies and procedures and remedial actions to address any deficiencies in the policies and procedures will help to ensure that SCI entities maintain robust policies and procedures and update them when necessary so that the benefits of Rules 1001(a), (b), and (c) should continue to be realized. As such, the Commission believes that Rules 1001(a)(3), (b)(3), and (c)(2) will help realize the benefits of Regulation SCI, and would facilitate price discovery and liquidity flow, as discussed in Section VI.C.1. These requirements, however, will impose costs on SCI entities because they will have to use resources to review the policies and procedures required by Rules 1001(a), (b), and (c) beyond the resources currently expended for this purpose or will have to take more prompt remedial action to remedy any identified deficiencies. The Commission expects that these costs generally will arise following an SCI entity's periodic review of the effectiveness of its policies and procedures and as a result of SCI events. The Commission believes that the costs associated with the review and update requirements are attributed to paperwork burdens, which are discussed in Section V.D.1.a above.
                        <SU>1988</SU>
                        <FTREF/>
                         However, the Commission recognizes that, if an SCI entity takes prompt or unplanned remedial action following the discovery of deficiencies in its policies and procedures, this may result in indirect costs (
                        <E T="03">i.e.,</E>
                         opportunity costs) to SCI entities because they may need to delay or shift their resources away from profitable projects and reallocate their resources towards taking prompt or unplanned remedial actions required by the rules. However, it is difficult to assess such indirect costs imposed on SCI entities because the Commission lacks information necessary to provide a reasonable estimate. For example, the Commission does not have 
                        <PRTPAGE P="72423"/>
                        comprehensive and detailed information on the value of the potential forgone projects of SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1988</SU>
                             As noted in Section V.D.1.a above, the paperwork burden related to the review of the policies and procedures is included in the estimated annual ongoing burden of Rules 1001(a), (b), and (c).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Corrective Action—Rule 1002(a)</HD>
                    <P>
                        Rule 1002(a) requires an SCI entity to begin to take appropriate corrective action upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred. Rule 1002(a) also requires corrective action to include, at a minimum, mitigating potential harm to investors and market integrity resulting from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable. Thus, it would not be appropriate for an SCI entity to unnecessarily delay the start of corrective action once its responsible SCI personnel have a reasonable basis to conclude that an SCI event has occurred, and the SCI entity would be required to focus on mitigating potential harm to investors and market integrity resulting from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable. The Commission believes that SCI entities already have a variety of procedures in place to take corrective actions when system issues occur. However, Rule 1002(a) will likely require modifications to those existing practices in part because the rule specifies the timing and enumerates certain goals for corrective action.
                        <SU>1989</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1989</SU>
                             For example, although the Commission believes that market participants already take corrective actions when system issues occur, currently, when taking corrective action, market participants may not always focus on mitigating potential harm to investors and market integrity or devoting adequate resources to remedy the issues as soon as reasonably practicable, as SCI entities are required to do under Rule 1002(a).
                        </P>
                    </FTNT>
                    <P>The Commission believes that the corrective action requirement will reduce the length of systems disruptions, systems compliance issues, and systems intrusions, and thus, as noted in Section VI.C.1, reduce the negative effects of those interruptions on the SCI entity and market participants. Additionally, to the extent that corrective action could involve wide-scale systems upgrades, some SCI entities may potentially seek to accelerate capital expenditures, for example, by updating their systems with newer technology earlier than they might have otherwise to comply with Regulation SCI. As such, Rule 1002(a) could further help ensure that SCI entities invest sufficient resources as soon as reasonably practicable to address systems issues.</P>
                    <P>
                        The Commission recognizes that Rule 1002(a) may require SCI entities to undertake corrective action sooner and/or to increase investments in newer and more updated systems earlier than they might have otherwise. The Commission thus believes that Rule 1002(a) could impose modestly higher costs for SCI entities in responding to SCI events relative to their current practice.
                        <SU>1990</SU>
                        <FTREF/>
                         But, given the wide variety of current practices, the Commission is unable to estimate the incremental costs associated with the required changes. Furthermore, if Regulation SCI reduces the frequency and severity of SCI events in the future, the cost of corrective action could similarly decline over time. However, the Commission cannot estimate these costs because the degree to which Regulation SCI will reduce the frequency and severity of SCI events is unknown. The Commission also believes that, if an SCI entity takes corrective action sooner than they might have without the requirements of Regulation SCI, this may impose indirect costs (
                        <E T="03">i.e.,</E>
                         opportunity costs) to SCI entities because they may have to delay or reallocate their resources away from profitable projects and direct their resources toward taking corrective action required by the rule. However, the Commission acknowledges that it is difficult to assess such indirect costs imposed on SCI entities. For instance, the Commission does not have comprehensive and detailed information on the value of the potential foregone projects of SCI entities. Consequently, the Commission is, at this time, unable to estimate the costs of Rule 1002(a) of Regulation SCI because the Commission lacks information necessary to provide a reasonable cost estimate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1990</SU>
                             
                            <E T="03">See also</E>
                             MSRB Letter at 32 (commenting that under most circumstances, any increased cost due to proposed Rule 1000(b)(3) would be modest since corrective action normally would already be taken).
                        </P>
                    </FTNT>
                    <P>
                        Several commenters stated that the requirements of proposed Rule 1000(b)(3) put too great an emphasis on immediate corrective action at the expense of thoroughly analyzing the SCI event and its cause, considering potential remedies, and/or acting in accordance with internal policies and procedures before committing to a plan to take corrective action.
                        <SU>1991</SU>
                        <FTREF/>
                         Partly in response to this concern, the Commission has modified the rule as adopted from the proposal. The Commission agrees that an SCI entity should be given appropriate time to perform an initial analysis and preliminary investigation into a potential systems issue before the corrective obligations are triggered. If a corrective action were to be applied without such analysis or investigation, then the impact of an SCI event could persist, exacerbating or prolonging its negative effects on markets and market participants. The Commission notes that Rule 1002(a) does not use the term “immediate.” Rather, Rule 1002(a) requires that corrective action be taken “as soon as reasonably practicable” once the triggering standard has been met. The Commission believes that, because the facts and circumstances of each specific SCI event will be different, this standard would help ensure that an SCI entity takes necessary corrective action soon after an SCI event, but not without sufficient time to first consider what is the appropriate action to remedy the SCI event in a particular situation and how such corrective action should be implemented.
                        <SU>1992</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1991</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 3; OCC Letter at 14; Joint SROs Letter at 11; LiquidPoint Letter at 4; DTCC Letter at 10; and Direct Edge Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1992</SU>
                             
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             Section IV.B.3.a (discussing in more detail the triggering standard for corrective action, Commission notification, and information dissemination) and Section IV.B.3.b (discussing the corrective action requirement).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Commission Notification—Rule 1002(b)</HD>
                    <P>As discussed above in Section IV.B.3.c, Rule 1002(b) requires SCI entities to provide notifications to the Commission regarding SCI events. Specifically, upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, an SCI entity is required to notify the Commission of the SCI event immediately. Within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, an SCI entity is required to submit a more detailed written notification, on a good faith, best efforts basis, pertaining to the SCI event. Until such time as the SCI event is resolved and the SCI entity's investigation of the SCI event is closed, the SCI entity is required to provide updates regularly, or at such frequency as requested by a representative of the Commission. The SCI entity is also required to submit a detailed final written notification after the SCI event is resolved and the SCI entity's investigation of the event is closed (and an additional interim written notification, if the SCI event is not resolved or the investigation is not closed within a specified period of time). Finally, SCI entities are required to notify the Commission of information regarding de minimis systems disruptions and de minimis systems intrusions on a quarterly basis.</P>
                    <P>
                        The Commission believes that most, if not all, major systems incidents are 
                        <PRTPAGE P="72424"/>
                        reported by ARP entities to the Commission and that many “de minimis” systems issues are documented internally by SCI entities as part of their incident management systems. For those entities that do not participate in the ARP Inspection Program, the Commission also believes that some internal documentation of systems incidents exists. In addition, the Commission notes that some SCI entities currently notify the Commission of certain systems compliance issues.
                    </P>
                    <P>
                        Rule 1002(b) will apply to more entities (
                        <E T="03">e.g.,</E>
                         some SCI ATSs), more systems (
                        <E T="03">e.g.,</E>
                         market regulation and market surveillance systems, additional market data systems), and more types of systems issues (
                        <E T="03">e.g.,</E>
                         systems compliance issues) than the ARP Policy Statements, and also require more detailed reporting to the Commission.
                        <SU>1993</SU>
                        <FTREF/>
                         The Commission believes that Rule 1002(b) will enhance the effectiveness of Commission oversight of the operation of SCI entities. For example, one commenter suggested that SCI events notification results in greater transparency for the Commission, with multiple benefits, including ensuring that the Commission has a view into problems at particular SCI entities for regulatory purposes as well as perspective on the effect of a single problem to the market at-large.
                        <SU>1994</SU>
                        <FTREF/>
                         Further, the Commission believes that providing written notifications to the Commission could help prevent systems failures from being dismissed as momentary issues, because notification would help focus the SCI entity's attention on the issue and encourage allocation of SCI entity resources to resolve the issue as soon as reasonably practicable.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1993</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.c (discussing in detail the requirements of Rule 1002(b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1994</SU>
                             
                            <E T="03">See</E>
                             Lauer Letter at 8.
                        </P>
                    </FTNT>
                    <P>
                        As noted in Section IV.B.3.c, the Commission received comment letters that discuss the resource and efficiency demands of the Commission notification requirement.
                        <SU>1995</SU>
                        <FTREF/>
                         Some commenters expressed concern that SCI entities may feel compelled to characterize and report a greater number of systems anomalies as disruptions to comply with Regulation SCI,
                        <SU>1996</SU>
                        <FTREF/>
                         and that the proposal would result in SCI entities having “shadow staff” on hand solely for reporting SCI events so as to not divert staff away from working to resolve SCI events.
                        <SU>1997</SU>
                        <FTREF/>
                         While the Commission is adopting the definitions of systems disruptions, systems compliance issues, and systems intrusions, and providing discussions of these definitions in this release, the Commission acknowledges that some SCI entities could be overly cautious in seeking to be in compliance with Regulation SCI and therefore over-report systems issues to the Commission. Furthermore, the Commission notes that some SCI entities currently notify the Commission of systems related issues under the ARP Inspection Program or as part of their current business practice, but the Commission believes that SCI entities will have to allocate additional resources to meet the Commission notification requirement. Although the estimated cost to comply with the adopted notification provisions is greater than the estimate in the SCI Proposal, the Commission is not persuaded that the adopted rule, with its more targeted scope, will require SCI entities to have a “shadow staff” on hand solely for reporting SCI events. As discussed in Section IV.B.3.c, the Commission believes that concerns with respect to resource demands regarding the Commission notification requirements have been substantially mitigated by the numerous changes from the proposal, such as the adoption of a quarterly reporting framework for de minimis systems disruptions and de minimis systems intrusions; the adoption of an exception from the Commission notification requirements for de minimis systems compliance issues; the revised definitions of SCI systems, indirect SCI systems, systems disruption, and systems compliance issue; and the reduction in the obligations SCI entities have with respect to reporting requirements. In addition, the Commission is not persuaded that the burden of the Commission notification requirement will significantly reduce SCI entities' ability to adequately respond to SCI events. It is the Commission's experience that the staff engaging in corrective action to resolve an SCI event is generally distinct from the staff that has been charged with notifying the Commission of systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1995</SU>
                             
                            <E T="03">See, e.g.,</E>
                             UBS Letter at 3; Omgeo Letter at 16; MSRB Letter at 19; OCC Letter at 14; SunGard Letter at 5; Joint SROs Letter at 7; and NYSE Letter at 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1996</SU>
                             
                            <E T="03">See</E>
                             Joint SROs Letter at 9-10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1997</SU>
                             
                            <E T="03">See</E>
                             FINRA Letter at 19.
                        </P>
                    </FTNT>
                    <P>
                        The compliance costs associated with Rule 1002(b) are attributed to the paperwork burden of Commission notifications of SCI events, including recordkeeping and submission of quarterly reports with respect to de minimis SCI events, as applicable.
                        <SU>1998</SU>
                        <FTREF/>
                         As discussed in the PRA, with respect to SCI events that are not de minimis, the Commission has estimated the total annual hourly burden to comply with Rules 1002(b)(1)-(4) to be 125,180 hours for all SCI entities (monetized to be approximately $40 million), or 2,845 hours per SCI entity.
                        <SU>1999</SU>
                        <FTREF/>
                         This estimate is greater than that estimated in the SCI Proposal (which estimate was 58,080 hours for all SCI entities, or 1,320 hour per SCI entity to comply with proposed Rules 1000(b)(4)(i)-(iii)). As more fully explained in the PRA, the Commission has increased its estimate to comply with the Commission notification provisions in Rules 1002(b)(1)-(4), notwithstanding the more targeted scope of the adopted rule, as compared to the proposed rule. These increased estimates are in response to comment that the estimates in the SCI Proposal were too low, particularly with respect to the time necessary for an SCI entity to prepare, review, and submit the required notifications.
                        <SU>2000</SU>
                        <FTREF/>
                         In addition, for Rule 1002(b)(5), which requires recordkeeping of all de minimis SCI events and quarterly reporting of de minimis systems disruptions and de minimis systems intrusions, the Commission has estimated a total of 7,040 hours for all SCI entities (monetized to be approximately $2 million), or 160 hours per SCI entity, for Commission notification. The number of SCI events (de minimis and otherwise), and the burdens to comply with notification requirements will likely vary among individual SCI entities, based on the nature of their business, technology, and the relative criticality of each of their SCI systems.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1998</SU>
                             When monetized, the paperwork burden would result in approximately $42 million, in addition to approximately $2 million in outsourcing cost, annually for all SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>1999</SU>
                             
                            <E T="03">See supra</E>
                             Section V.D.2.a (discussing the Commission's estimate of the hours required to comply with Rule 1002(b)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2000</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        In addition, the Commission believes that most, if not all, SCI entities already have some internal procedures for determining the severity of a systems issue. Nevertheless, to the extent that an SCI entity must determine whether an SCI event is a de minimis SCI event, Rule 1002(b) may impose one-time implementation costs on SCI entities associated with developing a process for ensuring that they are able to quickly and correctly make such determinations, as well as ongoing costs in reviewing the adopted process. The initial and ongoing burden associated with identifying certain systems and SCI events is discussed in Section V.D.3.b.
                        <SU>2001</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2001</SU>
                             When monetized, the paperwork burden would result in approximately $1.1 million initially and $413,000 annually for all ARP entities in the aggregate, and approximately $885,000 initially and $292,000 annually for all non-ARP entities in the aggregate. These estimates include the 
                            <PRTPAGE/>
                            identification of critical SCI systems, major SCI events, and de minimis SCI events.
                        </P>
                    </FTNT>
                    <PRTPAGE P="72425"/>
                    <P>Proposed Rule 1000(b)(4) did not distinguish de minimis SCI events from other SCI events in terms of the timing or type of Commission notifications. The Commission believes that the adopted quarterly Commission reporting requirement for de minimis systems disruptions and de minimis systems intrusions, and the exception from the Commission reporting requirement for de minimis systems compliance issues, will reduce costs related to Commission reporting (as compared to the costs of complying with the proposed Commission notification requirements) for SCI entities, and could facilitate more efficient allocation of SCI entities' resources toward more significant systems issues because de minimis SCI events would be subject to a recordkeeping requirement and de minimis systems disruptions and de minimis systems intrusions would be subject to a quarterly reporting requirement, rather than a requirement to report such events to the Commission more immediately. As de minimis SCI events are defined to have no or a de minimis impact on the SCI entity's operations or on market participants, the Commission believes that the recordkeeping requirement and quarterly reporting requirement, as applicable, will allow both the SCI entity and its personnel, as well as the Commission and its staff, to focus more of their attention and resources on other, more significant SCI events. Moreover, the quarterly Commission notification requirement for de minimis systems disruptions and de minimis systems intrusions will help SCI entities and the Commission to gather information on the nature, types, and frequency of de minimis SCI events and, thus, help identify potential weaknesses in systems across SCI entities and Commission's ability to monitor market events. The Commission believes that the quarterly reporting requirement for de minimis systems disruptions and de minimis systems intrusions balances the interest of SCI entities in having a limited reporting burden for de minimis systems disruptions and de minimis systems intrusions with the Commission's interest in oversight of the information technology programs of SCI entities.</P>
                    <P>
                        Furthermore, proposed Rule 1000(b)(4)(iii) would have required an SCI entity to submit written updates pertaining to an SCI event until the SCI event is resolved. The Commission has revised the update requirement from the proposal in adopted Rule 1002(b)(3) so that the submission of updates may be provided either orally or in written form.
                        <SU>2002</SU>
                        <FTREF/>
                         This revision should reduce costs as compared to proposed Rule 1000(b)(4) by providing flexibility to SCI entities and because oral notifications will likely result in a lower burden than written notifications.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2002</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.3.c.
                        </P>
                    </FTNT>
                    <P>The Commission has also modified the 24-hour written notification requirement in adopted Rule 1002(b) to make clear that the written notification provided within 24 hours be submitted on a good faith, best effort basis. Compared to the proposed rule, the Commission believes the adopted rules will help provide certainty to SCI entities that they will not be accountable for unintentional inaccuracies or omissions contained in these submissions. The “best efforts” standard will also help to ensure that SCI entities will make a diligent and timely attempt to provide all the information required by the written notification requirement, thus permitting the Commission to effectively monitor SCI events.</P>
                    <P>As discussed in Section IV.B.3.c, with respect to submitting final written notifications, proposed Rule 1000(b)(4)(ii) would have required the submission of the information required to be included in the final written notification within a shorter time frame. By requiring that the final written notification be submitted after resolution of an SCI event, the Commission believes that the adopted rule will encourage SCI entities to allocate their resources efficiently in resolving the SCI event.</P>
                    <P>
                        One commenter expressed concern that, without a safe harbor and a guarantee of immunity, the disclosures to the Commission required under Regulation SCI would provide a roadmap for litigation against non-SRO entities.
                        <SU>2003</SU>
                        <FTREF/>
                         As discussed in Section IV.B.2.b, the occurrence of a systems compliance issue does not necessarily mean that the SCI entity will be subject to an enforcement action. Rather, the Commission will exercise its discretion to initiate an enforcement action if the Commission determines that action is warranted, based on the particular facts and circumstances of an individual situation. Moreover, the Commission recognizes that compliance with Regulation SCI will increase the amount of information about SCI events available to the Commission and SCI entities' members and participants, and that the greater availability of this information has some potential to increase litigation risks for SCI entities, including the risk of private civil litigation. Commenters did not provide estimates of potential litigation costs and Commission staff were unable to find readily-available public information from which to estimate specific costs of possible litigation associated with the increased information available about SCI events, but based on staff experience, depending on the complexity, scope, and length of the litigation, the costs to defend an individual case could be quite significant. The Commission notes, however, that it is not clear that the incremental increase in costs due to Regulation SCI will be significant in the aggregate. Regulation SCI does not alter the elements of any available private cause of action, and the elements of such actions are likely to limit the potential for recovery. Moreover, to the extent members and participants suffer damages when SCI events occur, SCI entities are already subject to litigation risk.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2003</SU>
                             
                            <E T="03">See</E>
                             OTC Markets Letter at 15-16 (stating that “entities that do not have SRO immunity, such as ATSs, may be subject to liability based on information reported under Reg. SCI's Rule 1000(b)(4)(iv) . . . [w]ithout a safe harbor and a guarantee of immunity, this kind of disclosure provides a roadmap for litigation against non-SRO SCI entities”). 
                            <E T="03">See also</E>
                             FIF Letter at 5.
                        </P>
                    </FTNT>
                    <P>
                        As an alternative to the adopted rule, some commenters suggested that non-material systems intrusions not be reported to the Commission at all, and only be recorded by the SCI entity to reduce the instances in which notice of systems intrusions would be required.
                        <SU>2004</SU>
                        <FTREF/>
                         The Commission continues to believe that reporting intrusions in SCI systems and indirect SCI systems will help the Commission and its staff to detect patterns or understand trends over time and the nature of systems intrusions that may be occurring at multiple SCI entities and, thus, help ensure effective Commission oversight. As discussed in Section IV.B.3.c in detail, to reduce the burden associated with the Commission notification requirement, the Commission established separate reporting requirements (
                        <E T="03">e.g.,</E>
                         quarterly reporting) for de minimis systems disruptions and de minimis systems intrusions and provided an exception from the Commission reporting requirement for de minimis systems compliance issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2004</SU>
                             
                            <E T="03">See</E>
                             Omgeo Letter at 12; and DTCC Letter at 8.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Information Dissemination—Rule 1002(c)</HD>
                    <P>
                        Rule 1002(c) requires an SCI entity to disseminate information regarding 
                        <PRTPAGE P="72426"/>
                        certain major SCI events to all of its members or participants and certain other SCI events to affected members or participants. Specifically, promptly after any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, an SCI entity is required to disseminate certain information regarding the SCI event. When certain additional information becomes known, the SCI entity is required to promptly disseminate such information. Until the SCI event is resolved, the SCI entity is required to provide regular updates on the required information.
                        <SU>2005</SU>
                        <FTREF/>
                         As adopted, the information dissemination requirement does not apply to SCI events to the extent they relate to market regulation or market surveillance systems and de minimis SCI events. Rule 1002(c) imposes new requirements that are not currently part of the ARP Inspection Program. However, some entities currently provide their members or participants and, in some cases, market participants or the public more generally, with notices of systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2005</SU>
                             Rule 1002(c)(2) provides an exception to the information dissemination requirement for systems intrusions when an SCI entity determines that dissemination of information would likely compromise the security of the SCI entity's systems, or an investigation of the systems intrusion, and documents the reasons for such determination.
                        </P>
                    </FTNT>
                    <P>
                        As discussed in Section IV.B.3.d, a major SCI event is defined to mean an SCI event that has any impact on a critical SCI system or a significant impact on the SCI entity's operations or on market participants. The Commission believes that, in the context of a major SCI event, where the impact of the SCI event is most likely to be felt by many market participants, the goal of aiding market participants in evaluating the impact of the event would be efficiently served by dissemination of information to all members or participants of the SCI entity.
                        <SU>2006</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2006</SU>
                             At the same time, the Commission recognizes that some SCI events that meet the definition of “major SCI event” could also qualify as de minimis SCI events. Like other de minimis SCI events, they are excepted from the information dissemination requirement. In particular, because major SCI events are a subset of SCI events, the exception under Rule 1002(c)(4)(ii) applies to major SCI events that meet the requirements of that rule.
                        </P>
                    </FTNT>
                    <P>The Commission believes that Rule 1002(c) will help market participants—specifically the members or participants of SCI entities estimated to be affected by an SCI event and any additional members or participants subsequently estimated to be affected by an SCI event and, in some cases, all members or participants of an SCI entity—to better evaluate the operations of SCI entities by requiring certain information to be disclosed. Furthermore, increased awareness of SCI events through information disseminated to members or participants should provide SCI entities additional incentives to maintain robust systems and minimize the occurrence of SCI events. More robust SCI systems and the reduction in the occurrence of SCI events could reduce interruptions in price discovery process and liquidity flows as discussed above in Section VI.C.1.</P>
                    <P>
                        One commenter provided information about the benefits of the proposed information dissemination requirements. Specifically, according to this commenter, one of the major benefits of Regulation SCI could be better sharing of information about technology problems.
                        <SU>2007</SU>
                        <FTREF/>
                         According to this commenter, sharing information about hardware failures, systems intrusions, and software glitches will alert others in the industry about such problems and help reduce system-wide costs of diagnosing problems, as well as result in improved responses to technology problems.
                        <SU>2008</SU>
                        <FTREF/>
                         This commenter also believed that the information will serve as warnings to other SCI entities to stay vigilant to prevent similar problems.
                        <SU>2009</SU>
                        <FTREF/>
                         The Commission believes that benefits identified by the commenter could be benefits of Rule 1002(c).
                    </P>
                    <FTNT>
                        <P>
                            <SU>2007</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2008</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2009</SU>
                             
                            <E T="03">See id.</E>
                             However, this commenter also disagreed with the Commission that SCI entities may be reluctant to admit publicly to their glitches. 
                            <E T="03">See id.</E>
                             at 14. According to this commenter, market participants interact repeatedly with each other on a real-time basis and are acutely aware of glitches when they occur. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As discussed above, while some entities currently provide their members or participants and, in some cases, market participants or the public more generally, with notices of certain systems issues (
                        <E T="03">e.g.,</E>
                         system outages), Rule 1002(c) imposes new requirements that are not currently part of the ARP Inspection Program. As such, the requirements of Rule 1002(c) will impose costs—which are attributed to paperwork burdens—on SCI entities with respect to preparing, drafting, reviewing, and making the information available to members or participants. These costs are discussed in more detail in Section V.D.2.b.
                        <SU>2010</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2010</SU>
                             When monetized, the paperwork burden would result in approximately $26 million, in addition to approximately $1.6 million in outsourcing cost, annually for all SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <P>
                        In the SCI Proposal, the Commission recognized that SCI entities incur costs to determine whether an event needs to be disseminated. While the SCI events subject to the adopted information dissemination requirements are different from those that would have been subject to the proposed requirements, the Commission continues to recognize that the determination imposes costs. Specifically, identifying major SCI events may impose one-time implementation costs on SCI entities associated with developing a process for ensuring that they are able to quickly and correctly make such determinations, as well as periodic costs in reviewing the adopted process. These costs are discussed in more detail in Section V.D.3.b.
                        <SU>2011</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2011</SU>
                             
                            <E T="03">See also supra</E>
                             note 2001.
                        </P>
                    </FTNT>
                    <P>
                        One commenter expressed concern that SCI entities may over-report issues out of an abundance of caution if SCI entities are not given clear guidelines as to what and to whom they are required to provide information.
                        <SU>2012</SU>
                        <FTREF/>
                         This commenter believed that a flood of notifications, taken out of context, may create investor impression based on the quantity, not the quality, of the notifications disseminated, that certain counterparties pose serious risks to the market, when that is not the case.
                        <SU>2013</SU>
                        <FTREF/>
                         For the reasons discussed in Section IV.B.3.d, the Commission believes that information about SCI events (other than major SCI events and de minimis SCI events) should be disseminated to affected members or participants, and information about major SCI events (other than those that qualify as de minimis SCI events) should be disseminated to all members or participants of an SCI entity. At the same time, as compared to proposed Rule 1000(b)(5), the Commission is limiting the requirement for information dissemination to all members or participants of an SCI entity to major SCI events; limiting other information dissemination to members or participants affected by the SCI event; and excluding de minimis SCI events and SCI events related to market regulation or market surveillance systems from the information dissemination requirement. These changes would limit the compliance cost for Rule 1002(c), and are responsive to the commenter's concern that SCI entities may over-disclose systems issues.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2012</SU>
                             
                            <E T="03">See</E>
                             Fidelity Letter at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2013</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As an alternative to the adopted rule, one commenter suggested broadening the proposed rule to require an SCI entity to disseminate information on SCI events to the public, and not just to its 
                        <PRTPAGE P="72427"/>
                        members or participants.
                        <SU>2014</SU>
                        <FTREF/>
                         This commenter believed that public dissemination of the facts of an SCI event would help enhance investor confidence by preventing speculation and misinformation, and would provide important learning opportunities for the industry and other SCI entities.
                        <SU>2015</SU>
                        <FTREF/>
                         The Commission acknowledges that there can be additional benefits from disseminating major SCI events to the public as noted by the commenter. Under the adopted rule, an SCI entity is required to disseminate information on major SCI events (other than those that qualify as de minimis SCI events) to all of its members and participants. The Commission believes that these market participants are the most likely to act on this information and, thus, induce additional competitive incentives for SCI entities to avoid systems issues. As such, the Commission believes that it can achieve the purposes of the rule without requiring public dissemination, and also believes any additional gain in benefits from public dissemination would be minimal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2014</SU>
                             
                            <E T="03">See</E>
                             MFA Letter at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2015</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">v. Material Systems Changes—Rule 1003(a)</HD>
                    <P>Rule 1003(a)(1) requires an SCI entity to provide quarterly reports to the Commission, describing completed, ongoing, and planned material systems changes to its SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters. Rule 1003(a)(1) also requires an SCI entity to establish reasonable written criteria for identifying a change to its SCI systems and the security of its indirect SCI systems as material. Rule 1003(a)(2) requires an SCI entity to promptly submit a supplemental report to notify the Commission of a material error in or material omission from a previously submitted report.</P>
                    <P>Entities that participate in the ARP Inspection Program currently provide some material systems change notifications to the Commission and the Commission believes that all SCI entities have some internal processes for documenting systems changes as a matter of prudent business practice. For example, consistent with the ARP Policy Statements, certain entities provide annual reports on significant systems changes and notify the Commission on an as-needed basis regarding certain significant systems changes. In addition, ATSs are required notify the Commission of certain systems changes pursuant to Rule 301(b)(2)(ii) and Rule 301(b)(6)(ii)(G) of Regulation ATS, as applicable. Rule 1003(a) changes some of the current practices and sets forth more detailed requirements for these notifications. For example, Rule 1003(a) covers material changes on a broader set of systems than the ARP Inspection Program or Regulation ATS. Rule 1003(a) also requires an SCI entity to submit quarterly reports on Form SCI regarding material systems changes, but does not require separate notification for each material systems change. Further, Rule 1003(a) requires an SCI entity to promptly notify the Commission (by submitting Form SCI) of a material error in or material omission from a previously submitted report. To the extent that Rule 1003(a) requires SCI entities to notify the Commission of material systems changes for more types of systems and to the extent that it requires notification at a higher frequency than current practice (quarterly reports vs. annual reports), the Commission believes that Rule 1003(a) should enhance the Commission's oversight of the operation of SCI entities.</P>
                    <P>
                        The compliance costs of Rule 1003(a) primarily entail costs associated with preparing and submitting Form SCI in accordance with the instructions thereto. The initial and ongoing cost estimates associated with preparing and submitting Form SCI with regard to material systems changes under Rules 1003(a)(1) and (2) are discussed in detail in Section V.D.2.c.
                        <SU>2016</SU>
                        <FTREF/>
                         The Commission does not expect Rule 1003(a) will impose significant costs on SCI entities other than those discussed in Section V.D.2.c.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2016</SU>
                             When monetized, the paperwork burden would result in approximately $6.8 million annually for all SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <P>
                        According to one commenter, “[t]he larger market participants [that will be subject to Regulation SCI] are generally experienced and circumspect with regards to significant infrastructure changes, such as data center migrations and major platform upgrades.” 
                        <SU>2017</SU>
                        <FTREF/>
                         This commenter expected that, for these larger entities, integrating Regulation SCI compliance into their existing programs can occur without crippling disruption or exorbitant cost, and expected that insight from the implementation of Regulation SCI would contribute to overall stability and resiliency of the markets over time.
                        <SU>2018</SU>
                        <FTREF/>
                         However, this commenter expressed concern that compliance with the Commission notification requirement will result in incremental costs that may in some cases delay or discourage innovation.
                        <SU>2019</SU>
                        <FTREF/>
                         Another commenter similarly expressed concern about the compliance burden and the resulting impact on competition and innovation associated with the 30-day advance Commission notification requirement for material systems changes.
                        <SU>2020</SU>
                        <FTREF/>
                         In addition, one commenter noted that the Commission underestimated the cost of lost business opportunities and the inability to swiftly deploy corrective solutions that would result from the 30-day advance systems change notification requirements.
                        <SU>2021</SU>
                        <FTREF/>
                         This commenter noted that most ATS operators with advanced systems purposefully implement frequent agile modifications instead of major episodic changes in order to continuously improve their systems and minimize the impact of the changes.
                        <SU>2022</SU>
                        <FTREF/>
                         This commenter expressed concern that a built-in 30-day delay in implementing changes would encourage the deployment of larger, riskier changes more infrequently, thereby creating longer periods of time during which a systems issue and/or erroneous configuration would continue without correction.
                        <SU>2023</SU>
                        <FTREF/>
                         This commenter also stated that the 30-day advance notification process has the potential to delay the deployment of corrective solutions that are necessary to ensure the provision of uninterrupted and efficient order matching services at the best available prices.
                        <SU>2024</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2017</SU>
                             
                            <E T="03">See</E>
                             SunGard Letter at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2018</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2019</SU>
                             
                            <E T="03">See id..</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2020</SU>
                             
                            <E T="03">See</E>
                             BATS Letter at 15. 
                            <E T="03">See also, e.g., supra</E>
                             notes 999-1000 (discussing the views of commenters that the proposed 30-day advance notification requirement would stifle innovation and interfere with an SCI entity's natural planning and development process).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2021</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2022</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2023</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2024</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        As noted above, as adopted, Regulation SCI does not include the proposed 30-day advance Commission notification requirement for material systems changes. Rather, Rule 1003(a)(1) requires quarterly reports of material systems changes. Elimination of the proposed 30-day advance Commission notification requirement addresses the concern of some commenters that the rule would impede agile development methodology and favor the waterfall development methodology, or delay the implementation of systems changes or innovations, particularly for smaller SCI entities. The quarterly reports will also provide the Commission and its staff with a more efficient framework to review material systems changes, 
                        <PRTPAGE P="72428"/>
                        because including all relevant material systems changes in a single report will allow the Commission to more easily and clearly understand an SCI entity's framework for systems changes, including how certain material systems changes are related.
                        <SU>2025</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2025</SU>
                             As discussed above, Commission staff will not use material systems change reports to require any approval of planned systems changes in advance of their implementation pursuant to any provision of Regulation SCI, or to delay implementation of material systems changes pursuant to any provision of Regulation SCI. 
                            <E T="03">See supra</E>
                             Section IV.B.4.b.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vi. SCI Review—Rule 1003(b)</HD>
                    <P>
                        Rule 1003(b) requires an SCI entity to conduct an SCI review of its compliance with Regulation SCI not less than once each year,
                        <SU>2026</SU>
                        <FTREF/>
                         and submit a report of the SCI review to senior management of the SCI entity for review no more than 30 calendar days after completion of such SCI review. Rule 1003(b) also requires an SCI entity to submit a report of the SCI review to the Commission and to the board of directors of the SCI entity or the equivalent of such board, together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2026</SU>
                             However, penetration test reviews of the network, firewalls, and production systems are required to be conducted not less than once every three years. 
                            <E T="03">See</E>
                             Rule 1003(b)(i). Assessments of SCI systems directly supporting market regulation or market surveillance are required to be conducted at a frequency based upon the risk assessment conducted as part of the SCI review, but also not less than once every three years. 
                            <E T="03">See</E>
                             Rule 1003(b)(1)(ii).
                        </P>
                    </FTNT>
                    <P>
                        Systems reviews have been part of the ARP Inspection Program, and through this program, the Commission understands that many SCI entities currently undertake annual systems reviews and that senior management and/or the board of directors or a committee thereof reviews reports of such reviews. However, the Commission believes that the scope of the systems reviews, and the level of senior management and/or board involvement in such reviews, varies among ARP entities. The Commission expects that the SCI review requirement would produce greater consistency in the approach that SCI entities take in systems reviews, which would help improve the efficiency of the Commission's oversight (
                        <E T="03">e.g.,</E>
                         inspection) of SCI entities' systems. In addition, the Commission believes that the SCI review requirement would result in SCI entities having an improved awareness of the relative strengths and weaknesses of their systems independent of the assessment of Commission staff, which should, in turn, improve systems and reduce the number of SCI events. As discussed in Section VI.C.1, the reduction in occurrence of SCI events could reduce interruptions in the price discovery process and liquidity flows.
                    </P>
                    <P>
                        The initial and ongoing paperwork burden associated with conducting an SCI review, submitting a report of the SCI review to senior management of the SCI entity for review, and submitting a report of the SCI review and any response by senior management to the Commission and to the board of directors of the SCI entity or the equivalent of such board is discussed in Section V.D.2.d.
                        <SU>2027</SU>
                        <FTREF/>
                         SCI entities will also incur costs in addition to the paperwork burden to comply with the SCI review requirement. Although the Commission understands that most SCI entities currently undertake annual systems reviews, Rule 1003(b) sets forth specific requirements related to the SCI review. In particular, an SCI review is required to include a risk assessment with respect to SCI systems and indirect SCI systems of an SCI entity, an assessment of internal control design and effectiveness of SCI systems and indirect SCI systems, and penetration testing reviews. Moreover, Rule 1003(b) specifies that the SCI review is to determine the SCI entity's compliance with Regulation SCI. Rule 1003(b) also requires a report of the SCI review and any senior management response to be submitted to the board of directors of the SCI entity or the equivalent of such board and thus SCI entities may incur an additional cost as a result of additional time the board allocates to evaluate the review. The Commission cannot estimate costs other than paperwork burdens because the Commission does not have the information necessary to provide a reasonable estimate. In particular, the Commission lacks information on how SCI entities will structure their reviews.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2027</SU>
                             When monetized, the paperwork burden would result in approximately $9.7 million, in addition to approximately $2.2 million in outsourcing cost, annually for all SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <P>
                        As discussed above in Section IV.B.5, the Commission is not adopting a requirement that SCI reviews be conducted by an independent third party because the Commission believes that the goals of Regulation SCI can be achieved through reviews by either internal objective personnel or external objective personnel. The Commission acknowledges that, in some cases, there could be potential benefits from requiring third party reviews. However, as noted in Section IV.B.5, third parties can also have conflicts of interest that prevent a particular entity or personnel from meeting the objectivity standard required for an SCI review. In addition, during the Technology Roundtable in which participants discussed third party review, some panelists suggested that the use of an external third party is unnecessary because, for example, the training for a third party as well as the costs involved with third party evaluations would be large with little additional benefit.
                        <SU>2028</SU>
                        <FTREF/>
                         The Commission agrees that SCI entities would likely need to provide significant guidance to third-party reviewers on the specific features of the entity's systems. The Commission recognizes that a third-party review requirement could impose additional costs on SCI entities, and believes that it is appropriate at this time to allow SCI entities to decide whether to incur such costs instead of mandating third-party review.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2028</SU>
                             
                            <E T="03">See</E>
                             Transcript of the Technology Roundtable, at 86-91.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vii. Business Continuity and Disaster Recovery Plan Testing—Rule 1004</HD>
                    <P>Rule 1004(b) requires the testing of an SCI entity's business continuity and disaster recovery plans at least once every 12 months. Rules 1004(a) and (b) require participation in such testing by those members or participants that an SCI entity reasonably determines are, taken as a whole, the minimum number necessary for the maintenance of fair and orderly markets in the event of the activation of its business continuity and disaster recovery plans. Rule 1004(c) requires an SCI entity to coordinate such testing on an industry- or sector-wide basis with other SCI entities.</P>
                    <P>
                        The requirements under Rule 1004 are not a part of the ARP Inspection Program. As discussed above in Section VI.B.2, the securities industry generally has a voluntary system for testing business continuity and disaster recovery plans and market participants, including exchanges, members of exchanges, clearing agencies, clearing members, and ATSs, already coordinate certain business continuity and disaster recovery plan testing to some extent. For example, some SCI entities already require some of their members or participants to connect to their backup systems. Further, although participation is not always mandatory, some SCI entities already provide their members or participants with the opportunity to test the SCI entity's business continuity and disaster recovery plans. However, because not all SCI entities require member or participant participation in business continuity and disaster recovery plans testing, the Commission 
                        <PRTPAGE P="72429"/>
                        understands that not all market participants participate in such testing. Moreover, the Commission understands that, to the extent such participation occurs, it may in many cases be limited in nature (
                        <E T="03">e.g.,</E>
                         testing for connectivity to backup systems).
                        <SU>2029</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2029</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18164.
                        </P>
                    </FTNT>
                    <P>The Commission believes that, for SCI entities, voluntary testing is insufficient, and that business continuity and disaster recovery planning for market centers and certain members or participants must be an integral component of business continuity and disaster recovery preparedness. The Commission further believes that the requirements under Rule 1004 should help ensure that the securities markets will have improved backup infrastructure and fewer market-wide shutdowns. As discussed in detail in Section VI.C.1, fewer market-wide shutdowns should help facilitate continuous liquidity flows in markets, reduce pricing errors, and thus improve the quality of the price discovery process.</P>
                    <P>
                        With respect to these benefits, one commenter suggested measuring benefits of reducing outages and technical issues by looking at, for example, loss of trading commissions due to outages.
                        <SU>2030</SU>
                        <FTREF/>
                         This commenter estimated that the potential loss of equity commissions by broker-dealers over the two-day market closure from Superstorm Sandy may have been approximately $374 million.
                        <SU>2031</SU>
                        <FTREF/>
                         The Commission believes that measuring potential benefits in terms of transaction costs (commission revenue) does not fully account for other benefits, such as uninterrupted liquidity flows and price discovery.
                        <SU>2032</SU>
                        <FTREF/>
                         Furthermore, the Commission believes that the estimated commission loss noted by the commenter likely overstates the actual losses in commissions because some of the “lost” trading may have only been delayed until the markets re-opened after Superstorm Sandy. Accordingly, the Commission is not persuaded that the estimate provided by the commenter represents the quantified benefit associated with this component of Regulation SCI. The Commission is unable to estimate the benefit of this component of Regulation SCI because the Commission does not have quantified information on the extent that a reduction in SCI events will help facilitate liquidity flows in markets, reduce pricing errors, and thus improve the quality of the price discovery process. Furthermore, the Commission is unable to quantify the impact of “delayed” trading because it lacks the information necessary to provide a reasonable estimate. In particular, data on the trading activity lost as opposed to “delayed” due to the two-day market closure would be extremely difficult to piece together in a meaningful way.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2030</SU>
                             
                            <E T="03">See</E>
                             Angel Letter at 15-16. The Commission also notes that this commenter and others expressed the view that enhanced BC/DR testing would have substantial benefits. 
                            <E T="03">See, e.g., id.</E>
                             at 9-10 (stating that the “ability of SROs to require their members to participate in testing is an important step forward in making sure that testing is as realistic as possible . . . [and] is one of the most valuable parts of Regulation SCI and will do the most to ensure improved market network reliability”); and UBS Letter at 5 (stating that the “critical task of BCP testing should not be undertaken in isolated silos by individual firms. Individual BCP testing that does not involve realistic scenarios with connected participants may mask gaps and/or be insufficient from a systems integrity standpoint” and that the benefits of a “new and more comprehensive BCP testing paradigm” would be “broad and considerable”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2031</SU>
                             This commenter based this estimate on FINRA member equity commissions in 2010 obtained from SIFMA. 
                            <E T="03">See</E>
                             Angel Letter at 16. In addition, this commenter referred to the losses and legal and administrative costs associated with the Facebook IPO, as well as the losses associated with the May 6, 2010 incident. 
                            <E T="03">See id.</E>
                             at 15-16. This commenter also more generally stated that the benefits of reducing outages and major technical issues are pretty straightforward—catastrophic failures in exchange systems are extremely costly, both in terms of direct losses to participants and in reduced investor confidence in the markets. 
                            <E T="03">See id.</E>
                             at 15. According to this commenter, even a modest reduction in the overall risk of a meltdown is quite cost effective to the economy as a whole. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2032</SU>
                             As noted by this commenter, the $374 million loss does not include lost trading profits to investors, or loss of utility from being able to hedge risk, monetize holdings, or otherwise trade. 
                            <E T="03">See id.</E>
                             at 16.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Costs to SCI Entities</HD>
                    <P>
                        The mandatory testing of SCI entity business continuity and disaster recovery plans, including backup systems, as required under Rule 1004, will result in additional costs to SCI entities. The Commission notes that some SCI entities already offer availability for their members or participants to test business continuity and disaster recovery plans. Furthermore, as mentioned above, market participants, including SCI entities, already coordinate certain business continuity plan testing to an extent. However, Rule 1004 mandates participation in testing for some entities that do not currently participate, requires more rigorous testing than currently required, and requires greater coordination than SCI entities and market participants currently engage in. In particular, Rule 1004 requires SCI entities to designate their members or participants to participate in business continuity and disaster recovery plan testing and to coordinate such testing with other SCI entities on an industry- or sector-wide basis. The requirement of member or participant designation in business continuity and disaster recovery plan testing under Rule 1004 imposes additional costs as an SCI would have to allocate resources towards initially establishing and later updating standards for the designation of its members and participants for testing. Furthermore, the requirement to coordinate industry- or sector-wide testing will impose additional administrative costs because an SCI entity would be required to notify its members or participants and also organize, schedule, and manage the coordinated testing.
                        <SU>2033</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2033</SU>
                             Administrative costs associated with coordinating testing are included as part of the PRA burden of Rule 1004. 
                            <E T="03">See supra</E>
                             Section V.D.1.b. As discussed in Section V.D.1.b, the Commission continues to believe that plan processors will outsource the work related to compliance with Rule 1004.
                        </P>
                    </FTNT>
                    <P>
                        Some commenters stated that the scope of the proposed testing requirement would impose costs on SCI entities that the Commission did not account for, including the cost to reconfigure their systems to engage in functional and performance testing, the cost of establishing effective coordinated test scripts for the testing, and time necessary to conduct the required testing.
                        <SU>2034</SU>
                        <FTREF/>
                         Another commenter stated that testing will be costly to ATSs and their subscribers, and that the aggregate cost for all would be higher than the $66 million estimated in the SCI Proposal.
                        <SU>2035</SU>
                        <FTREF/>
                         This commenter noted that the cost includes the time, resources, and professional staff that would be devoted to the testing process, and the resulting lost business opportunities associated with the ability to focus on revenue generating projects.
                        <SU>2036</SU>
                        <FTREF/>
                         In addition, this commenter stated that, while connectivity between an ATS and its subscribers may already be established, additional configurations and build out of systems may be required to create a testing environment that simulates live market conditions.
                        <SU>2037</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2034</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.6.b (discussing comments on proposed Rule 1000(b)(9)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2035</SU>
                             
                            <E T="03">See</E>
                             ITG Letter at 15-16.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2036</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2037</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Another commenter stated that there are dozens of man-days of pre-test planning, preparation, pre-testing testing, testing, and post-mortem reviews for SCI entities associated with the industry test initiatives.
                        <SU>2038</SU>
                        <FTREF/>
                         According to this commenter, there are anywhere from tens to hundreds of business and technology staff engaged 
                        <PRTPAGE P="72430"/>
                        in this initiative.
                        <SU>2039</SU>
                        <FTREF/>
                         This commenter estimated the following staff levels required to support testing: Exchanges—175-200+ man-days; member firms—80-85 man-days; and ATSs—12-25 man-days.
                        <SU>2040</SU>
                        <FTREF/>
                         Based on the commenter's upper estimates measured in man-days, the Commission estimated monetary values by allocating hours among the traders, technologists, programmers/system administrators, exchange personnel, and analysts necessary for implementation of disaster recovery testing. This estimation yields implied annual average total cost estimates of $500,000 and $60,000 for exchanges and ATSs, respectively.
                        <SU>2041</SU>
                        <FTREF/>
                         For the reasons discussed below, the Commission believes that this commenter's cost estimate does not accurately reflect the costs to SCI entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2038</SU>
                             
                            <E T="03">See</E>
                             Tellefsen Letter at 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2039</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2040</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2041</SU>
                             The allocations are based on Commission staff experience that exchanges would divide their personnel as 85% technologists, 5% exchange rule enforcement personnel, and 10% business analysts, and ATSs are assumed to divide their personnel as 90% technologists and 10% business analysts based on staff experience. The hourly rates are from SIFMA's 
                            <E T="03">Management &amp; Professional Earnings in the Securities Industry 2012,</E>
                             modified by Commission staff to account for an 1800-hour work-year and multiplied by 5.35 to account for bonuses, firm size, employee benefits and overhead. The calculation for ATSs was as follows: 25 days × (10% time required by analysts × $245/hour + 90% time required by technologists × $282/hour) = $55,660 per ATS. For each exchange: 200 days × (85% time required by technologists × $282/hour + 10% time required by analysts × $245/hour + 5% time required by supervisors × $446/hour) = $458,400 per exchange. The Commission has rounded up because the breakdown between analysts, supervisors, and technologists may vary between ATSs and Exchanges.
                        </P>
                        <P>In the absence of a specific estimate provided by the commenter for plan processors or clearing agencies, the estimate for exchanges is assumed to apply to these types of SCI entities. Estimates for members and participants are discussed separately below.</P>
                    </FTNT>
                    <P>
                        The Commission recognizes that the factors described by commenters will contribute to costs for SCI entities associated with business continuity and disaster recovery plans testing. For example, as discussed in Section IV.B.6.b, the Commission acknowledges that systems reconfiguration for functional and performance testing and establishing an effective coordinated test script could be a complex process and result in costs. At the same time, the Commission believes that systems reconfiguration and the establishment of an effective coordinated test script is an important first step in establishing robust and effective business continuity and disaster continuity plans testing. The Commission also notes that costs of Rule 1004 are likely to be lower than those estimated by commenters because of changes made to the proposed rule. For example, although Rule 1004 would require testing of BC/DR plans that is more rigorous than some types of testing urged by some commenters, the adopted rule includes a more targeted member and participant designation provision than the proposed rule. As discussed above in Section IV.B.6.b, compared to proposed Rule 1000(b)(9), the Commission believes that the adoption of a more targeted designation requirement is likely to result in a smaller number of SCI entity members or participants being designated to participate in business continuity and disaster recovery plans testing and thus should result in lower costs for SCI entities to coordinate testing.
                        <SU>2042</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2042</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.B.6.b (discussing the designation requirement in adopted Rule 1004).
                        </P>
                    </FTNT>
                    <P>
                        The Commission is unable to provide a quantified estimate of the specific costs for SCI entities associated with the mandatory testing of SCI entity business continuity and disaster recovery plans, including backup systems. Although several commenters provided general estimates as to the costs of compliance with Rule 1004, these commenters did not provide their assumptions or a description of the quantified costs associated with each potential source of costs. Given the lack of information provided by commenters and that these costs could vary significantly based on the specific systems of each SCI entity, the Commission is unable to determine whether the costs provided by commenters are representative. Additionally, the Commission notes that commenters appeared to focus on costs as if assuming there is no testing today. Because SCI entities currently engage in some coordinated BC/DR testing, the Commission believes that the average 
                        <E T="03">incremental</E>
                         cost to SCI entities, in addition to the burden estimated in the PRA, would be lower than these commenters' cost estimates. The Commission also believes that costs would be significantly lower in the year following the initial year of testing. Because the Commission does not have detailed information regarding the current level of BC/DR testing and coordination of such testing by each SCI entity, and the cost associated with such testing and coordination, however, the Commission cannot at this time provide a quantified estimate of the cost for SCI entities to comply with Rule 1004.
                    </P>
                    <HD SOURCE="HD3">Costs to SCI Entity Members and Participants</HD>
                    <P>
                        The Commission believes that Rule 1004 will also impose costs on SCI entity designated members and participants. In the SCI Proposal, based on discussions with market participants, the Commission estimated that the cost of business continuity and disaster recovery plan testing would range from immaterial administrative costs (for SCI entity members and participants that currently maintain connections to SCI entity backup systems) to a range of $24,000 to $60,000 per year per member or participant in connection with each SCI entity.
                        <SU>2043</SU>
                        <FTREF/>
                         As noted in the SCI Proposal and also above, the Commission understood that most of the larger members or participants of SCI entities already maintain connectivity with the backup systems of SCI entities and, thus, the additional connectivity costs imposed by proposed Rule 1000(b)(9) to these larger members or participants may be minimal.
                        <SU>2044</SU>
                        <FTREF/>
                         However, among smaller members or participants of SCI entities, the number of members or participants who maintain such connectivity is lower.
                        <SU>2045</SU>
                        <FTREF/>
                         Therefore, costs at the higher end of the estimated range would accrue for members or participants who would need to invest in additional infrastructure and to maintain connectivity with an SCI entity's backup systems in order to participate in testing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2043</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18172.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2044</SU>
                             
                            <E T="03">See id.</E>
                             at 18172 and n. 642.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2045</SU>
                             
                            <E T="03">See id.</E>
                             at 18172.
                        </P>
                    </FTNT>
                    <P>
                        Furthermore, in the SCI Proposal, the Commission acknowledged that it is difficult to provide an estimate for the total aggregate cost to SCI entity members or participants under proposed Rule 1000(b)(9).
                        <SU>2046</SU>
                        <FTREF/>
                         Because each SCI entity had discretion in determining its standards for designating members or participants for the testing required by proposed Rule 1000(b)(9)(i), the Commission did not have enough information to estimate the number of members or participants at each SCI entity that would be designated as required to participate in testing and to determine whether such designated members or participants are those that already maintain connections to SCI entity backup systems. With limited information, the Commission provided a total aggregate annual cost estimate in the SCI Proposal of approximately $66 million for designated members and participants to participate in business continuity and disaster recovery plans testing.
                        <SU>2047</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2046</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2047</SU>
                             
                            <E T="03">See id.</E>
                             at 18172 and n.643.
                        </P>
                    </FTNT>
                    <P>
                        Several commenters stated that the Commission underestimated the cost of 
                        <PRTPAGE P="72431"/>
                        business continuity and disaster recovery plan testing under proposed Rule 1000(b)(9). One commenter noted that the Commission failed to take into account those SCI entities that engage in systems-specific testing upon implementation or initial connection by a market participant, but do not engage in business continuity and disaster recovery testing with the participation of market participants.
                        <SU>2048</SU>
                        <FTREF/>
                         One commenter noted that the average cost for a broker-dealer to maintain fully redundant systems at all relevant exchange backup facilities would be approximately $3 million annually, according to one of its informal surveys.
                        <SU>2049</SU>
                        <FTREF/>
                         Further, this cost would not include the initial capital costs related to the infrastructure or the labor/employment necessary for the maintenance and monitoring of backup connection and facilities.
                        <SU>2050</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2048</SU>
                             
                            <E T="03">See</E>
                             MSRB Letter at 38.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2049</SU>
                             
                            <E T="03">See</E>
                             FIA PTG Letter at 3. 
                            <E T="03">See also</E>
                             BIDS Letter at 8 (commenting that testing and backup connections are expensive, and the expense of the connections could outweigh the value or the utilization of the value that certain venues provide).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2050</SU>
                             
                            <E T="03">See</E>
                             FIA PTG Letter at 3. This commenter noted that the costs vary widely among members and exchanges but are not insubstantial. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Other commenters stated that the Commission underestimated other aspects of the cost of business continuity and disaster recovery plan testing under proposed Rule 1000(b)(9). One commenter believed that the requirement for members to connect to an SCI entity's backup site could pose significant economic burden and provide little benefit to the market.
                        <SU>2051</SU>
                        <FTREF/>
                         This commenter believed that the cost of such connections would be well over the $10,000 per connection that the Commission estimated.
                        <SU>2052</SU>
                        <FTREF/>
                         According to this commenter, establishing and maintaining a connection with comparable trading capability and latency could cost a broker-dealer that co-locates at an SCI entity's data center between $15,000 and $20,000 monthly simply for the necessary communication lines.
                        <SU>2053</SU>
                        <FTREF/>
                         In addition, this commenter noted that such members would need additional hardware (estimated to be up to $500,000) to establish an appropriate presence at the backup site to ensure that they could trade in an efficient manner with low latency.
                        <SU>2054</SU>
                        <FTREF/>
                         This commenter believed that compliance with the Rule 1000(b)(9) requirements could cause broker-dealers to reduce the number of SCI entities through which they trade.
                        <SU>2055</SU>
                        <FTREF/>
                         This commenter suggested that the standard for designating members should be those members “critical to the operation of the SCI entity.” 
                        <SU>2056</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2051</SU>
                             
                            <E T="03">See</E>
                             ISE Letter at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2052</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2053</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2054</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2055</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2056</SU>
                             
                            <E T="03">See id.</E>
                             According to this commenter, under the suggested standard, its focus would be on its seven Primary Market Makers who provide continuous liquidity, and these members would provide a baseline of liquidity for trading. 
                            <E T="03">See id.</E>
                             However, this commenter believed that, in order to satisfy the standard to provide “fair and orderly trading,” it may need to require some or all of its 145 Electronic Access Members who access liquidity. 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Another commenter estimated that the costs to a market making firm to support fully redundant exchange and ATS backup facilities would be approximately $7 million to $10 million in initial capital, with annual costs of between $5 million and $9 million.
                        <SU>2057</SU>
                        <FTREF/>
                         According to this commenter, this cost is not justified by the benefits because backup facilities would not be used in the event of an outage at the primary site,
                        <SU>2058</SU>
                        <FTREF/>
                         and would lead firms to reconsider their ability to make markets on as many trading platforms and potentially reduce price competition.
                        <SU>2059</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2057</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 4, 12. This commenter stated that the cost of supporting a backup facility of an SCI entity would be reduced, if the backup facility of an SCI entity were at the primary site of another SCI entity where the market maker traded. 
                            <E T="03">See id.</E>
                             at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2058</SU>
                             
                            <E T="03">See id.</E>
                             at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2059</SU>
                             
                            <E T="03">See id.</E>
                             at 12.
                        </P>
                    </FTNT>
                    <P>
                        The same commenter who provided an estimate of burdens for SCI entities expressed the view that there are also dozens of man-days of pre-test planning, preparation, pre-testing testing, testing, and post-mortem reviews for members and participants that would be associated with industry test initiatives.
                        <SU>2060</SU>
                        <FTREF/>
                         Based on the commenter's upper estimates for member firms, measured in man-days, the Commission assigned monetary values using appropriate hours allocation among the traders, technologists, programmers/system administrators, exchange personnel, and analysts necessary for implementation of disaster recovery testing. This procedure yields an annual average total cost estimate of about $200,000 for each member firm.
                        <SU>2061</SU>
                        <FTREF/>
                         For the reasons discussed below, the Commission believes that this commenter's cost estimate does not accurately reflect the costs to members or participants.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2060</SU>
                             
                            <E T="03">See also</E>
                              
                            <E T="03">supra</E>
                             note 2038 and accompanying text (discussing this commenter's cost estimate for SCI entities).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2061</SU>
                             The allocations are based on the staff experience that member firms divide their personnel as 45% traders, 45% technologists, and 10% business analysts. The hourly rates are from SIFMA's 
                            <E T="03">Management &amp; Professional Earnings in the Securities Industry 2012,</E>
                             modified by Commission staff to account for an 1800-hour work-year and multiplied by 5.35 to account for bonuses, firm size, employee benefits and overhead. The calculation for member firms was as follows: 85 days × (10% time required by analysts × $245/hour + 45% time required by technologists × $282/hour + 45% time required by traders × $312/hour) = $198,424 per member firm.
                        </P>
                    </FTNT>
                    <P>The Commission acknowledges that members or participants will incur costs as a result of Rule 1004. However, the Commission believes that the members or participants likely to be designated to participate in such testing are those that conduct a high level of activity with the SCI entity, or that play an important role for the SCI entity (such as market makers), and who are more likely to have already established connections to the SCI entity's backup site. The Commission believes that many of these members or participants already have established connectivity with the SCI entity's backup site and already monitor and maintain such connectivity, and thus the additional connectivity costs imposed by Rule 1004 would be modest to these members or participants.</P>
                    <P>
                        For members or participants that currently do not have connectivity, the Commission recognizes the requirements of Rule 1004 will impose costs on members or participants in establishing, maintaining, and monitoring backup connection and facilities. The Commission believes that a few commenters who stated that the Commission underestimated these costs may have based their cost estimates for proposed Rule 1000(b)(9) on the assumption that member connections to SCI entities' backup systems need to be the same as those at the primary site.
                        <SU>2062</SU>
                        <FTREF/>
                         However, as discussed above in Section IV.B.6, Rule 1004 does not require SCI entity members or participants to maintain the same level of connectivity with the backup sites of an SCI entity as they do with the primary sites. In the event of a wide-scale disruption in the securities markets, the Commission acknowledges that an SCI entity and its members or participants may not be able to provide the same level of liquidity as on a normal trading day. In addition, the Commission recognizes that the concept of “fair and orderly markets” does not require that trading on a day when business continuity and disaster recovery plans are in effect reflect the same level of liquidity, depth, volatility, and other characteristics of trading on a normal trading day.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2062</SU>
                             
                            <E T="03">See supra</E>
                             notes 2049, 2050, 2052-2054, and 2057 and accompanying text (discussing commenters' estimates of the cost to maintain fully redundant systems at relevant SCI entity backup facilities).
                        </P>
                    </FTNT>
                    <P>
                        The Commission, however, is unable to provide a quantified estimate of the 
                        <PRTPAGE P="72432"/>
                        specific costs for SCI entity members or participants associated with the mandatory testing required by Rule 1004. Although several commenters provided general estimates as to the costs of compliance with Rule 1004, these commenters did not provide their assumptions or a description of the quantified costs associated with each potential source of costs. Given the lack of information provided by commenters and that these costs could vary significantly based on the specific systems of each SCI entity and member or participant, the Commission is unable to determine whether the costs provided by commenters are representative. Additionally, the Commission notes that some commenters appeared to focus on costs as if assuming there is no testing today. Because some members and participants of SCI entities currently participate in SCI entities' BC/DR testing, these members and participants would not incur the full costs estimated by the commenters. Thus the Commission believes that the average 
                        <E T="03">incremental</E>
                         cost to members or participants would be lower than these commenter's estimates because the estimates do not account for current practices. The Commission also believes that costs will be highly variable among member firms, and will be significantly lower in the year following the initial year of testing. Because the Commission does not have detailed information regarding the current level of engagement by members or participants in BC/DR testing and the associated costs, or the details of the BC/DR testing that SCI entities will implement pursuant to Rule 1004, the Commission cannot at this time provide a precise quantified estimate of the cost for SCI entities' designated members or participants to comply with Rule 1004.
                        <SU>2063</SU>
                        <FTREF/>
                         The Commission also notes that it is critical that SCI entities and their designated members or participants be able to operate with the SCI entities' backup systems in the event of a wide-scale disruption, and believes that the costs that would be incurred by essential market participants are appropriate in light of the benefits discussed above.
                        <SU>2064</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2063</SU>
                             Although the Commission cannot at this time precisely estimate the total cost of compliance with Rule 1004, the Commission believes that $10,000 on average per SCI entity is a reasonable estimate solely for the incremental cost of connectivity associated with the requirements of Rule 1004. As noted above, the Commission continues to believe that it is reasonable to estimate that the members or participants of SCI entities that are most likely to be designated as required to participate in testing are those that conduct a high level of activity with the SCI entity, or that play an important role for the SCI entity (such as market makers), and that such members or participants are likely to already maintain connectivity with an SCI entity's backup systems. Therefore, the Commission is not persuaded that its estimate of the average connectivity cost for each member or participant of an SCI entity should be modified from $10,000.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2064</SU>
                             Further, in response to comment that the added benefit of requiring fully redundant backup systems is almost impossible to measure while the cost of implementation is significant, the Commission acknowledges that testing of a BC/DR plan does not guarantee flawless execution of that plan, but still believes testing is warranted because a tested plan is likely to be more reliable and effective than an inadequately tested plan.
                        </P>
                    </FTNT>
                    <P>
                        Although the Commission generally believes that the aggregate cost to SCI entity members or participants under Rule 1004 will be lower than the cost estimated for proposed Rule 1000(b)(9), the Commission continues to believe it is difficult to provide an estimate for the aggregate cost to SCI entity members or participants because under Rule 1004, each SCI entity has reasonable discretion in designating its members or participants for the required testing, and, as noted above, the Commission does not possess necessary information to estimate the number of designated members or participants and to determine whether such designated members or participants are those that already have established and maintained connectivity to the SCI entity's backup systems. Accordingly, the Commission cannot at this time provide a quantified estimate of the total aggregate cost to SCI entity members or participants under Rule 1004.
                        <SU>2065</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2065</SU>
                             The Commission believes that it can reasonably estimate connectivity costs but not all costs associated with BC/DR testing. With respect to connectivity, the Commission now estimates that Rule 1004 will impose a total aggregate annual cost of approximately $18 million for designated members and participants. This estimate assumes that each of the 44 SCI entities will designate between 10 and 20 percent of its members or participants to participate in the necessary testing. This 10-20 percent estimate is based on staff experience and takes into consideration comment that typically 20 percent of an SCI entity's members might provide 80 percent of the order flow or liquidity (
                            <E T="03">see</E>
                             Tellefsen Letter at 9), and balances it against another commenter's view that if the standard for designation was to identify those firms “critical to the operation of the SCI entity” (which is more targeted than the adopted standard), this commenter would designate approximately five percent of its members to participate in testing (
                            <E T="03">see</E>
                             ISE Letter at 9). The Commission understands that many SCI entities have between 200 and 400 members or participants, although some have more and some have fewer. Therefore, the Commission estimates that on average, each SCI entity will designate approximately 40 members or participants in such testing. Based on these assumptions, the Commission estimates the total aggregate cost for connectivity to all designated members or participants of all SCI entities to be approximately $17.6 million (44 SCI entities × 40 members or participants × $10,000 = $17.6 million).
                        </P>
                    </FTNT>
                    <P>Moreover, as noted above in Section IV.B.6.b, the Commission believes that adoption of a designation requirement that requires SCI entities to exercise reasonable discretion to identify those members or participants that, taken as a whole, are the “minimum necessary” for the maintenance of fair and orderly markets in the event of the activation of such plans is likely to result in a smaller number of SCI entity members or participants being designated for participation in testing as compared to the SCI Proposal, thus reducing total costs to all members or participants combined. Because the Commission believes that SCI entities have an incentive to limit the imposition of the cost and burden associated with testing to the minimum necessary to comply with the rule, it also believes that, given the option, most SCI entities would, in the exercise of reasonable discretion, prefer to designate fewer members or participants to participate in testing, than to designate more. On balance, the Commission believes that the adopted rule will incentivize SCI entities to designate those members and participants that are in fact the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of their BC/DR plans, and that this should reduce the number of designations to which any particular member or participant would be subject, compared to the SCI Proposal.</P>
                    <P>
                        It remains possible, as some commenters noted, that firms that are members of multiple SCI entities will be the subject of multiple designations, and that multiple designations could require certain firms to maintain connections to backup sites and participate in testing of the BC/DR plans of multiple SCI entities. As discussed in Section IV.B.6.b, the Commission believes this possibility, though real, may be mitigated by the fact that designations are likely to be made to firms that are already connected to one or more SCI entity backup facilities, because they are more likely to be significant members or participants of the applicable SCI entities; and that, because some SCI entity backup facilities are located in close proximity to each other, multiple connections to such backup facilities may be less costly than if SCI entity backup facilities were not so located. The Commission recognizes that there would be greater costs to a firm being designated by multiple SCI entities to participate in the testing of their business continuity and disaster recovery plans, but believes that these greater costs are warranted for such firms, as they represent significant participants in each of the SCI entities for which they are designated, and their participation in the testing of each such 
                        <PRTPAGE P="72433"/>
                        SCI entity's business continuity and disaster recovery plans is necessary to evaluate whether such plans are reliable and effective. The Commission recognizes that a firm that is designated to participate in testing with multiple SCI entities may assess the costs and burdens of participating in every test to be too great, and make business decisions to withdraw its membership or participation from one or more such SCI entities so as to avoid the costs and burdens of such testing. The Commission believes such a scenario is unlikely because such firm is likely to be a larger firm with a significant level of participation in such SCI entity and is likely to already have connections to backup facilities of the SCI entity.
                    </P>
                    <P>
                        The Commission believes that the cost associated with Rule 1004 is unlikely to induce the designated members or participants to reduce the number of SCI entities through which they trade and adversely affect price competitiveness in markets.
                        <SU>2066</SU>
                        <FTREF/>
                         As noted above, the Commission also recognizes that costs to some SCI entity members or participants associated with Rule 1004 could be significant, and also highly variable depending on the business continuity and disaster recovery plans being tested. Based on industry sources, the Commission understands that most of the larger members or participants of SCI entities already maintain connectivity with the backup systems of SCI entities. However, the Commission understands that there is a lower incidence of smaller members or participants maintaining connectivity with the backup sites of SCI entities.
                        <SU>2067</SU>
                        <FTREF/>
                         As such, the Commission believes that the compliance costs associated with Rule 1004 would be higher for those members or participants that are designated for testing by SCI entities who would need to invest in additional infrastructure to maintain connectivity with an SCI entity's backup systems to participate in testing, which the Commission believes is more likely to be the case for smaller members or participants designated for testing.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2066</SU>
                             
                            <E T="03">See supra</E>
                             notes 2055 and 2059 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2067</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18172, n. 642.
                        </P>
                    </FTNT>
                    <P>The Commission acknowledges that the compliance costs associated with Rule 1004 could raise barriers to entry and affect competition among members or participants of SCI entities. Specifically, to the extent that members or participants could be subject to designation in business continuity and disaster recovery plan testing and could incur additional compliance costs, the member or participant designation requirement of Rule 1004 could raise barriers to entry. Also, as discussed above, the compliance costs of the rule will likely be higher for smaller members or participants of SCI entities compared to larger members or participants of SCI entities. However, the Commission believes the adverse effect on competition may be mitigated to some extent as the most likely members or participants to be designated for testing are larger members or participants who already maintain connectivity with an SCI entity's backup systems. Further, the adverse effect on competition could be partially mitigated to the extent that larger firms, which are members of multiple SCI entities, could incur additional compliance costs as these larger member firms could be subject to multiple designations for business continuity and disaster recovery plan testing.</P>
                    <P>
                        One commenter noted that mere network connectivity to an exchange or ATS would be insufficient for a market maker to provide meaningful liquidity on an SCI entity.
                        <SU>2068</SU>
                        <FTREF/>
                         This commenter noted that, if the Commission does not intend for SCI entities to be able to trade in the same way from a backup facility as it trades from the primary site, then market makers could maintain a more limited remote connectivity to the backup site and incur less cost, although this commenter believed that such an approach would not facilitate the posting of competitive quotes.
                        <SU>2069</SU>
                        <FTREF/>
                         This commenter believed that this alternative approach would result in unusually wide markets, and would not result in any benefits.
                        <SU>2070</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2068</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2069</SU>
                             
                            <E T="03">See id.</E>
                             at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2070</SU>
                             
                            <E T="03">See id.</E>
                             at 13.
                        </P>
                    </FTNT>
                    <P>As discussed in Section IV.B.6, Rule 1001(a) does not require that backup facilities of SCI entities fully duplicate the features of primary facilities. Further as discussed in Section IV.B.6, SCI entity members or participants are not required by Regulation SCI to maintain the same level of connectivity with the backup sites of an SCI entity as they do with the primary sites. In the event of a wide-scale disruption in the securities markets, the Commission acknowledges that SCI entities and their members or participants may not be able to provide the same level of liquidity as on a normal trading day. However, the Commission expects that, on a day when business continuity and disaster recovery plans are in effect due to a wide-scale disruption in the securities markets, the requirements of Rule 1004 will help ensure adequate levels of liquidity and pricing efficiency to facilitate trading and maintain fair and orderly markets without imposing excessive costs on SCI entities and market participants by requiring them to maintain the same connectivity with the backup systems as with the primary sites.</P>
                    <HD SOURCE="HD3">Alternatives</HD>
                    <P>
                        Several commenters suggested alternatives to the proposed BC/DR testing requirements.
                        <SU>2071</SU>
                        <FTREF/>
                         Two commenters suggested that few ATSs are critical enough to warrant inclusion in the BC/DR testing requirement.
                        <SU>2072</SU>
                        <FTREF/>
                         One commenter suggested that only SCI entities that provide market functions on which other market participants depend be subject to the requirements for separate backup and recovery capabilities.
                        <SU>2073</SU>
                        <FTREF/>
                         Furthermore, one commenter urged that BC/DR testing coordination only be required among providers of singular services in the market (
                        <E T="03">i.e.,</E>
                         exchange that lists securities, exclusive processors under NMS plans, and clearing and settlement agencies).
                        <SU>2074</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2071</SU>
                             
                            <E T="03">See</E>
                             SIFMA Letter at 17; BIDS Letter at 8; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2072</SU>
                             
                            <E T="03">See</E>
                             BIDS Letter at 8; and ITG Letter at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2073</SU>
                             
                            <E T="03">See</E>
                             KCG Letter at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2074</SU>
                             
                            <E T="03">See</E>
                             Direct Edge Letter at 9.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is not persuaded that SCI ATSs should be excluded from the requirements of BC/DR testing plans. In today's market, as discussed in Section IV.A.1.b, ATSs collectively represent a significant source of liquidity for stock trading. Although the concept of “fair and orderly markets” when BC/DR plans are in effect does not require the same level of liquidity, depth, volatility, and other characteristics of trading on a normal trading day, the Commission believes that excluding significant ATSs from BC/DR testing could harm liquidity, depth, and volatility when BC/DR plans are in effect and, thus, could significantly reduce the benefits of Rule 1004. Furthermore, with respect to the commenter that urged the Commission only to include providers of singular services in BC/DR testing coordination, as mentioned in Section IV.A.1.b, because trading in the U.S. securities markets today is dispersed among exchanges, ATSs, and other trading venues, and often involves trading strategies that require access to multiple trading venues, including ATSs, simultaneously, including all SCI entities, the Commission believes that requiring SCI entities to coordinate testing would result in testing under 
                        <PRTPAGE P="72434"/>
                        more realistic market conditions and help ensure that securities markets have improved backup infrastructure, fewer market shutdowns, and fair and orderly markets in the event of the activation of BC/DR plans.
                    </P>
                    <P>
                        Furthermore, one commenter stated that coordinated BC/DR testing is a good aspirational goal, but expressed concern that too much is outside of the control of an individual SCI entity, and therefore the rule should, at most, require SCI entities to attempt to coordinate such testing.
                        <SU>2075</SU>
                        <FTREF/>
                         With respect to the comment suggesting that BC/DR testing coordination should be an aspirational goal rather than a requirement, the Commission believes that voluntary BC/DR testing is insufficient and will not further the goal of Regulation SCI as evidenced by Superstorm Sandy discussed in Section IV.B.6. As discussed above, the Commission acknowledges that there could be potential difficulties, including communicating with other SCI entities, in coordinating BC/DR testing on an industry- or sector-wide basis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2075</SU>
                             
                            <E T="03">See</E>
                             CME Letter at 13.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Recordkeeping and Electronic Filing—Rules 1005-1007</HD>
                    <P>
                        Entities that participate in the ARP Inspection Program currently keep records related to the ARP Inspection Program. However, the recordkeeping requirements of Rules 1005-1007 would apply to more entities, systems, and types of systems issues than the ARP Inspection Program. In addition, SCI entities are already subject to certain Commission recordkeeping requirements.
                        <SU>2076</SU>
                        <FTREF/>
                         However, records relating to Regulation SCI may not be specifically addressed in the recordkeeping requirements of certain rules.
                        <SU>2077</SU>
                        <FTREF/>
                         The Commission believes that the recordkeeping requirements specifically related to Regulation SCI would enhance the ability of the Commission to evaluate SCI entities' compliance with Regulation SCI.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2076</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 240.17a-1, applicable to SCI SROs; 17 CFR 240.17a-3 and 17a-4, applicable to broker-dealers; and 17 CFR 242.301-303, applicable to ATSs.
                        </P>
                        <P> It has been the experience of the Commission that SCI entities presently subject to the ARP Inspection Program (nearly all of whom are SCI SROs that are also subject to the recordkeeping requirements of Rule 17a-1(a)) do generally keep and preserve the types of records that would be subject to the requirements of Rule 1005. Nevertheless, the Commission continues to believe that Regulation SCI's codification of these preservation practices will support an accurate, timely, and efficient inspection and examination process and help ensure that all types of SCI entities keep and preserve such records.</P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2077</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18128.
                        </P>
                    </FTNT>
                    <P>
                        With respect to SCI SROs in particular, the Commission notes that they are subject to the recordkeeping requirements of Rule 17a-1 under the Exchange Act, and the breadth of Rule 17a-1 is such that it would require SCI SROs to make, keep, and preserve records relating to their compliance with Regulation SCI. Therefore, Rule 1005(a) requires each SCI SRO to make, keep, and preserve all documents relating to its compliance with Regulation SCI as prescribed in Rule 17a-1 under the Exchange Act.
                        <SU>2078</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2078</SU>
                             
                            <E T="03">See supra</E>
                             Section IV.C.1.a (discussing recordkeeping requirements for SROs under Rule 17a-1).
                        </P>
                    </FTNT>
                    <P>Rule 1005(b) requires each SCI entity that is not an SCI SRO to make, keep, and preserve at least one copy of all documents relating to its compliance with Regulation SCI. Each such SCI entity is required to keep all such documents for a period of not less than five years, the first two years in a place that is readily accessible to the Commission or its representatives for inspection and examination. Each such SCI entity is also required to promptly furnish copies of such documents to Commission representatives upon request. Rule 1005(c) requires each such SCI entity, upon or immediately prior to ceasing to do business or ceasing to be registered under the Exchange Act, to take all necessary action to ensure that the records required to be made, kept, and preserved by Rule 1005 shall be accessible to the Commission and its representatives in the manner required by Rule 1005 and for the remainder of the period required by Rule 1005.</P>
                    <P>According to Rule 1007, if the records required to be filed or kept by an SCI entity under Regulation SCI are prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity is required to ensure that such records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service to that effect.</P>
                    <P>
                        For SCI entities other than SCI SROs, Rule 1005 specifically addresses recordkeeping requirements with respect to records relating to Regulation SCI compliance. The Commission believes that Rules 1005 and 1007 would allow Commission staff to perform efficient inspections and examinations of SCI entities for their compliance with Regulation SCI, and would increase the likelihood that Commission staff can identify conduct inconsistent with Regulation SCI at earlier stages in the inspection and examination process. Furthermore, as discussed in Section IV.C.1.a, although many SCI events may be resolved in a short time frame, there may be other SCI events that may not be discovered for an extended period of time after their occurrences, or may take significant periods of time to fully resolve. In such cases, having an SCI entity's records available for a longer period of time or even after it has ceased to do business or be registered under the Exchange Act would be beneficial. Preserved information should provide the Commission with an additional source to help determine the causes and consequences of one or more SCI events and better understand how such events may have impacted trade execution, price discovery, liquidity, and investor participation. Consequently, the Commission believes that the requirements of Rules 1005 and 1007 would help ensure compliance with Regulation SCI and help realize the potential benefits (
                        <E T="03">e.g.,</E>
                         better pricing efficiency, price discovery, and liquidity flows) of the regulation.
                    </P>
                    <P>
                        As noted above, the breadth of Rule 17a-1 under the Exchange Act is such that it would require SCI SROs to make, keep, and preserve records relating to their compliance with Regulation SCI. Therefore, for SCI SROs, the incremental compliance costs associated with Rules 1005 and 1007 will be modest.
                        <SU>2079</SU>
                        <FTREF/>
                         On the other hand, for SCI entities that are not SCI SROs, the recordkeeping requirements of Rules 1005 and 1007 will impose additional costs, including one-time cost to set up or modify an existing recordkeeping system to comply with Rules 1005 and 1007. The initial and ongoing compliance costs associated with the recordkeeping requirements are attributed to paperwork burdens, which are discussed in Section V.D.4 above.
                        <SU>2080</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2079</SU>
                             As noted above, it has been the experience of the Commission that SCI entities presently subject to the ARP Inspection Program generally keep and preserve the types of records that would be subject to the requirements of Rule 1005. Nearly all of these ARP participants are SCI SROs that are also subject to the recordkeeping requirements of Rule 17a-1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2080</SU>
                             When monetized, the paperwork burden associated with all recordkeeping requirements would result in approximately $857,000 initially for all non-SRO SCI entities in the aggregate, and $27,000 annually for all non-SRO SCI entities in the aggregate.
                        </P>
                    </FTNT>
                    <P>
                        Rule 1006 requires SCI entities to electronically file all written information to the Commission on Form SCI (except for notifications submitted pursuant to Rules 1002(b)(1) and (b)(3)). 
                        <PRTPAGE P="72435"/>
                        Rule 1006 should provide a uniform manner in which the Commission would receive—and SCI entities would provide—written notifications, reviews, descriptions, analyses, or reports required by Regulation SCI.
                        <SU>2081</SU>
                        <FTREF/>
                         Rule 1006 should add efficiency for SCI entities in drafting and submitting the required reports, and for the Commission in reviewing, analyzing, and responding to the information provided.
                        <SU>2082</SU>
                        <FTREF/>
                         All costs associated with Form SCI are attributed to paperwork burdens discussed in Section V.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2081</SU>
                             
                            <E T="03">See</E>
                             Proposing Release, 
                            <E T="03">supra</E>
                             note 13, at 18129-30.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2082</SU>
                             
                            <E T="03">See id.</E>
                             at 18130.
                        </P>
                    </FTNT>
                    <P>
                        Every SCI entity will be required to have the ability to electronically submit Form SCI through the EFFS system, and every person designated to sign Form SCI will be required to have an electronic signature and a digital ID. Each SCI entity will also be required to submit documents attached as exhibits through the EFFS system in a text-searchable format, subject to a limited exception.
                        <SU>2083</SU>
                        <FTREF/>
                         The Commission believes that requiring documents to be submitted in a text-searchable format, subject to a limited exception, is necessary to allow Commission staff to efficiently review and analyze information provided by SCI entities. Additionally, the Commission believes that this requirement will not impose an additional burden on SCI entities, as SCI entities likely already prepare documents in an electronic format that is text searchable or can readily be converted into a format that is text searchable. The Commission also believes that many SCI entities currently have the ability to access the EFFS system and electronically submit Form SCI such that the requirement to submit Form SCI electronically will not impose significant new implementation or ongoing costs.
                        <SU>2084</SU>
                        <FTREF/>
                         The Commission also believes that some of the persons who will be designated to sign Form SCI already have digital IDs and the ability to provide an electronic signature. To the extent that some persons do not have digital IDs, the additional cost to obtain and maintain digital IDs is accounted for in the paperwork burden.
                        <SU>2085</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2083</SU>
                             As noted in Section IV.C.2, the General Instructions to Form SCI, Item A. specify that documents filed through the EFFS system must be in a text-searchable format without the use of optical character recognition, with a limited exception to allow for a portion of a Form SCI submission (
                            <E T="03">e.g.,</E>
                             an image or diagram) that cannot be made available in a text-searchable format to be submitted in a non-text-searchable format.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2084</SU>
                             The initial and ongoing costs associated with various electronic submissions of Form SCI are discussed in the Paperwork Reduction Act section above. 
                            <E T="03">See supra</E>
                             Section V.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2085</SU>
                             
                            <E T="03">See supra</E>
                             Section V.D.2.e.
                        </P>
                    </FTNT>
                    <P>As an alternative to the adopted electronic submission requirement, the Commission considered requiring data to be submitted in a tagged data format such as XBRL. Requiring reports to be filed in a tagged data format such as XBRL would likely permit faster and more efficient analysis of information disclosed in reports but would also likely impose additional compliance costs associated with tagging information in the narrative responses.</P>
                    <P>
                        Rather than requiring the use of XBRL formatting for Form SCI, the Commission notes that certain fields in Sections I-III of Form SCI will require information provided by SCI entities to be in a format that will allow the Commission to gather information in a structured manner (
                        <E T="03">e.g.,</E>
                         the submission type and SCI event type in Section I). By collecting information on Form SCI in a way that allows the Commission to gather key information in a structured manner, the Commission believes it will be able to more efficiently review and process filings made on Form SCI. Moreover, gathering certain information in Sections I-III of Form SCI in a structured format should not result in an additional cost to SCI entities.
                    </P>
                    <HD SOURCE="HD1">VII. Regulatory Flexibility Act Certification</HD>
                    <P>
                        The Regulatory Flexibility Act (“RFA”) 
                        <SU>2086</SU>
                        <FTREF/>
                         requires Federal agencies, in promulgating rules, to consider the impact of those rules on small entities. The Commission certified in the SCI Proposal, pursuant to Section 605(b) of the Regulatory Flexibility Act of 1980 (“RFA”),
                        <SU>2087</SU>
                        <FTREF/>
                         that proposed Regulation SCI would not, if adopted, have a significant impact on a substantial number of small entities. The Commission received no comments on this certification.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2086</SU>
                             5 U.S.C. 601 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2087</SU>
                             5 U.S.C. 605(b).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. SCI Entities</HD>
                    <P>
                        Paragraph (a) of Rule 0-10 provides that for purposes of the RFA, a small entity when used with reference to a “person” other than an investment company means a person that, on the last day of its most recent fiscal year, had total assets of $5 million or less.
                        <SU>2088</SU>
                        <FTREF/>
                         With regard to broker-dealers, small entity means a broker or dealer that had total capital of less than $500,000 on the date in the prior fiscal year as of which its audited financial statements were prepared pursuant to Rule 17a-5(d) under the Exchange Act, or, if not required to file such statements, had total capital of less than $500,000 on the last business day of the preceding fiscal year (or in the time that it has been in business, if shorter), and that is not affiliated with any person (other than a natural person) that is not a small business or small organization.
                        <SU>2089</SU>
                        <FTREF/>
                         With regard to clearing agencies, small entity means a clearing agency that compared, cleared, and settled less than $500 million in securities transactions during the preceding fiscal year (or in the time that it has been in business, if shorter), had less than $200 million of funds and securities in its custody or control at all times during the preceding fiscal year (or in the time that it has been in business, if shorter), and is not affiliated with any person (other than a natural person) that is not a small business or small organization.
                        <SU>2090</SU>
                        <FTREF/>
                         With regard to exchanges, small entity means an exchange that has been exempt from the reporting requirements of Rule 601 under Regulation NMS, and is not affiliated with any person (other than a natural person) that is not a small business or small organization.
                        <SU>2091</SU>
                        <FTREF/>
                         With regard to securities information processors, small entity means a securities information processor that had gross revenue of less than $10 million during the preceding fiscal year (or in the time it has been in business, if shorter), provided service to fewer than 100 interrogation devices or moving tickers at all times during the preceding fiscal year (or in the time it has been in business, if shorter), and is not affiliated with any person (that is not a natural person) that is not a small business or small organization.
                        <SU>2092</SU>
                        <FTREF/>
                         Under the standards adopted by the Small Business Administration (“SBA”), entities engaged in financial investments and related activities are considered small entities if they have $35.5 million or less in average annual receipts.
                        <SU>2093</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2088</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.0-10(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2089</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.0-10(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2090</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.0-10(d).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2091</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.0-10(e).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2092</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.0-10(g).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2093</SU>
                             
                            <E T="03">See</E>
                             SBA's Table of Small Business Size Standards, Subsector 523 and 13 CFR 121.201. Such entities include firms engaged in investment banking and securities dealing, securities brokerage, commodity contracts dealing, commodity contracts brokerage, securities and commodity exchanges, miscellaneous intermediation, portfolio management, investment advice, trust, fiduciary and custody activities, and miscellaneous financial investment activities.
                        </P>
                    </FTNT>
                    <P>
                        Based on the Commission's existing information about the entities that will be subject to Regulation SCI, the Commission believes that SCI entities that are self-regulatory organizations 
                        <PRTPAGE P="72436"/>
                        (national securities exchanges, national securities associations, registered clearing agencies, and the MSRB) or exempt clearing agencies subject to ARP would not fall within the Commission's definition of small entity as described above. With regard to plan processors, which are defined under Rule 600(b)(55) of Regulation NMS to mean a self-regulatory organization or securities information processor acting as an exclusive processor in connection with the development, implementation and/or operation of any facility contemplated by an effective NMS plan,
                        <SU>2094</SU>
                        <FTREF/>
                         the Commission's definition of small entity as it relates to self-regulatory organizations and securities information processors would apply. The Commission does not believe that any plan processor would be a small entity as defined above. With regard to SCI ATSs, because they are registered as broker-dealers, the Commission's definition of small entity as it relates to broker-dealers would apply. The Commission does not believe that any of the SCI ATSs would be a small entity as defined above.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2094</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.600(b)(55).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Certification</HD>
                    <P>For the foregoing reasons, the Commission again certifies that Regulation SCI will not have a significant economic impact on a substantial number of small entities.</P>
                    <HD SOURCE="HD1">VIII. Statutory Authority and Text of Amendments</HD>
                    <P>
                        Pursuant to the Exchange Act, 15 U.S.C. 78a 
                        <E T="03">et seq.,</E>
                         and particularly, Sections 2, 3, 5, 6, 11A, 15, 15A, 17, 17A, 23(a), and 24 thereof, 15 U.S.C. 78b, 78c, 78e, 78f, 78k-1, 78
                        <E T="03">o,</E>
                         78
                        <E T="03">o</E>
                        -3, 78q, 78q-1, 78x, and 78w(a), the Commission adopts Regulation SCI under the Exchange Act and Form SCI under the Exchange Act, and amends Regulation ATS and Rule 24b-2 under the Exchange Act.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 17 CFR Parts 240, 242, and 249</HD>
                        <P>Brokers; Confidential business information; Reporting and recordkeeping requirements; and Securities.</P>
                    </LSTSUB>
                    <P>In accordance with the foregoing, Title 17, Chapter II of the Code of Federal Regulations is amended as follows:</P>
                    <REGTEXT TITLE="17" PART="240">
                        <PART>
                            <HD SOURCE="HED">PART 240—GENERAL RULES AND REGULATIONS, SECURITIES EXCHANGE ACT OF 1934</HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 240 continues to read in part as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 15 U.S.C. 77c, 77d, 77g, 77j, 77s, 77z-2, 77z-3, 77eee, 77ggg, 77nnn, 77sss, 77ttt, 78c, 78c-3, 78c-5, 78d, 78e, 78f, 78g, 78i, 78j, 78j-1, 78k, 78k-1, 78
                                <E T="03">l,</E>
                                 78m, 78n, 78n-1, 78
                                <E T="03">o,</E>
                                 78
                                <E T="03">o</E>
                                -4, 78
                                <E T="03">o</E>
                                -10, 78p, 78q, 78q-1, 78s, 78u-5, 78w, 78x, 78
                                <E T="03">ll,</E>
                                 78mm, 80a-20, 80a-23, 80a-29, 80a-37, 80b-3, 80b-4, 80b-11, 7201 
                                <E T="03">et seq.,</E>
                                 and 8302; 7 U.S.C. 2(c)(2)(E); 12 U.S.C. 5221(e)(3); 18 U.S.C. 1350, unless otherwise noted.
                            </P>
                        </AUTH>
                        <STARS/>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="240">
                        <AMDPAR>2. Amend § 240.24b-2 by:</AMDPAR>
                        <AMDPAR>a. After the words PRELIMINARY NOTE: Adding the words “Except as otherwise provided in this rule,” and revising the word “Confidential” to read “confidential”.</AMDPAR>
                        <AMDPAR>b. Adding at the beginning of paragraph (b) introductory text the words “Except as otherwise provided in paragraph (g) of this section,” and revising the word “The” to read “the”.</AMDPAR>
                        <AMDPAR>c. Adding paragraph (g).</AMDPAR>
                        <P>The addition reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 240.24b-2. </SECTNO>
                            <SUBJECT>Nondisclosure of information filed with the Commission and with any exchange.</SUBJECT>
                            <STARS/>
                            <P>
                                (g) An SCI entity (as defined in § 242.1000 of this chapter) shall not omit the confidential portion from the material filed in electronic format on Form SCI pursuant to Regulation SCI, § 242.1000 
                                <E T="03">et. seq.,</E>
                                 and, in lieu of the procedures described in paragraph (b) of this section, may request confidential treatment of all information provided on Form SCI by completing Section IV of Form SCI.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="242">
                        <PART>
                            <HD SOURCE="HED">PART 242—REGULATIONS M, SHO, ATS, AC, NMS AND SCI AND CUSTOMER MARGIN REQUIREMENTS FOR SECURITY FUTURES</HD>
                        </PART>
                        <AMDPAR>3. The authority citation for part 242 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 15 U.S.C. 77g, 77q(a), 77s(a), 78b, 78c, 78g(c)(2), 78i(a), 78j, 78k-1(c), 78
                                <E T="03">l,</E>
                                 78m, 78n, 78
                                <E T="03">o</E>
                                (b), 78
                                <E T="03">o</E>
                                (c), 78
                                <E T="03">o</E>
                                (g), 78q(a), 78q(b), 78q(h), 78w(a), 78dd-1, 78mm, 80a23, 80a-29, and 80a-37.
                            </P>
                        </AUTH>
                        <STARS/>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="242">
                        <AMDPAR>4. The heading of part 242 is revised to read as set forth above.</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 242.301 </SECTNO>
                            <SUBJECT>[Amended]</SUBJECT>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="242">
                        <AMDPAR>5. Amend § 242.301 by removing paragraphs (b)(6)(i)(A) and (B) and redesignating paragraphs (b)(6)(i)(C) and (D) as paragraphs (b)(6)(i)(A) and (B), respectively.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="242">
                        <AMDPAR>6. Add §§ 242.1000 through 242.1007 to read as follows:</AMDPAR>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SUBPART>
                                <HD SOURCE="HED">Regulation SCI—Systems Compliance and Integrity</HD>
                                <SECTNO>242.1000 </SECTNO>
                                <SUBJECT>Definitions.</SUBJECT>
                                <SECTNO>242.1001 </SECTNO>
                                <SUBJECT>Obligations related to policies and procedures of SCI entities.</SUBJECT>
                                <SECTNO>242.1002 </SECTNO>
                                <SUBJECT>Obligations related to SCI events.</SUBJECT>
                                <SECTNO>242.1003 </SECTNO>
                                <SUBJECT>Obligations related to systems changes; SCI review.</SUBJECT>
                                <SECTNO>242.1004 </SECTNO>
                                <SUBJECT>SCI entity business continuity and disaster recovery plans testing requirements for members or participants.</SUBJECT>
                                <SECTNO>242.1005 </SECTNO>
                                <SUBJECT>Recordkeeping requirements related to compliance with Regulation SCI.</SUBJECT>
                                <SECTNO>242.1006 </SECTNO>
                                <SUBJECT>Electronic filing and submission.</SUBJECT>
                                <SECTNO>242.1007 </SECTNO>
                                <SUBJECT>Requirements for service bureaus.</SUBJECT>
                            </SUBPART>
                        </CONTENTS>
                        <SECTION>
                            <SECTNO>§ 242.1000 </SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <P>For purposes of Regulation SCI (§§ 242.1000 through 242.1007), the following definitions shall apply:</P>
                            <P>
                                <E T="03">Critical SCI systems</E>
                                 means any SCI systems of, or operated by or on behalf of, an SCI entity that:
                            </P>
                            <P>(1) Directly support functionality relating to:</P>
                            <P>(i) Clearance and settlement systems of clearing agencies;</P>
                            <P>(ii) Openings, reopenings, and closings on the primary listing market;</P>
                            <P>(iii) Trading halts;</P>
                            <P>(iv) Initial public offerings;</P>
                            <P>(v) The provision of consolidated market data; or</P>
                            <P>(vi) Exclusively-listed securities; or</P>
                            <P>(2) Provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets.</P>
                            <P>
                                <E T="03">Electronic signature</E>
                                 has the meaning set forth in § 240.19b-4(j) of this chapter.
                            </P>
                            <P>
                                <E T="03">Exempt clearing agency subject to ARP</E>
                                 means an entity that has received from the Commission an exemption from registration as a clearing agency under Section 17A of the Act, and whose exemption contains conditions that relate to the Commission's Automation Review Policies (ARP), or any Commission regulation that supersedes or replaces such policies.
                            </P>
                            <P>
                                <E T="03">Indirect SCI systems</E>
                                 means any systems of, or operated by or on behalf of, an SCI entity that, if breached, would be reasonably likely to pose a security threat to SCI systems.
                            </P>
                            <P>
                                <E T="03">Major SCI event</E>
                                 means an SCI event that has had, or the SCI entity reasonably estimates would have:
                            </P>
                            <P>
                                (1) Any impact on a critical SCI system; or
                                <PRTPAGE P="72437"/>
                            </P>
                            <P>(2) A significant impact on the SCI entity's operations or on market participants.</P>
                            <P>
                                <E T="03">Plan processor</E>
                                 has the meaning set forth in § 242.600(b)(55).
                            </P>
                            <P>
                                <E T="03">Responsible SCI personnel</E>
                                 means, for a particular SCI system or indirect SCI system impacted by an SCI event, such senior manager(s) of the SCI entity having responsibility for such system, and their designee(s).
                            </P>
                            <P>
                                <E T="03">SCI alternative trading system</E>
                                 or 
                                <E T="03">SCI ATS</E>
                                 means an alternative trading system, as defined in § 242.300(a), which during at least four of the preceding six calendar months:
                            </P>
                            <P>(1) Had with respect to NMS stocks:</P>
                            <P>(i) Five percent (5%) or more in any single NMS stock, and one-quarter percent (0.25%) or more in all NMS stocks, of the average daily dollar volume reported by applicable transaction reporting plans; or</P>
                            <P>(ii) One percent (1%) or more in all NMS stocks of the average daily dollar volume reported by applicable transaction reporting plans; or</P>
                            <P>(2) Had with respect to equity securities that are not NMS stocks and for which transactions are reported to a self-regulatory organization, five percent (5%) or more of the average daily dollar volume as calculated by the self-regulatory organization to which such transactions are reported;</P>
                            <P>(3) Provided, however, that such SCI ATS shall not be required to comply with the requirements of Regulation SCI until six months after satisfying any of paragraphs (a) or (b) of this section, as applicable, for the first time.</P>
                            <P>
                                <E T="03">SCI entity</E>
                                 means an SCI self-regulatory organization, SCI alternative trading system, plan processor, or exempt clearing agency subject to ARP.
                            </P>
                            <P>
                                <E T="03">SCI event</E>
                                 means an event at an SCI entity that constitutes:
                            </P>
                            <P>(1) A systems disruption;</P>
                            <P>(2) A systems compliance issue; or</P>
                            <P>(3) A systems intrusion.</P>
                            <P>
                                <E T="03">SCI review</E>
                                 means a review, following established procedures and standards, that is performed by objective personnel having appropriate experience to conduct reviews of SCI systems and indirect SCI systems, and which review contains:
                            </P>
                            <P>(1) A risk assessment with respect to such systems of an SCI entity; and</P>
                            <P>(2) An assessment of internal control design and effectiveness of its SCI systems and indirect SCI systems to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards.</P>
                            <P>
                                <E T="03">SCI self-regulatory organization</E>
                                 or 
                                <E T="03">SCI SRO</E>
                                 means any national securities exchange, registered securities association, or registered clearing agency, or the Municipal Securities Rulemaking Board; 
                                <E T="03">provided however,</E>
                                 that for purposes of this section, the term SCI self-regulatory organization shall not include an exchange that is notice registered with the Commission pursuant to 15 U.S.C. 78f(g) or a limited purpose national securities association registered with the Commission pursuant to 15 U.S.C. 78
                                <E T="03">o</E>
                                -3(k).
                            </P>
                            <P>
                                <E T="03">SCI systems</E>
                                 means all computer, network, electronic, technical, automated, or similar systems of, or operated by or on behalf of, an SCI entity that, with respect to securities, directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance.
                            </P>
                            <P>
                                <E T="03">Senior management</E>
                                 means, for purposes of Rule 1003(b), an SCI entity's Chief Executive Officer, Chief Technology Officer, Chief Information Officer, General Counsel, and Chief Compliance Officer, or the equivalent of such employees or officers of an SCI entity.
                            </P>
                            <P>
                                <E T="03">Systems compliance issue</E>
                                 means an event at an SCI entity that has caused any SCI system of such entity to operate in a manner that does not comply with the Act and the rules and regulations thereunder or the entity's rules or governing documents, as applicable.
                            </P>
                            <P>
                                <E T="03">Systems disruption</E>
                                 means an event in an SCI entity's SCI systems that disrupts, or significantly degrades, the normal operation of an SCI system.
                            </P>
                            <P>
                                <E T="03">Systems intrusion</E>
                                 means any unauthorized entry into the SCI systems or indirect SCI systems of an SCI entity.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1001 </SECTNO>
                            <SUBJECT>Obligations related to policies and procedures of SCI entities.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Capacity, integrity, resiliency, availability, and security.</E>
                                 (1) Each SCI entity shall establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems and, for purposes of security standards, indirect SCI systems, have levels of capacity, integrity, resiliency, availability, and security, adequate to maintain the SCI entity's operational capability and promote the maintenance of fair and orderly markets.
                            </P>
                            <P>(2) Policies and procedures required by paragraph (a)(1) of this section shall include, at a minimum:</P>
                            <P>(i) The establishment of reasonable current and future technological infrastructure capacity planning estimates;</P>
                            <P>(ii) Periodic capacity stress tests of such systems to determine their ability to process transactions in an accurate, timely, and efficient manner;</P>
                            <P>(iii) A program to review and keep current systems development and testing methodology for such systems;</P>
                            <P>(iv) Regular reviews and testing, as applicable, of such systems, including backup systems, to identify vulnerabilities pertaining to internal and external threats, physical hazards, and natural or manmade disasters;</P>
                            <P>(v) Business continuity and disaster recovery plans that include maintaining backup and recovery capabilities sufficiently resilient and geographically diverse and that are reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption;</P>
                            <P>(vi) Standards that result in such systems being designed, developed, tested, maintained, operated, and surveilled in a manner that facilitates the successful collection, processing, and dissemination of market data; and</P>
                            <P>(vii) Monitoring of such systems to identify potential SCI events.</P>
                            <P>(3) Each SCI entity shall periodically review the effectiveness of the policies and procedures required by this paragraph (a), and take prompt action to remedy deficiencies in such policies and procedures.</P>
                            <P>(4) For purposes of this paragraph (a), such policies and procedures shall be deemed to be reasonably designed if they are consistent with current SCI industry standards, which shall be comprised of information technology practices that are widely available to information technology professionals in the financial sector and issued by an authoritative body that is a U.S. governmental entity or agency, association of U.S. governmental entities or agencies, or widely recognized organization. Compliance with such current SCI industry standards, however, shall not be the exclusive means to comply with the requirements of this paragraph (a).</P>
                            <P>
                                (b) 
                                <E T="03">Systems compliance.</E>
                                 (1) Each SCI entity shall establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its SCI systems operate in a manner that complies with the Act and the rules and regulations thereunder and the entity's rules and governing documents, as applicable.
                            </P>
                            <P>(2) Policies and procedures required by paragraph (b)(1) of this section shall include, at a minimum:</P>
                            <P>(i) Testing of all SCI systems and any changes to SCI systems prior to implementation;</P>
                            <P>(ii) A system of internal controls over changes to SCI systems;</P>
                            <P>
                                (iii) A plan for assessments of the functionality of SCI systems designed to 
                                <PRTPAGE P="72438"/>
                                detect systems compliance issues, including by responsible SCI personnel and by personnel familiar with applicable provisions of the Act and the rules and regulations thereunder and the SCI entity's rules and governing documents; and
                            </P>
                            <P>(iv) A plan of coordination and communication between regulatory and other personnel of the SCI entity, including by responsible SCI personnel, regarding SCI systems design, changes, testing, and controls designed to detect and prevent systems compliance issues.</P>
                            <P>(3) Each SCI entity shall periodically review the effectiveness of the policies and procedures required by this paragraph (b), and take prompt action to remedy deficiencies in such policies and procedures.</P>
                            <P>(4) Safe harbor from liability for individuals. Personnel of an SCI entity shall be deemed not to have aided, abetted, counseled, commanded, caused, induced, or procured the violation by an SCI entity of this paragraph (b) if the person:</P>
                            <P>(i) Has reasonably discharged the duties and obligations incumbent upon such person by the SCI entity's policies and procedures; and</P>
                            <P>(ii) Was without reasonable cause to believe that the policies and procedures relating to an SCI system for which such person was responsible, or had supervisory responsibility, were not established, maintained, or enforced in accordance with this paragraph (b) in any material respect.</P>
                            <P>
                                (c) 
                                <E T="03">Responsible SCI personnel.</E>
                                 (1) Each SCI entity shall establish, maintain, and enforce reasonably designed written policies and procedures that include the criteria for identifying responsible SCI personnel, the designation and documentation of responsible SCI personnel, and escalation procedures to quickly inform responsible SCI personnel of potential SCI events.
                            </P>
                            <P>(2) Each SCI entity shall periodically review the effectiveness of the policies and procedures required by paragraph (c)(1) of this section, and take prompt action to remedy deficiencies in such policies and procedures.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1002 </SECTNO>
                            <SUBJECT>Obligations related to SCI events.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Corrective action.</E>
                                 Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, each SCI entity shall begin to take appropriate corrective action which shall include, at a minimum, mitigating potential harm to investors and market integrity resulting from the SCI event and devoting adequate resources to remedy the SCI event as soon as reasonably practicable.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Commission notification and recordkeeping of SCI events.</E>
                                 Each SCI entity shall:
                            </P>
                            <P>(1) Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, notify the Commission of such SCI event immediately;</P>
                            <P>(2) Within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that the SCI event has occurred, submit a written notification pertaining to such SCI event to the Commission, which shall be made on a good faith, best efforts basis and include:</P>
                            <P>(i) A description of the SCI event, including the system(s) affected; and</P>
                            <P>(ii) To the extent available as of the time of the notification: The SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event;</P>
                            <P>(3) Until such time as the SCI event is resolved and the SCI entity's investigation of the SCI event is closed, provide updates pertaining to such SCI event to the Commission on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, to correct any materially incorrect information previously provided, or when new material information is discovered, including but not limited to, any of the information listed in paragraph (b)(2)(ii) of this section;</P>
                            <P>(4)(i)(A) If an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 calendar days of the occurrence of the SCI event, then within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event, submit a final written notification pertaining to such SCI event to the Commission containing the information required in paragraph (b)(4)(ii) of this section.</P>
                            <P>
                                (B)(
                                <E T="03">1</E>
                                ) If an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 calendar days of the occurrence of the SCI event, then submit an interim written notification pertaining to such SCI event to the Commission within 30 calendar days after the occurrence of the SCI event containing the information required in paragraph (b)(4)(ii) of this section, to the extent known at the time.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Within five business days after the resolution of such SCI event and closure of the investigation regarding such SCI event, submit a final written notification pertaining to such SCI event to the Commission containing the information required in paragraph (b)(4)(ii) of this section.
                            </P>
                            <P>(ii) Written notifications required by paragraph (b)(4)(i) of this section shall include:</P>
                            <P>(A) A detailed description of: The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event;</P>
                            <P>(B) A copy of any information disseminated pursuant to paragraph (c) of this section by the SCI entity to date regarding the SCI event to any of its members or participants; and</P>
                            <P>(C) An analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss.</P>
                            <P>(5) The requirements of paragraphs (b)(1) through (4) of this section shall not apply to any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. For such events, each SCI entity shall:</P>
                            <P>(i) Make, keep, and preserve records relating to all such SCI events; and</P>
                            <P>(ii) Submit to the Commission a report, within 30 calendar days after the end of each calendar quarter, containing a summary description of such systems disruptions and systems intrusions, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such systems disruptions and systems intrusions during the applicable calendar quarter.</P>
                            <P>
                                (c) 
                                <E T="03">Dissemination of SCI events.</E>
                                 (1) Each SCI entity shall:
                            </P>
                            <P>(i) Promptly after any responsible SCI personnel has a reasonable basis to conclude that an SCI event that is a systems disruption or systems compliance issue has occurred, disseminate the following information about such SCI event:</P>
                            <P>
                                (A) The system(s) affected by the SCI event; and
                                <PRTPAGE P="72439"/>
                            </P>
                            <P>(B) A summary description of the SCI event; and</P>
                            <P>(ii) When known, promptly further disseminate the following information about such SCI event:</P>
                            <P>(A) A detailed description of the SCI event;</P>
                            <P>(B) The SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; and</P>
                            <P>(C) A description of the progress of its corrective action for the SCI event and when the SCI event has been or is expected to be resolved; and</P>
                            <P>(iii) Until resolved, provide regular updates of any information required to be disseminated under paragraphs (c)(1)(i) and (ii) of this section.</P>
                            <P>(2) Each SCI entity shall, promptly after any responsible SCI personnel has a reasonable basis to conclude that a SCI event that is a systems intrusion has occurred, disseminate a summary description of the systems intrusion, including a description of the corrective action taken by the SCI entity and when the systems intrusion has been or is expected to be resolved, unless the SCI entity determines that dissemination of such information would likely compromise the security of the SCI entity's SCI systems or indirect SCI systems, or an investigation of the systems intrusion, and documents the reasons for such determination.</P>
                            <P>
                                (3) The information required to be disseminated under paragraphs (c)(1) and (2) of this section promptly after any responsible SCI personnel has a reasonable basis to conclude that an SCI event has occurred, shall be promptly disseminated by the SCI entity to those members or participants of the SCI entity that any responsible SCI personnel has reasonably estimated may have been affected by the SCI event, and promptly disseminated to any additional members or participants that any responsible SCI personnel subsequently reasonably estimates may have been affected by the SCI event; 
                                <E T="03">provided, however,</E>
                                 that for major SCI events, the information required to be disseminated under paragraphs (c)(1) and (2) of this section shall be promptly disseminated by the SCI entity to all of its members or participants.
                            </P>
                            <P>(4) The requirements of paragraphs (c)(1) through (3) of this section shall not apply to:</P>
                            <P>(i) SCI events to the extent they relate to market regulation or market surveillance systems; or</P>
                            <P>(ii) Any SCI event that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1003 </SECTNO>
                            <SUBJECT>Obligations related to systems changes; SCI review.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Systems changes.</E>
                                 Each SCI entity shall:
                            </P>
                            <P>(1) Within 30 calendar days after the end of each calendar quarter, submit to the Commission a report describing completed, ongoing, and planned material changes to its SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion. An SCI entity shall establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material and report such changes in accordance with such criteria.</P>
                            <P>(2) Promptly submit a supplemental report notifying the Commission of a material error in or material omission from a report previously submitted under this paragraph (a).</P>
                            <P>
                                (b) 
                                <E T="03">SCI review.</E>
                                 Each SCI entity shall:
                            </P>
                            <P>
                                (1) Conduct an SCI review of the SCI entity's compliance with Regulation SCI not less than once each calendar year; 
                                <E T="03">provided, however,</E>
                                 that:
                            </P>
                            <P>(i) Penetration test reviews of the network, firewalls, and production systems shall be conducted at a frequency of not less than once every three years; and</P>
                            <P>(ii) Assessments of SCI systems directly supporting market regulation or market surveillance shall be conducted at a frequency based upon the risk assessment conducted as part of the SCI review, but in no case less than once every three years; and</P>
                            <P>(2) Submit a report of the SCI review required by paragraph (b)(1) of this section to senior management of the SCI entity for review no more than 30 calendar days after completion of such SCI review; and</P>
                            <P>(3) Submit to the Commission, and to the board of directors of the SCI entity or the equivalent of such board, a report of the SCI review required by paragraph (b)(1) of this section, together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1004 </SECTNO>
                            <SUBJECT>SCI entity business continuity and disaster recovery plans testing requirements for members or participants.</SUBJECT>
                            <P>With respect to an SCI entity's business continuity and disaster recovery plans, including its backup systems, each SCI entity shall:</P>
                            <P>(a) Establish standards for the designation of those members or participants that the SCI entity reasonably determines are, taken as a whole, the minimum necessary for the maintenance of fair and orderly markets in the event of the activation of such plans;</P>
                            <P>(b) Designate members or participants pursuant to the standards established in paragraph (a) of this section and require participation by such designated members or participants in scheduled functional and performance testing of the operation of such plans, in the manner and frequency specified by the SCI entity, provided that such frequency shall not be less than once every 12 months; and</P>
                            <P>(c) Coordinate the testing of such plans on an industry- or sector-wide basis with other SCI entities.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1005 </SECTNO>
                            <SUBJECT>Recordkeeping requirements related to compliance with Regulation SCI.</SUBJECT>
                            <P>(a) An SCI SRO shall make, keep, and preserve all documents relating to its compliance with Regulation SCI as prescribed in § 240.17a-1 of this chapter.</P>
                            <P>(b) An SCI entity that is not an SCI SRO shall:</P>
                            <P>(1) Make, keep, and preserve at least one copy of all documents, including correspondence, memoranda, papers, books, notices, accounts, and other such records, relating to its compliance with Regulation SCI, including, but not limited to, records relating to any changes to its SCI systems and indirect SCI systems;</P>
                            <P>(2) Keep all such documents for a period of not less than five years, the first two years in a place that is readily accessible to the Commission or its representatives for inspection and examination; and</P>
                            <P>(3) Upon request of any representative of the Commission, promptly furnish to the possession of such representative copies of any documents required to be kept and preserved by it pursuant to paragraphs (b)(1) and (2) of this section.</P>
                            <P>(c) Upon or immediately prior to ceasing to do business or ceasing to be registered under the Securities Exchange Act of 1934, an SCI entity shall take all necessary action to ensure that the records required to be made, kept, and preserved by this section shall be accessible to the Commission and its representatives in the manner required by this section and for the remainder of the period required by this section.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1006 </SECTNO>
                            <SUBJECT>Electronic filing and submission.</SUBJECT>
                            <P>
                                (a) Except with respect to notifications to the Commission made pursuant to § 242.1002(b)(1) or updates to the Commission made pursuant to paragraph § 242.1002(b)(3), any notification, review, description, analysis, or report to the Commission 
                                <PRTPAGE P="72440"/>
                                required to be submitted under Regulation SCI shall be filed electronically on Form SCI (§ 249.1900 of this chapter), include all information as prescribed in Form SCI and the instructions thereto, and contain an electronic signature; and
                            </P>
                            <P>(b) The signatory to an electronically filed Form SCI shall manually sign a signature page or document, in the manner prescribed by Form SCI, authenticating, acknowledging, or otherwise adopting his or her signature that appears in typed form within the electronic filing. Such document shall be executed before or at the time Form SCI is electronically filed and shall be retained by the SCI entity in accordance with § 242.1005.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 242.1007 </SECTNO>
                            <SUBJECT>Requirements for service bureaus.</SUBJECT>
                            <P>If records required to be filed or kept by an SCI entity under Regulation SCI are prepared or maintained by a service bureau or other recordkeeping service on behalf of the SCI entity, the SCI entity shall ensure that the records are available for review by the Commission and its representatives by submitting a written undertaking, in a form acceptable to the Commission, by such service bureau or other recordkeeping service, signed by a duly authorized person at such service bureau or other recordkeeping service. Such a written undertaking shall include an agreement by the service bureau to permit the Commission and its representatives to examine such records at any time or from time to time during business hours, and to promptly furnish to the Commission and its representatives true, correct, and current electronic files in a form acceptable to the Commission or its representatives or hard copies of any or all or any part of such records, upon request, periodically, or continuously and, in any case, within the same time periods as would apply to the SCI entity for such records. The preparation or maintenance of records by a service bureau or other recordkeeping service shall not relieve an SCI entity from its obligation to prepare, maintain, and provide the Commission and its representatives access to such records.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="17" PART="249">
                        <PART>
                            <HD SOURCE="HED">PART 249—FORMS, SECURITIES EXCHANGE ACT OF 1934</HD>
                        </PART>
                        <AMDPAR>7. The general authority citation for part 249 continues to read in part as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 15 U.S.C. 78a 
                                <E T="03">et seq.</E>
                                 and 7201; and 18 U.S.C. 1350 unless otherwise noted.
                            </P>
                        </AUTH>
                        <STARS/>
                        <AMDPAR>8. Add subpart T, consisting of § 249.1900 to read as follows:</AMDPAR>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart T—Form SCI, for filing notices and reports as required by Regulation SCI.</HD>
                            <SECTION>
                                <SECTNO>§ 249.1900. </SECTNO>
                                <SUBJECT>Form SCI, for filing notices and reports as required by Regulation SCI.</SUBJECT>
                                <P>Form SCI shall be used to file notices and reports as required by Regulation SCI (§§ 242.1000 through 242.1007).</P>
                                <NOTE>
                                    <HD SOURCE="HED">Note:</HD>
                                    <P> The text of Form SCI does not, and the amendments will not, appear in the Code of Federal Regulations.</P>
                                </NOTE>
                                <BILCOD>BILLING CODE P</BILCOD>
                                <GPH SPAN="3" DEEP="640">
                                    <PRTPAGE P="72441"/>
                                    <GID>ER05DE14.000</GID>
                                </GPH>
                                <GPH SPAN="3" DEEP="640">
                                    <PRTPAGE P="72442"/>
                                    <GID>ER05DE14.001</GID>
                                </GPH>
                                <GPH SPAN="3" DEEP="424">
                                    <PRTPAGE P="72443"/>
                                    <GID>ER05DE14.002</GID>
                                </GPH>
                                <GPOTABLE COLS="2" OPTS="L2,tp0,p1,8/9,i1" CDEF="xs100,r150">
                                    <TTITLE> </TTITLE>
                                    <BOXHD>
                                        <CHED H="1"> </CHED>
                                        <CHED H="1"> </CHED>
                                    </BOXHD>
                                    <ROW>
                                        <ENT I="01">
                                            Exhibit 1: Rule 1002(b)(2) Notification of SCI Event
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>
                                            Within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that the SCI event has occurred, the SCI entity shall submit a written notification pertaining to such SCI event to the Commission, which shall be made on a good faith, best efforts basis and include:
                                            <LI O="oi3">(a) a description of the SCI event, including the system(s) affected; and </LI>
                                        </ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="22"> </ENT>
                                        <ENT O="oi3">(b) to the extent available as of the time of the notification: The SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">
                                            Exhibit 2: Rule 1002(b)(4) Final or Interim Report of SCI Event
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>
                                            When submitting a final report pursuant to either Rule 1002(b)(4)(i)(A) or Rule 1002(b)(4)(i)(B)(
                                            <E T="03">2</E>
                                            ), the SCI entity shall include:
                                            <LI O="oi3">(a) a detailed description of: The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event;</LI>
                                        </ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="22"> </ENT>
                                        <ENT O="oi3">(b) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="22"> </ENT>
                                        <ENT O="oi3">(c) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="22"> </ENT>
                                        <ENT>
                                            When submitting an interim report pursuant to Rule 1002(b)(4)(i)(B)(
                                            <E T="03">1</E>
                                            ), the SCI entity shall include such information to the extent known at the time.
                                        </ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">
                                            Exhibit 3: Rule 1002(b)(5)(ii) Quarterly Report of De Minimis SCI Events
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>The SCI entity shall submit a report, within 30 calendar days after the end of each calendar quarter, containing a summary description of systems disruptions and systems intrusions that have had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such SCI events during the applicable calendar quarter.</ENT>
                                    </ROW>
                                    <ROW>
                                        <PRTPAGE P="72444"/>
                                        <ENT I="01">
                                            Exhibit 4: Rule 1003 (a) Quarterly Report of Systems Changes
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>When submitting a report pursuant to Rule 1003(a)(1), the SCI entity shall provide a report, within 30 calendar days after the end of each calendar quarter, describing completed, ongoing, and planned material changes to its SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion. An SCI entity shall establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material and report such changes in accordance with such criteria. </ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="22"> </ENT>
                                        <ENT>When submitting a report pursuant to Rule 1003(a)(2), the SCI entity shall provide a supplemental report of a material error in or material omission from a report previously submitted under Rule 1003(a)(1).</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">
                                            Exhibit 5: Rule 1003(b)(3) Report of SCI review
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>The SCI entity shall provide a report of the SCI review, together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">
                                            Exhibit 6: Optional Attachments
                                            <LI O="xl">Add/Remove/View</LI>
                                        </ENT>
                                        <ENT>This exhibit may be used in order to attach other documents that the SCI entity may wish to submit as part of a Rule 1002(b)(1) initial notification submission or Rule 1002(b)(3) update submission.</ENT>
                                    </ROW>
                                </GPOTABLE>
                                <HD SOURCE="HD1">General Instructions for Form SCI</HD>
                                <HD SOURCE="HD2">A. Use of the Form</HD>
                                <P>
                                    Except with respect to notifications to the Commission made pursuant to Rule 1002(b)(1) or updates to the Commission made pursuant to Rule 1002(b)(3), any notification, review, description, analysis, or report required to be submitted pursuant to Regulation SCI under the Securities Exchange Act of 1934 (“Act”) shall be filed in an electronic format through an electronic form filing system (“EFFS”), a secure Web site operated by the Securities and Exchange Commission (“Commission”). Documents attached as exhibits filed through the EFFS system must be in a text-searchable format without the use of optical character recognition. If, however, a portion of a Form SCI submission (
                                    <E T="03">e.g.,</E>
                                     an image or diagram) cannot be made available in a text-searchable format, such portion may be submitted in a non-text searchable format.
                                </P>
                                <HD SOURCE="HD2">B. Need for Careful Preparation of the Completed Form, Including Exhibits</HD>
                                <P>
                                    This form, including the exhibits, is intended to elicit information necessary for Commission staff to work with SCI self-regulatory organizations, SCI alternative trading systems, plan processors, and exempt clearing agencies subject to ARP (collectively, “SCI entities”) to ensure the capacity, integrity, resiliency, availability, security, and compliance of their automated systems. An SCI entity must provide all the information required by the form, including the exhibits, and must present the information in a clear and comprehensible manner. A filing that is incomplete or similarly deficient may be returned to the SCI entity. Any filing so returned shall for all purposes be deemed not to have been filed with the Commission. 
                                    <E T="03">See also</E>
                                     Rule 0-3 under the Act (17 CFR 240.0-3).
                                </P>
                                <HD SOURCE="HD2">C. When To Use the Form</HD>
                                <P>Form SCI is comprised of six types of required submissions to the Commission pursuant to Rules 1002 and 1003. In addition, Form SCI permits SCI entities to submit to the Commission two additional types of submissions pursuant to Rules 1002(b)(1) and 1002(b)(3); however, SCI entities are not required to use Form SCI for these two types of submissions to the Commission. In filling out Form SCI, an SCI entity shall select the type of filing and provide all information required by Regulation SCI specific to that type of filing.</P>
                                <P>The first two types of required submissions relate to Commission notification of certain SCI events:</P>
                                <P>(1) “Rule 1002(b)(2) Notification of SCI Event” submissions for notifications regarding systems disruptions, systems compliance issues, or systems intrusions (collectively, “SCI events”), other than any systems disruption or systems intrusion that has had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants; and</P>
                                <P>
                                    (2) “Rule 1002(b)(4) Final or Interim Report of SCI Event” submissions, of which there are two kinds (a final report under Rule 1002(b)(4)(i)(A) or Rule 1002(b)(4)(i)(B)(
                                    <E T="03">2</E>
                                    ); or an interim status report under Rule 1002(b)(4)(i)(B)(
                                    <E T="03">1</E>
                                    )).
                                </P>
                                <P>The other four types of required submissions are periodic reports, and include:</P>
                                <P>(1) “Rule 1002(b)(5)(ii)” submissions for quarterly reports of systems disruptions and systems intrusions which have had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants (“de minimis SCI events”);</P>
                                <P>(2) “Rule 1003(a)(1)” submissions for quarterly reports of material systems changes;</P>
                                <P>(3) “Rule 1003(a)(2)” submissions for supplemental reports of material systems changes; and</P>
                                <P>(4) “Rule 1003(b)(3)” submissions for reports of SCI reviews.</P>
                                <HD SOURCE="HD3">Required Submissions for SCI Events</HD>
                                <P>For 1002(b)(2) submissions, an SCI entity must notify the Commission using Form SCI by selecting the appropriate box in Section I and filling out all information required by the form, including Exhibit 1. 1002(b)(2) submissions must be submitted within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred.</P>
                                <P>
                                    For 1002(b)(4) submissions, if an SCI event is resolved and the SCI entity's investigation of the SCI event is closed within 30 calendar days of the occurrence of the SCI event, an SCI entity must file a final report under Rule 1002(b)(4)(i)(A) within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event. However, if an SCI event is not resolved or the SCI entity's investigation of the SCI event is not closed within 30 calendar days of the occurrence of the SCI event, an SCI entity must file an interim status report under Rule 1002(b)(4)(i)(B)(
                                    <E T="03">1</E>
                                    ) within 30 calendar days after the occurrence of the SCI event. For SCI events in which an interim status report is required to be filed, an SCI entity must file a final report under Rule 1002(b)(4)(i)(B)(
                                    <E T="03">2</E>
                                    ) within five business days after the resolution of the SCI event and closure of the investigation regarding the SCI event. For 1002(b)(4) submissions, an SCI entity must notify the Commission using Form SCI by selecting the appropriate box in Section I and filling out all information required by the form, including Exhibit 2.
                                </P>
                                <HD SOURCE="HD3">Required Submissions for Periodic Reporting</HD>
                                <P>
                                    For 1002(b)(5)(ii) submissions, an SCI entity must submit quarterly reports of systems disruptions and systems intrusions which have had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants. The SCI entity must select 
                                    <PRTPAGE P="72445"/>
                                    the appropriate box in Section II and fill out all information required by the form, including Exhibit 3.
                                </P>
                                <P>For 1003(a)(1) submissions, an SCI entity must submit its quarterly report of material systems changes to the Commission using Form SCI. The SCI entity must select the appropriate box in Section II and fill out all information required by the form, including Exhibit 4.</P>
                                <P>
                                    Filings made pursuant to Rule 1002(b)(5)(ii) and Rule 1003(a)(1) must be submitted to the Commission within 30 calendar days after the end of each calendar quarter (
                                    <E T="03">i.e.,</E>
                                     March 31st, June 30th, September 30th and December 31st) of each year.
                                </P>
                                <P>For 1003(a)(2) submissions, an SCI entity must submit a supplemental report notifying the Commission of a material error in or material omission from a report previously submitted under Rule 1003(a). The SCI entity must select the appropriate box in Section II and fill out all information required by the form, including Exhibit 4.</P>
                                <P>For 1003(b)(3) submissions, an SCI entity must submit its report of its SCI review, together with any response by senior management, to the Commission using Form SCI. A 1003(b)(3) submission is required within 60 calendar days after the report of the SCI review has been submitted to senior management of the SCI entity. The SCI entity must select the appropriate box in Section II and fill out all information required by the form, including Exhibit 5.</P>
                                <HD SOURCE="HD3">Optional Submissions</HD>
                                <P>An SCI entity may, but is not required to, use Form SCI to submit a notification pursuant to Rule 1002(b)(1). If the SCI entity uses Form SCI to submit a notification pursuant to Rule 1002(b)(1), it must select the appropriate box in Section I and provide a short description of the SCI event. Documents may also be attached as Exhibit 6 if the SCI entity chooses to do so. An SCI entity may, but is not required to, use Form SCI to submit an update pursuant to Rule 1002(b)(3). Rule 1002(b)(3) requires an SCI entity to, until such time as the SCI event is resolved and the SCI entity's investigation of the SCI event is closed, provide updates pertaining to such SCI event to the Commission on a regular basis, or at such frequency as reasonably requested by a representative of the Commission, to correct any materially incorrect information previously provided, or when new material information is discovered, including but not limited to, any of the information listed in Rule 1002(b)(2)(ii). If the SCI entity uses Form SCI to submit an update pursuant to Rule 1002(b)(3), it must select the appropriate box in Section I and provide a short description of the SCI event. Documents may also be attached as Exhibit 6 if the SCI entity chooses to do so.</P>
                                <HD SOURCE="HD2">D. Documents Comprising the Completed Form </HD>
                                <P>
                                    The completed form filed with the Commission shall consist of Form SCI, responses to all applicable items, and any exhibits required in connection with the filing. Each filing shall be marked on Form SCI with the initials of the SCI entity, the four-digit year, and the number of the filing for the year (
                                    <E T="03">e.g.,</E>
                                     SCI Name-YYYY-XXX).
                                </P>
                                <HD SOURCE="HD2">E. Contact Information; Signature; and Filing of the Completed Form</HD>
                                <P>Each time an SCI entity submits a filing to the Commission on Form SCI, the SCI entity must provide the contact information required by Section III of Form SCI. Space for additional contact information, if appropriate, is also provided.</P>
                                <P>All notifications and reports required to be submitted through Form SCI shall be filed through the EFFS. In order to file Form SCI through the EFFS, SCI entities must request access to the Commission's External Application Server by completing a request for an external account user ID and password. Initial requests will be received by contacting (202) 551-5777. An email will be sent to the requestor that will provide a link to a secure Web site where basic profile information will be requested. A duly authorized individual of the SCI entity shall electronically sign the completed Form SCI as indicated in Section IV of the form. In addition, a duly authorized individual of the SCI entity shall manually sign one copy of the completed Form SCI, and the manually signed signature page shall be preserved pursuant to the requirements of Rule 1005.</P>
                                <HD SOURCE="HD2">F. Withdrawals of Commission Notifications and Periodic Reports</HD>
                                <P>If an SCI entity determines to withdraw a Form SCI, it must complete Page 1 of the Form SCI and indicate by selecting the appropriate check box to withdraw the submission.</P>
                                <HD SOURCE="HD2">G. Paperwork Reduction Act Disclosure</HD>
                                <P>This collection of information will be reviewed by the Office of Management and Budget in accordance with the clearance requirements of 44 U.S.C. 3507. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number. The Commission estimates that the average burden to respond to Form SCI will be between one and 125 hours, depending upon the purpose for which the form is being filed. Any member of the public may direct to the Commission any comments concerning the accuracy of this burden estimate and any suggestions for reducing this burden.</P>
                                <P>Except with respect to notifications to the Commission made pursuant to Rule 1002(b)(1) or updates to the Commission made pursuant to Rule 1002(b)(3), it is mandatory that an SCI entity file all notifications, reviews, descriptions, analyses, and reports required by Regulation SCI using Form SCI. The Commission will keep the information collected pursuant to Form SCI confidential to the extent permitted by law. Subject to the provisions of the Freedom of Information Act, 5 U.S.C. 522 (“FOIA”), and the Commission's rules thereunder (17 CFR 200.80(b)(4)(iii)), the Commission does not generally publish or make available information contained in any reports, summaries, analyses, letters, or memoranda arising out of, in anticipation of, or in connection with an examination or inspection of the books and records of any person or any other investigation.</P>
                                <HD SOURCE="HD2">H. Exhibits</HD>
                                <P>List of exhibits to be filed, as applicable:</P>
                                <P>
                                    <E T="03">Exhibit 1: Rule 1002(b)(2)—Notification of SCI Event.</E>
                                     Within 24 hours of any responsible SCI personnel having a reasonable basis to conclude that the SCI event has occurred, the SCI entity shall submit a written notification pertaining to such SCI event to the Commission, which shall be made on a good faith, best efforts basis and include: (a) A description of the SCI event, including the system(s) affected; and (b) to the extent available as of the time of the notification: the SCI entity's current assessment of the types and number of market participants potentially affected by the SCI event; the potential impact of the SCI event on the market; a description of the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved or timeframe within which the SCI event is expected to be resolved; and any other pertinent information known by the SCI entity about the SCI event.
                                </P>
                                <P>
                                    <E T="03">Exhibit 2: Rule 1002(b)(4)—Final or Interim Report of SCI Event.</E>
                                     When submitting a final report pursuant to either Rule 1002(b)(4)(i)(A) or Rule 1002(b)(4)(i)(B)(
                                    <E T="03">2</E>
                                    ), the SCI entity shall include: (a) A detailed description of: 
                                    <PRTPAGE P="72446"/>
                                    The SCI entity's assessment of the types and number of market participants affected by the SCI event; the SCI entity's assessment of the impact of the SCI event on the market; the steps the SCI entity has taken, is taking, or plans to take, with respect to the SCI event; the time the SCI event was resolved; the SCI entity's rule(s) and/or governing document(s), as applicable, that relate to the SCI event; and any other pertinent information known by the SCI entity about the SCI event; (b) a copy of any information disseminated pursuant to Rule 1002(c) by the SCI entity to date regarding the SCI event to any of its members or participants; and (c) an analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. When submitting an interim report pursuant to Rule 1002(b)(4)(i)(B)(
                                    <E T="03">1</E>
                                    ), the SCI entity shall include such information to the extent known at the time.
                                </P>
                                <P>
                                    <E T="03">Exhibit 3: Rule 1002(b)(5)(ii)—Quarterly Report of De Minimis SCI Events.</E>
                                     The SCI entity shall submit a report, within 30 calendar days after the end of each calendar quarter, containing a summary description of systems disruptions and systems intrusions that have had, or the SCI entity reasonably estimates would have, no or a de minimis impact on the SCI entity's operations or on market participants, including the SCI systems and, for systems intrusions, indirect SCI systems, affected by such SCI events during the applicable calendar quarter.
                                </P>
                                <P>
                                    <E T="03">Exhibit 4: Rule 1003(a)—Quarterly Report of Systems Changes.</E>
                                     When submitting a report pursuant to Rule 1003(a)(1), the SCI entity shall provide a report, within 30 calendar days after the end of each calendar quarter, describing completed, ongoing, and planned material changes to its SCI systems and the security of indirect SCI systems, during the prior, current, and subsequent calendar quarters, including the dates or expected dates of commencement and completion. An SCI entity shall establish reasonable written criteria for identifying a change to its SCI systems and the security of indirect SCI systems as material and report such changes in accordance with such criteria. When submitting a report pursuant to Rule 1003(a)(2), the SCI entity shall provide a supplemental report of a material error in or material omission from a report previously submitted under Rule 1003(a); provided, however, that a supplemental report is not required if information regarding a material systems change is or will be provided as part of a notification made pursuant to Rule 1002(b).
                                </P>
                                <P>
                                    <E T="03">Exhibit 5: Rule 1003(b)(3)—Report of SCI Review.</E>
                                     The SCI entity shall provide a report of the SCI review, together with any response by senior management, within 60 calendar days after its submission to senior management of the SCI entity.
                                </P>
                                <P>
                                    <E T="03">Exhibit 6: Optional Attachments.</E>
                                     This exhibit may be used in order to attach other documents that the SCI entity may wish to submit as part of a Rule 1002(b)(1) initial notification submission or Rule 1002(b)(3) update submission.
                                </P>
                                <HD SOURCE="HD2">I. Explanation of Terms</HD>
                                <P>Critical SCI systems means any SCI systems of, or operated by or on behalf of, an SCI entity that: (1) directly support functionality relating to:  (i) clearance and settlement systems of clearing agencies; (ii) openings, reopenings, and closings on the primary listing market; (iii)  trading halts; (iv) initial public offerings; (v) the provision of consolidated market data; or (vi) exclusively-listed securities; or (2) provide functionality to the securities markets for which the availability of alternatives is significantly limited or nonexistent and without which there would be a material impact on fair and orderly markets.</P>
                                <P>Indirect SCI systems means any systems of, or operated by or on behalf of, an SCI entity that, if breached, would be reasonably likely to pose a security threat to SCI systems.</P>
                                <P>Major SCI event means an SCI event that has had, or the SCI entity reasonably estimates would have: (1) Any impact on a critical SCI system; or (2) a significant impact on the SCI entity's operations or on market participants.</P>
                                <P>Responsible SCI personnel means, for a particular SCI system or indirect SCI system impacted by an SCI event, such senior manager(s) of the SCI entity having responsibility for such system, and their designee(s).</P>
                                <P>SCI entity means an SCI self-regulatory organization, SCI alternative trading system, plan processor, or exempt clearing agency subject to ARP.</P>
                                <P>SCI event means an event at an SCI entity that constitutes: (1) A systems disruption; (2) a systems compliance issue; or (3) a systems intrusion.</P>
                                <P>SCI review means a review, following established procedures and standards, that is performed by objective personnel having appropriate experience to conduct reviews of SCI systems and indirect SCI systems, and which review contains: (1) A risk assessment with respect to such systems of an SCI entity; and (2) an assessment of internal control design and effectiveness of its SCI systems and indirect SCI systems to include logical and physical security controls, development processes, and information technology governance, consistent with industry standards.</P>
                                <P>SCI systems means all computer, network, electronic, technical, automated, or similar systems of, or operated by or on behalf of, an SCI entity that, with respect to securities, directly support trading, clearance and settlement, order routing, market data, market regulation, or market surveillance.</P>
                                <P>Systems Compliance Issue means an event at an SCI entity that has caused any SCI system of such entity to operate in a manner that does not comply with the Act and the rules and regulations thereunder or the entity's rules or governing documents, as applicable.</P>
                                <P>Systems Disruption means an event in an SCI entity's SCI systems that disrupts, or significantly degrades, the normal operation of an SCI system.</P>
                                <P>Systems Intrusion means any unauthorized entry into the SCI systems or indirect SCI systems of an SCI entity.</P>
                            </SECTION>
                        </SUBPART>
                    </REGTEXT>
                    <SIG>
                        <P>By the Commission.</P>
                        <DATED>Dated: November 19, 2014.</DATED>
                        <NAME>Brent J. Fields,</NAME>
                        <TITLE>Secretary.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Exhibit A</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-1">Key to Comment Letters Cited in Regulation SCI Adopting Release (File No. S7-01-13)</FP>
                        <FP SOURCE="FP-1">Letter from Charles V. Rossi, President, The Securities Transfer Association, Inc. to Elizabeth Murphy, Secretary, Commission, dated April 3, 2013 (“STA Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from John J. Rapa, President/Chief Executive Officer, Tellefsen and Company, L.L.C., Northborough, Massachusetts to Elizabeth Murphy, Commission, dated April 19, 2013 (“Tellefsen Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Cynthia Fuller, Executive Director, on behalf of Accredited Standards Committee X9, Inc. Financial Industry Standards to the Commission, dated May 23, 2013 (“X9 Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Scott Cooper, Vice President, Government Relations and Public Policy, American National Standards Institute to the Commission, dated May 23, 2013 (“ANSI Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from James J. Angel, Ph.D., CFA, Visiting Associate Professor, The Wharton School, University of Pennsylvania to the Commission, dated June 3, 2013 (“Angel Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Raymond M. Tierney III, President and Chief Executive Officer, Bloomberg Tradebook LLC to Elizabeth Murphy, Secretary, Commission, dated June 19, 2013 (“Tradebook Letter”)</FP>
                        <FP SOURCE="FP-1">
                            Letter from Jay M. Goldstone, Chairman, Municipal Securities Rulemaking Board, Alexandria, Virginia to Elizabeth Murphy, Secretary, Commission, dated June 28, 2013 (“MSRB Letter”)
                            <PRTPAGE P="72447"/>
                        </FP>
                        <FP SOURCE="FP-1">Letter from Thomas V. D'Ambrosio, Chairman, Committee on Futures and Derivatives, New York City Bar Association to Elizabeth Murphy, Secretary, Commission, dated July 1, 2013 (“NYC Bar Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Richard M. Whiting, Executive Director and General Counsel, The Financial Services Roundtable to Elizabeth Murphy, Secretary, Commission, dated July 5, 2013 (“FSR Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Rob Flatley, Chief Executive Officer and President, CoreOne Technologies to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“CoreOne Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Manisha Kimmel, Executive Director, Financial Information Forum to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“FIF Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Larry E. Thompson, Managing Director and General Counsel, The Depository Trust Clearing Corporation to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“DTCC Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Raymond Tamayo, Chief Information Officer, Options Clearing Corporation to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“OCC Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Timothy J. Mahoney, CEO, BIDS Trading, L.P., New York, New York to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“BIDS Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Michael Simon, Secretary, International Securities Exchange, LLC to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“ISE Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Courtney D. McGuinn, Operations Director, FIX Protocol Ltd., New York, New York to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“FIX Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from R.T. Leuchtkafer to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Leuchtkafer Letter ”)</FP>
                        <FP SOURCE="FP-1">Letter from Dennis M. Kelleher, President &amp; CEO; Stephen W. Hall, Securities Specialist; Katelynn O. Bradley, Attorney; and David Frenk, Director of Research; Better Markets, Inc. to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Better Markets Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Lev Lesokhin, Executive Vice President, Strategy and Markets, CAST, Inc., New York, New York to the Commission, dated July 8, 2013 (“CAST Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Robert J. McCarthy, Director of Regulatory Policy, Wells Fargo Advisors to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Wells Fargo Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Marcia E. Asquith, Senior Vice President and Corporate Secretary, FINRA to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“FINRA Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Dr. Bill Curtis, Director, Consortium for IT Software Quality to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“CISQ Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Howard Meyerson, General Counsel, Liquidnet, Inc., New York, New York to the Commission, dated July 8, 2013 (“Liquidnet Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from David T. Bellaire, Esq., Executive Vice President and General Counsel, Financial Services Institute, Washington, District of Columbia to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“FSI Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Scott C. Goebel, General Counsel, Fidelity Management and Research Co., Boston, Massachusetts to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Fidelity Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Joseph Adamczyk, Executive Director, Associate General Counsel, CME Group Inc. to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“CME Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Norman M. Reed, Omgeo LLC, New York, New York to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Omgeo Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from David Lauer, Market Structure and Technology Architecture Consultant, Step Ahead Technologies, LLC to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“Lauer Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Theodore R. Lazo, Managing Director and Associate General Counsel, SIFMA to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“SIFMA Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Jeffrey Wallis, Managing Partner, SunGard Consulting Services, New York, New York to Elizabeth Murphy, Secretary, Commission, dated July 8, 2013 (“SunGard Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Janet McGinness, EVP &amp; Corporate Secretary, NYSE Euronext to Elizabeth Murphy, Secretary, Commission, dated July 9, 2013 (“NYSE Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Eric J. Swanson, Secretary, BATS Global Markets to Elizabeth Murphy, Secretary, Commission, dated July 10, 2013 (“BATS Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Mary Ann Burns, Futures Industry Association Principal Traders Group, Washington, District of Columbia to Elizabeth Murphy, Secretary, Commission, dated July 11, 2013 (“FIA PTG Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from James P. Selway, III, P. Mats Goebels and Sudhanshu Arya, ITG Inc. to Elizabeth Murphy, Secretary, Commission, dated July 11, 2013 (“ITG Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Karrie McMillan, General Counsel, Investment Company Institute to Elizabeth Murphy, Secretary, Commission, dated July 12, 2013 (“ICI Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Stuart J. Kaswell, Executive Vice President &amp; Managing Director, Managed Funds Association, and Jirí Król, Deputy CEO, Head of Government and Regulatory Affairs, Alternative Investment Management Association to Elizabeth Murphy, Secretary, Commission, dated July 17, 2013 (“MFA Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Anthony J. Saliba, Chief Executive Officer, LiquidPoint, LLC to Elizabeth Murphy, Secretary, Commission, dated July 22, 2013 (“LiquidPoint Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Elizabeth K. King, Global Head of Regulatory Affairs, KCG Holdings, Inc., Jersey City, New Jersey to Elizabeth Murphy, Secretary, Commission, dated July 25, 2013 (“KCG Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Roger Anerella, Managing Director, Global Head of Securities Execution Services, UBS Investment Bank to Elizabeth Murphy, Secretary, Commission, dated July 26, 2013 (“UBS Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Eric Swanson, SVP, General Counsel and Secretary, BATS Global Markets, Inc., et al. to Elizabeth Murphy, Secretary, Commission, dated July 30, 2013 (“Joint SROs Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Thomas S. Vales, Chief Executive Officer, TMC Bonds LLC to Elizabeth Murphy, Secretary, Commission, dated August 6, 2013 (“TMC Bonds Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from James J. Angel, Ph.D., CFA, Visiting Associate Professor, The Wharton School, University of Pennsylvania to the Commission, dated September 3, 2013 (“Angel2 Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Benjamin R. Londergan, Chief Executive Officer, Group One Trading L.P. to Elizabeth Murphy, Secretary, Commission, dated September 3, 2013 (“Group One Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Ari Gabinet, Executive Vice President and General Counsel, OFI Global Asset Management to Elizabeth Murphy, Secretary, Commission, dated September 9, 2013 (“Oppenheimer Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Daniel Zinn, General Counsel, OTC Markets Group Inc. to Elizabeth Murphy, Secretary, Commission, dated September 12, 2013 (“OTC Markets Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Dr. Bill Curtis, Director, Consortium for IT Software Quality to Elizabeth Murphy, Secretary, Commission, dated September 17, 2013 (“CISQ2 Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from William O'Brien, Chief Executive Officer, Direct Edge Holdings to Elizabeth M. Murphy, Secretary, Commission, dated September 25, 2013 (“Direct Edge Letter”)</FP>
                        <FP SOURCE="FP-1">Letter from Richie Prager, Managing Director, Head of Trading &amp; Liquidity Strategies, Hubert De Jesus, Managing Director, Co-Head of Market Structure &amp; Electronic Trading, Supurna Vedbrat, Managing Director, Co-Head of Market Structure &amp; Electronic Trading, and Joanne Medero, Managing Director, Government Relations &amp; Public Policy, BlackRock, Inc. to Mary Jo White, Chair, Commission, dated September 12, 2014 (“BlackRock Letter”).</FP>
                    </EXTRACT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2014-27767 Filed 12-4-14; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="72449"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P"> Department of the Interior</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 17</CFR>
            <TITLE>Endangered and Threatened Wildlife and Plants; Review of Native Species That Are Candidates for Listing as Endangered or Threatened; Annual Notice of Findings on Resubmitted Petitions; Annual Description of Progress on Listing Actions; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="72450"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-HQ-ES-2014-0032; FF09E21000 FXES11190900000 145]</DEPDOC>
                    <SUBJECT>Endangered and Threatened Wildlife and Plants; Review of Native Species That Are Candidates for Listing as Endangered or Threatened; Annual Notice of Findings on Resubmitted Petitions; Annual Description of Progress on Listing Actions</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of review.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>In this Candidate Notice of Review (CNOR), we, the U.S. Fish and Wildlife Service (Service), present an updated list of plant and animal species native to the United States that we regard as candidates for or have proposed for addition to the Lists of Endangered and Threatened Wildlife and Plants under the Endangered Species Act of 1973, as amended. Identification of candidate species can assist environmental planning efforts by providing advance notice of potential listings, allowing landowners and resource managers to alleviate threats and thereby possibly remove the need to list species as endangered or threatened. Even if we subsequently list a candidate species, the early notice provided here could result in more options for species management and recovery by prompting candidate conservation measures to alleviate threats to the species.</P>
                        <P>The CNOR summarizes the status and threats that we evaluated in order to determine that species qualify as candidates, to assign a listing priority number (LPN) to each species, and to determine whether a species should be removed from candidate status. Additional material that we relied on is available in the Species Assessment and Listing Priority Assignment Forms (species assessment forms) for each candidate species.</P>
                        <P>Overall, this CNOR recognizes 23 new candidates, changes the LPN for one candidate, and removes one species from candidate status. Combined with other decisions for individual species that were published separately from this CNOR in the past year, the current number of species that are candidates for listing is 146.</P>
                        <P>This document also includes our findings on resubmitted petitions and describes our progress in revising the Lists of Endangered and Threatened Wildlife and Plants (Lists) during the period October 1, 2013, through September 30, 2014.</P>
                        <P>We request additional status information that may be available for the 146 candidate species identified in this CNOR.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>We will accept information on any of the species in this Candidate Notice of Review at any time.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            This notice is available on the Internet at 
                            <E T="03">http://www.regulations.gov</E>
                             and 
                            <E T="03">http://www.fws.gov/endangered/what-we-do/cnor.html.</E>
                             Species assessment forms with information and references on a particular candidate species' range, status, habitat needs, and listing priority assignment are available for review at the appropriate Regional Office listed below in 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             or at the Branch of Communications and Candidate Conservation, Falls Church, VA (see address under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ), or on our Web site (
                            <E T="03">http://ecos.fws.gov/tess_public/pub/candidateSpecies.jsp</E>
                            ). Please submit any new information, materials, comments, or questions of a general nature on this notice to the Falls Church, VA, address listed under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            . Please submit any new information, materials, comments, or questions pertaining to a particular species to the address of the Endangered Species Coordinator in the appropriate Regional Office listed in 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                            . Species-specific information and materials we receive will be available for public inspection by appointment, during normal business hours, at the appropriate Regional Office listed below under Request for Information in 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                            . General information we receive will be available at the Branch of Communications and Candidate Conservation, Falls Church, VA (see address under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ).
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Chief, Branch of Communications and Candidate Conservation, U.S. Fish and Wildlife Service Headquarters, MS: ES, 5275 Leesburg Pike, Falls Church, VA 22041-3803 (telephone 703-358-2171). Persons who use a telecommunications device for the deaf may call the Federal Information Relay Service at 800-877-8339.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>We request additional status information that may be available for any of the candidate species identified in this CNOR. We will consider this information to monitor changes in the status or LPN of candidate species and to manage candidates as we prepare listing documents and future revisions to the notice of review. We also request information on additional species to consider including as candidates as we prepare future updates of this notice.</P>
                    <HD SOURCE="HD1">Candidate Notice of Review</HD>
                    <HD SOURCE="HD2">Background</HD>
                    <P>
                        The Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ) (ESA), requires that we identify species of wildlife and plants that are endangered or threatened based on the best available scientific and commercial information. As defined in section 3 of the ESA, an endangered species is any species that is in danger of extinction throughout all or a significant portion of its range, and a threatened species is any species that is likely to become an endangered species within the foreseeable future throughout all or a significant portion of its range. Through the Federal rulemaking process, we add species that meet these definitions to the List of Endangered and Threatened Wildlife at 50 CFR 17.11 or the List of Endangered and Threatened Plants at 50 CFR 17.12. As part of this program, we maintain a list of species that we regard as candidates for listing. A candidate species is one for which we have on file sufficient information on biological vulnerability and threats to support a proposal for listing as endangered or threatened, but for which preparation and publication of a proposal is precluded by higher priority listing actions. We may identify a species as a candidate for listing after we have conducted an evaluation of its status on our own initiative, or resulting from a petition we have received. If we have made a positive finding on a petition to list a species, but we have found that listing is warranted but precluded by other higher priority listing actions, we will add the species to our list of candidates.
                    </P>
                    <P>
                        We maintain this list of candidates for a variety of reasons: (1) To notify the public that these species are facing threats to their survival; (2) to provide advance knowledge of potential listings that could affect decisions of environmental planners and developers; (3) to provide information that may stimulate and guide conservation efforts that will remove or reduce threats to these species and possibly make listing unnecessary; (4) to request input from interested parties to help us identify those candidate species that may not require protection under the ESA as well as additional species that may require the ESA's protections; and (5) to request necessary information for setting priorities for preparing listing proposals. We strongly encourage collaborative 
                        <PRTPAGE P="72451"/>
                        conservation efforts for candidate species, and offer technical and financial assistance to facilitate such efforts. For additional information regarding such assistance, please contact the appropriate Regional Office listed under Request for Information or visit our Web site, 
                        <E T="03">http://www.fws.gov/endangered/what-we-do/cca.html.</E>
                    </P>
                    <HD SOURCE="HD2">Previous Notices of Review</HD>
                    <P>
                        We have been publishing candidate notices of review (CNOR) since 1975. The most recent CNOR (prior to this CNOR) was published on November 22, 2013 (78 FR 70104). CNORs published since 1994 are available on our Web site, 
                        <E T="03">http://www.fws.gov/endangered/what-we-do/cnor.html.</E>
                         For copies of CNORs published prior to 1994, please contact the Branch of Communications and Candidate Conservation (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section above).
                    </P>
                    <P>On September 21, 1983, we published guidance for assigning an LPN for each candidate species (48 FR 43098). Using this guidance, we assign each candidate an LPN of 1 to 12, depending on the magnitude of threats, immediacy of threats, and taxonomic status; the lower the LPN, the higher the listing priority (that is, a species with an LPN of 1 would have the highest listing priority). Section 4(h)(3) of the ESA (16 U.S.C. 1533(h)(3)) requires the Secretary to establish guidelines for such a priority-ranking guidance system. As explained below, in using this system, we first categorize based on the magnitude of the threat(s), then by the immediacy of the threat(s), and finally by taxonomic status.</P>
                    <P>Under this priority-ranking system, magnitude of threat can be either “high” or “moderate to low.” This criterion helps ensure that the species facing the greatest threats to their continued existence receive the highest listing priority. It is important to recognize that all candidate species face threats to their continued existence, so the magnitude of threats is in relative terms. For all candidate species, the threats are of sufficiently high magnitude to put them in danger of extinction, or make them likely to become in danger of extinction in the foreseeable future. But for species with higher magnitude threats, the threats have a greater likelihood of bringing about extinction or are expected to bring about extinction on a shorter timescale (once the threats are imminent) than for species with lower magnitude threats. Because we do not routinely quantify how likely or how soon extinction would be expected to occur absent listing, we must evaluate factors that contribute to the likelihood and time scale for extinction. We therefore consider information such as: (1) The number of populations or extent of range of the species affected by the threat(s), or both; (2) the biological significance of the affected population(s), taking into consideration the life-history characteristics of the species and its current abundance and distribution; (3) whether the threats affect the species in only a portion of its range, and, if so, the likelihood of persistence of the species in the unaffected portions; (4) the severity of the effects and the rapidity with which they have caused or are likely to cause mortality to individuals and accompanying declines in population levels; (5) whether the effects are likely to be permanent; and (6) the extent to which any ongoing conservation efforts reduce the severity of the threat.</P>
                    <P>As used in our priority-ranking system, immediacy of threat is categorized as either “imminent” or “nonimminent,” and is based on when the threats will begin. If a threat is currently occurring or likely to occur in the very near future, we classify the threat as imminent. Determining the immediacy of threats helps ensure that species facing actual, identifiable threats are given priority for listing proposals over those for which threats are only potential or species that are intrinsically vulnerable to certain types of threats but are not known to be presently facing such threats.</P>
                    <P>Our priority ranking system has three categories for taxonomic status: Species that are the sole members of a genus; full species (in genera that have more than one species); and subspecies and distinct population segments of vertebrate species (DPS).</P>
                    <P>
                        The result of the ranking system is that we assign each candidate a listing priority number of 1 to 12. For example, if the threats are of high magnitude, with immediacy classified as imminent, the listable entity is assigned an LPN of 1, 2, or 3 based on its taxonomic status (
                        <E T="03">i.e.,</E>
                         a species that is the only member of its genus would be assigned to the LPN 1 category, a full species to LPN 2, and a subspecies or DPS would be assigned to LPN 3). In summary, the LPN ranking system provides a basis for making decisions about the relative priority for preparing a proposed rule to list a given species. No matter which LPN we assign to a species, each species included in this notice as a candidate is one for which we have sufficient information to prepare a proposed rule for listing because it is in danger of extinction or likely to become endangered within the foreseeable future throughout all or a significant portion of its range.
                    </P>
                    <P>
                        For more information on the process and standards used in assigning LPNs, a copy of the 1983 guidance is available on our Web site at: 
                        <E T="03">http://www.fws.gov/endangered/esa-library/pdf/48fr43098-43105.pdf.</E>
                         Information on the LPN assigned to a particular species is summarized in this CNOR and the species assessment for each candidate contains the LPN chart and a rationale for the determination of the magnitude and immediacy of threat(s) and assignment of the LPN.
                    </P>
                    <P>This revised notice supersedes all previous animal, plant, and combined candidate notices of review for native species and supersedes previous 12-month warranted-but-precluded petition findings for those candidate species that were petitioned for listing.</P>
                    <HD SOURCE="HD2">Summary of This CNOR</HD>
                    <P>
                        Since publication of the previous CNOR on November 22, 2013 (78 FR 70104), we reviewed the available information on candidate species to ensure that a proposed listing is justified for each species, and reevaluated the relative LPN assigned to each species. We also evaluated the need to emergency list any of these species, particularly species with higher priorities (
                        <E T="03">i.e.,</E>
                         species with LPNs of 1, 2, or 3). This review and reevaluation ensures that we focus conservation efforts on those species at greatest risk.
                    </P>
                    <P>
                        In addition to reviewing candidate species since publication of the last CNOR, we have worked on findings in response to petitions to list species, and on proposed and final determinations for rules to list species under the ESA. Some of these findings and determinations have been completed and published in the 
                        <E T="04">Federal Register</E>
                        , while work on others is still under way (see 
                        <E T="03">Preclusion and Expeditious Progress,</E>
                         below, for details).
                    </P>
                    <P>
                        Based on our review of the best available scientific and commercial information, with this CNOR, we are identifying 23 new candidates, we change the LPN for one candidate, and determine that a listing proposal is not warranted for one species and thus remove it from candidate status (see Candidate Removals, below). Combined with the other decisions published separately from this CNOR, a total of 146 species (67 plant and 79 animal species) are now candidates awaiting preparation of rules proposing their listing. These 146 species, along with the 36 species currently proposed for listing (including 1 species proposed for listing due to similarity in appearance), are included in Table 1.
                        <PRTPAGE P="72452"/>
                    </P>
                    <P>Table 2 lists the changes from the previous CNOR, and includes 49 species identified in the previous CNOR as either proposed for listing or classified as candidates that are no longer in those categories. This includes 33 species for which we published a final listing rule, 11 candidate species for which we published a separate not-warranted finding and removed from candidate status, 3 species for which we published a withdrawal of a proposed rule, 1 species for which we published a separate notice of removal from candidate status, and the 1 species in this notice that we have determined does not meet the definition of an endangered or threatened species and therefore does not warrant listing. We have removed this species from candidate status in this CNOR.</P>
                    <HD SOURCE="HD1">New Candidates</HD>
                    <P>We have identified 23 new candidate species through this notice discussed below.</P>
                    <HD SOURCE="HD2">Birds</HD>
                    <P>
                        Ma'oma'o (
                        <E T="03">Gymnomyza samoensis</E>
                        )—The ma'oma'o is a large, dusky olive-green honeyeater that is known for making a variety of loud distinctive calls. The genus 
                        <E T="03">Gymnomyza</E>
                         consists of three honeyeaters restricted to a few islands in the southwestern Pacific. The ma'oma'o is endemic to Upolu and Savaii, Independent Samoa (Samoa), and Tutuila Island, American Samoa. The ma'oma'o is now believed to be extirpated from Tutuila Island, American Samoa. It is currently only found in small populations on the islands of Savaii and Upolu in Samoa. The ma'oma'o is primarily restricted to mature, well-developed, moist, mossy forests at upper elevations. Monitoring over the last decade has provided evidence of a decline in the relative abundance of the species. In 2007, the total population was estimated to be approximately 500 individuals.
                    </P>
                    <P>
                        Little mature forest remains in Samoa, and the loss of forested habitat due to logging, agricultural clearing, and catastrophic storms is the primary threat to the ma'oma'o. Two storms in the 1990s, Cyclones Ofa (1990) and Val (1991), destroyed much of the forested habitat in Samoa, reducing forest canopy cover by 73 percent. In 2012, Cyclone Evan caused additional severe forest damage. Loss of mature forest is likely to affect the ma'oma'o by reducing breeding and foraging habitat, increasing forest fragmentation, and increasing the abundance and diversity of invasive species. Other threats to the species include habitat degradation, predation by nonnative species, and small population size. Habitat quality has degraded with the loss of closed forest space and the spread of nonnative invasive weeds. Nest predation by rats (
                        <E T="03">Rattus</E>
                         spp.) and feral cats (
                        <E T="03">Felis catus</E>
                        ) is an important threat to many island birds, including the ma'oma'o, and may impede population growth. Small populations are more susceptible to inbreeding depression (reduced reproductive vigor) and extirpation from stochastic events (
                        <E T="03">e.g.,</E>
                         inclement weather, population demographics, and altered predation patterns). Based on our evaluation that these ongoing threats pose an imminent risk of a high magnitude, we assign a LPN of 2 for this species.
                    </P>
                    <HD SOURCE="HD2">Flowering Plants</HD>
                    <P>
                        Eighteen Hawaiian flowering plants (
                        <E T="03">Cyanea kauaulaensis, Cyperus neokunthianus, Cyrtandra hematos, Exocarpos menziesii, Kadua haupuensis, Labordia lorenciana, Lepidium orbiculare, Phyllostegia brevidens, Phyllostegia helleri, Phyllostegia stachyoides, Portulaca villosa, Pritchardia bakeri, Sanicula sandwicensis, Santalum involutum, Schiedea diffusa</E>
                         ssp. 
                        <E T="03">diffusa, Sicyos lanceoloideus, Stenogyne kaalae</E>
                         ssp. 
                        <E T="03">sherffii, Wikstromoemia skottsbergiana</E>
                        )—Each of these 18 species is endemic to one or more islands in the State of Hawaii ((
                        <E T="03">Cyanea kauaulaensis</E>
                         (Maui), 
                        <E T="03">Cyperus neokunthianus</E>
                         (Maui), 
                        <E T="03">Cyrtandra hematos</E>
                         (Molokai), 
                        <E T="03">Exocarpos menziesii</E>
                         (Hawaii Island; extirpated from Lanai), 
                        <E T="03">Kadua haupuensis</E>
                         (Kauai), 
                        <E T="03">Labordia lorenciana</E>
                         (Kauai), 
                        <E T="03">Lepidium orbiculare</E>
                         (Kauai), 
                        <E T="03">Phyllostegia brevidens</E>
                         (Maui; extirpated from Hawaii Island), 
                        <E T="03">Phyllostegia helleri</E>
                         (Kauai), 
                        <E T="03">Phyllostegia stachyoides</E>
                         (Maui, Molokai, and Hawaii Island), 
                        <E T="03">Portulaca villosa</E>
                         (Maui and Nihoa), 
                        <E T="03">Pritchardia bakeri</E>
                         (Oahu), 
                        <E T="03">Sanicula sandwicensis</E>
                         (Maui and Hawaii Island), 
                        <E T="03">Santalum involutum</E>
                         (Kauai), 
                        <E T="03">Schiedea diffusa</E>
                         ssp. 
                        <E T="03">diffusa</E>
                         (Maui), 
                        <E T="03">Sicyos lanceoloideus</E>
                         (Kauai and Oahu), 
                        <E T="03">Stenogyne kaalae</E>
                         ssp. 
                        <E T="03">sherffii</E>
                         (Oahu), and 
                        <E T="03">Wikstromoemia skottsbergiana</E>
                         (Kauai)), and each is negatively affected by nonnative animals and plants.
                    </P>
                    <P>Introduced, nonnative animals damage and destroy plants and seeds, modify habitat, create habitat more conducive to nonnative plant introductions, and spread nonnative plant seeds. Nonnative plants displace and outcompete native species. Introduced, nonnative plants and animals are serious and ongoing threats to these species rangewide, and these threats are increased by the continued inadequacy of existing protective regulations. In addition, small population size (each species has fewer than 100 individuals) is a serious and ongoing threat to each of these species because (1) they may experience reduced reproductive vigor due to ineffective pollination or inbreeding depression; (2) they may experience reduced levels of genetic variability, leading to diminished capacity to adapt and respond to environmental changes, thereby lessening the probability of long-term persistence; and (3) a single catastrophic event may result in extirpation of remaining populations and extinction of the species. Climate change may pose a threat to the ecosystems that support these species, thus exacerbating the effects of the aforementioned threats. There are varying degrees of conservation efforts ongoing for these species; however, at a minimum, all of these species are listed on the Hawaii Plant Extinction Prevention Program (PEPP) species list. Species on the PEPP list are prioritized for monitoring, surveys, collection and storing of seeds, propagation, and outplanting. The threats to each of these species are imminent and of high magnitude, leading to a relatively high likelihood of extinction. Therefore, we assign a LPN of 2 for the above plants that are full species and an LPN of 3 for those that are subspecies or varieties.</P>
                    <HD SOURCE="HD2">Ferns and Allies</HD>
                    <P>
                        Four Hawaiian ferns (
                        <E T="03">Asplenium diellaciniatum, Deparia kaalaana, Dryopteris glabra</E>
                         var. 
                        <E T="03">pusilla, Hypolepis hawaiiensis</E>
                         var. 
                        <E T="03">mauiensis</E>
                        )—Each of these four species is endemic to one or more islands in the State of Hawaii (
                        <E T="03">Asplenium diellaciniatum</E>
                         (Kauai), 
                        <E T="03">Deparia kaalaana</E>
                         (Maui; extirpated from Kauai and Hawaii Island), 
                        <E T="03">Dryopteris glabra</E>
                         var. 
                        <E T="03">pusilla</E>
                         (Kauai), 
                        <E T="03">Hypolepis hawaiiensis</E>
                         var. 
                        <E T="03">mauiensis</E>
                         (Maui)); and each is negatively affected by nonnative animals and plants. Introduced, nonnative animals damage and destroy plants and seeds, modify habitat, create habitat more conducive to nonnative plant introductions, and spread nonnative plant seeds. Nonnative plants displace and outcompete native species. Introduced nonnative plants and animals are serious and ongoing threats to these species rangewide, and these threats are increased by the continued inadequacy of existing protective regulations. In addition, small population size (each species has fewer than 100 individuals) is a serious and ongoing threat to each of these species because (1) they may experience reduced reproductive vigor due to ineffective pollination or inbreeding depression; (2) they may 
                        <PRTPAGE P="72453"/>
                        experience reduced levels of genetic variability, leading to diminished capacity to adapt and respond to environmental changes, thereby lessening the probability of long-term persistence; and (3) a single catastrophic event may result in extirpation of remaining populations and extinction of the species. Climate change may pose a threat to the ecosystems that support these species, thus exacerbating the effects of the aforementioned threats. There are varying degrees of conservation efforts ongoing for these species; however, at a minimum, all of these species are listed on the Hawaii Plant Extinction Prevention Program (PEPP) species list. Species on the PEPP list are prioritized for monitoring, surveys, collection and storing of seeds, propagation, and outplanting. The threats to each of these species are imminent and of high magnitude, leading to a relatively high likelihood of extinction. Therefore, we assign a LPN of 2 for 
                        <E T="03">Asplenium diellaciniatum</E>
                         and 
                        <E T="03">Deparia kaalaana</E>
                         and an LPN of 3 for 
                        <E T="03">Dryopteris glabra</E>
                         var. 
                        <E T="03">pusilla</E>
                         and 
                        <E T="03">Hypolepis hawaiiensis</E>
                         var. 
                        <E T="03">mauiensis.</E>
                    </P>
                    <HD SOURCE="HD1">Listing Priority Changes in Candidates</HD>
                    <P>We reviewed the LPN for all candidate species and are changing the number for the following species discussed below.</P>
                    <HD SOURCE="HD2">Birds</HD>
                    <P>
                        Sprague's pipit (
                        <E T="03">Anthus spragueii</E>
                        )—The Sprague's pipit is a small grassland bird characterized by its high breeding flight display and otherwise very secretive behavior. Sprague's pipits are strongly associated with native prairie (land that has never been plowed), especially on the breeding grounds. Its current breeding range includes portions of Montana, North Dakota, South Dakota, and Canada. The wintering range includes south-central and southeast Arizona, southern New Mexico, Texas, southern Oklahoma, southern Arkansas, northwest Mississippi, southern Louisiana, and northern Mexico; the vast majority of the U.S. winter sightings have been in Texas. During migration, the species has been sighted in areas outside of the direct flight path between its breeding and wintering sites, including Michigan, western Ontario, Ohio, Massachusetts, and Gulf and Atlantic States from Mississippi east and north to South Carolina. Sprague's pipits also have been sighted in California during fall migration.
                    </P>
                    <P>The primary stressor to the species is habitat conversion on the breeding grounds. The Breeding Bird Survey shows a long-term decline from 1966 through 2012. From 2002 through 2012, however, the long-term population decline has leveled off and currently, there is no discernable trend. The Christmas Bird Count data also indicates that the population decline has stopped and the population trend has no direction, either increasing or decreasing between 2003 and 2012.</P>
                    <P>In the Service's 12-month finding published on September 15, 2010, we identified oil and gas development and associated infrastructure as having a strong negative influence on the species based upon the available information at that time. New information suggests that Sprague's pipit avoidance response of these features is highly variable across the range and thus the species' response to oil and gas development and roads does not indicate that these are a threat.</P>
                    <P>Landscape modelling to predict Sprague's pipit habitat use on the breeding range indicates the population is concentrated in north-central Montana, Alberta, and Saskatchewan, Canada. Analysis of the likelihood of prairie conversion in the area where most pipits occur suggests that the risk of widespread conversion is low, with the most likely risk scenario of future conversion to cropland predicting a relatively low proportion (10-15 percent) of the breeding population affected.</P>
                    <P>On the wintering range, conversion of prairie to cropland appears to be accelerating. The species is widely distributed and mobile during winter, but grassland conversion is ongoing and apparently widespread. At this time, we believe that the species' trends can be explained by the habitat changes that have occurred on the breeding range; however, we will be more closely assessing the changes to the wintering range and whether those changes threaten the Sprague's pipit.</P>
                    <P>
                        The threats to the Sprague's pipit described above are moderate to low in magnitude. Because of the relatively large population remaining and the stable-to-uncertain (
                        <E T="03">i.e.</E>
                         not showing a clear decline) trends shown by surveys on both the breeding and wintering grounds, the potential decline is nonimminent. In addition, the threat from conversion of habitat on the breeding grounds is now nonimment. Therefore, we are revising the LPN from 8 to an 11.
                    </P>
                    <HD SOURCE="HD1">Candidate Removals</HD>
                    <P>As summarized below, we have evaluated the threats to the following species and considered factors that, individually and in combination, currently or potentially could pose a risk to the species and its habitats. After a review of the best available scientific and commercial data, we conclude that listing this species under the Endangered Species Act is not warranted because this species is not likely to become an endangered species within the foreseeable future throughout all or a significant portion of its range. Therefore, we no longer consider it to be a candidate species for listing. We will continue to monitor the status of this species and to accept additional information and comments concerning this finding. We will reconsider our determination in the event that new information indicates that the threats to the species are of a considerably greater magnitude or imminence than identified through assessments of information contained in our files, as summarized here.</P>
                    <HD SOURCE="HD2">Flowering Plants</HD>
                    <P>
                        <E T="03">Astragalus cusickii</E>
                         var. 
                        <E T="03">packardiae</E>
                         (Packard's milkvetch)—The following summary is based on information contained in our files. Packard's milkvetch is narrowly endemic to a specific group of light-colored sedimentary outcrops in southwestern Idaho. The total range of the species covers approximately 26 square kilometers (km
                        <SU>2</SU>
                        ) (10 square miles (mi
                        <SU>2</SU>
                        )) in Payette County. Suboccurrences of Packard's milkvetch, which are typically represented by individual occupied outcrops, are found at elevations ranging from 793 to 915 meters (m) (2,600 to 3,000 feet (ft)). Occupied outcrops tend to be found on steep, south- to west-facing slopes, and are relatively sparsely vegetated.
                    </P>
                    <P>Packard's milkvetch became a candidate species in 2010, based on the identified primary threat of habitat degradation due to off highway vehicles (OHVs). In response, on December 13, 2013, the Bureau of Land Management (BLM) made a decision that permanently closed 5,620 acres within and near Packard's milkvetch habitat to OHV use, covering 68 percent of the species' occurrences. Monitoring data collected since the closure was implemented in 2011 indicates that the OHV closure has been effective at eliminating the primary threat to the species throughout a large majority of the species' range.</P>
                    <P>
                        Other natural and anthropogenic activities identified at the time it was designated a candidate included an altered wildfire regime due to invasive nonnative plant species and livestock use. There was little data at the time to suggest whether these potential threats were significant, but out of an abundance of caution, the Idaho Fish and Wildlife Office (IFWO) considered 
                        <PRTPAGE P="72454"/>
                        these activities along with the OHV monitoring data from 2008-2010 when making the 2010 decision. However, by 2013, a 5-year monitoring dataset (2008-2013) suggested a stable population and no association between cover of nonnative plant species and wildfire and the abundance of Packard's milkvetch.
                    </P>
                    <P>In 2010, the population of Packard's milkvetch was estimated at approximately 5,000 plants located within 26 suboccurrences with abundance ranges from 3 to approximately 500 plants per suboccurrence. Surveys in 2012 documented several additional occupied outcrops collectively totaling approximately 2,000 individuals, which revised the range-wide population estimate to 6,500 plants occurring within 28 suboccurrences. The 5-year monitoring dataset (2008-2013) has suggested a stable population overall.</P>
                    <P>
                        Therefore, based on (1) the reduction of the species' primary threat (
                        <E T="03">i.e.,</E>
                         OHV use), (2) the increase in number of known suboccurrences and resulting increase in the overall population, and (3) the species' overall stable population status over a 5-year monitoring period, we find that listing of Packard's milkvetch as threatened or endangered throughout all or a significant portion of its range is no longer warranted; the species no longer meets the definition of a candidate species, and we are removing it from candidate status.
                    </P>
                    <P>In addition to the factors that led us to conclude that Packard's milkvetch no longer warrants candidate status, the BLM and IFWO signed a 20-year Candidate Conservation Agreement (CCA) on December 20, 2013, which further supports the BLM's OHV closure decision and commits to continued enforcement and monitoring of the OHV closure. The CCA also outlines the BLM's plans for long-term monitoring and future proactive conservation measures to address new potential threats that may arise.</P>
                    <HD SOURCE="HD1">Petition Findings</HD>
                    <P>The ESA provides two mechanisms for considering species for listing. One method allows the Secretary, on the Secretary's own initiative, to identify species for listing under the standards of section 4(a)(1). We implement this authority through the candidate program, discussed above. The second method for listing a species provides a mechanism for the public to petition us to add a species to the Lists. The CNOR serves several purposes as part of the petition process: (1) In some instances (in particular, for petitions to list species that the Service has already identified as candidates on its own initiative), it serves as the initial petition finding; (2) for candidate species for which the Service has made a warranted-but-precluded petition finding, it serves as a “resubmitted” petition finding that the ESA requires the Service to make each year; and (3) it documents the Service's compliance with the statutory requirement to monitor the status of species for which listing is warranted but precluded, and to ascertain if they need emergency listing.</P>
                    <P>First, the CNOR serves as an initial petition finding in some instances. Under section 4(b)(3)(A), when we receive a listing petition, we must determine within 90 days, to the maximum extent practicable, whether the petition presents substantial information indicating that listing may be warranted (a “90-day finding”). If we make a positive 90-day finding, we must promptly commence a status review of the species under section 4(b)(3)(A); we must then make and publish one of three possible findings within 12 months of the receipt of the petition (a “12-month finding”):</P>
                    <P>(1) The petitioned action is not warranted;</P>
                    <P>(2) The petitioned action is warranted (in which case we are required to promptly publish a proposed regulation to implement the petitioned action; once we publish a proposed rule for a species, sections 4(b)(5) and 4(b)(6) of the ESA govern further procedures, regardless of whether we issued the proposal in response to a petition); or</P>
                    <P>(3) The petitioned action is warranted, but (a) the immediate proposal of a regulation and final promulgation of a regulation implementing the petitioned action is precluded by pending proposals to determine whether any species is endangered or threatened, and (b) expeditious progress is being made to add qualified species to the Lists. We refer to this third option as a “warranted-but-precluded finding.”</P>
                    <P>We define “candidate species” to mean those species for which the Service has on file sufficient information on biological vulnerability and threat(s) to support issuance of a proposed rule to list, but for which issuance of the proposed rule is precluded (61 FR 64481; December 5, 1996). The standard for making a species a candidate through our own initiative is identical to the standard for making a warranted-but-precluded 12-month petition finding on a petition to list, and we add all petitioned species for which we have made a warranted-but-precluded 12-month finding to the candidate list.</P>
                    <P>
                        Therefore, all candidate species identified through our own initiative already have received the equivalent of substantial 90-day and warranted-but-precluded 12-month findings. Nevertheless, we review the status of the newly petitioned candidate species and through this CNOR publish specific section 4(b)(3) findings (
                        <E T="03">i.e.,</E>
                         substantial 90-day and warranted-but-precluded 12-month findings) in response to the petitions to list these candidate species. We publish these findings as part of the first CNOR following receipt of the petition. We have identified the candidate species for which we received petitions by the code “C*” in the category column on the left side of Table 1 below.
                    </P>
                    <P>Second, the CNOR serves as a “resubmitted” petition finding. Section 4(b)(3)(C)(i) of the ESA requires that when we make a warranted-but-precluded finding on a petition, we treat the petition as one that is resubmitted on the date of the finding. Thus, we must make a 12-month petition finding in compliance with section 4(b)(3)(B) of the ESA at least once a year, until we publish a proposal to list the species or make a final not-warranted finding. We make these annual findings for petitioned candidate species through the CNOR. These annual findings supercede any findings from previous CNORs and the initial 12-month warranted-but-precluded finding, although all previous findings are part of the administrative record for the new finding, and we may rely upon them or incorporate them by reference in the new finding as appropriate.</P>
                    <P>
                        Third, through undertaking the analysis required to complete the CNOR, the Service determines if any candidate species needs emergency listing. Section 4(b)(3)(C)(iii) of the ESA requires us to “implement a system to monitor effectively the status of all species” for which we have made a warranted-but-precluded 12-month finding, and to “make prompt use of the [emergency listing] authority [under section 4(b)(7)] to prevent a significant risk to the well being of any such species.” The CNOR plays a crucial role in the monitoring system that we have implemented for all candidate species by providing notice that we are actively seeking information regarding the status of those species. We review all new information on candidate species as it becomes available, prepare an annual species assessment form that reflects monitoring results and other new information, and identify any species for which emergency listing may be appropriate. If we determine that emergency listing is appropriate for any 
                        <PRTPAGE P="72455"/>
                        candidate, we will make prompt use of the emergency listing authority under section 4(b)(7). For example, on August 10, 2011, we emergency listed the Miami blue butterfly (76 FR 49542). We have been reviewing and will continue to review, at least annually, the status of every candidate, whether or not we have received a petition to list it. Thus, the CNOR and accompanying species assessment forms constitute the Service's system for monitoring and making annual findings on the status of petitioned species under sections 4(b)(3)(C)(i) and 4(b)(3)(C)(iii) of the ESA.
                    </P>
                    <P>A number of court decisions have elaborated on the nature and specificity of information that we must consider in making and describing the petition findings in the CNOR. The CNOR that published on November 9, 2009 (74 FR 57804), describes these court decisions in further detail. As with previous CNORs, we continue to incorporate information of the nature and specificity required by the courts. For example, we include a description of the reasons why the listing of every petitioned candidate species is both warranted and precluded at this time. We make our determinations of preclusion on a nationwide basis to ensure that the species most in need of listing will be addressed first and also because we allocate our listing budget on a nationwide basis (see below). Regional priorities can also be discerned from Table 1, below, which includes the lead region and the LPN for each species. Our preclusion determinations are further based upon our budget for listing activities for unlisted species only, and we explain the priority system and why the work we have accomplished does preclude action on listing candidate species.</P>
                    <P>
                        In preparing this CNOR, we reviewed the current status of, and threats to, the 112 candidates for which we have received a petition to list and the 5 listed species for which we have received a petition to reclassify from threatened to endangered, where we found the petitioned action to be warranted but precluded. We find that the immediate issuance of a proposed rule and timely promulgation of a final rule for each of these species, except for the Selkirk ecosystem population and the Cabinet-Yaak ecosystem population of Grizzly bear (see 
                        <E T="03">Petitions To Reclassify Species Already Listed</E>
                        ), has been, for the preceding months, and continues to be, precluded by higher priority listing actions. Additional information that is the basis for this finding is found in the species assessments and our administrative record for each species.
                    </P>
                    <P>Our review included updating the status of, and threats to, petitioned candidate or listed species for which we published findings, under section 4(b)(3)(B) of the ESA, in the previous CNOR. We have incorporated new information we gathered since the prior finding and, as a result of this review, we are making continued warranted-but-precluded 12-month findings on the petitions for these species.</P>
                    <P>The immediate publication of proposed rules to list these species was precluded by our work on higher priority listing actions, listed below, during the period from October 1, 2013, through September 30, 2014. Below we describe the actions that continue to preclude the immediate proposal and final promulgation of a regulation implementing each of the petitioned actions for which we have made a warranted-but-precluded finding, and we describe the expeditious progress we are making to add qualified species to, and remove species from, the Lists. We will continue to monitor the status of all candidate species, including petitioned species, as new information becomes available to determine if a change in status is warranted, including the need to emergency-list a species under section 4(b)(7) of the ESA.</P>
                    <P>
                        In addition to identifying petitioned candidate species in Table 1 below, we also present brief summaries of why each of these candidates warrants listing. More complete information, including references, is found in the species assessment forms. You may obtain a copy of these forms from the Regional Office having the lead for the species, or from the Fish and Wildlife Service's Internet Web site: 
                        <E T="03">http://ecos.fws.gov/tess_public/pub/candidateSpecies.jsp.</E>
                         As described above, under section 4 of the ESA, we identify and propose species for listing based on the factors identified in section 4(a)(1), and section 4 also provides a mechanism for the public to petition us to add species to the Lists of Endangered or Threatened Wildlife and Plants under the ESA.
                    </P>
                    <HD SOURCE="HD2">Preclusion and Expeditious Progress</HD>
                    <P>To make a finding that a particular action is warranted but precluded, the Service must make two determinations: (1) That the immediate proposal and timely promulgation of a final regulation is precluded by pending listing proposals and (2) that expeditious progress is being made to add qualified species to either of the lists and to remove species from the lists. 16 U.S.C. 1533(b)(3)(B)(iii).</P>
                    <HD SOURCE="HD3">Preclusion</HD>
                    <P>A listing proposal is precluded if the Service does not have sufficient resources available to complete the proposal, because there are competing demands for those resources, and the relative priority of those competing demands is higher. Thus, in any given fiscal year (FY), multiple factors dictate whether it will be possible to undertake work on a listing proposal regulation or whether promulgation of such a proposal is precluded by higher priority listing actions—(1) The amount of resources available for completing the listing function, (2) the estimated cost of completing the proposed listing, and (3) the Service's workload and prioritization of the proposed listing in relation to other actions.</P>
                    <HD SOURCE="HD3">Available Resources</HD>
                    <P>The resources available for listing actions are determined through the annual Congressional appropriations process. In FY 1998 and for each fiscal year since then, Congress has placed a statutory cap on funds that may be expended for the Listing Program. This spending cap was designed to prevent the listing function from depleting funds needed for other functions under the ESA (for example, recovery functions, such as removing species from the Lists), or for other Service programs (see House Report 105-163, 105th Congress, 1st Session, July 1, 1997). The funds within the spending cap are available to support work involving the following listing actions: Proposed and final listing rules; 90-day and 12-month findings on petitions to add species to the Lists or to change the status of a species from threatened to endangered; annual “resubmitted” petition findings on prior warranted-but-precluded petition findings as required under section 4(b)(3)(C)(i) of the ESA; critical habitat petition findings; proposed and final rules designating critical habitat; and litigation-related, administrative, and program-management functions (including preparing and allocating budgets, responding to Congressional and public inquiries, and conducting public outreach regarding listing and critical habitat).</P>
                    <P>
                        We cannot spend more for the Listing Program than the amount of funds within the spending cap without violating the Anti-Deficiency Act (see 31 U.S.C. 1341(a)(1)(A)). In addition, since FY 2002, the Service's budget has included a critical habitat subcap to ensure that some funds are available for completing Listing Program actions other than critical habitat designations 
                        <PRTPAGE P="72456"/>
                        (“The critical habitat designation subcap will ensure that some funding is available to address other listing activities” (House Report No. 107-103, 107th Congress, 1st Session. June 19, 2001)). In FY 2002 and each year until FY 2006, the Service had to use virtually the entire critical habitat subcap to address court-mandated designations of critical habitat, and consequently none of the critical habitat subcap funds were available for other listing activities. In some FYs since 2006, we have been able to use some of the critical habitat subcap funds to fund proposed listing determinations for high-priority candidate species. In other FYs, while we were unable to use any of the critical habitat subcap funds to fund proposed listing determinations, we did use some of this money to fund the critical habitat portion of some proposed listing determinations so that the proposed listing determination and proposed critical habitat designation could be combined into one rule, thereby being more efficient in our work. In FY 2014, based on the Service's workload, we were able to use some of the critical habitat subcap funds to fund proposed listing determinations.
                    </P>
                    <P>For FY 2012 Congress also put in place two additional subcaps within the listing cap: One for listing actions for foreign species and one for petition findings. As with the critical habitat subcap, if the Service does not need to use all of the funds within the subcap, we are able to use the remaining funds for completing proposed or final listing determinations. In FY 2014, based on the Service's workload, we were able to use some of the funds within the foreign species subcap and the petitions subcap to fund proposed listing determinations.</P>
                    <P>We make our determinations of preclusion on a nationwide basis to ensure that the species most in need of listing will be addressed first, and also because we allocate our listing budget on a nationwide basis. Through the listing cap, the three subcaps, and the amount of funds needed to complete court-mandated actions within those subcaps, Congress and the courts have in effect determined the amount of money available for other listing activities nationwide. Therefore, the funds in the listing cap—other than those within the subcaps needed to comply with court orders or court-approved settlement agreements requiring critical habitat actions for already-listed species, listing actions for foreign species, and petition findings—set the framework within which we make our determinations of preclusion and expeditious progress.</P>
                    <P>For FY 2014, on January 17, 2014, Congress passed a Consolidated Appropriations Act, 2014 (Pub. L. 113-76), which provided funding through September 30, 2014. In particular, it included an overall spending cap of $20,515,000 for the listing program. Of that, no more than $1,504,000 could be used for listing actions for foreign species, and no more than $1,501,000 could be used to make 90-day or 12-month findings on petitions. The Service thus had $ 12,905,000 available to work on proposed and final listing determinations for domestic species. In addition, if the Service had funding available within the critical habitat, foreign species, or petition subcaps after those workloads had been completed, it could use those funds to work on listing actions other than critical habitat designations or foreign species.</P>
                    <P>
                        <E T="03">Costs of Listing Actions.</E>
                         The work involved in preparing various listing documents can be extensive, and may include, but is not limited to: Gathering and assessing the best scientific and commercial data available and conducting analyses used as the basis for our decisions; writing and publishing documents; and obtaining, reviewing, and evaluating public comments and peer review comments on proposed rules and incorporating relevant information into final rules. The number of listing actions that we can undertake in a given year also is influenced by the complexity of those listing actions; that is, more complex actions generally are more costly. The median cost for preparing and publishing a 90-day finding is $39,276; for a 12-month finding, $100,690; for a proposed rule with critical habitat, $345,000; and for a final listing rule with critical habitat, $305,000.
                    </P>
                    <P>
                        <E T="03">Prioritizing Listing Actions.</E>
                         The Service's Listing Program workload is broadly composed of four types of actions, which the Service prioritizes as follows: (1) Compliance with court orders and court-approved settlement agreements requiring that petition findings or listing or critical habitat determinations be completed by a specific date; (2) essential litigation-related, administrative, and listing program-management functions; (3) section 4 (of the Act) listing and critical habitat actions with absolute statutory deadlines; and (4) section 4 listing actions that do not have absolute statutory deadlines. In the last few years, the Service received many new petitions and a single petition to list 404 species, significantly increasing the number of actions within the second category of our workload—actions that have absolute statutory deadlines. As a result of the petitions to list hundreds of species, we currently have over 450 12-month petition findings yet to be initiated and completed.
                    </P>
                    <P>An additional way in which we prioritize work in the section 4 program is application of the listing priority guidelines (48 FR 43098; September 21, 1983). Under those guidelines, we assign each candidate an LPN of 1 to 12, depending on the magnitude of threats (high or moderate to low), immediacy of threats (imminent or nonimminent), and taxonomic status of the species (in order of priority: Monotypic genus (a species that is the sole member of a genus), species, or part of a species (subspecies or distinct population segment)). The lower the listing priority number, the higher the listing priority (that is, a species with an LPN of 1 would have the highest listing priority). A species with a higher LPN would generally be precluded from listing by species with lower LPNs, unless work on a proposed rule for the species with the higher LPN can be combined with work on a proposed rule for other high-priority species. In addition to prioritizing species with our 1983 guidance, because of the large number of high-priority species we have had in the recent past, we had further ranked the candidate species with an LPN of 2 by using the following extinction-risk type criteria: International Union for the Conservation of Nature and Natural Resources (IUCN) Red list status/rank, Heritage rank (provided by NatureServe), Heritage threat rank (provided by NatureServe), and species currently with fewer than 50 individuals, or 4 or fewer populations. Those species with the highest IUCN rank (critically endangered), the highest Heritage rank (G1), the highest Heritage threat rank (substantial, imminent threats), and currently with fewer than 50 individuals, or fewer than 4 populations, originally comprised a group of approximately 40 candidate species (“Top 40”). These 40 candidate species had the highest priority to receive funding to work on a proposed listing determination and we used this to formulate our work plan for FYs 2010 and 2011 that was included in the MDL Settlement Agreement (see below), as well as for work on proposed and final listing rules for the remaining candidate species with LPNs of 2 and 3.</P>
                    <P>
                        Finally, proposed rules for reclassification of threatened species to endangered species are lower priority, because as listed species, they are already afforded the protections of the Act and implementing regulations. However, for efficiency reasons, we may choose to work on a proposed rule to 
                        <PRTPAGE P="72457"/>
                        reclassify a species to endangered if we can combine this with work that is subject to a court order or court-approved deadline.
                    </P>
                    <P>Since before Congress first established the spending cap for the Listing Program in 1998, the Listing Program workload has required considerably more resources than the amount of funds Congress has allowed for the Listing Program. It is therefore important that we be as efficient as possible in our listing process. As we implement our listing work plan and work on proposed rules for the highest priority species in the next several years, we are preparing multi-species proposals when appropriate, and these may include species with lower priority if they overlap geographically or have the same threats as one of the highest priority species. In addition, we take into consideration the availability of staff resources when we determine which high-priority species will receive funding to minimize the amount of time and resources required to complete each listing action.</P>
                    <P>
                        <E T="03">Listing Program Workload.</E>
                         Each FY we determine, based on the amount of funding Congress has made available within the Listing Program spending cap, specifically which actions we will have the resources to work on in that FY. We then prepare Allocation Tables that identify the actions that we are funding for that FY, and how much we estimate it will cost to complete each action; these Allocation Tables are part of our record for this notice and the listing program. Our Allocation Table for FY 2012, which incorporated the Service's approach to prioritizing its workload, was adopted as part of a settlement agreement in a case before the U.S. District Court for the District of Columbia (Endangered Species Act Section 4 Deadline Litigation, No. 10-377 (EGS), MDL Docket No. 2165 (“MDL Litigation”), Document 31-1 (D.D.C. May 10, 2011) (“MDL Settlement Agreement”)). The requirements of paragraphs 1 through 7 of that settlement agreement, combined with the work plan attached to the agreement as Exhibit B, reflected the Service's Allocation Tables for FY 2011 and FY 2012. In addition, paragraphs 2 through 7 of the agreement require the Service to take numerous other actions through FY 2017—in particular, complete either a proposed listing rule or a not-warranted finding for all 251 species designated as “candidates” in the 2010 candidate notice of review (“CNOR”) before the end of FY 2016, and complete final listing determinations for those species proposed for listing within the statutory deadline (usually one year from the proposal). Paragraph 10 of that settlement agreement sets forth the Service's conclusion that “fulfilling the commitments set forth in this Agreement, along with other commitments required by court orders or court-approved settlement agreements already in existence at the signing of this Settlement Agreement (listed in Exhibit A), will require substantially all of the resources in the Listing Program.” As part of the same lawsuit, the court also approved a separate settlement agreement with the other plaintiff in the case; that settlement agreement requires the Service to complete additional actions in specific fiscal years—including 12-month petition findings for 11 species, 90-day petition findings for 477 species, and proposed listing determinations or not-warranted findings for 39 species.
                    </P>
                    <P>These settlement agreements have led to a number of results that affect our preclusion analysis. First, the Service has been, and will continue to be, limited in the extent to which it can undertake additional actions within the Listing Program through FY 2017, beyond what is required by the MDL Settlement Agreements. Second, because the settlement is court approved, two broad categories of actions now fall within the Service's highest priority (compliance with a court order): (1) The actions required to be completed in FY 2014 by the MDL Settlement Agreements; and (2) completion, before the end of FY 2016, of proposed listings or not-warranted findings for most of the candidate species identified in this CNOR (in particular, for those candidate species that were included in the 2010 CNOR). Therefore, each year, one of the Service's highest priorities is to make steady progress towards completing by the end of 2017 proposed and final listing determinations for the 2010 candidate species—based on the Service's LPN prioritization system, preparing multi-species actions when appropriate, and taking into consideration the availability of staff resources.</P>
                    <P>Based on these prioritization factors, we continue to find that proposals to list the petitioned candidate species included in Table 1 are all precluded by higher priority listing actions including those with court-ordered and court-approved settlement agreements and listing actions with absolute statutory deadlines.</P>
                    <HD SOURCE="HD3">Expeditious Progress</HD>
                    <P>As explained above, a determination that listing is warranted but precluded must also demonstrate that expeditious progress is being made to add and remove qualified species to and from the Lists. As with our “precluded” finding, the evaluation of whether progress in adding qualified species to the Lists has been expeditious is a function of the resources available for listing and the competing demands for those funds. (Although we do not discuss it in detail here, we are also making expeditious progress in removing species from the list under the Recovery program in light of the resources available for delisting, which is funded by a separate line item in the budget of the Endangered Species Program. During FY 2014, we completed a delisting rule for one species.) As discussed below, given the limited resources available for listing, we find that we made expeditious progress in FY 2014 in the Listing Program.</P>
                    <P>We provide below tables cataloguing the work of the Service's Listing Program in FY 2014. This work includes all three of the steps necessary for adding species to the Lists: (1) Identifying species that warrant listing; (2) undertaking the evaluation of the best available scientific data about those species and the threats they face, and preparing proposed and final listing rules; and (3) adding species to the Lists by publishing proposed and final listing rules that include a summary of the data on which the rule is based and show the relationship of that data to the rule. After taking into consideration the limited resources available for listing, the competing demands for those funds, and the completed work catalogued in the tables below, we find that we made expeditious progress to add qualified species to the Lists in FY 2014.</P>
                    <P>First, we made expeditious progress in the third and final step: Listing qualified species. In FY 2014, we resolved the status of 35 species that we determined, or had previously determined, qualified for listing. Moreover, for 32 species, the resolution was to add them to the Lists, most with concurrent designations of critical habitat, and for 3 species we published a withdrawal of the proposed rule. We also proposed to list an additional 24 qualified species, most with concurrent critical habitat proposals.</P>
                    <P>
                        Second, we are making expeditious progress in the second step: Working towards adding qualified species to the Lists. In FY 2014, we worked on developing proposed listing rules for 34 species (most of them with concurrent critical habitat proposals). Although we have not yet completed those actions, we are making expeditious progress towards doing so.
                        <PRTPAGE P="72458"/>
                    </P>
                    <P>Third, we are making expeditious progress in the first step towards adding qualified species to the Lists: Identifying additional species that qualify for listing. In FY 2014, we completed two 90-day petition findings for two species.</P>
                    <P>
                        Our accomplishments this year should also be considered in the broader context of our commitment to reduce the number of candidate species for which we have not made final determinations whether or not to list. On May 10, 2011, the Service filed in the MDL Litigation a settlement agreement that put in place an ambitious schedule for completing proposed and final listing determinations at least through FY 2016; the court approved that settlement agreement on September 9, 2011. That agreement required, among other things, that for all 251 species that were included as candidates in the 2010 CNOR, the Service submit to the 
                        <E T="04">Federal Register</E>
                         proposed listing rules or not-warranted findings by the end of FY 2016, and for any proposed listing rules, the Service complete final listing determinations within the statutory time frame. Paragraph 6 of the agreement provided indicators that the Service is making adequate progress towards meeting that requirement: Completing proposed listing rules or not-warranted findings for at least 130 of the species by the end of FY 2013, at least 160 species by the end of FY 2014, and at least 200 species by the end of FY 2015. The Service has completed proposed listing rules or not-warranted findings for 166 of the 2010 candidate species, as well as final listing rules for 118 of those proposed rules, and is therefore is making adequate progress towards meeting all of the requirements of the MDL settlement agreement. Both by entering into the settlement agreement and by making adequate progress towards making final listing determinations for the 251 species on the 2010 candidate, the Service is making expeditious progress to add qualified species to the lists.
                    </P>
                    <P>The Service's progress in FY 2014 included completing and publishing the following determinations:</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r100,r100,xs80">
                        <TTITLE>FY 2014 Completed Listing Actions</TTITLE>
                        <BOXHD>
                            <CHED H="1">Publication date</CHED>
                            <CHED H="1">Title</CHED>
                            <CHED H="1">Actions</CHED>
                            <CHED H="1">FR Pages</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">11/14/2013</ENT>
                            <ENT>12-Month Finding on a Petition To List the Gunnison's Prairie Dog as an Endangered or Threatened Species</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted</ENT>
                            <ENT>78 FR 68660-68685.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/26/2013</ENT>
                            <ENT>Initiation of Status Review of Arctic Grayling in the Upper Missouri River System</ENT>
                            <ENT>Notice of Status Review</ENT>
                            <ENT>78 FR 70525-70527.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/19/2013</ENT>
                            <ENT>12-Month Finding on a Petition To List Coleman's Coralroot as an Endangered or Threatened Species</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted</ENT>
                            <ENT>78 FR 76795-76807.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/20/2013</ENT>
                            <ENT>
                                Threatened Status for 
                                <E T="03">Eriogonum codium</E>
                                 (Umtanum Desert Buckwheat) and 
                                <E T="03">Physaria douglasii</E>
                                 subsp. 
                                <E T="03">tuplashensis</E>
                                 (White Bluffs Bladderpod) and Designation of Critical Habitat
                            </ENT>
                            <ENT>Final Rule—Revision</ENT>
                            <ENT>78 FR 76995-77005.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/24/2014</ENT>
                            <ENT>Determination of Threatened Species Status for the Georgetown Salamander and Salado Salamander Throughout Their Ranges</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 10235-10293.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/31/2014</ENT>
                            <ENT>90-Day Finding on a Petition To List the Alexander Archipelago Wolf as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-day petition finding, Substantial</ENT>
                            <ENT>79 FR 17993-17995.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/9/2014</ENT>
                            <ENT>Threatened Species Status for the Olympia Pocket Gopher, Roy Prairie Pocket Gopher, Tenino Pocket Gopher, and Yelm Pocket Gopher, with Special Rule</ENT>
                            <ENT>Final Listing Threatened, with Special Rule</ENT>
                            <ENT>79 FR 19759-19796.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/10/2014</ENT>
                            <ENT>Determination of Threatened Status for the Lesser Prairie-Chicken</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 19973-20071.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/29/2014</ENT>
                            <ENT>Endangered Species Status for Sierra Nevada Yellow-Legged Frog and Northern Distinct Population Segment of the Mountain Yellow-Legged Frog, and Threatened Species Status for Yosemite Toad</ENT>
                            <ENT>Final Listing Threatened and Endangered</ENT>
                            <ENT>79 FR 24255-24310.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5/6/2014</ENT>
                            <ENT>
                                Determination of Threatened Status for 
                                <E T="03">Leavenworthia exigua</E>
                                 var. 
                                <E T="03">laciniata</E>
                                 (Kentucky Glade Cress)
                            </ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 25683-25688.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/3/2014</ENT>
                            <ENT>
                                Threatened Species Status for 
                                <E T="03">Ivesia webberi</E>
                            </ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 31878-31883.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/10/2014</ENT>
                            <ENT>Determination of Endangered Status for the New Mexico Meadow Jumping Mouse Throughout Its Range</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 33119-33137.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/8/2014</ENT>
                            <ENT>Threatened Status for the Northern Mexican Gartersnake and Narrow-Headed Gartersnake</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 38677-38746.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/24/2014</ENT>
                            <ENT>Endangered Species Status for the Zuni Bluehead Sucker</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 43131-43161.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/1/2014</ENT>
                            <ENT>
                                Endangered Status for 
                                <E T="03">Physaria globosa</E>
                                 (Short's bladderpod), 
                                <E T="03">Helianthus verticillatus</E>
                                 (whorled sunflower), and 
                                <E T="03">Leavenworthia crassa</E>
                                 (fleshy-fruit gladecress)
                            </ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 44712-44718.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/4/2014</ENT>
                            <ENT>Determination of Endangered Status for the Sharpnose Shiner and Smalleye Shiner</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 45273-45286.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72459"/>
                            <ENT I="01">8/6/2014</ENT>
                            <ENT>
                                Withdrawal of the Proposed Rules To List Graham's Beardtongue (
                                <E T="03">Penstemon grahamii</E>
                                ) and White River Beardtongue (
                                <E T="03">Penstemon scariosus</E>
                                 var. 
                                <E T="03">albifluvis</E>
                                ) and Designate Critical Habitat
                            </ENT>
                            <ENT>Proposed Listing Withdrawal</ENT>
                            <ENT>79 FR 46041-46087.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/12/2014</ENT>
                            <ENT>Endangered Status for the Florida Leafwing and Bartram's Scrub-Hairstreak Butterflies</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 47222-47244.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/13/2014</ENT>
                            <ENT>12-Month Finding on a Petition To List the Warton's Cave Meshweaver as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 47413-47415.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/13/2014</ENT>
                            <ENT>Threatened Status for the Distinct Population Segment of the North American Wolverine Occurring in the Contiguous United States; Establishment of a Nonessential Experimental Population of the North American Wolverine in Colorado, Wyoming, and New Mexico</ENT>
                            <ENT>Proposed Listing Withdrawal</ENT>
                            <ENT>79 FR 47521-47545.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/19/2014</ENT>
                            <ENT>90-Day Finding on a Petition To List the Island Marble Butterfly as an Endangered Species</ENT>
                            <ENT>Notice of 90-day petition finding, Substantial</ENT>
                            <ENT>79 FR 49045-49047.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/20/2014</ENT>
                            <ENT>Revised 12-Month Finding on a Petition To List the Upper Missouri River Distinct Population Segment of Arctic Grayling as an Endangered or Threatened Species</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 49383-49422.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/26/2014</ENT>
                            <ENT>12-Month Finding on the Petition To List Least Chub as an Endangered or Threatened Species</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 51041-51066.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/26/2014</ENT>
                            <ENT>Endangered Status for Vandenberg Monkeyflower</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 50844-50854.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/29/2014</ENT>
                            <ENT>Threatened Status for Oregon Spotted Frog</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 51657-51710.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/4/2014</ENT>
                            <ENT>
                                Endangered Species Status for 
                                <E T="03">Brickellia mosieri</E>
                                 (Florida Brickell-bush) and 
                                <E T="03">Linum carteri</E>
                                 var. 
                                <E T="03">carteri</E>
                                 (Carter's Small-flowered Flax)
                            </ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>79 FR 52567-52575.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/9/2014</ENT>
                            <ENT>
                                Endangered Species Status for 
                                <E T="03">Agave eggersiana</E>
                                 and 
                                <E T="03">Gonocalyx concolor,</E>
                                 and Threatened Species Status for 
                                <E T="03">Varronia rupicola</E>
                            </ENT>
                            <ENT>Final Listing Endangered and Threatened</ENT>
                            <ENT>79 FR 53315-53344.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/12/2014</ENT>
                            <ENT>
                                Threatened Status for 
                                <E T="03">Arabis georgiana</E>
                                 (Georgia rockcress)
                            </ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 54627-54635.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/12/2014</ENT>
                            <ENT>Revised Designation of Critical Habitat for the Contiguous United States Distinct Population Segment of the Canada Lynx and Revised Distinct Population Segment Boundary</ENT>
                            <ENT>Final Critical Habitat Final Listing—adding New Mexico to DPS boundary</ENT>
                            <ENT>79 FR 54781-54846.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/18/2014</ENT>
                            <ENT>
                                12-Month Finding on a Petition To List 
                                <E T="03">Eriogonum kelloggii</E>
                                 (Red Mountain buckwheat) and 
                                <E T="03">Sedum eastwoodiae</E>
                                 (Red Mountain stonecrop) as Endangered or Threatened Species
                            </ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 56029-56040.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/18/2014</ENT>
                            <ENT>
                                12-Month Finding on a Petition To List 
                                <E T="03">Symphyotrichum georgianum</E>
                                 (Georgia aster) as Endangered or Threatened Species
                            </ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 56041-56047.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/23/2014</ENT>
                            <ENT>12-Month Finding on a Petition To List the Tucson Shovel-Nosed Snake</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 56730-56738.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/24/2014</ENT>
                            <ENT>
                                12-Month Finding on a Petition To List 
                                <E T="03">Eriogonum corymbosum</E>
                                 var. 
                                <E T="03">nilesii</E>
                                 and 
                                <E T="03">Eriogonum diatomaceum</E>
                            </ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 57032-57041.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/1/2014</ENT>
                            <ENT>12-Month Finding on a Petition To List Rio Grande Cutthroat Trout as an Endangered or Threatened Species</ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 59140-59150.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/1/2014</ENT>
                            <ENT>
                                12-Month Finding on a Petition To List Yellow-Billed Loon (
                                <E T="03">Gavia adamsii</E>
                                ) as an  Endangered or Threatened Species
                            </ENT>
                            <ENT>Notice of 12-month petition finding, Not warranted Candidate removal</ENT>
                            <ENT>79 FR 59195-59204.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/1/2014</ENT>
                            <ENT>Proposed Endangered Status for 21 Species and Proposed Threatened Status for 2 Species in Guam and the Commonwealth of the Northern Mariana Islands</ENT>
                            <ENT>Proposed Listing Endangered and Threatened</ENT>
                            <ENT>79 FR 59363-59413.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72460"/>
                            <ENT I="01">10/3/2014</ENT>
                            <ENT>Threatened Species Status for the Western Distinct Population Segment of the Yellow-billed Cuckoo</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>79 FR 59991-60038.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/7/2014</ENT>
                            <ENT>Threatened Species Status for Black Pinesnake</ENT>
                            <ENT>Proposed Listing Threatened</ENT>
                            <ENT>79 FR 60406-60419.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/7/2014</ENT>
                            <ENT>Threatened Species Status for West Coast Distinct Population Segment of Fisher</ENT>
                            <ENT>Proposed Listing Threatened</ENT>
                            <ENT>79 FR 60419-60443.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/9/2014</ENT>
                            <ENT>
                                Endangered Species Status for 
                                <E T="03">Trichomanes punctatum ssp. floridanum</E>
                                 (Florida Bristle Fern)
                            </ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>79 FR 61135-61161.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Our expeditious progress also included work on listing actions that we funded in previous fiscal years and in FY 2014 but did not complete in FY 2014. For these species, we have completed the first step, and have been working on the second step, necessary for adding species to the Lists. These actions are listed below. All the actions in the table are being conducted under a deadline set by a court through a court order or settlement agreement.</P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,xs72">
                        <TTITLE>Actions Funded in Previous FYs and FY 2014 But Not Completed in FY 2014</TTITLE>
                        <BOXHD>
                            <CHED H="1">Species</CHED>
                            <CHED H="1">Action</CHED>
                        </BOXHD>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">Actions Subject to Court Order/Settlement Agreement</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Gunnison sage-grouse</ENT>
                            <ENT>Final listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dakota skipper and Poweshiek skipperling</ENT>
                            <ENT>Final listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Red knot (rufa subspecies)</ENT>
                            <ENT>Final listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Northern long-eared bat</ENT>
                            <ENT>Final listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Greater sage-grouse—Bi-State DPS</ENT>
                            <ENT>Final listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Washington ground squirrel</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Xantus's murrelet</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Columbia spotted frog—Great Basin DPS</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sequatchie caddisfly</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Four Florida Keys plants (sand flax, Big Pine partridge pea, Blodgett's silverbush, and wedge spurge)</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Four Florida plants (Florida pineland crabgrass, Florida prairie clover, pineland sandmat, and Everglades bully)</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">White fringeless orchid</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Black warrior waterdog</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Black mudalia</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Elfin-woods warbler</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kentucky arrow darter and Cumberland arrow darter</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Six Cave beetles (Nobletts, Baker Station, Fowler's, Indian Grave Point, inquirer, and Coleman)</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Sicyos macrophyllus</E>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Highlands tiger beetle</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sicklefin redhorse</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Headwater chub</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Roundtail chub DPS</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Page springsnail</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sonoran desert tortoise</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Texas hornshell</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New England cottontail</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eastern massasauga</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        We also funded work on resubmitted petitions findings for 112 candidate species (species petitioned prior to the last CNOR). In our resubmitted petition finding for the Columbia Basin population of the greater sage-grouse in this notice, although we completed a new analysis of the threats facing the species, we did not include new information, as the significance of the Columbia Basin DPS of the greater sage-grouse will require further review and we will update our finding when we resolve the status of the greater sage-grouse at a later date (see 75 FR 13910; March 23, 2010). We also did not include an updated assessment form as part of our resubmitted petition findings for the 34 candidate species for which we are preparing proposed listing determinations. However, for both the Columbia Basin DPS of the greater sage-grouse and for the other resubmitted petition findings, in the course of preparing proposed listing determinations, we continue to monitor new information about their status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the well-being of any of these candidate species; see summaries below regarding publication of these determinations (these species will remain on the candidate list until a proposed listing rule is published). We also funded a revised 12-month petition finding for the petitioned candidate species that we are removing from candidate status, which is being published as part of this CNOR (see Candidate Removals). Because the majority of these petitioned species were already candidate species prior to our receipt of a petition to list them, we had already assessed their status using funds from our Candidate Conservation Program, so we continue to monitor the 
                        <PRTPAGE P="72461"/>
                        status of these species through our Candidate Conservation Program. The cost of updating the species assessment forms and publishing the joint publication of the CNOR and resubmitted petition findings is shared between the Listing Program and the Candidate Conservation Program.
                    </P>
                    <P>
                        During FY 2014, we also funded work on resubmitted petition findings for uplisting five listed species (three grizzly bear populations, Delta smelt, and 
                        <E T="03">Sclerocactus brevispinus</E>
                         (Pariette cactus)), for which we had previously received a petition and made a warranted-but-precluded finding.
                    </P>
                    <P>Another way that we have been expeditious in making progress to add qualified species to the Lists is that we have endeavored to make our listing actions as efficient and timely as possible, given the requirements of the relevant law and regulations and constraints relating to workload and personnel. We are continually considering ways to streamline processes or achieve economies of scale, such as by batching related actions together. Given our limited budget for implementing section 4 of the ESA, these efforts also contribute towards finding that we are making expeditious progress to add qualified species to the Lists.</P>
                    <P>Although we have not been able to resolve the listing status of many of the candidates, we continue to contribute to the conservation of these species through several programs in the Service. In particular, the Candidate Conservation Program, which is separately budgeted, focuses on providing technical expertise for developing conservation strategies and agreements to guide voluntary on-the-ground conservation work for candidate and other at-risk species. The main goal of this program is to address the threats facing candidate species. Through this program, we work with our partners (other Federal agencies, State agencies, Tribes, local governments, private landowners, and private conservation organizations) to address the threats to candidate species and other species at risk. We are currently working with our partners to implement voluntary conservation agreements for more than 110 species covering 3.6 million ac of habitat. In some instances, the sustained implementation of strategically designed conservation efforts culminates in making listing unnecessary for species that are candidates for listing or for which listing has been proposed.</P>
                    <HD SOURCE="HD1">Findings for Petitioned Candidate Species</HD>
                    <P>Below are updated summaries for petitioned candidates for which we published findings under section 4(b)(3)(B). In accordance with section 4(b)(3)(C)(i), we treat any petitions for which we made warranted-but-precluded 12-month findings within the past year as having been resubmitted on the date of the warranted-but-precluded finding. We are making continued warranted-but-precluded 12-month findings on the petitions for these species (for 12-month findings on resubmitted petitions for species that we determined no longer meet the definition of “endangered species” or “threatened species,” see summaries above under Candidate Removals).</P>
                    <HD SOURCE="HD2">Mammals</HD>
                    <P>
                        Pacific sheath-tailed bat, American Samoa DPS (
                        <E T="03">Emballonura semicaudata semicaudata</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This small insectivorous bat is a member of the Emballonuridae family, an Old World bat family that has an extensive distribution, primarily in the tropics. 
                        <E T="03">Emballonura semicaudata semicaudata</E>
                         was once common and widespread in Polynesia and Micronesia. The species as a whole (
                        <E T="03">E. semicaudata</E>
                        ) occurred on several of the Caroline Islands (Palau, Chuuk, and Pohnpei), Samoa (Independent and American), the Mariana Islands (Guam and the Commonwealth of the Northern Mariana Islands (CNMI)), Tonga, Fiji, and Vanuatu. While populations appear to be healthy in some locations, mainly in the Caroline Islands, they have declined substantially in other areas, including Independent and American Samoa, the Mariana Islands, Fiji, and possibly Tonga. Scientists recognize four subspecies: 
                        <E T="03">E. s. rotensis,</E>
                         endemic to the Mariana Islands (Guam and the Commonwealth of the Northern Mariana Islands (CNMI)); 
                        <E T="03">E. s. sulcata,</E>
                         occurring in Chuuk and Pohnpei; 
                        <E T="03">E. s. palauensis,</E>
                         found in Palau; and 
                        <E T="03">E. s. semicaudata,</E>
                         occurring in American and Independent Samoa, Tonga, Fiji, and Vanuatu. The candidate assessment form addresses the DPS of 
                        <E T="03">E. s. semicaudata</E>
                         that occurs in American Samoa.
                    </P>
                    <P>
                        <E T="03">Emballonura semicaudata semicaudata</E>
                         historically occurred in American and Independent Samoa, Tonga, Fiji, and Vanuatu. It is extant in Fiji and Tonga, but may be extirpated from Vanuatu and Independent Samoa. There is some concern that it is also extirpated from American Samoa, the location of this DPS, where surveys are currently ongoing to ascertain its status. The factors that led to the decline of this subspecies and the DPS are poorly understood; however, current threats to this subspecies and the DPS include habitat loss, predation by introduced species, and its small population size and distribution, which make the taxon extremely vulnerable to extinction due to typhoons and similar natural catastrophes. The subspecies may also be susceptible to disturbance in its roosting caves. The threats are imminent and of high magnitude, since they are ongoing and severe enough to pose a relatively high likelihood of extinction. Therefore, we have retained an LPN of 3 for this DPS of a subspecies.
                    </P>
                    <P>
                        Peñasco least chipmunk (
                        <E T="03">Tamias minimus atristria</E>
                        )—The following summary is based on information contained in our files. Peñasco least chipmunk is endemic to the White Mountains, Otero and Lincoln Counties, and the Sacramento Mountains, Otero County, New Mexico. The Peñasco least chipmunk historically had a broad distribution throughout the Sacramento Mountains within ponderosa pine forests. The last verification of persistence of the Sacramento Mountains population of Peñasco least chipmunk was in 1966, and the subspecies appears to be extirpated from the Sacramento Mountains. The only remaining known distribution of the least chipmunk is restricted to open, high-elevation talus slopes within a subalpine grassland, located in the Sierra Blanca area of the White Mountains in Lincoln and Otero Counties, New Mexico.
                    </P>
                    <P>
                        The Peñasco least chipmunk faces threats from present or threatened destruction, modification, and curtailment of its habitat from the alteration or loss of mature ponderosa pine forests in one of the two historically occupied areas. The documented decline in occupied localities, in conjunction with the small numbers of individuals captured, are linked to widespread habitat alteration. Moreover, the highly fragmented nature of its distribution is a significant contributor to the vulnerability of this subspecies and increases the likelihood of very small, isolated populations being extirpated. As a result of this fragmentation, even if suitable habitat exists (or is restored) in the Sacramento Mountains, the likelihood of natural recolonization of historical habitat or population expansion from the White Mountains is extremely remote. Considering the high magnitude and immediacy of these threats to the subspecies and its habitat, and the 
                        <PRTPAGE P="72462"/>
                        vulnerability of the White Mountains population, we conclude that the least chipmunk is in danger of extinction throughout all of its known range now or in the foreseeable future.
                    </P>
                    <P>
                        The one known remaining extant population of Peñasco least chipmunk in the White Mountains is particularly susceptible to extinction as a result of small, reduced population sizes and its isolation. Because of the reduced population size and lack of contiguous habitat adjacent to the extant White Mountains population, even a small impact on the White Mountains could have a very large impact on the status of the species as a whole. As a result of its restricted range, apparent small population size, and fragmented historical habitat, the White Mountains population is inherently vulnerable to extinction due to effects of small, population sizes (
                        <E T="03">e.g.</E>
                         loss of genetic diversity). These impacts are likely to be seen in the population at some point in the foreseeable future, but do not appear to be affecting this population currently as it appears to be stable at this time. Therefore, we conclude that the threats to this population are of high magnitude, but not imminent. Therefore, we assign an LPN of 6 to the subspecies.
                    </P>
                    <P>
                        New England cottontail (
                        <E T="03">Sylvilagus transitionalis</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Southern Idaho ground squirrel (
                        <E T="03">Urocitellus endemicus</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The southern Idaho ground squirrel is endemic to four counties in southwest Idaho; its total known range is approximately 292,000 hectares (ha) (722,000 acres (ac)). The population declined significantly between 1985 and 2001, and approximately 37 percent of the historical known sites were occupied in 1999 by a relatively small number of individuals. More recently, southern Idaho ground squirrels have increased in abundance, and monitoring suggests that the population may now be stable.
                    </P>
                    <P>
                        Threats to southern Idaho ground squirrels include: Habitat degradation; direct killing from shooting, trapping, or poisoning; predation; and competition with other ground squirrel species. Habitat degradation appears to be the primary threat. Nonnative annuals such as 
                        <E T="03">Bromus tectorum</E>
                         (cheatgrass) and 
                        <E T="03">Taeniatherum caput-medusae</E>
                         (medusahead) now dominate much of this species' range and have altered the fire regime by increasing the frequency of wildfire. Nonnative annuals may provide inconsistent forage quality for southern Idaho ground squirrels compared to native vegetation. A programmatic Candidate Conservation Agreement with Assurances (CCAA) has been completed for this species and contains conservation measures that minimize ground disturbing activities, allow for the investigation of methods to restore currently degraded habitat, provide for additional protection to southern Idaho ground squirrels from recreational shooting and other direct killing on enrolled lands, and allow for the translocation of squirrels to or from enrolled lands, if necessary. The acreage enrolled through the CCAA encompasses approximately 9 percent of the known range of the species. While the ongoing conservation efforts have helped to reduce the magnitude of threats to a moderate level, habitat degradation remains the primary threat to the species throughout most of its range. This threat is imminent, due to the ongoing and increasing prevalence of nonnative vegetation. Therefore, we have retained an LPN of 8 for this species.
                    </P>
                    <P>
                        Washington ground squirrel (
                        <E T="03">Urocitellus washingtoni</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Red tree vole, north Oregon coast DPS (
                        <E T="03">Arborimus longicaudus</E>
                        )—The following summary is based on information contained in our files and in our initial warranted-but-precluded finding, published in the 
                        <E T="04">Federal Register</E>
                         on October 13, 2011 (76 FR 63720). Red tree voles are small, mouse-sized rodents that live in conifer forests and spend almost all of their time in the tree canopy. They are one of the few animals that can persist on a diet of conifer needles, which is their principal food. Red tree voles are endemic to the humid, coniferous forests of western Oregon (generally west of the crest of the Cascade Range) and northwestern California (north of the Klamath River). The north Oregon coast DPS of the red tree vole comprises that portion of the Oregon Coast Range from the Columbia River south to the Siuslaw River. Red tree voles demonstrate strong selection for nesting in older conifer forests, which are now relatively rare across the DPS; they avoid nesting in younger forests.
                    </P>
                    <P>Although data are not available to rigorously assess population trends, information from retrospective surveys indicates red tree voles have declined in the DPS and are largely absent in areas where they were once relatively abundant. Older forests that provide habitat for red tree voles are limited and highly fragmented, while ongoing forest practices in much of the DPS maintain the remnant patches of older forest in a highly fragmented and isolated condition. Modeling indicates that only 11 percent of the DPS currently contains tree vole habitat, largely restricted to the 22 percent of the DPS that is under Federal ownership.</P>
                    <P>Existing regulatory mechanisms on State and private lands are inadequate to prevent continued harvest of forest stands at a scale and extent that would be meaningful for conserving red tree voles. Biological characteristics of red tree voles, such as small home ranges, limited dispersal distances, and low reproductive potential, limit their ability to respond to and persist in areas of extensive habitat loss and alteration. These biological characteristics also make it difficult for the tree voles to recolonize isolated habitat patches. Due to its reduced distribution, the red tree vole is now vulnerable to random environmental disturbances that may remove or further isolate large blocks of already limited habitat, and to extirpation within the DPS from such factors as lack of genetic variability, inbreeding depression, and demographic stochasticity. Although the entire population is experiencing threats, the impact is less pronounced on Federal lands, where much of the red tree vole habitat remains. Hence, the magnitude of these threats is moderate to low. The threats are imminent because habitat loss and reduced distribution are currently occurring within the DPS. Therefore, we have retained an LPN of 9 for this DPS.</P>
                    <P>
                        Pacific walrus (
                        <E T="03">Odobenus rosmarus divergens</E>
                        )—The following information 
                        <PRTPAGE P="72463"/>
                        is based on information in our files and our warranted-but-precluded 12-month petition finding published on February 10, 2011 (76 FR 7634). The Pacific walrus is an ice-dependent species found across the continental shelf waters of the northern Bering and Chukchi Seas. Unlike seals, which can remain in the water for extended periods, walrus must haul out onto ice or land periodically. Pacific walrus is a traditional and important source of food and products to native Alaskans, especially those living on Saint Lawrence Island, and to native Russians.
                    </P>
                    <P>Annually, walrus migrate up to 1,500 kilometers (km) (932 miles (mi)) between winter breeding areas in the sub-Arctic (northern Bering Sea) and summer foraging areas in the Arctic. Historically, the females and calves remained on pack ice over the continental shelf of the Chukchi Sea throughout the summer, using it as a platform for resting after making shallow foraging dives for invertebrates on the sea floor. Sea ice also provides isolation from disturbance and terrestrial predators such as polar bears. Since 1979, the extent of summer Arctic sea ice has declined. The five lowest records of minimum sea ice extent occurred from 2007 to 2012. Based on the best scientific information available, we anticipate that sea ice will retreat northward off the Chukchi continental shelf for 1 to 5 months every year in the foreseeable future.</P>
                    <P>When the ice melts beyond the limits of the continental shelf (and the ability of the walrus to obtain food), thousands of walrus congregate at coastal haulouts. Although coastal haulouts have historically provided a place to rest, the aggregation of so many animals, in particular females and calves, at this time of year has increased in the last 5 years. Not only are the number of animals more concentrated at coastal haulouts than on widely dispersed sea ice, but also the probability of disturbance from humans and terrestrial animals is much higher. Disturbances at coastal haulouts can cause stampedes, leading to mortalities and injuries. In addition, there is also concern that the concentration of animals will cause local prey depletion, leading to longer foraging trips, increased energy costs, and potential effects on female condition and calf survival. We expect these effects to lead to a population decline.</P>
                    <P>We recognize that Pacific walrus face additional stressors from ocean warming, ocean acidification, disease, oil and gas exploration and development, increased shipping, commercial fishing, and subsistence harvest, but none rise to the level of a threat except subsistence harvest. We found that subsistence harvest will rise to the level of a threat if the population declines but harvest levels remain the same. Because both the loss of sea ice habitat and the ongoing practice of subsistence harvest are presently occurring, these threats are imminent. However, these threats are not having significant population-level effects currently, but are projected to, we determined that the magnitude of the threats is moderate, not high. Thus, we assigned an LPN of 9 to this subspecies.</P>
                    <HD SOURCE="HD2">Birds</HD>
                    <P>
                        Spotless crake, American Samoa DPS (
                        <E T="03">Porzana tabuensis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The spotless crake is a small, dark, cryptic bird found in wetlands and rank scrublands or forests in the Philippines, Australia, Fiji, Tonga, Society Islands, Marquesas, Independent Samoa, and American Samoa (Ofu, Tau). The genus 
                        <E T="03">Porzana</E>
                         is widespread in the Pacific, where it is represented by numerous island-endemic and flightless species (many of which are extinct as a result of anthropogenic disturbances), as well as several more cosmopolitan species, including 
                        <E T="03">P. tabuensis.</E>
                         No subspecies of 
                        <E T="03">P. tabuensis</E>
                         are recognized.
                    </P>
                    <P>The American Samoa population is the only population of spotless crakes under U.S. jurisdiction. The available information indicates that distinct populations of the spotless crake, a species not noted for long-distance dispersal, are definable. The population of spotless crakes in American Samoa is discrete in relation to the remainder of the species as a whole, which is distributed in widely separated locations. Although the spotless crake (and other rails) have dispersed widely in the Pacific, flight in island rails has atrophied or been completely lost over evolutionary time, causing populations to become isolated (and vulnerable to terrestrial predators such as rats). The population of this species in American Samoa is therefore distinct based on geographic and distributional isolation from spotless crake populations on other islands in the oceanic Pacific, the Philippines, and Australia. The American Samoa population of the spotless crake links the Central and Eastern Pacific portions of the species' range. The loss of this population would result in an increase of roughly 500 mi (805 km) in the distance between the central and eastern Polynesian portions of the spotless crake's range, and could result in the isolation of the Marquesas and Society Islands populations by further limiting the potential for even rare genetic exchange. Based on the discreteness and significance of the American Samoa population of the spotless crake, we consider this population to be a distinct vertebrate population segment.</P>
                    <P>
                        Threats to this population have not changed over the past year. The population in American Samoa is threatened by small population size, limited distribution, predation by nonnative and native animals, continued development of wetland habitat, and natural catastrophes such as hurricanes. The co-occurrence of a known predator of ground-nesting birds, the Norway rat (
                        <E T="03">Rattus norvegicus</E>
                        ), and native predators, the Pacific boa (
                        <E T="03">Candoia bibroni</E>
                        ) and the Purple Swamphen (
                        <E T="03">Porphyrio porphyrio</E>
                        ), along with the extremely restricted observed distribution and low numbers, indicates that the threats to the American Samoa DPS of the spotless crake continue to be both imminent and high in magnitude because the ongoing threats have a high likelihood of affecting the ability of the species to survive in a relatively short time frame. Based on this assessment of existing information about the imminence and high magnitude of these threats, we have retained an LPN of 3 for this DPS.
                    </P>
                    <P>
                        Friendly ground-dove, American Samoa DPS (
                        <E T="03">Gallicolumba stairi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The genus 
                        <E T="03">Gallicolumba</E>
                         is distributed throughout the Pacific and Southeast Asia. The genus is represented in the oceanic Pacific by six species: Three are endemic to Micronesian islands or archipelagos, two are endemic to island groups in French Polynesia, and 
                        <E T="03">G. stairi</E>
                         is endemic to Samoa, Tonga, and Fiji. Some authors recognize two subspecies of the friendly ground-dove, one, slightly smaller, in the Samoan archipelago (
                        <E T="03">G. s. stairi</E>
                        ), and one in Tonga and Fiji (
                        <E T="03">G. s. vitiensis</E>
                        ), but because morphological differences between the two are minimal, we are not recognizing separate subspecies at this time.
                    </P>
                    <P>
                        In American Samoa, the friendly ground-dove has been found on the islands of Ofu and Olosega (Manua Group). Threats to this species have not changed over the past year. Predation by nonnative species and natural catastrophes such as hurricanes are the primary threats to the DPS. Of these, predation by nonnative species is 
                        <PRTPAGE P="72464"/>
                        thought to be occurring now and likely has been occurring for several decades. This predation may be an important impediment to population growth. Predation by introduced species has played a significant role in reducing, limiting, and extirpating populations of island birds, especially ground-nesters like the friendly ground-dove, in the Pacific and other locations worldwide. Nonnative predators known or thought to occur in the range of the friendly ground-dove in American Samoa include feral cats (
                        <E T="03">Felis catus</E>
                        ), Polynesian rats (
                        <E T="03">Rattus exulans</E>
                        ), black rats (
                        <E T="03">R. rattus</E>
                        ), and Norway rats (
                        <E T="03">R. norvegicus</E>
                        ).
                    </P>
                    <P>
                        In January 2004 and February of 2005, hurricanes virtually destroyed the habitat of 
                        <E T="03">G. stairi</E>
                         in the area on Olosega Island where the species had been most frequently recorded. Although this species has evolved on islands subject to severe storms, this example illustrates the potential for natural disturbance to exacerbate the effect of anthropogenic disturbance on small populations. Consistent monitoring using a variety of methods over the last 5 years yielded few observations and no change in the relative abundance of this taxon in American Samoa. The total population size remains poorly known but is unlikely to number more than a few hundred pairs. The distribution of the friendly ground-dove is limited to steep, forested slopes with an open understory and a substrate of fine scree or exposed earth; this habitat is not common in American Samoa. The threats are ongoing and therefore imminent, and the magnitude is moderate because relative abundance has remained unchanged for several years. Thus, we have retained an LPN of 9 for this DPS.
                    </P>
                    <P>
                        Xantus's murrelet (
                        <E T="03">Synthliboramphus hypoleucus</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Red-crowned parrot (
                        <E T="03">Amazona viridigenalis</E>
                        )—The following summary is based on information contained in the notice of 12-month finding (76 FR 62016) as well as communication with the U.S. Fish and Wildlife Service (Service), Texas Parks and Wildlife Department, The Nature Conservancy, Rio Grande Joint Venture, World Birding Center, Rio Grande Valley Birding Festival, and the Universidad Autónoma de Tamaulipas. As of April, 2014, there are no changes to the range or distribution of the red-crowned parrot. The red-crowned parrot is non-migratory, and occurs in fragmented isolated habitat in the Mexican States of Tamaulipas, Veracruz, San Luis Potosi, Nuevo Leon, and northeast Queretaro. The species also occurs within the southern tip of Texas, in the cities of Mission, McAllen, Pharr, and Edinburg (Hidalgo County), and in Brownsville, Los Fresnos, San Benito, and Harlingen (Cameron County). Feral populations also exist in southern California, Puerto Rico, Hawaii, and Florida and escaped birds have been reported in central Texas. As of 2004, half of the native population is believed to be found in the United States. The species is nomadic during the winter (non-breeding) season when large flocks range widely to forage, moving tens of kilometers during a single flight in Mexico. In Texas, red-crowned parrots are thought to move between urban areas in search of food and other available resources. There has not been systematic annual monitoring of red-crowned parrot populations in Texas's Lower Rio Grande Valley (LRGV), so no population trend information is available; instead, numbers of parrots are most often reported from more informal surveys including Christmas Bird Counts and E-bird; surveys with wide variation in observers' skill levels. Counts of nesting pairs have not been documented since McKinney's 1995 survey. In Mexico, the level of monitoring of red-crowned parrots within the last two decades is not well known; however, community groups did include the species in bird surveys in the Ejido El Sabinito, in Sierras of Tamaulipas, in 2012 and 2013, where they reported approximately 2,500 and 1,889 individuals, respectively. Anecdotal reports from Mexico suggest that the species may be increasing in numbers in urban areas of Tamaulipas and Neuvo Leon.
                    </P>
                    <P>The primary threats within Mexico and Texas remain habitat destruction and modification from logging, deforestation, and conversion of suitable habitat for agricultural and urban development purposes. In addition, existing regulations do not adequately address the habitat or capture and trade threats to the species. Thus, the inadequacy of existing regulations and their enforcement continue to threaten the red-crowned parrot. Disease and predation are not documented to threaten the species. Pesticide exposure is not known to affect the red-crowned parrot. Conservation efforts include the artificial nest structure projects, as well as habitat creation projects such as one initiated by the Service and the Rio Grande Joint Venture in the LRGV to understand and compare how birds are using revegetated tracts of land that were previously affected by flooding. The project is in its initial steps and no results are yet available. Threats to the species are imminent because habitat destruction and inadequate regulatory mechanisms are ongoing. In addition, the threats are high in magnitude, because they affect the species extensively at a population level; therefore, we have determined that a LPN of 2 remains appropriate for the species.</P>
                    <P>
                        Sprague's pipit (
                        <E T="03">Anthus spragueii</E>
                        )—See above in “Listing Priority Changes in Candidates.”
                    </P>
                    <P>
                        Greater sage-grouse (
                        <E T="03">Centrocercus urophasianus)</E>
                        —The following summary is based on information in our files and in the petition we received on January 30, 2002. Currently, greater sage-grouse occur in 11 States (Washington, Oregon, California, Nevada, Idaho, Montana, Wyoming, Colorado, Utah, South Dakota, and North Dakota) and 2 Canadian provinces (Alberta and Saskatchewan), occupying approximately 56 percent of their historical range. Greater sage-grouse depend on a variety of shrub-steppe habitats throughout their life cycle, and are obligate users of several species of sagebrush.
                    </P>
                    <P>
                        The primary threat to greater sage-grouse is ongoing fragmentation and loss of shrub-steppe habitats through a variety of mechanisms. Most importantly, increasing fire cycles and invasive plants (and the interaction between them) in more westerly parts of the range, along with energy development and related infrastructure in more easterly areas, are negatively affecting the species. In addition, direct loss of habitat and fragmentation is occurring due to agriculture, urbanization, and infrastructure such as roads and power lines built in support of several activities. We also have determined that currently existing regulatory mechanisms are inadequate to protect the species from these ongoing threats. However, many of these habitat impacts are being actively addressed through conservation actions taken by local working groups, and State and Federal agencies. Notably, the Natural Resources Conservation Service has committed significant financial and technical resources to address threats to this species on private lands through 
                        <PRTPAGE P="72465"/>
                        their Sage-grouse Initiative. Also notably, the Bureau of Land Management and U.S. Forest Service are in the process of revising 98 Land Management Plans through 6 Environmental Impact Statements to provide adequate regulatory mechanisms. These efforts, when fully implemented, will potentially provide important conservation benefits to the greater sage-grouse and its habitats. We consider the threats to the greater sage-grouse to be of moderate magnitude, because the threats are not occurring with uniform intensity or distribution across the wide range of the species at this time, and substantial habitat still remains to support the species in many areas. The threats are imminent because the species is currently facing them in many portions of its range. Therefore, we assigned the greater sage-grouse an LPN of 8.
                    </P>
                    <P>
                        Greater sage-grouse, Columbia Basin DPS (
                        <E T="03">Centrocercus urophasianus</E>
                        )—The following summary is based on information in our files and a petition, dated May 14, 1999, requesting the listing of the Washington population of the western sage-grouse (
                        <E T="03">C. u. phaios</E>
                        ). This population was historically found in northern Oregon and central Washington. On May 7, 2001, we concluded that listing the Columbia Basin DPS of the western sage-grouse was warranted, but precluded by higher priority listing actions (66 FR 22984). Following our May 7, 2001, finding, the Service received additional petitions requesting listing actions for various other greater sage-grouse populations, including one for the nominal western subspecies, dated January 24, 2002, and three for the entire species, dated June 18, 2002, and March 19 and December 22, 2003. The Service subsequently found that the petition for the western subspecies did not present substantial information indicating that listing may be warranted (68 FR 6500; February 7, 2003), and that listing the greater sage-grouse was not warranted (70 FR 2244; January 12, 2005). The court subsequently remanded these latter findings to the Service for further consideration. In response, we initiated a new rangewide status review for the entire species (73 FR 10218; February 26, 2008). On March 5, 2010, we found that listing of the greater sage-grouse was warranted but precluded by higher priority listing actions (75 FR 13909; March 23, 2010), and it was added to the list of candidates. We also found that the western subspecies of the greater sage-grouse, the taxonomic entity we relied on in our DPS analysis for the Columbia Basin population, was no longer considered a valid subspecies. In light of our conclusions regarding the taxonomic invalidity of the western sage-grouse subspecies, the significance of the Columbia Basin DPS to the greater sage-grouse will require further review. The Service intends to complete an analysis to determine if this population continues to warrant recognition as a DPS in accordance with our Policy Regarding the Recognition of Distinct Vertebrate Population Segments (61 FR 4722; February 7, 1996) at the time we make a listing decision on the status of the greater sage-grouse. Until that time, the Columbia Basin DPS will remain a candidate for listing.
                    </P>
                    <P>
                        Band-rumped storm-petrel, Hawaii DPS (
                        <E T="03">Oceanodroma</E>
                          
                        <E T="03">castro</E>
                        )—The following summary is based on information contained in our files and the petition we received on May 8, 1989. No new information was provided in the second petition received on May 11, 2004. The band-rumped storm-petrel is a small seabird that is found in several areas of the subtropical Pacific and Atlantic Oceans. In the Pacific, there are three widely separated breeding populations—one in Japan, one in Hawaii, and one in the Galapagos. Populations in Japan and the Galapagos are comparatively large and number in the thousands, while the Hawaiian birds represent a small, remnant population of possibly only a few hundred pairs. Band-rumped storm-petrels are most commonly found in close proximity to breeding islands. The three populations in the Pacific are separated by long distances across the ocean where birds are not found. Extensive at-sea surveys of the Pacific have revealed a broad gap in distribution of the band-rumped storm-petrel to the east and west of the Hawaiian Islands, indicating that the distribution of birds in the central Pacific around Hawaii is disjunct from other nesting areas. The available information indicates that distinct populations of band-rumped storm-petrels are definable and that the Hawaiian population is distinct based on geographic and distributional isolation from other band-rumped storm-petrel populations in Japan, the Galapagos, and the Atlantic Ocean. Loss of the Hawaiian population would cause a significant gap in the distribution of the band-rumped storm-petrel in the Pacific, and could result in the complete isolation of the Galapagos and Japan populations without even occasional genetic exchange. Therefore, the population is both discrete and significant, and constitutes a DPS.
                    </P>
                    <P>
                        The band-rumped storm-petrel probably was common on all of the main Hawaiian Islands when Polynesians arrived about 1,500 years ago, based on storm-petrel bones found in middens on the island of Hawaii and in excavation sites on Oahu and Molokai, Hawaii. Nesting colonies of this species in the Hawaiian Islands currently are restricted to remote cliffs on Kauai and Lehua Island and high-elevation lava fields on Hawaii. Vocalizations of the species were heard in Haleakala Crater on Maui as recently as 2006; however, no nesting sites have been located on the island to date. The significant reduction in numbers and range of the band-rumped storm-petrel is due primarily to predation by nonnative species introduced by humans, including the domestic cat (
                        <E T="03">Felis catus</E>
                        ), small Indian mongoose (
                        <E T="03">Herpestes auropunctatus</E>
                        ), common barn owl (
                        <E T="03">Tyto alba</E>
                        ), black rat (
                        <E T="03">Rattus rattus</E>
                        ), Polynesian rat (
                        <E T="03">R. exulans</E>
                        ), and Norway rat (
                        <E T="03">R. norvegicus</E>
                        ). These nonnative predators occur throughout the main Hawaiian Islands, with the exception of the mongoose, which is not established on Kauai. Attraction of fledglings to artificial lights, which disrupt their night-time navigation, resulting in collisions with buildings and other objects, and collisions with artificial structures such as communication towers and utility lines, are also threats. Erosion of nest sites caused by the actions of nonnative ungulates is a potential threat in some locations. Efforts are under way in some areas to reduce light pollution and mitigate the threat of collisions, as well as to control some of the nonnative predators in the Hawaiian Islands; however, the threats are ongoing and are therefore imminent. They are of a high magnitude, because they can severely affect the survival of this DPS, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 3 for this DPS.
                    </P>
                    <P>
                        Elfin-woods warbler (
                        <E T="03">Dendroica angelae</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <HD SOURCE="HD2">Reptiles</HD>
                    <P>
                        Eastern massasauga rattlesnake (
                        <E T="03">Sistrurus catenatus</E>
                        )—We continue to 
                        <PRTPAGE P="72466"/>
                        find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Louisiana pine snake (
                        <E T="03">Pituophis ruthveni</E>
                        )—The following summary is based on information contained in our files and the petition we received on July 20, 2000, and updated through April 22, 2014. The Louisiana pine snake historically occurred in the fire-maintained longleaf pine ecosystem within west-central Louisiana and extreme east-central Texas. Most of the historical longleaf pine habitat of the Louisiana pine snake has been destroyed or degraded due to logging, fire suppression, roadways, short rotation silviculture, and grazing. Over time, the extensive loss, degradation, and fragmentation of the longleaf pine ecosystem, coupled with the disruption of natural fire regimes, have resulted in extant Louisiana pine snake populations that are isolated and small.
                    </P>
                    <P>The Louisiana pine snake is currently restricted to six small, isolated naturally occupied areas; four of these areas occur on Federal lands, and two occur mainly on private industrial timberlands. All of these remnant individuals may be vulnerable to factors associated with low population sizes and demographic isolation, such as reduced genetic heterozygosity. The currently occupied area in Louisiana and Texas is estimated to be approximately 58,497 ha (144,549 ac). All remnant Louisiana pine snake habitats require active management to remain suitable. A Candidate Conservation Agreement (CCA) was completed in 2003 to maintain and enhance occupied and potential habitat on public lands, and to protect known Louisiana pine snake populations. This proactive habitat management has likely slowed or reversed the rate of Louisiana pine snake habitat degradation on many portions of Federal lands. The 2003 CCA was updated in 2013. The 2013 updated CCA directly links the specific conservation actions performed by the cooperators to the specific threats affecting the species. However, the historical and ongoing loss or unavailability of preferable habitat (via fire suppression, conversion to short rotation, dense-canopy, off-site pine plantations, increases in the number and width of roads, and urbanization) on private lands in the matrix between these extant populations has eliminated dispersal among remnant populations and the natural recolonization of vacant habitat patches. Because corridors linking extant populations are extremely unlikely to be established, the loss of any extant population would be permanent without future reintroduction of captive-bred individuals.</P>
                    <P>All populations require active habitat management, and the lack of adequate amounts of suitable habitat remains a threat for several populations. The potential threats to nearly all extant Louisiana pine snake populations, coupled with the likely permanence of these effects and the species' low fecundity and low population sizes (based on capture rates and occurrence data), lead us to conclude that the threats have a relatively high likelihood of bringing about extinction and therefore remain high in magnitude. The threats are not imminent, because, while the extent of Louisiana pine snake habitat loss has been great in the past, the rate of habitat loss on Federal lands is declining and habitat conditions within occupied or preferable areas is improving due to proactive habitat management and other threat reduction through the CCA. Thus, based on nonimminent, high-magnitude threats, we assign an LPN of 5 to this species.</P>
                    <P>
                        Desert tortoise, Sonoran (
                        <E T="03">Gopherus morafkai</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Gopher tortoise, eastern population (
                        <E T="03">Gopherus polyphemus</E>
                        ) — The following summary is based on information in our files. The gopher tortoise is a large, terrestrial, herbivorous turtle that reaches a total length up to 15 inches (in) (38 centimeters (cm)), and typically inhabits the sandhills, pine/scrub oak uplands, and pine flatwoods associated with the longleaf pine (
                        <E T="03">Pinus palustris</E>
                        ) ecosystem. A fossorial animal, the gopher tortoise is usually found in areas with well-drained, deep, sandy soils, an open tree canopy, and a diverse, abundant herbaceous groundcover.
                    </P>
                    <P>The gopher tortoise ranges from extreme southern South Carolina south through peninsular Florida, and west through southern Georgia, Florida, southern Alabama, and Mississippi, into extreme southeastern Louisiana. The eastern population of the gopher tortoise in South Carolina, Florida, Georgia, and Alabama (east of the Mobile and Tombigbee Rivers) is a candidate species; the gopher tortoise is federally listed as threatened in the western portion of its range, which includes Alabama (west of the Mobile and Tombigbee Rivers), Mississippi, and Louisiana.</P>
                    <P>The primary threat to the gopher tortoise is habitat fragmentation, destruction, and modification (either deliberately or from inattention), including conversion of longleaf pine forests to incompatible silvicultural or agricultural habitats, urbanization, shrub/hardwood encroachment (mainly from fire exclusion or insufficient fire management), and establishment and spread of invasive species. Other threats include disease, predation (mainly on nests and young tortoises), and inadequate regulatory mechanisms, specifically those needed to protect and enhance relocated tortoise populations in perpetuity. The magnitude of threats to the eastern range of the gopher tortoise is considered to be moderate to low, since populations extend over a broad geographic area and conservation measures are in place in some areas. However, since the species is currently being affected by a number of threats including destruction and modification of its habitat, disease, predation, exotics, and inadequate regulatory mechanisms, the threats are imminent. Thus, we have assigned a LPN of 8 for this species.</P>
                    <P>
                        Sonoyta mud turtle (
                        <E T="03">Kinosternon sonoriense longifemorale</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Sonoyta mud turtle occurs in a spring and pond at Quitobaquito Springs on Organ Pipe Cactus National Monument in Arizona, and in the Rio Sonoyta and Quitovac Spring of Sonora, Mexico. Loss and degradation of stream habitat from water diversion and groundwater pumping, along with its very limited distribution, are the primary threats to the Sonoyta mud turtle. Sonoyta mud turtles are highly aquatic and depend on permanent water for survival. The area of southwest Arizona and northern Sonora where the Sonoyta mud turtle occurs is one of the driest regions in the Southwest. While 
                        <PRTPAGE P="72467"/>
                        currently there is sufficient water for the turtles, so the threats are not imminent we expect drought and irrigated agriculture in the region to cause surface water in the Rio Sonoyta and Quitobaquito Springs to dwindle further in the foreseeable future and negatively affect this species. National Park Service staff continue to implement actions to stabilize the water levels in the pond at Quitobaquito Springs. However, surface water use in the Rio Sonoyta, in Sonora Mexico, will have a significant impact on the survival of this water-dependent subspecies. We retained a LPN of 6 for Sonoyta mud turtle due to high-magnitude, nonimminent threats.
                    </P>
                    <HD SOURCE="HD2">Amphibians</HD>
                    <P>
                        Columbia spotted frog, Great Basin DPS (
                        <E T="03">Rana luteiventris</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Relict leopard frog (
                        <E T="03">Lithobates onca</E>
                        )—The following summary is based on information contained in our files. Natural relict leopard frog populations occur in two general areas in Nevada: near the Overton Arm area of Lake Mead and Black Canyon below Lake Mead. These two areas include a small fraction of the historical distribution of the species. Its historical range included springs, streams, and wetlands within the Virgin River drainage downstream from the vicinity of Hurricane, Utah; along the Muddy River in Nevada; and along the Colorado River in Nevada and Arizona, from its confluence with the Virgin River downstream to Black Canyon below Lake Mead.
                    </P>
                    <P>Factors contributing to the decline of the species include alteration, loss, and degradation of aquatic habitat due to water developments and impoundments, and scouring and erosion; changes in plant communities that result in dense growth and the prevalence of vegetation; introduced predators; climate change; and stochastic events. The presence of chytrid fungus in relict leopard frogs at Lower Blue Point Spring is a concern and warrants further evaluation of the threat of disease to the relict leopard frog. The size of natural and translocated populations is small and, therefore, these populations are vulnerable to stochastic events, such as floods and wildfire. Climate change that results in reduced spring flow, habitat loss, and increased prevalence of wildfire would adversely affect relict leopard frog populations.</P>
                    <P>In 2005, the National Park Service, in cooperation with the Fish and Wildlife Service and other Federal, State, and local partners, developed a conservation agreement and strategy, which is intended to improve the status of the species through prescribed management actions and protection. Conservation actions identified in the agreement and strategy include captive rearing of tadpoles for translocation and refugium populations, habitat and natural history studies, habitat enhancement, population and habitat monitoring, and translocation. New sites within the historical range of the species have been successfully established with captive-reared frogs. Conservation is proceeding under the agreement and strategy; however, additional time is needed to determine whether or not the agreement and strategy will be effective in eliminating or reducing the threats to the point that the relict leopard frog is no longer a candidate for listing. In consideration of these conservation efforts and the overall threat level to the species, we determined that the magnitude of existing threats is moderate to low. Potential water development and other habitat effects, presence of introduced predators, chytrid fungus, limited distribution, small population size, and climate change are ongoing, and thus, imminent threats. Therefore, we continue to assign a LPN of 8 to this species.</P>
                    <P>
                        Striped newt (
                        <E T="03">Notophthalmus perstriatus</E>
                        )—The following summary is based on information contained in our files. The striped newt is a small salamander that inhabits ephemeral ponds surrounded by upland habitats of high pine, scrubby flatwoods, and scrub. Longleaf pine-turkey oak stands with intact ground cover containing wiregrass are the preferred upland habitat for striped newts, followed by scrub, then flatwoods. Life-history stages of the striped newt are complex, and include the use of both aquatic and terrestrial habitats throughout their life cycle. Striped newts are opportunistic feeders that prey on a variety of items such as frog eggs, worms, snails, fairy shrimp, spiders, and insects (adult and larvae) that are of appropriate size. They occur in appropriate habitats from the Atlantic Coastal Plain of southeastern Georgia to the north-central peninsula of Florida and through the Florida panhandle into portions of southwest Georgia. Prior to 2014, there was thought to be a 125-km (78-mile (mi)) separation between the western and eastern portions of the striped newt's range. However, the discovery of five adult striped newts in Taylor County, Florida, represents a significant possible range connection. The historical range of the striped newt was likely similar to the current range. However, loss of native longleaf habitat, fire suppression, and the natural patchy distribution of upland habitats used by striped newts have resulted in fragmentation of existing populations.
                    </P>
                    <P>Other threats to the species include disease, drought, and inadequate regulatory mechanisms. Overall, we conclude that the magnitude of the threats is moderate because most of the known striped newt metapopulations are on conservation lands which reduces the threat from further habitat fragmentation, and currently no diseases have been found in striped newts. Since the majority of threats are ongoing, they are imminent. Therefore, we assigned an LPN of 8 to this species. However, due to recent information that suggests the striped newt is likely extirpated from Apalachicola National Forest, the LPN may warrant changing to a lower number in the future.</P>
                    <P>
                        Berry Cave salamander (
                        <E T="03">Gyrinophilus gulolineatus</E>
                        )—The following summary is based on information in our files. The Berry Cave salamander is recorded from Berry Cave in Roane County; from Mud Flats, Aycock Spring, Christian, Meades Quarry, Meades River, and Fifth caves in Knox County; from Blythe Ferry Cave in Meigs County; and from an unknown cave in Athens, McMinn County, Tennessee. In May of 2012, the species was also discovered in an additional cave, The Lost Puddle Cave, in Knox County. These cave systems are all located within the Upper Tennessee River and Clinch River drainages. A total of 113 caves in Middle and East Tennessee were surveyed from the time period of April 2004 through June 2007, resulting in observations of 63 Berry Cave salamanders. These surveys concluded that Berry Cave salamander populations are robust at Berry and Mudflats caves where population declines had been previously reported, and documented two new populations of Berry Cave salamanders at Aycock Spring and Christian caves. Three Berry Cave salamanders were spotted during the May, 2012, survey in The Lost Puddle, and local cavers also reported sighting one individual in August 2012. Surveys for new populations are planned along the Valley and Ridge 
                        <PRTPAGE P="72468"/>
                        Province between Knoxville and Chattanooga.
                    </P>
                    <P>Ongoing threats to this species are in the form of lye leaching in the Meades Quarry Cave as a result of past quarrying activities, the possible development of a roadway with potential to impact the recharge area for the Meades Quarry Cave system, urban development in Knox County, water quality impacts despite existing State and Federal laws, and hybridization between spring salamanders and Berry Cave salamanders in Meades Quarry Cave. These threats, coupled with confined distribution of the species and apparent low population densities, are all factors that leave the Berry Cave salamander vulnerable to extirpation. We have determined that the Berry Cave salamander faces imminent threats of moderate magnitude. The threats are moderate because the species still occurs in several different cave systems, and existing populations appear stable. Based on moderate-magnitude imminent threats, we continue to assign this species a LPN of 8.</P>
                    <P>
                        Black Warrior waterdog (
                        <E T="03">Necturus alabamensis</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <HD SOURCE="HD2">Fishes</HD>
                    <P>
                        Headwater chub (
                        <E T="03">Gila nigra</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Roundtail chub (
                        <E T="03">Gila robusta</E>
                        ), Lower Colorado River DPS—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Arkansas darter (
                        <E T="03">Etheostoma cragini</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This fish species occurs in Arkansas, Colorado, Kansas, Missouri, and Oklahoma. The species is found most often in sand- or pebble-bottomed pools of small, spring-fed streams and marshes, with cool water and broadleaved aquatic vegetation. Its current distribution is indicative of a species that once was widely dispersed throughout its range, but has been relegated to isolated areas separated by unsuitable habitat that prevents dispersal.
                    </P>
                    <P>Factors influencing the current distribution include: Surface and groundwater irrigation resulting in decreased flows or stream dewatering; the dewatering of long reaches of riverine habitat; conversion of prairie to cropland, which influences groundwater recharge and spring flows; water quality degradation from a variety of sources; and the construction of dams, which act as barriers preventing emigration upstream and downstream through the reservoir pool. A current drought in the western portions of the species' range is also a threat. If drought conditions continue into the future, these conditions are likely to have a severe impact on many of these isolated populations. However, at present, the magnitude of threats facing this species is still moderate to low, given the number of different locations where the species occurs, and the fact that no single threat or combination of threats affects more than a portion of the species' widely distributed range. The immediacy of threats varies across the species' range; groundwater pumping is an ongoing concern in the western portion of the species range, although it has declined in some portions, and groundwater levels continue to support surface spring and stream flow in the majority of the species' range. Development, spills, and runoff are not currently affecting the species on a rangewide basis. Overall, the threats are nonimminent. Thus, we are retaining an LPN of 11 for the Arkansas darter.</P>
                    <P>
                        Pearl darter (
                        <E T="03">Percina aurora</E>
                        )—The following summary is based on information contained in our files. Little is known about the specific habitat requirements or natural history of the Pearl darter. Pearl darters have been collected from a variety of river/stream attributes, mainly over gravel bottom substrate. This species is historically known only from localized sites within the Pascagoula and Pearl River drainages in Mississippi and Louisiana. Currently, the Pearl darter is considered extirpated from the Pearl River drainage and rare in the Pascagoula River drainage. Since 1983, the range of the Pearl darter has decreased by 55 percent.
                    </P>
                    <P>The Pearl darter is vulnerable to non-point source pollution caused by urbanization and other land use activities; gravel mining and resultant changes in river geomorphology, especially head cutting; and the possibility of water quantity decline from the proposed Department of Energy Strategic Petroleum Reserve project and a proposed dam on the Bouie River. Additional threats are posed by the apparent lack of adequate State and Federal water quality regulations resulting in the continued degradation of water quality within the species' habitat. The Pearl darter's localized distribution and apparent low population numbers may indicate a species with lower genetic diversity; this would also make this species more vulnerable to catastrophic events. Threats affecting the Pearl darter are localized in nature, affecting only portions of the population within the drainage having only a localized impact on the species and its' habitat. While water quality degradation is the most pervasive threat, it is not significant within the areas protected through The Nature Conservancy ownership and other areas where best managmenet practices are routinely practiced. Thus, we assigned a threat magnitude of moderate to low to this species. In addition, the threats are imminent since the identified threats are currently impacting this species in some portions of its range. Therefore, we have assigned an LPN of 8 for this species.</P>
                    <P>
                        Sicklefin redhorse (
                        <E T="03">Moxostoma</E>
                         sp.)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an 
                        <PRTPAGE P="72469"/>
                        emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Longfin smelt (
                        <E T="03">Spirinchus thaleichthys</E>
                        ), Bay-Delta DPS—The following summary is based on information contained in our files and the petition we received on August 8, 2007. On April 2, 2012 (77 FR19756), we determined that listing the longfin smelt San Francisco Bay-Delta distinct population segment (Bay-Delta DPS) was warranted but precluded. Longfin smelt measure 9-11 cm (3.5-4.3 in) standard length. Longfin smelt are considered pelagic and anadromous, although anadromy in longfin smelt is poorly understood, and certain populations in other parts of the species' range are not anadromous and complete their entire life cycle in freshwater lakes and streams. Longfin smelt usually live for 2 years, spawn, and then die, although some individuals may spawn as 1- or 3-year-old fish before dying. In the Bay-Delta, longfin smelt are believed to spawn primarily in freshwater in the lower reaches of the Sacramento River and San Joaquin River.
                    </P>
                    <P>Longfin smelt numbers in the Bay-Delta have declined significantly since the 1980s. Abundance indices derived from the Fall Midwater Trawl (FMWT), Bay Study Midwater Trawl (BSMT), and Bay Study Otter Trawl (BSOT) all show marked declines in Bay-Delta longfin smelt populations from 2002 to 2012. Longfin smelt abundance over the last decade is the lowest recorded in the 40-year history of CDFG's FMWT monitoring surveys.</P>
                    <P>The primary threat to the DPS is from reduced freshwater flows. Freshwater flows, especially winter-spring flows, are significantly correlated with longfin smelt abundance—longfin smelt abundance is lower when winter-spring flows are lower. The long-term decline in abundance of longfin smelt in the Bay-Delta has been partially attributed to reductions in food availability and disruptions of the Bay-Delta food web caused by establishment of the nonnative overbite clam and likely by increasing ammonium concentrations. In the 2012, 12-month finding, we determined that threats were high in magnitude and imminent, resulting in an LPN of 3. The threats still remain high in magnitude since they pose a significant risk to the DPS throughout its range. The threats are ongoing, and thus are imminent. We are maintaining an LPN of 3 for this population.</P>
                    <HD SOURCE="HD2">Clams</HD>
                    <P>
                        Texas fatmucket (
                        <E T="03">Lampsilis bracteata</E>
                        )—The following summary is based on information contained in our files. The Texas fatmucket is a large, elongated freshwater mussel that is endemic to central Texas. Its shell can be moderately thick, smooth, and rhomboidal to oval in shape. Its external coloration varies from tan to brown with continuous dark brown, green-brown, or black rays, and internally it is pearly white, with some having a light salmon tint. This species historically occurred throughout the Colorado and Guadalupe-San Antonio River basins but is now known to occur only in nine streams within these basins in very limited numbers. All existing populations are represented by only one or two individuals and are not likely to be stable or recruiting.
                    </P>
                    <P>The Texas fatmucket is primarily threatened by habitat destruction and modification from impoundments, which scour river beds, thereby removing mussel habitat; decrease water quality; modify stream flows; and prevent fish host migration and distribution of freshwater mussels. This species is also threatened by sedimentation, dewatering, sand and gravel mining, and chemical contaminants. Additionally, these threats may be exacerbated by the current and projected effects of climate change, population fragmentation and isolation, and the anticipated threat of nonnative species. Threats to the Texas fatmucket and its habitat are not being adequately addressed through existing regulatory mechanisms. Because of the limited distribution of this endemic species and its lack of mobility, these threats are likely to result in the extinction of the Texas fatmucket in the foreseeable future.</P>
                    <P>The threats to the Texas fatmucket are high in magnitude, because habitat loss and degradation from impoundments, sedimentation, sand and gravel mining, and chemical contaminants are widespread throughout the range of the Texas fatmucket and profoundly affect its survival and recruitment. These threats are exacerbated by climate change, which will increase the frequency and magnitude of droughts. Remaining populations are small, isolated, and highly vulnerable to stochastic events, which could lead to extirpation or extinction. These threats are imminent because they are ongoing and will continue in the foreseeable future. Habitat loss and degradation have already occurred and will continue as the human population continues to grow in central Texas. Texas fatmucket populations may already be below the minimum viable population requirement, which causes a reduction in the number of populations and an increase in the species' vulnerability to extinction. Based on imminent, high-magnitude threats, we maintained an LPN of 2 for the Texas fatmucket.</P>
                    <P>
                        Texas fawnsfoot (
                        <E T="03">Truncilla macrodon</E>
                        )—The following summary is based on information contained in our files. The Texas fawnsfoot is a small, relatively thin-shelled freshwater mussel that is endemic to central Texas. Its shell is long and oval, generally free of external sculpturing, with external coloration that varies from yellowish- or orangish-tan, brown, reddish-brown, to smoky-green with a pattern of broken rays or irregular blotches. The internal color is bluish-white or white and iridescent posteriorly. This species historically occurred throughout the Colorado and Brazos River basins and is now known from only five locations. The Texas fawnsfoot has been extirpated from nearly all of the Colorado River basin and from much of the Brazos River basin. Of the populations that remain, only three are likely to be stable and recruiting; the remaining populations are disjunct and restricted to short stream reaches.
                    </P>
                    <P>The Texas fawnsfoot is primarily threatened by habitat destruction and modification from impoundments, which scour river beds, thereby removing mussel habitat; decrease water quality; modify stream flows; and prevent fish host migration and distribution of freshwater mussels, as well as by sedimentation, dewatering, sand and gravel mining, and chemical contaminants. Additionally, these threats may be exacerbated by the current and projected effects of climate change, population fragmentation and isolation, and the anticipated threat of nonnative species. Threats to the Texas fawnsfoot and its habitat are not being adequately addressed through existing regulatory mechanisms. Because of the limited distribution of this endemic species and its lack of mobility, these threats are likely to result in the extinction of the Texas fawnsfoot in the foreseeable future.</P>
                    <P>
                        The threats to the Texas fawnsfoot are high in magnitude. Habitat loss and degradation from impoundments, sedimentation, sand and gravel mining, and chemical contaminants are widespread throughout the range of the Texas fawnsfoot and profoundly affect its habitat. These threats are exacerbated by climate change, which will increase the frequency and magnitude of droughts. Remaining populations are small, isolated, and highly vulnerable to stochastic events. These threats are imminent because they are ongoing and will continue in the foreseeable future. Habitat loss and degradation has already occurred and will continue as the 
                        <PRTPAGE P="72470"/>
                        human population continues to grow in central Texas. The Texas fawnsfoot populations may already be below the minimum viable population requirement, which causes a reduction in the number of populations and an increase in the species' vulnerability to extinction. Based on imminent, high-magnitude threats, we assigned the Texas fawnsfoot an LPN of 2.
                    </P>
                    <P>
                        Texas hornshell (
                        <E T="03">Popenaias popei</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Golden orb (
                        <E T="03">Quadrula aurea</E>
                        )—The following summary is based on information contained in our files. The golden orb is a small, round-shaped freshwater mussel that is endemic to central Texas. This species historically occurred throughout the Nueces-Frio and Guadalupe-San Antonio River basins and is now known from only nine locations in four rivers. The golden orb has been eliminated from nearly the entire Nueces-Frio River basin. Four of these populations appear to be stable and reproducing, and the remaining five populations are small and isolated and show no evidence of recruitment. It appears that the populations in the middle Guadalupe and lower San Marcos Rivers are likely connected. The remaining extant populations are highly fragmented and restricted to short reaches.
                    </P>
                    <P>The golden orb is primarily threatened by habitat destruction and modification from impoundments, which scour river beds (thereby removing mussel habitat), decrease water quality, modify stream flows, and prevent fish host migration and distribution of freshwater mussels. The species is also threatened by sedimentation, dewatering, sand and gravel mining, and chemical contaminants. Additionally, these threats may be exacerbated by the current and projected effects of climate change, population fragmentation and isolation, and the anticipated threat of nonnative species. Threats to the golden orb and its habitat are not being adequately addressed through existing regulatory mechanisms. Because of the limited distribution of this endemic species and its lack of mobility, these threats may be likely to result in the golden orb becoming in danger of extinction in the foreseeable future.</P>
                    <P>The threats to the golden orb are moderate in magnitude. Although habitat loss and degradation from impoundments, sedimentation, sand and gravel mining, and chemical contaminants are widespread throughout the range of the golden orb, and are likely to be exacerbated by climate change, which will increase the frequency and magnitude of droughts, four large populations remain, including one that was recently discovered, suggesting that the threats are not high in magnitude. The threats from habitat loss and degradation are imminent because habitat loss and degradation have already occurred and will likely continue as the human population continues to grow in central Texas. Several golden orb populations may already be below the minimum viable population requirement, which causes a reduction in the number of populations and an increase in the species' vulnerability to extinction. Based on imminent, moderate threats, we maintain an LPN of 8 for the golden orb.</P>
                    <P>
                        Smooth pimpleback (
                        <E T="03">Quadrula houstonensis</E>
                        )—The following summary is based on information contained in our files. The smooth pimpleback is a small, round-shaped freshwater mussel that is endemic to central Texas. This species historically occurred throughout the Colorado and Brazos River basins and is now known from only nine locations. The smooth pimpleback has been eliminated from nearly the entire Colorado River and all but one of its tributaries, and has been limited to the central and lower Brazos River drainage. Five of the populations are represented by no more than a few individuals and are small and isolated. Six of the existing populations appear to be relatively stable and recruiting.
                    </P>
                    <P>The smooth pimpleback is primarily threatened by habitat destruction and modification from impoundments, which scour river beds (thereby removing mussel habitat), decrease water quality, modify stream flows, and prevent fish host migration and distribution of freshwater mussels. The species is also threatened by sedimentation, dewatering, sand and gravel mining, and chemical contaminants. Additionally, these threats may be exacerbated by the current and projected effects of climate change, population fragmentation and isolation, and the anticipated threat of nonnative species. Threats to the smooth pimpleback and its habitat are not being adequately addressed through existing regulatory mechanisms. Because of the limited distribution of this endemic species and its lack of mobility, these threats may be likely to result in the smooth pimpleback becoming in danger of extinction in the foreseeable future.</P>
                    <P>The threats to the smooth pimpleback are moderate in magnitude. Although habitat loss and degradation from impoundments, sedimentation, sand and gravel mining, and chemical contaminants are widespread throughout the range of the smooth pimpleback, and may be exacerbated by climate change, which will increase the frequency and magnitude of droughts, several large populations remain, including one that was recently discovered, suggesting that the threats are not high in magnitude. The threats from habitat loss and degradation are imminent because they have already occurred and will continue as the human population continues to grow in central Texas. Several smooth pimpleback populations may already be below the minimum viable population requirement, which causes a reduction in the number of populations and an increase in the species' vulnerability to extinction. Based on imminent, moderate threats, we maintain an LPN of 8 for the smooth pimpleback.</P>
                    <P>
                        Texas pimpleback (
                        <E T="03">Quadrula petrina</E>
                        )—The following summary is based on information contained in our files. The Texas pimpleback is a large, freshwater mussel that is endemic to central Texas. This species historically occurred throughout the Colorado and Guadalupe-San Antonio River basins, but is now known to only occur in four streams within these basins. Only two populations appear large enough to be stable, but evidence of recruitment is limited in the Concho River population and is present in the San Saba River population, which may be the only remaining recruiting populations of Texas pimpleback. The remaining two populations are represented by one or two individuals and are highly disjunct.
                    </P>
                    <P>
                        The Texas pimpleback is primarily threatened by habitat destruction and modification from impoundments, which scour river beds (thereby removing mussel habitat), decrease water quality, modify stream flows, and prevent fish host migration and distribution of freshwater mussels. This species is also threatened by sedimentation, dewatering, sand and gravel mining, and chemical contaminants. Additionally, these threats may be exacerbated by the current and projected effects of climate change (which will increase the frequency and magnitude of droughts), 
                        <PRTPAGE P="72471"/>
                        population fragmentation and isolation, and the anticipated threat of nonnative species. Threats to the Texas pimpleback and its habitat are not being adequately addressed through existing regulatory mechanisms. Because of the limited distribution of this endemic species and its lack of mobility, these threats may be likely to result in the Texas pimpleback becoming in danger of extinction in the foreseeable future.
                    </P>
                    <P>The threats to the Texas pimpleback are high in magnitude, because habitat loss and degradation from impoundments, sedimentation, sand and gravel mining, and chemical contaminants are widespread throughout the entire range of the Texas pimpleback and profoundly affect its survival and recruitment. The only remaining populations are small, isolated, and highly vulnerable to stochastic events, which could lead to extirpation or extinction. The threats are imminent because habitat loss and degradation have already occurred and will continue as the human population continues to grow in central Texas. All Texas pimpleback populations may already be below the minimum viable population requirement, which causes a reduction in the number of populations and an increase in the species' vulnerability to extinction. Based on imminent, high-magnitude threats, we assigned the Texas pimpleback an LPN of 2.</P>
                    <HD SOURCE="HD2">Snails</HD>
                    <P>
                        Black mudalia (
                        <E T="03">Elimia melanoides</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Magnificent ramshorn (
                        <E T="03">Planorbella magnifica</E>
                        )—Magnificent ramshorn, is the largest North American air-breathing freshwater snail in the family Planorbidae. It has a relatively thin discoidal (
                        <E T="03">i.e.,</E>
                         coiling in one plane) shell that reaches a diameter commonly exceeding 35mm and heights exceeding 20mm. The great width of its shell, in relation to the diameter, makes it easily identifiable at all ages. The shell is brown colored (often with leopard-like spots) and fragile, thus indicating it is adapted to still or slow-flowing aquatic habitats. The magnificent ramshorn is believed to be a southeastern North Carolina endemic. The species is known from only four sites in the lower Cape Fear River Basin in North Carolina. Although the complete historical range of the species is unknown, the size of the species and the fact that it was not reported until 1903 are indications that the species may have always been rare and localized.
                    </P>
                    <P>
                        Salinity and pH are major factors limiting the distribution of the magnificent ramshorn, as the snail prefers freshwater bodies with circumneutral pH (
                        <E T="03">i.e.,</E>
                         pH within the range of 6.8-7.5). While members of the family Planorbidae are hermaphroditic, it is currently unknown whether magnificent ramshorns self-fertilize their eggs, mate with other individuals of the species, or both. Like other members of the Planorbidae family, the magnificent ramshorn is believed to be primarily a vegetarian, feeding on submerged aquatic plants, algae, and detritus. While several factors likely have contributed to the possible extirpation of the magnificent ramshorn in the wild, the primary factors include loss of habitat associated with the extirpation of beavers (and their impoundments) in the early 20th century and increased salinity and alteration of flow patterns, as well as increased input of nutrients and other pollutants.
                    </P>
                    <P>
                        The magnificent ramshorn appears to be extirpated from the wild due to habitat loss and degradation resulting from a variety of human-induced and natural factors. The only known surviving individuals of the species are presently being held and propagated at a private residence, a lab at North Carolina State University's Veterinary School, and the North Carolina Wildlife Resources Commission's Watha State Fish Hatchery. While efforts have been made to restore habitat for the magnificent ramshorn at one of the sites known to have previously supported the species, all of the sites continue to be affected or threatened by the same factors (
                        <E T="03">i.e.,</E>
                         salt water intrusion and other water-quality degradation, nuisance aquatic plant control, storms, sea level rise, etc.) believed to have resulted in extirpation of the species from the wild. Currently, only three captive populations exist; a single robust captive population of the species comprised of greater than 200 adults, and two small populations of 50 or more individuals. Although the robust captive population of the species has been maintained since 1993, a single catastrophic event affecting this captive population, such as a severe storm, disease, or predator infestation, could result in the near extinction of the species. Therefore, we assigned this species a LPN of 2.
                    </P>
                    <P>
                        Sisi snail (
                        <E T="03">Ostodes strigatus</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The sisi snail is a ground-dwelling species in the Potaridae family, and is endemic to American Samoa. The species is now known from a single population on the island of Tutuila, American Samoa.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails. The decline of the sisi snail in American Samoa has resulted, in part, from loss of habitat to logging and agriculture, and loss of forest structure to hurricanes and nonnative weeds that become established after these storms. All live sisi snails have been found in the leaf litter beneath remaining intact forest canopy. No snails were found in areas bordering agricultural plots or in forested areas that were severely damaged by hurricanes. Under natural historical conditions, loss of forest canopy to storms did not pose a great threat to the long-term survival of these snails; enough intact forest with healthy populations of snails would support dispersal back into newly regrown forest canopy. However, the presence of nonnative weeds such as mile-a-minute vine (
                        <E T="03">Mikania micrantha</E>
                        ) may reduce the likelihood that native forests will re-establish in areas damaged by hurricanes. This loss of habitat to storms is greatly exacerbated by expanding agriculture. Agricultural plots on Tutuila have spread from low elevation up to middle and some high elevations, greatly reducing the forested area and thus reducing the resilience of native forests and populations of native snails. These reductions also increase the likelihood that future storms will lead to the extinction of populations or species that rely on the remaining forest canopy. In an effort to eradicate the nonnative giant African snail (
                        <E T="03">Achatina fulica</E>
                        ), the nonnative rosy carnivore snail (
                        <E T="03">Euglandina rosea</E>
                        ) was introduced in 1980. The rosy carnivore snail has spread throughout the main island of Tutuila. Numerous studies show that the rosy carnivore snail feeds on endemic island snails, including the sisi snail, and is a major agent in their declines and extirpations. At present, the major threat to the long-term survival of the native snail fauna in American Samoa, including the sisi snail, is predation by nonnative predatory snails. The threats are 
                        <PRTPAGE P="72472"/>
                        imminent and of high magnitude, since they are severe enough to affect the continued existence of the species, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Tutuila tree snail (
                        <E T="03">Eua zebrina</E>
                        )—A tree-dwelling species, the Tutuila tree snail is a member of the Partulidae family of snails and is endemic to American Samoa. The species is known from 32 populations on the islands of Tutuila, Manua, and Ofu.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails and rats (
                        <E T="03">Rattus</E>
                         spp.). All live Tutuila tree snails were found on understory vegetation beneath remaining intact forest canopy. No snails were found in areas bordering agricultural plots or in forested areas that were severely damaged by three hurricanes (1987, 1990, and 1991). (See summary for the sisi snail, above, regarding impacts of nonnative weeds and of the rosy carnivore snail.) Rats have also been shown to devastate snail populations, and rat-damaged snail shells have been found at sites where the Tutuila snail occurs. At present, the major threat to the long-term survival of the native snail fauna in American Samoa is ongoing predation by nonnative predatory snails and rats. The magnitude of threats is high because they result in direct mortality leading to significant population declines to the Tutuila tree snail rangewide. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Huachuca springsnail (
                        <E T="03">Pyrgulopsis thompsoni</E>
                        )—The following is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. The Huachuca springsnail is endemic to Santa Cruz and Cochise Counties in southeastern Arizona and adjacent portions of northern Sonora, Mexico. Currently, the Huachuca springsnail inhabits at least 21 spring sites in southeastern Arizona and northern Sonora, Mexico. The species is most commonly found in shallow water habitats, often in rocky seeps at the spring source. Threats include habitat modification and destruction through catastrophic wildfire, unmanaged grazing at the landscape scale, and the inadequacy of regulatory mechanisms. Overall, the threats are low in magnitude, because threats are not occurring throughout the range of the species uniformly and not all populations would likely be affected simultaneously by the known threats. We have no site-specific information indicating that grazing is currently ongoing in or adjacent to occupied habitats, and catastrophic wildfire is not known to be an imminent threat. Accordingly, threats are nonimminent. Therefore, we retain an LPN of 11 for the Huachuca springsnail.
                    </P>
                    <P>
                        Page springsnail (
                        <E T="03">Pyrgulopsis morrisoni</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <HD SOURCE="HD2">Insects</HD>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus anthracinus</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus anthracinus</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) found in certain coastal areas and dry lowland forests containing native plant communities on the islands of Hawaii, Kahoolawe, Lanai, Maui, Molokai, and Oahu, Hawaii. 
                        <E T="03">Hylaeus anthracinus</E>
                         is currently known from 16 populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">Hylaeus anthracinus</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        Some 
                        <E T="03">H. anthracinus</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, no population is entirely protected from impacts to habitat, and predation on the species is not currently managed at any population site. Because the ongoing threats adversely affect 
                        <E T="03">H. anthracinus</E>
                         throughout its entire range, and cause impacts that are sufficiently severe that they could lead to population declines, the threats are high in magnitude and are imminent. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus assimulans</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus assimulans</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) found in certain coastal areas and dry lowland forests containing native plant communities on the islands of Hawaii, Kahoolawe, Lanai, Maui, Molokai, and Oahu, Hawaii. 
                        <E T="03">Hylaeus assimulans</E>
                         is currently known from five populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">Hylaeus assimulans</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        Some 
                        <E T="03">H. assimulans</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, no population is entirely protected from impacts to habitat, and predation on the species is not currently managed at any population site. Because the ongoing threats adversely affect 
                        <E T="03">H. assimulans</E>
                         throughout its entire range, and cause impacts that are sufficiently severe that they could lead to population declines, the threats are high in magnitude and are imminent. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus facilis</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus facilis</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) with a wide historical range of native plant community habitat including coastal areas, lowland dry and wet forests, and montane mesic forests on the islands of Lanai, Maui, Molokai, and Oahu, Hawaii. Now extirpated from the islands of Lanai and Maui, 
                        <E T="03">H. facilis</E>
                         is currently known from two populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">H. facilis</E>
                         is directly 
                        <PRTPAGE P="72473"/>
                        threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        Both of the 
                        <E T="03">Hylaeus facilis</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, neither population is entirely protected from impacts to habitat and predation upon the species is not currently managed within either population site. The threats to 
                        <E T="03">H. facilis</E>
                         are high in magnitude because their severity endangers the species with a relatively high likelihood of extinction throughout its entire range. The threats are ongoing throughout its entire range, thus the threats are imminent. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus hilaris</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus hilaris</E>
                         is a cleptoparasitic species of Hawaiian yellow-faced bee (family Colletidae) with a historical range in coastal habitat on the islands of Lanai, Maui, and Molokai, Hawaii. Now extirpated from the islands of Lanai and Maui, 
                        <E T="03">H. hilaris</E>
                         is currently known from a single population on Molokai containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">H. hilaris</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the small size of its remaining population, lack of additional populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        The 
                        <E T="03">Hylaeus hilaris</E>
                         population occurs within a private preserve that is managed for some of the threats affecting habitat; however, the population is not entirely protected from impacts to habitat, and predation upon the species is not currently managed at all. The threats to 
                        <E T="03">H. hilaris</E>
                         are high in magnitude because their severity presents a relatively high likelihood of extinction throughout its entire range. The threats to 
                        <E T="03">H. hilaris</E>
                         are imminent, since they are ongoing. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus kuakea</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus kuakea</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) found in lowland mesic forests on the island of Oahu, Hawaii. 
                        <E T="03">H. kuakea</E>
                         is currently known from two populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">H. kuakea</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        Both 
                        <E T="03">Hylaeus kuakea</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, neither population is entirely protected from impacts to habitat, and predation on the species is not currently managed within either population site. The threats to 
                        <E T="03">H. kuakea</E>
                         are high in magnitude because their severity presents a relatively high likelihood of extinction throughout its entire range. The threats to 
                        <E T="03">H. kuakea</E>
                         are imminent, since they are ongoing. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus longiceps</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus longiceps</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) found in certain coastal areas and dry lowland forest containing native plant communities on the islands of Lanai, Maui, Molokai, and Oahu, Hawaii. 
                        <E T="03">H. longiceps</E>
                         is currently known from six populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">H. longiceps</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        Some 
                        <E T="03">Hylaeus longiceps</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, no population is entirely protected from impacts to habitat, and predation on the species is not currently managed within any population site. The threats to 
                        <E T="03">H. longiceps</E>
                         are high in magnitude because their severity presents a relatively high likelihood of extinction throughout its entire range. The threats to 
                        <E T="03">H. longiceps</E>
                         are imminent, since they are ongoing. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hawaiian yellow-faced bee (
                        <E T="03">Hylaeus mana</E>
                        )—The following summary is based on information contained in our files and in the petition that we received for this species on March 23, 2009. 
                        <E T="03">Hylaeus mana</E>
                         is a species of Hawaiian yellow-faced bee (family Colletidae) found in lowland mesic forests on the island of Oahu, Hawaii. 
                        <E T="03">H. mana</E>
                         is currently known from four populations containing an unknown number of individuals. This species is threatened by ongoing habitat loss and modification due to the effects of feral ungulates, nonnative plants, wildfire, and climate change. 
                        <E T="03">H. mana</E>
                         is directly threatened by predation from yellow jacket wasps (
                        <E T="03">Vespula pensylvanica</E>
                        ) and several species of nonnative ants. Additional indirect threats to the species include the limited number and small size of populations, competition from European honey bees (
                        <E T="03">Apis mellifera</E>
                        ), the possibility of habitat destruction from stochastic and catastrophic events, and a lack of regulatory mechanisms affording protection to the species.
                    </P>
                    <P>
                        The 
                        <E T="03">Hylaeus mana</E>
                         populations occur in areas that are managed for one or more of the threats affecting habitat; however, the population is not entirely protected from impacts to habitat, and predation on the species is not currently managed at all. The threats to 
                        <E T="03">H. mana</E>
                         are high in magnitude because their severity presents a relatively high likelihood of extinction throughout its entire range. The threats to 
                        <E T="03">H. mana</E>
                         are imminent, since they are ongoing. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        Hermes copper butterfly (
                        <E T="03">Hermelycaena</E>
                         [Lycaena] 
                        <E T="03">hermes</E>
                        )—
                        <PRTPAGE P="72474"/>
                        Hermes copper butterfly primarily occurs in San Diego County, California, and a few records of the species have been documented in Baja California, Mexico. The species inhabits coastal sage scrub and southern mixed chaparral, and is dependent on its larval host plant, 
                        <E T="03">Rhamnus crocea</E>
                         (spiny redberry), to complete its lifecycle. Adult Hermes copper butterflies lay single eggs on spiny redberry stems where they hatch and feed until pupation occurs at the base of the plant. Hermes copper butterflies have one flight period occurring in mid-May to early-July, depending on weather conditions and elevation. We estimate there were at least 59 known separate historical populations throughout the species' range since the species was first described. Of the 59 known Hermes copper butterfly populations, 21 are extant, 27 are believed to have been extirpated, and 11 are of unknown status.
                    </P>
                    <P>Primary threats to Hermes copper butterfly are megafires (large wildfires), and small and isolated populations. Secondary threats include increased wildfire frequency that results in habitat loss, and combined impacts of existing development, possible future (limited) development, existing dispersal barriers, and fires that fragment habitat. Hermes copper butterfly occupies scattered areas of sage scrub and chaparral habitat in an arid region susceptible to wildfires of increasing frequency and size. The likelihood that individuals of the species will be burned as a result of catastrophic wildfires, combined with the isolation and small size of extant populations, makes Hermes copper butterfly particularly vulnerable to population extirpation rangewide. Overall, the threats that Hermes copper butterfly faces are high in magnitude, because the major threats (particularly mortality due to wildfire and increased wildfire frequency) occur throughout all of the species' range and are likely to result in significant adverse impacts to the status of the species. The threats are nonimminent overall, because the impact of wildfire to Hermes copper butterfly and its habitat occurs on a sporadic basis, and we do not have the ability to predict when wildfires will occur. This species faces high-magnitude nonimminent threats; therefore, we assigned this species a LPN of 5.</P>
                    <P>
                        Puerto Rican harlequin butterfly (
                        <E T="03">Atlantea tulita</E>
                        )—The following summary is based on information in our files and in the petition we received on February 29, 2009. The Puerto Rican harlequin butterfly is endemic to Puerto Rico, and one of the four species endemic to the Greater Antilles within the genus 
                        <E T="03">Atlantea.</E>
                         This species occurs within the subtropical moist forest life zone in the northern karst region (
                        <E T="03">i.e.,</E>
                         municipality of Quebradillas) of Puerto Rico, and in the subtropical wet forest (
                        <E T="03">i.e.,</E>
                         Maricao Commonwealth Forest, municipality of Maricao). The Puerto Rican harlequin butterfly has only been found utilizing 
                        <E T="03">Oplonia spinosa</E>
                         (prickly bush) as its host plant (
                        <E T="03">i.e.,</E>
                         a plant that is used for laying the eggs, and also serves as a food source for development of the larvae).
                    </P>
                    <P>The primary threats to the Puerto Rican harlequin butterfly are development, habitat fragmentation, and other natural or manmade factors such as human-induced fires, use of herbicides and pesticides, vegetation management, and climate change. These threats would substantially affect the distribution and abundance of the species, as well as its habitat. In addition, the lack of effective enforcement makes the existing policies and regulations inadequate for the protection of the species' habitat. Activities leading to habitat modification and destruction are expected to continue and potentially increase in the foreseeable future. These threats are high in magnitude and imminent because known populations occur in areas that are subject to ongoing development, increased traffic, and increased road maintenance and construction and they directly affect populations during all life stages throughout the range of the species. Therefore, we assigned a LPN of 2 to this species.</P>
                    <P>
                        Sequatchie caddisfly (
                        <E T="03">Glyphopsyche sequatchie</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species..
                    </P>
                    <P>
                        Clifton Cave beetle (
                        <E T="03">Pseudanophthalmus caecus</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Clifton Cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is cave dependent and is not found outside the cave environment. Clifton Cave beetle is known only from two privately owned caves in Woodford County, Kentucky. Soon after the species was first observed in 1963, the cave entrance was blocked due to road construction and placement of fill material along KY Highway 1964. We do not know whether the species still occurs at the original location or if it has been extirpated from the site by the closure of the cave entrance. A 2008 attempt to re-open the cave was unsuccessful. Other caves in the vicinity of this cave were surveyed for the species during 1995 and 1996, and only one additional site (Richardson's Spring) was found to support the Clifton Cave beetle.
                    </P>
                    <P>The limestone caves in which the Clifton Cave beetle is found provide a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances could have serious adverse impacts on on the survival of this species. Therefore, the magnitude of threat is high for this species. The threats are nonimminent because there are no known projects that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Coleman cave beetle (
                        <E T="03">Pseudanophthalmus colemanensis</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Icebox Cave beetle (
                        <E T="03">Pseudanophthalmus frigidus</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Icebox Cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is not found outside the cave 
                        <PRTPAGE P="72475"/>
                        environment, and is only known from one privately owned Kentucky cave in Bell County.
                    </P>
                    <P>The limestone cave in which this species is found provides a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The species has not been observed since it was originally collected, but species experts believe that it may still exist in the cave in low numbers. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills or discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances, could have serious adverse impacts on the survival of this species. The magnitude of threat is high for this species because it is limited in distribution and the threats would result in a high level of mortality or reduced reproductive capacity. The threats are nonimminent because there are no known projects that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Inquirer Cave beetle (
                        <E T="03">Pseudanophthalmus inquisitor</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        Louisville Cave beetle (
                        <E T="03">Pseudanophthalmus troglodytes</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Louisville cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon cave invertebrates. It is not found outside the cave environment and is only known from two privately owned Kentucky caves in Jefferson County. The cave entrance at the species' original location (Oxmoor, also called Highbaugh Cave) was closed due to residential development and placement of fill in the early 1990s. We do not know whether the species still occurs at the original location or if it has been extirpated from the site by the closure of the cave entrance. Several other caves in Jefferson County were surveyed for the species in 1994, but individuals of the species were observed at only one additional location, Eleven Jones Cave. This cave is located on the southeast bank of Beargrass Creek near Cave Hill Cemetery and Arboretum. Due to pollution and reportedly high carbon dioxide levels in the cave, additional searches of the cave have not been possible.
                    </P>
                    <P>The limestone caves in which this species is found provide a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances, could have serious adverse impacts on the survival of this species. The magnitude of threat is high for this species, because it is limited in distribution and the threats would have severe negative impacts on the species. The threats are non-imminent because there are no known projects that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Tatum Cave beetle (
                        <E T="03">Pseudanophthalmus parvus</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Tatum Cave beetle is a small, eyeless, reddish-brown predatory insect that feeds upon cave invertebrates. It is not found outside the cave environment and is only known from one privately owned Kentucky cave (Tatum Cave) in Marion County. Despite searches in 1980, 1996, 2004, and 2005, the species has not been observed in Tatum Cave since 1965.
                    </P>
                    <P>The limestone cave in which this species is found provides a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The species has not been observed since 1965, but species experts believe that it still exists in low numbers. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances, could have serious adverse impacts on this species. The magnitude of threat is high for this species, because its limited numbers mean that any threats could severely affect its continued existence. The threats are nonimminent, because there are no known projects that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Orangeblack Hawaiian damselfly (
                        <E T="03">Megalagrion xanthomelas</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The orangeblack Hawaiian damselfly is a stream- and pool-dwelling species endemic to the Hawaiian Islands of Kauai, Oahu, Molokai, Maui, Lanai, and Hawaii. The species no longer is found on Kauai, and is now restricted to a total of 16 populations distributed across the islands of Oahu, Maui, Molokai, Lanai, and Hawaii. This species is threatened by predation from nonnative aquatic species such as fish and predacious insects, and habitat loss through dewatering of streams and invasion by nonnative plants. Nonnative fish and insects prey on the larval-stage naiads of the damselfly, and loss of water reduces the amount of suitable habitat for the naiad life stage. Invasive plants (
                        <E T="03">e.g.,</E>
                         California grass (
                        <E T="03">Brachiaria mutica</E>
                        )) also contribute to loss of habitat by forming dense, monotypic stands that completely eliminate open water. Nonnative fish and plants are found in all the streams where orangeblack Hawaiian damselflies occur, except at the single Oahu population, where there are no nonnative fish. We have retained an LPN of 8 for this species because, although the threats are ongoing and therefore imminent, they affect the different populations of the species to varying degrees throughout the species' range and are thus of moderate magnitude.
                    </P>
                    <P>
                        Rattlesnake-master borer moth 
                        <E T="03">(Papaipema eryngii)</E>
                        —The following information is based on information in our files. Rattlesnake-master borer moths are obligate residents of undisturbed prairie remnants, savanna, and pine barrens that contain their only food plant—rattlesnake-master 
                        <E T="03">(Eryngium yuccifolium).</E>
                         The rattlesnake-master borer moth is known from 16 sites distributed over 5 States: Illinois, Arkansas, Kentucky, Oklahoma, 
                        <PRTPAGE P="72476"/>
                        and North Carolina. Currently 12 of the sites contain extant populations, 3 contain populations with unknown status, and 1 contains a population that is considered extirpated.
                    </P>
                    <P>Although the rattlesnake-master plant is widely distributed across 26 States and is a common plant in remnant prairies, it is a conservative species, meaning it is not found in disturbed areas, with relative frequencies of less than 1 percent. The habitat range for the rattlesnake-master borer moth is very narrow and appears to be limiting for the species. The ongoing effects of habitat loss, fragmentation, degradation, and modification from agriculture, development, flooding, invasive species, and secondary succession have resulted in fragmented populations and population declines. Rattlesnake-master borer moths are affected by habitat fragmentation and population isolation. Almost all of the sites with extant populations of the rattlesnake-master borer moth are isolated from one another, with the populations in Kentucky, North Carolina, and Oklahoma occurring within a single site for each State, thus precluding recolonization from other populations. These small, isolated populations are likely to become unviable over time due to lower genetic diversity reducing their ability to adapt to environmental change, effects of stochastic events, and inability to recolonize areas where they are extirpated.</P>
                    <P>Rattlesnake-master borer moths have life-history traits that make them more susceptible to outside stressors. They are univoltine (having a single flight per year), do not disperse widely, and are monophagous (have only one food source). The life history of the species makes it particularly sensitive to fire, which is the primary practice used in prairie management. The species is only safe from fire once it bores into the root of the host plant, which makes adult, egg, and first larval stages subject to mortality during prescribed burns and wildfires. Fire and grazing cause direct mortality to the moth and destroy food plants if the intensity, extent, or timing is not conducive to the species' biology. Although fire management is a threat to the species, lack of management is also a threat, and at least one site has become extirpated likely because of the succession to woody habitat. The species is sought after by collectors, and the host plant is very easy to identify, making the moth susceptible to collection, and thus many sites are kept undisclosed to the public.</P>
                    <P>Existing regulatory mechanisms provide protection for 12 of the 16 sites containing rattlesnake-master borer moth populations. Illinois' endangered species statute provides regulatory mechanisms to protect the species from potential impacts from actions such as development and collecting on the 10 Illinois sites; however, illegal collections of the species have occurred at two sites. A permit is required for collection by site managers within the sites in North Carolina and Oklahoma. The rattlesnake-master borer moth is also listed as endangered in Kentucky by the State's Nature Preserves Commission, although at this time the Kentucky legislature has not enacted any statute that provides legal protection for species listed as threatened or endangered. There are no statutory mechanisms in place to protect the populations in North Carolina, Arkansas, or Oklahoma.</P>
                    <P>Some threats that the rattlesnake-master moth faces are high in magnitude, such as habitat conversion and fragmentation, and population isolation. These threats with the highest magnitude occur in many of the populations throughout the species' range, but although they are likely to affect each population at some time, they are not likely to affect all of the populations at any one time. Other threats, such as agricultural and nonagricultural development, mortality from implementation of some prairie management tools (such as fire), flooding, succession, and climate change are of moderate to low magnitude. For example, the life history of rattlesnake-master borer moths makes them highly sensitive to fire, which can cause mortality of individuals through most of the year and can affect entire populations. Conversely, complete fire suppression can also be a threat to rattlesnake-master borer moths as prairie habitat declines and woody or invasive species become established such that the species' only food plant is not found in disturbed prairies. Although these threats can cause direct and indirect mortality of the species, they are of moderate or low magnitude because they affect only some populations throughout the range and to varying degrees. Overall, the threats are moderate. The threats are imminent because they are ongoing; every known population of rattlesnake-master borer moth has at least one ongoing threat, and some have several working in tandem. Thus, we assigned a LPN of 8 to this species.</P>
                    <P>
                        Stephan's riffle beetle (
                        <E T="03">Heterelmis stephani</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. The Stephan's riffle beetle is an endemic riffle beetle historically found in limited spring environments within the Santa Rita Mountains, Pima County, Arizona. In the most recent surveys conducted in 1993, the Stephan's riffle beetle was documented only in Sylvester Spring in Madera Canyon, Santa Cruz County, within the Coronado National Forest. Suspected potential threats to that spring are largely from habitat modification, and potential changes in water quality and quantity due to catastrophic natural events (such as wildfire or flooding from storms). The threats are of low to moderate magnitude because the Forest Service has no plans to modify the springs where this species occurs. In addition, the effects of the other threats are unlikely to be permanent, as they stem from occasional natural events that do not result in permanent water quality degradation. In addition, because of the physical habitat structure (large boulders surrounding the springs) and the location of the springs (on hillsides above the stream or in the headwaters where there is little watershed to generate large flood flows), flooding, resulting from thunderstorms or post-fire runoff is not a factor affecting this species at this time. Additionally, there is a higher likelihood that the species will persist in areas that are unaffected by the threats; it is unlikely that all areas of the spring would be simultaneously be affected. Threats from habitat modification have already occurred and are no longer ongoing. Therefore, the threats are not imminent. Thus, we retain an LPN of 11 for the Stephan's riffle beetle.
                    </P>
                    <P>
                        Arapahoe snowfly (
                        <E T="03">Capnia arapahoe</E>
                        )—The following summary is based on information contained in our files. This insect is a winter stonefly associated with clean, cool, running waters. Adult snowflies emerge in late winter from the space underneath stream ice. The Arapahoe snowfly is known to be found only in a short section of Elkhorn Creek, a small tributary of the Cache la Poudre River in the Roosevelt National Forest, Larimer County, Colorado. New surveys completed in 2013 indicate that the Arapahoe snowfly may occur in additional drainages other than Elkhorn Creek; however, the results are preliminary, and surveys are continuing in 2014. We will evaluate and incorporate the results of these new surveys into our review when they become available. The species previously occurred downriver at Young Gulch, but it is likely that either habitat became unsuitable or other unknown causes extirpated the species. Habitats 
                        <PRTPAGE P="72477"/>
                        at Young Gulch were further degraded by the High Park Fire in 2012, and potentially by a flash flood disaster in September 2013.
                    </P>
                    <P>Climate change is a threat to the Arapahoe snowfly, and modifies its habitats by reducing snowpacks, increasing temperatures, fostering mountain pine beetle outbreaks, and increasing the frequency of destructive wildfires. Limited dispersal capabilities, an extremely restricted range, dependence on pristine habitats, and a small population size make the Arapahoe snowfly vulnerable to demographic stochasticity, environmental stochasticity, and random catastrophes. Furthermore, regulatory mechanisms inadequately reduce these threats, which may act cumulatively to affect the species. The threats to the Arapahoe snowfly are high in magnitude because they occur throughout the species' limited range. However, the threats are nonimminent. While limited dispersal capabilities, restricted range, dependence on pristine habitats, and small population size are characteristics that make this species vulnerable to stochastic events and catastrophes (and potential impacts from climate change), these events are not currently occurring and increased temperatures will adversely affect the species in the future. Therefore, we have assigned the Arapahoe snowfly an LPN of 5.</P>
                    <P>
                        Meltwater lednian stonefly (
                        <E T="03">Lednia tumana</E>
                        )—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. This species is an aquatic insect in the order Plecoptera (stoneflies). Stoneflies are primarily associated with clean, cool streams and rivers. Eggs and nymphs (juveniles) of the meltwater lednian stonefly are found in high-elevation, alpine, and subalpine streams, most typically in locations closely linked to glacial runoff. The species is generally restricted to streams with mean summer water temperature less than 10 °C (50 °F). The only known meltwater lednian stonefly occurrences are within Glacier National Park (NP), Montana.
                    </P>
                    <P>Climate change, and the associated effects of glacier loss (with glaciers predicted to be gone by 2030)—including reduced streamflows, and increased water temperatures—are expected to significantly reduce the occurrence of populations and extent of suitable habitat for the species in Glacier NP. In addition, the existing regulatory mechanisms are not adequate to address these environmental changes due to global climate change. We determined that the meltwater lednian stonefly was a candidate for listing in a warranted-but-precluded 12-month petition finding published on April 5, 2011 (76 FR 18684). We have assigned the species an LPN of 5, based on three criteria: (1) The high magnitude of threat, which is projected to substantially reduce the amount of suitable habitat relative to the species' current range; (2) the low immediacy of the threat based on the lack of documented evidence that climate change is affecting stonefly habitat; and (3) the taxonomic status of the species, which is a full species.</P>
                    <P>
                        Highlands tiger beetle (
                        <E T="03">Cicindela highlandensis</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <HD SOURCE="HD2">Crustaceans</HD>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Metabetaeus lohena</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Metabetaeus lohena</E>
                         is a species of shrimp belonging to the family Alpheidae that inhabits anchialine pools. This species is endemic to the Hawaiian Islands, with populations on the islands of Oahu, Maui, and Hawaii. The primary threats to this species are predation by fish (
                        <E T="03">i.e.,</E>
                         fish species that do not naturally occur in the pools inhabited by this species) and habitat loss from degradation (primarily from illegal trash dumping). Populations of 
                        <E T="03">M. lohena</E>
                         on the islands of Maui and Hawaii are located within State Natural Area Reserves (NARs) and in a National Park. Both the State NARs and the National Park prohibit the collection of the species and the disturbance of the pools. However, enforcement of collection and disturbance prohibitions is difficult, and the negative effects from the introduction of fish can occur suddenly and could quickly decimate a population. On Oahu, four pools containing this species are located in a National Wildlife Refuge and are protected from collection and disturbance to the pool; however, on State-owned land where the species occurs, there is no protection from collection or disturbance of the pools. Threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, and are thus of a high magnitude. The primary threats of predation from fish and loss of habitat due to degradation are nonimminent, because on the islands of Maui and Hawaii no fish were observed in any of the pools where this species occurs, and there has been no documented trash dumping in these pools. Therefore, we have retained an LPN of 5 for this species.
                    </P>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Palaemonella burnsi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Palaemonella burnsi</E>
                         is a species of shrimp belonging to the family Palaemonidae, that inhabits anchialine pools. This species is endemic to the Hawaiian Islands with populations on the islands of Maui and Hawaii. The primary threats to this species are predation by nonnative fish (
                        <E T="03">i.e.,</E>
                         fish species that do not naturally occur in the pools inhabited by this species) and habitat loss due to degradation (primarily from illegal trash dumping). This species' populations on Maui are located within a State Natural Area Reserve (NAR). Hawaii's State statutes prohibit the collection of the species and the disturbance of the pools in State NARs. On the island of Hawaii, the species occurs within a State NAR and a National Park, where collection and disturbance are also prohibited. However, enforcement of these prohibitions is difficult, and the negative effects from the introduction of fish can occur suddenly and could quickly decimate a population. Therefore, threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, and thus are of a high magnitude. The threats are nonimminent, because surveys in 2004 and 2007 did not find fish in the pools where these shrimp occur on Maui or the island of Hawaii. Also, there was no evidence of recent habitat degradation at those pools. Therefore, we have retained an LPN of 5 for this species.
                    </P>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Procaris hawaiana</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Procaris hawaiana</E>
                         is a species of shrimp belonging to the family Procarididae that inhabits anchialine pools. This species is endemic to the Hawaiian Islands, and is currently 
                        <PRTPAGE P="72478"/>
                        known from 2 pools on the island of Maui and 12 pools on the island of Hawaii. The primary threats to this species are predation from nonnative fish (
                        <E T="03">i.e.,</E>
                         fish species that do not naturally occur in the pools inhabited by this species) and habitat loss due to degradation (primarily from illegal trash dumping). This species' populations on Maui are located within a State Natural Area Reserve (NAR). Twelve pools containing this species on the island of Hawaii are also located within a State NAR. Hawaii's State statutes prohibit the collection of the species and the disturbance of the pools in State NARs. However, enforcement of these prohibitions is difficult, and the negative effects from the introduction of fish can occur suddenly and could quickly decimate a population. In addition, there are no prohibitions for either removal of the species or disturbance to one pool containing this species located outside a NAR on the island of Hawaii. Therefore, threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, and thus remain at a high magnitude. The threats to the species are nonimminent, because, during 2004 and 2007 surveys, no nonnative fish were observed in the pools where these shrimp occur on Maui, nor were they observed in the one pool on the island of Hawaii that was surveyed in 2005. In addition, there were no signs of dumping or fill in any of the pools where the species occurs. Therefore, we have retained an LPN of 5 for this species.
                    </P>
                    <HD SOURCE="HD2">Flowering Plants</HD>
                    <P>
                        <E T="03">Abronia alpina</E>
                         (Ramshaw Meadows sand-verbena)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Abronia alpina</E>
                         is a small perennial herb in the Nyctaginaceae (four-o'clock) family, 2.5 to 15.2 cm (1 to 6 in) across, forming compact mats with lavender-pink, trumpet-shaped, and generally fragrant flowers. 
                        <E T="03">Abronia alpina</E>
                         is known from one main population center at Ramshaw Meadow and a smaller population at the adjacent Templeton Meadow. The meadows are located on the Kern River Plateau in the Sierra Nevada, on lands administered by the Inyo National Forest, in Tulare County, California. The total estimated area occupied is approximately 6 hectares (15 acres). The population fluctuates from year to year without any clear trends. Population estimates for the years from 1985 up to, but not including, 2012 range from a high of approximately 130,000 plants in 1997 to a low of approximately 40,000 plants in 2003. In 2012, when the population was last monitored, the estimated total population increased to approximately 156,000 plants.
                    </P>
                    <P>
                        The factors currently threatening 
                        <E T="03">Abronia alpina</E>
                         include natural and human habitat alteration, lowering of the water table due to erosion within the meadow system, and recreational use within meadow habitats. Lodgepole pines are encroaching upon meadow habitat with trees germinating within 
                        <E T="03">A. alpina</E>
                         habitat, occupying up to 20 percent of two 
                        <E T="03">A. alpina</E>
                         subpopulations. Lodgepole pine encroachment may alter soil characteristics by increasing organic matter levels, decreasing porosity, and moderating diurnal temperature fluctuations thus reducing the competitive ability of 
                        <E T="03">A. alpina</E>
                         to persist in an environment more hospitable to other plant species. The habitat occupied by 
                        <E T="03">Abronia alpina</E>
                         directly borders the meadow system, which is supported by the South Fork of the Kern River. The river flows through the meadow, at times coming within 15 m (50 ft) of 
                        <E T="03">Abronia alpina</E>
                         habitat, particularly in the vicinity of five subpopulations. Past livestock trampling and past removal of bank-stabilizing vegetation by grazing livestock have contributed to down-cutting of the river channel through the meadow, leaving the meadow subject to potential alteration by lowering of the water table. In 2001, the Forest Service began resting the grazing allotment for 10 years, thereby eliminating cattle use. The allotment is still being rested while the Forest Service assesses the data collected on the rested allotment for eventual inclusion in an environmental analysis to consider resumption of grazing. Established hiker, packstock, and cattle trails pass through 
                        <E T="03">A. alpina</E>
                         subpopulations. Two main hiker trails pass through Ramshaw Meadow, but in 1988 and 1997, they were rerouted out of 
                        <E T="03">A. alpina</E>
                         subpopulations. Occasional incidental use by horses and hikers sometimes occurs on the remnants of cattle trails that pass through subpopulations in several places.
                    </P>
                    <P>
                        The Service has funded studies to determine appropriate conservation measures for the species and is working with the U.S. Forest Service on developing a conservation strategy for the species. The remaining threats affect individuals in the population and have not appeared to have population-level effects. Therefore, the threats are low in magnitude. In addition, because the grazing activities have been eliminated for the time being and the hiking trails have been rerouted, the threats are not imminent. The LPN for 
                        <E T="03">A. alpina</E>
                         remains an 11 due to the presence of moderate-to-low threats, and the determination that the threats are not imminent at this point in time.
                    </P>
                    <P>
                        <E T="03">Argythamnia blodgettii</E>
                         (Blodgett's silverbush)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Artemisia</E>
                          
                        <E T="03">borealis</E>
                         var. 
                        <E T="03">wormskioldii</E>
                         (Northern wormwood)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Historically known from eight sites, 
                        <E T="03">Artemisia campestris</E>
                         var. 
                        <E T="03">wormskioldii</E>
                         (formerly 
                        <E T="03">A. borealis</E>
                         var. 
                        <E T="03">wormskioldii</E>
                        ) is currently known from two natural populations (one in Klickitat County and one in Grant County, Washington) and four outplanted populations in Oregon and Washington. This plant is restricted to exposed basalt, cobbly-sandy terraces, and sand habitat along the shore of, and on islands within, the Columbia River. Annual monitoring indicates that the two natural populations have declined from historical numbers and now total roughly 550 individuals. Two populations were outplanted with approximately 3,000 individuals, and when monitored in 2012, approximately 900 individuals still remained; the other two outplanted populations have not been monitored since 120 individuals were outplanted at the sites in 2013. It is possible that additional natural populations of the species exist as there are relatively large stretches of the mid-Columbia River and its tributaries that have not been surveyed specifically for this plant; however, we currently know of the species only from the above six locations. The species is also cultivated 
                        <E T="03">ex situ</E>
                         for future translocation projects.
                    </P>
                    <P>
                        Habitat loss from inundation behind hydroelectric dams and placement of riprap along the Columbia River is thought to be the cause of historical population loss. Current threats to northern wormwood include possible direct loss of habitat through regulation of water levels in the Columbia River; 
                        <PRTPAGE P="72479"/>
                        human trampling of plants from recreation; competition with nonnative invasive species; burial by wind- and water-borne sediments; small population sizes; susceptibility to genetic drift and inbreeding; and the potential for hybridization with two other species of 
                        <E T="03">Artemisia.</E>
                         At the Grant County site, ongoing conservation actions have reduced trampling, but have not eliminated or reduced the other threats. At the Klickitat County site (Miller Island), active conservation measures are not currently in place. The magnitude of these threats is high, as the remaining populations are small, isolated, and each could be eliminated by a single disturbance. The threats are imminent because recreational use is ongoing, invasive nonnative species occur at both sites, erosion of the substrate is ongoing at the Klickitat County site, and high water flows may occur unpredictably in any year. Therefore, we have retained an LPN of 3 for this variety.
                    </P>
                    <P>
                        <E T="03">Astragalus anserinus</E>
                         (Goose Creek milkvetch)—The following summary is based on information in our files and in the petition received on February 3, 2004. The majority (over 80 percent) of Goose Creek milkvetch sites in Idaho, Utah, and Nevada occur on Federal lands managed by the Bureau of Land Management. The rest of the sites occur as small populations on private and State lands in Utah and on private land in Idaho and Nevada. Goose Creek milkvetch occurs in a variety of habitats, but is typically associated with dry, tuffaceous soils (made up of rock consisting of smaller kinds of volcanic detritus) from the Salt Lake Formation. The species grows on steep or flat sites, with soil textures ranging from silty to sandy to somewhat gravelly. The species tolerates some level of disturbance, based on its occurrence on steep slopes, where downhill movement of soil is common.
                    </P>
                    <P>The primary threat to Goose Creek milkvetch is habitat degradation and modification resulting from an altered wildfire regime, fire suppression activities, and rehabilitation efforts to recover lands that have burned. Other factors that also appear to threaten Goose Creek milkvetch include livestock use and invasive nonnative species. The existing regulatory mechanisms are not adequate to address these threats. Climate change effects to Goose Creek drainage habitats are possible, but we are unable to predict the specific impacts of this change to Goose Creek milkvetch at this time.</P>
                    <P>The magnitude of threats is high as available monitoring data indicate declines in excess of 70 percent within the perimeter of wildfires that occurred in 2007 which negatively affected nearly 50 percent of the known occurrences in Nevada and Utah. In addition, livestock use impacts were observed at all sites visited in Utah in 2011 with 25 percent of the sites (containing 73 percent of the individuals) being directly affected. The threats to the species are imminent, or currently occurring, largely as a result of land management actions taken since fires initially altered the habitat. The threats associated with livestock grazing and invasive species are occurring throughout a large portion of the species' range. The high magnitude and immediacy of threats leave the species and its small populations more vulnerable to stochastic events. Therefore, we have assigned the Goose Creek milkvetch an LPN of 2.</P>
                    <P>
                        <E T="03">Astragalus microcymbus</E>
                         (Skiff milkvetch)—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. Skiff milkvetch is a perennial forb that dies back to the ground every year. It has a very limited range and a spotty distribution within Gunnison and Saguache Counties in Colorado, where it is found in open, park-like landscapes in the sagebrush-steppe ecosystem on rocky or cobbly, moderate-to-steep slopes of hills and draws.
                    </P>
                    <P>The most significant threats to skiff milkvetch are recreation, roads, trails, and habitat fragmentation and degradation. Existing regulatory mechanisms are not adequate to protect the species from these threats. Recreational impacts are likely to increase, given the close proximity of skiff milkvetch to the town of Gunnison and the increasing popularity of mountain biking, motorcycling, and all-terrain vehicles. Furthermore, the Hartman Rocks Recreation Area draws users, and contains over 40 percent of the skiff milkvetch units. Other threats to the species include residential and urban development; livestock, deer, and elk use; climate change; increasing periodic drought; nonnative invasive cheatgrass; and wildfire. The threats to skiff milkvetch are moderate in magnitude, because, while serious and occurring rangewide, they do not collectively result in population declines on a short time scale. The threats are imminent, because the species is currently facing them in many portions of its range. Therefore, we have assigned skiff milkvetch an LPN of 8.</P>
                    <P>
                        <E T="03">Astragalus schmolliae</E>
                         (Schmoll milkvetch)—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. Schmoll milkvetch is a narrow endemic perennial plant that grows in the mature pinyon-juniper woodland of mesa tops in the Mesa Verde National Park area and in the Ute Mountain Ute Tribal Park in Colorado.
                    </P>
                    <P>The most significant threats to the species are degradation of habitat by fire, followed by invasion by nonnative cheatgrass and subsequent increase in fire frequency. These threats currently affect about 40 percent of the species' entire known range, and cheatgrass is likely to increase, given (1) its rapid spread and persistence in habitat disturbed by wildfires, fire and fuels management and development of infrastructure, and (2) the inability of land managers to control it on a landscape scale. Other threats to Schmoll milkvetch include fire break clearings, drought, and feral livestock grazing; existing regulatory mechanisms are not adequate to address these threats. The threats to the species overall are imminent, because they are ongoing, and moderate in magnitude, because the species is currently facing them in many portions of its range, but the threats do not collectively result in population declines on a short time scale. Therefore, we have assigned Schmoll milkvetch an LPN of 8.</P>
                    <P>
                        <E T="03">Astragalus tortipes</E>
                         (sleeping Ute milkvetch)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Sleeping Ute milkvetch is a perennial plant that grows only on the Smokey Hills layer of the Mancos Shale Formation on the Ute Mountain Ute Indian Reservation in Montezuma County, Colorado.
                    </P>
                    <P>
                        In 2000, a total of 3,744 plants were recorded at 24 locations covering 500 acres within an overall range of 6,400 acres. Available information from 2000 and 2009 indicated that the species' status was stable at that time. However, previous and ongoing threats from borrow pit excavation, off-highway vehicles, irrigation canal construction, and a prairie dog colony have had minor impacts that reduced the range and number of plants by small amounts. Off road-vehicle use of the habitat has reportedly been controlled by fencing. Oil and gas development is active in the general area, but the Service has received no information to indicate that there is development within plant habitat. In 2011, the tribal Environmental Programs Department reported habitat disturbance by vehicles and activity at the shooting range located within the plant habitat. The Tribe reported that the status of the species remained unchanged. The Tribe has been working on a management 
                        <PRTPAGE P="72480"/>
                        plan that will include a monitoring program for this species, among others. We had expected the final plan to be released in 2010, but it still has not been completed. We have no documentation concerning the current status of the plants, condition of habitat, and terms of the species management plan being drafted by the Tribe. Thus, at this time, we cannot accurately assess whether populations are being adequately protected from previously existing threats. The threats are moderate in magnitude, since they have had only minor impacts. Until the management plan is completed there are no regulatory mechanisms in place to protect the species from the threats described above. Overall, we conclude that threats are moderate to low and nonimminent. Therefore, we assigned an LPN of 11 to this species.
                    </P>
                    <P>
                        <E T="03">Boechera pusilla</E>
                         (Fremont County rockcress)—The following summary is based on information in our files and in the petition received on July 24, 2007. 
                        <E T="03">Boechera pusilla</E>
                         is a perennial herb that occupies sparsely vegetated, coarse granite soil pockets in exposed granite-pegmatite outcrops, with slopes generally less than 10 degrees, at an elevation between 2,438 and 2,469 m (8,000 and 8,100 ft). The only known population of 
                        <E T="03">B. pusilla</E>
                         is located in Wyoming on lands administered by the Bureau of Land Management in the southern foothills of the Wind River Range. 
                        <E T="03">B. pusilla</E>
                         is likely restricted in distribution by the limited occurrence of pegmatite (a very coarse-grained rock formed from magma or lava) in the area. The specialized habitat requirements of 
                        <E T="03">B. pusilla</E>
                         have allowed the plant to persist without competition from other herbaceous plants or sagebrush-grassland species that are present in the surrounding landscape.
                    </P>
                    <P>
                        <E T="03">Boechera pusilla</E>
                         has a threat that is not identified, but that is indicated by the small and overall declining population size. Although the threat is not fully understood, we know it exists as indicated by the declining population. The population size may be declining from a variety of unknown causes, with drought or disease possibly contributing to the trend. The downward trend may have been leveled off somewhat recently, but without improved population numbers, the species may reach a population level at which other stressors become threats. We are unable to determine how climate change may affect the species in the future. To the extent that we understand the species, other potential habitat-related threats have been removed through the implementation of Federal regulatory mechanisms and associated actions. Overutilization, predation, and the inadequacy of regulatory mechanisms are likely threats to the species. The threats that 
                        <E T="03">B. pusilla</E>
                         faces are moderate in magnitude, primarily because of the recent leveling off of the population decline. The threat to 
                        <E T="03">B. pusilla</E>
                         is imminent, because we have evidence that the species is currently facing a threat indicated by reduced population size. The threat appears to be ongoing, although we are unsure of the extent and timing of its effects on the species. Thus, we have assigned 
                        <E T="03">B. pusilla</E>
                         an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Calamagrostis expansa</E>
                         (Maui reedgrass)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Calamagrostis expansa</E>
                         is a perennial grass found in wet forests and bogs, and in bog margins, on the Hawaiian Islands of Maui and Hawaii. This species is known from 13 populations collectively totaling fewer than 750 individuals.
                    </P>
                    <P>
                        <E T="03">Calamagrostis expansa</E>
                         is threatened by habitat degradation and loss by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), and by competition with nonnative plants. All of the known populations of 
                        <E T="03">C. expansa</E>
                         on Maui occur in managed areas. Pig exclusion fences have been constructed, and control of nonnative plants is ongoing within the exclosures but still pose a threat to the species. On the island of Hawaii, the population in the Upper Waiakea Forest Reserve has been fenced entirely. This species is not represented in an 
                        <E T="03">ex situ</E>
                         collection. Threats to this species from feral pigs and nonnative plants are still ongoing despite the conservation actions, and are thus imminent and of high magnitude, given the limited number of individuals, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Calochortus persistens</E>
                         (Siskiyou mariposa lily)—The following summary is based on information contained in our files and the petition we received on September 10, 2001. The Siskiyou mariposa lily is a narrow endemic that is restricted to three disjunct ridge tops in the Klamath-Siskiyou Range near the California-Oregon border. The southernmost occurrence of this species is composed of nine separate sites on approximately 17.6 ha (43.4 ac) of Klamath National Forest and privately owned lands that stretch for 10 km (6 mi) along the Gunsight-Humbug Ridge, Siskiyou County, California. In 2007, a new occurrence was confirmed in the locality of Cottonwood Peak and Little Cottonwood Peak, Siskiyou County, where several populations are distributed over 164 ha (405 ac) on three individual mountain peaks in the Klamath National Forest and on private lands. The northernmost occurrence consists of not more than five Siskiyou mariposa lily plants that were discovered in 1998, on Bald Mountain, west of Ashland, Jackson County, Oregon.
                    </P>
                    <P>
                        Major threats include competition and shading by native and nonnative species fostered by suppression of wildfire; increased fuel loading and subsequent risk of wildfire; fragmentation by roads, fire breaks, tree plantations, and radio-tower facilities; maintenance and construction around radio towers and telephone relay stations located on Gunsight Peak and Mahogany Point; and soil disturbance, direct damage, and nonnative weed and grass species introduction as a result of heavy recreational use and construction of fire breaks. Dyer's woad (
                        <E T="03">Isatis tinctoria</E>
                        ), an invasive, nonnative plant that may prevent germination of Siskiyou mariposa lily seedlings, has invaded 75 percent of the known lily habitat on Gunsight-Humbug Ridge, the southernmost California occurrence. Forest Service staff and the Klamath-Siskiyou Wildlands Center cite competition with dyer's woad as a significant and chronic threat to the survival of Siskiyou mariposa lily.
                    </P>
                    <P>
                        The combination of restricted range, extremely low numbers (five plants) in one of three disjunct populations, poor competitive ability, short seed dispersal distance, slow growth rates, low seed production, apparently poor survival rates in some years, herbivory, habitat disturbance, and competition from nonnative invasive plants threatens the continued existence of this species. The main threat is competition by dyer's woad. However, because efforts are under way to reduce the threat of dyer's woad where it is found and there is no evidence of a decline in 
                        <E T="03">C. persistens</E>
                         populations where this weed has become most widely distributed, the magnitude of existing threats is moderate. Overall, the threats are nonimment since the threats of competition from nonnative invasive plants has been reduced to localized areas and are not anticipated to overwhelm a large portion of the species' range in the immediate future. The likelihood that a large proportion of the Gunsight-Humbug Ridge range would be affected by disturbance, and therefore invaded by dyer's woad at the same time, is low. Therefore, we have assigned a LPN of 11 to this species.
                    </P>
                    <P>
                        <E T="03">Chamaecrista lineata</E>
                         var. 
                        <E T="03">keyensis</E>
                         (Big Pine partridge pea)—We continue to find that listing this species is 
                        <PRTPAGE P="72481"/>
                        warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">pinetorum</E>
                         (Pineland sandmat)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">serpyllum</E>
                         (Wedge spurge)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         (San Fernando Valley spineflower)—The following summary is based on information contained in our files and the petition received on December 14, 1999. 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         is a low-growing herbaceous annual plant in the buckwheat family. Germination occurs following the onset of late-fall and winter rains and typically represents different cohorts from the seed bank. Flowering occurs in the spring, generally between April and June. The plant currently is known from two disjunct localities: The first is in the southeastern portion of Ventura County on a site within the Upper Las Virgenes Canyon Open Space Preserve, formerly known as Ahmanson Ranch, and the second is in an area of southwestern Los Angeles County known as Newhall Ranch. Investigations of historical locations and seemingly suitable habitat within the range of the species have not revealed any other occurrences.
                    </P>
                    <P>
                        The threats facing 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         include threatened destruction, modification, or curtailment of its habitat or range (Factor A), inadequacy of existing regulatory mechanisms (Factor D), and other natural or manmade factors (Factor E). The threats to 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         from habitat destruction or modification are lower in magnitude than they were 9 years ago when we originally determined that the species was a candidate for listing. One of the two populations (Upper Las Virgenes Canyon Open Space Preserve) is now in permanent public ownership and is being managed by an agency that is working to conserve the plant; however, the use of adjacent habitat for Hollywood film productions was brought to our attention in 2007, and the potential impacts to 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         are not yet clear. During a site visit to the Preserve in April 2012, we noted an abundance of nonnative species that, if not managed, could degrade the quality of the habitat for 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         over time. We will be working with the landowners to manage the site for the benefit of 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina.</E>
                    </P>
                    <P>
                        The other population (Newhall Ranch) is under the threat of development. A CCA was being developed with the landowner to address conservation of the plants; however, as of 2014, work on the CCA has been suspended. Until such an agreement is finalized, the threat of development and the potential damage to the Newhall Ranch population still exist, as shown by the destruction of some plants during installation of an agave farm. Furthermore, cattle grazing on Newhall Ranch may be a current threat. Cattle grazing may harm 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         by trampling and soil compaction. Grazing activity could also alter the nutrient (
                        <E T="03">e.g.,</E>
                         elevated organic material levels) content of the soils for 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         habitat through fecal inputs, which in turn may favor the growth of other plant species that would otherwise not grow so readily on the mineral-based soils. Over time, changes in species composition may render the sites less favorable for the persistence of 
                        <E T="03">C. parryi</E>
                         var. 
                        <E T="03">fernandina. Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         may be threatened by invasive nonnative plants, including grasses, which could potentially displace it from available habitat; compete for light, water, and nutrients; and reduce survival and establishment.
                    </P>
                    <P>
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         is particularly vulnerable to extinction due to its concentration in two isolated areas. The existence of only two areas of occurrence, and a relatively small range, makes the variety highly susceptible to extinction or extirpation from a significant portion of its range due to random events such as fire, drought, and erosion. We retained an LPN of 6 for this species due to high-magnitude, nonimminent threats.
                    </P>
                    <P>
                        <E T="03">Cirsium wrightii</E>
                         (Wright's marsh thistle)—The following summary is based on information from the 12-month warranted-but-precluded finding published November 4, 2010 (75 FR 67925), as well as any new information gathered since then. Wright's marsh thistle is a flowering plant in the sunflower family. It is prickly with short black spines and a 3- to 8-foot (ft) (0.9- to 2.4-meter (m)) single stalk covered with succulent leaves. Flowers are white to pale pink in areas of the Sacramento Mountains, but are vivid pink in all the Pecos Valley locations. There are eight general confirmed locations of Wright's marsh thistle in New Mexico: Santa Rosa, Guadalupe County; Bitter Lake National Wildlife Refuge, Chaves County; Blue Spring, Eddy County; La Luz Canyon, Karr Canyon, Silver Springs, and Tularosa Creek, Otero County; and Alamosa Creek, Socorro County. Wright's marsh thistle has been extirpated from all previously known locations in Arizona, and was misidentified and likely not ever present in Texas. The status of the species in Mexico is uncertain, with few verified collections.
                    </P>
                    <P>
                        Wright's marsh thistle faces threats primarily from natural and human-caused modifications of its habitat due to ground and surface water depletion, drought, invasion of 
                        <E T="03">Phragmites australis,</E>
                         and from the inadequacy of existing regulatory mechanisms. The species occupies relatively small areas of seeps, springs, and wetland habitat in an arid region plagued by drought and ongoing and future water withdrawals. The species' highly specific requirements of saturated soils with surface or subsurface water flow make it particularly vulnerable.
                    </P>
                    <P>
                        Long-term drought, in combination with ground and surface waterwithdrawal, pose a current and future threat to Wright's marsh thistle and its habitat. In addition, we expect that these threats will likely intensify in the foreseeable future. However, the threats are moderate in magnitude because the majority of the threats (habitat loss and degradation due to alteration of the hydrology of its rare wetland habitat), while serious and 
                        <PRTPAGE P="72482"/>
                        occurring rangewide, do not at this time collectively and significantly adversely affect the species at a population level. All of the threats are ongoing and therefore imminent. Thus, we continue to assign an LPN of 8 to Wright's marsh thistle.
                    </P>
                    <P>
                        <E T="03">Dalea carthagenensis</E>
                         ssp. 
                        <E T="03">floridana</E>
                         (Florida prairie-clover)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Dichanthelium hirstii</E>
                         (Hirst Brothers' panic grass)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Dichanthelium hirstii</E>
                         is a perennial grass that produces erect, leafy, flowering stems from May to October. The species occurs in coastal plain intermittent ponds, usually in wet savanna or pine barren habitats, and is known to occur at only three sites in New Jersey, one site in Delaware, and two sites in North Carolina. While all six extant 
                        <E T="03">D. hirstii</E>
                         populations are located on public land, threats to the species from encroachment of woody and herbaceous vegetation, competition from rhizomatous perennials, fluctuations in hydrology, and threats associated with small population number and size are significant. Given the naturally fluctuating number of plants found at each site, and the isolated nature of the wetlands (limiting dispersal opportunities), even small changes in the species' habitat could result in local extirpation. With so few populations, the loss of any known sites would constitute a significant contraction of the species' range and increase the risk of extinction of the species. Because most of the significant threats to 
                        <E T="03">D. hirstii</E>
                         affect the species over a period of years and, in some cases, are being managed to some extent, the threats are nonimminent. Based on nonimminent threats of a high magnitude, we retain a LPN of 5 for this species.
                    </P>
                    <P>
                        <E T="03">Digitaria pauciflora</E>
                         (Florida pineland crabgrass)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Eriogonum soredium</E>
                         (Frisco buckwheat)—The following summary is based on information in our files and the petition we received on July 30, 2007. Frisco buckwheat is a narrow endemic perennial plant restricted to soils derived from Ordovician limestone outcrops. The range of the species is less than 5 sq mi (13 sq km), with four known populations. All four populations occur exclusively on private lands in Beaver County, Utah, and each population occupies a very small area with high densities of plants. Available population estimates are highly variable and inaccurate due to the limited access for surveys associated with private lands.
                    </P>
                    <P>The primary threat to Frisco buckwheat is habitat destruction from precious metal and gravel mining. Mining for precious metals historically occurred within the vicinity of all four populations. Three of the populations are currently in the immediate vicinity of active limestone quarries. Ongoing mining in the species' habitat has the potential to extirpate one population in the near future and extirpate all populations in the foreseeable future. Ongoing exploration for precious metals and gravel indicate that mining will continue, but will take time for the mining operations to be put into place. This will result in the loss and fragmentation of Frisco buckwheat populations over a longer time scale. Other threats to the species include nonnative species, vulnerability associated with small population size, and climate change. Existing regulatory mechanisms are inadequate to protect the species from these threats. The threats that Frisco buckwheat faces are moderate in magnitude, because while serious and occurring rangewide, the threats do not significantly reduce populations on a short time scale. The threats are imminent, because three of the populations are currently in the immediate vicinity of active limestone quarries. Therefore, we have assigned Frisco buckwheat an LPN of 8.</P>
                    <P>
                        <E T="03">Festuca hawaiiensis</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is a cespitose (growing in dense, low tufts) annual found in dry forests on Hawaii Island. 
                        <E T="03">Festuca hawaiiensis</E>
                         is known from four populations collectively totaling approximately 1,000 individuals in and around the Pohakuloa Training Area. Historically, this species was also found on Hualalai and Puu Huluhulu, but it no longer occurs at these sites. In addition, the historical range of 
                        <E T="03">F. hawaiiensis</E>
                         may have included Maui.
                    </P>
                    <P>
                        This species is threatened by pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), mouflon (
                        <E T="03">Ovis musimon</E>
                        ), and feral sheep (
                        <E T="03">O. aries</E>
                        ) that degrade and destroy habitat; fire; military training activities; and nonnative plants that outcompete and displace it. Feral pigs, goats, mouflon, and feral sheep have been fenced out of a portion of the populations of 
                        <E T="03">F. hawaiiensis</E>
                         and nonnative plants have been reduced in the fenced area, but the majority of the populations are still affected by threats from ungulates. The threats are imminent because they are not controlled and are ongoing in the remaining, unfenced populations. Firebreaks have been established to protect two populations, but fire is an imminent threat to the remaining populations that have no firebreaks. There are no 
                        <E T="03">ex situ</E>
                         collections. The threats are of a high magnitude because they could adversely affect the majority of 
                        <E T="03">F. hawaiiensis</E>
                         populations resulting in direct mortality or reduced reproductive capacity which could bring about extinction on a relatively short time scale. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Festuca ligulata</E>
                         (Guadalupe fescue)—The following summary is based on information obtained from the original species petition, received in 1975, and from our files, on-line herbarium databases, and scientific publications. Six small populations of Guadalupe fescue, a member of the Poaceae (grass family), have been documented in mountains of the Chihuahuan desert in Texas and in Coahuila, Mexico. Only two extant populations have been confirmed in the last 5 years: One in the Chisos Mountains, Big Bend National Park (BIBE), Texas, and one in the privately owned 
                        <E T="03">Area de Protección de Flora y Fauna</E>
                         (APFF, Protected Area for Flora and Fauna) Maderas del Carmen in northern Coahuila. Despite intensive searches, a population known from Guadalupe Mountains National Park, Texas, has not been found since 1952, and is presumed extirpated. In 2009, botanists confirmed Guadalupe fescue at one site in APFF Maderas del Carmen, but could not find the species at the 
                        <PRTPAGE P="72483"/>
                        original site, known as Sierra El Jardín, which was first reported in 1973. Two additional Mexican populations, near Fraile in southern Coahuila, and the Sierra de la Madera in central Coahuila, have not been monitored since 1941 and 1977, respectively. A great amount of potentially suitable habitat in Coahuila and adjacent Mexican States has never been surveyed; due to prevailing security issues in northern Mexico. We do not know if or when these sites can be safely monitored. The BIBE site was monitored in September 2013; at that time the total population was estimated to be less than 200 individual plants.
                    </P>
                    <P>The potential threats to Guadalupe fescue include changes in the wildfire cycle and vegetation structure, trampling from humans and pack animals, possible grazing, trail runoff, fungal infection of seeds, small sizes and isolation of populations, and limited genetic diversity. A historically unprecedented period of exceptional drought and high temperatures prevailed throughout the species' range from October 2010 until November 2011. The Service and the National Park Service established a candidate conservation agreement (CCA) in 2008 to provide additional protection for the Chisos Mountains population and to promote cooperative conservation efforts with U.S. and Mexican partners. The threats to Guadalupe fescue are of moderate magnitude and are not imminent due to the provisions of the CCA and other conservation efforts that address threats from trampling, grazing, trail runoff, and genetic diversity. Thus, we maintained an LPN of 11 for this species.</P>
                    <P>
                        <E T="03">Gardenia remyi</E>
                         (Nanu)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Gardenia remyi</E>
                         is a tree found in mesic to wet forests on the Hawaiian Islands of Kauai, Molokai, Maui, and Hawaii. 
                        <E T="03">Gardenia remyi</E>
                         is known from 19 populations collectively totaling between 85 and 87 individuals. This species is threatened by pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), and deer (
                        <E T="03">Axis axis</E>
                         and 
                        <E T="03">Odocoileus hemionus</E>
                        ), which degrade and destroy habitat and possibly forage upon the species, and by nonnative plants that outcompete and displace it. 
                        <E T="03">G. remyi</E>
                         is also threatened by landslides and reduced reproductive vigor on the island of Hawaii. This species is represented in 
                        <E T="03">ex situ</E>
                         collections. On Kauai, 
                        <E T="03">G. remyi</E>
                         individuals have been outplanted within ungulate-proof exclosures in two locations. Feral pigs have been fenced out of the west Maui populations of 
                        <E T="03">G. remyi,</E>
                         and nonnative plants have been reduced in those areas. However, these threats are ongoing in the remaining, unfenced populations, and are therefore imminent. In addition, the threat from goats and deer is ongoing and imminent throughout the range of the species, because no goat or deer control measures have been undertaken for any of the populations of 
                        <E T="03">G. remyi.</E>
                         All of the threats are of a high magnitude, because habitat destruction, predation, and landslides could significantly affect the entire species, resulting in direct mortality or reduced reproductive capacity, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Joinvillea ascendens</E>
                         ssp. 
                        <E T="03">ascendens</E>
                         (Ohe)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Joinvillea ascendens</E>
                         ssp. 
                        <E T="03">ascendens</E>
                         is an erect herb found in wet to mesic 
                        <E T="03">Metrosideros polymorpha-Acacia koa</E>
                         (ohia-koa) lowland and montane forests on the Hawaiian Islands of Kauai, Oahu, Molokai, Maui, and Hawaii. This subspecies is known from 44 widely scattered populations collectively totaling approximately 200 individuals. Many of the populations, which are widely separated, include only one or two individuals. This subspecies is threatened by destruction or modification of habitat by pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), and deer (
                        <E T="03">Axis axis</E>
                         and 
                        <E T="03">Odocoileus hemionus</E>
                        ), and by nonnative plants that outcompete and displace native plants. Herbivory by pigs, goats, deer, and rats (
                        <E T="03">Rattus exulans, R. norvegicus,</E>
                         and 
                        <E T="03">R. rattus</E>
                        ) is a likely threat to this species. Landslides are a potential threat to populations on Kauai and Molokai. Seedlings have rarely been observed in the wild. Seeds germinate in cultivation, but most die soon thereafter. It is uncertain if the apparent low seedling recruitment is typical of this subspecies, or if it is related to habitat disturbance. Feral pigs have been fenced out of a few of the populations of this subspecies, and nonnative plants have been reduced in those populations that are fenced. However, these threats are not controlled and are ongoing in the remaining, unfenced populations. This species is represented in 
                        <E T="03">ex situ</E>
                         collections. The threats are imminent because they are ongoing and are of high magnitude because habitat degradation, nonnative plants, and predation result in mortality and may severely affect the reproductive capacity of the majority of populations of this species, leading to a relatively high probability of extinction. Therefore, we have retained an LPN of 3 for this subspecies.
                    </P>
                    <P>
                        <E T="03">Kadua</E>
                         (=
                        <E T="03">Hedyotis) fluviatilis</E>
                         (Kamapuaa)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Kadua fluviatilis</E>
                         (formerly 
                        <E T="03">Hedyotis fluviatilis</E>
                        ) is a scandent (climbing) shrub found in mixed shrubland to wet lowland forests on the islands of Oahu and Kauai, Hawaii. This species is known from 11 populations collectively totaling between 400 and 900 individuals. 
                        <E T="03">Kadua fluviatilis</E>
                         is threatened by pigs (
                        <E T="03">Sus scrofa</E>
                        ) and goats (
                        <E T="03">Capra hircus</E>
                        ) that degrade and destroy habitat, and by nonnative plants that outcompete and displace it. Landslides and hurricanes are a potential threat to populations on Kauai. Herbivory by pigs and goats is a likely threat. This species is not represented in an 
                        <E T="03">ex situ</E>
                         collection. Threats to this species are imminent because they are ongoing, and are of high magnitude, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Lepidium ostleri</E>
                         (Ostler's peppergrass)—The following summary is based on information in our files and the petition we received on July 30, 2007. Ostler's peppergrass is a long-lived perennial herb in the mustard family that grows in dense, cushion-like tufts. Ostler's peppergrass is a narrow endemic restricted to soils derived from Ordovician limestone outcrops. The range of the species is less than 5 sq mi (13 sq km), with only four known populations. All four populations occur exclusively on private lands in the southern San Francisco Mountains of Beaver County, Utah. Available population estimates are highly variable and inaccurate due largely to the limited access for surveys associated with private lands.
                    </P>
                    <P>
                        The primary threat to Ostler's peppergrass is habitat destruction from precious metal and gravel mining. Mining for precious metals historically occurred within the vicinity of all four populations. Three of the populations are currently in the immediate vicinity of active limestone quarries, but mining is only currently occurring in the area of one population. Ongoing mining in the species' habitat has the potential to extirpate one population in the near future. Ongoing exploration for precious metals and gravel indicate that mining will continue, but will take time for the mining operations to be put into place. This will result in the loss and fragmentation of Ostler's peppergrass populations over a longer time scale. 
                        <PRTPAGE P="72484"/>
                        Other threats to the species include nonnative species, vulnerability associated with small population size, climate change, and the overall inadequacy of existing regulatory mechanisms. The threats that Ostler's peppergrass faces are moderate in magnitude, because, while serious and occurring rangewide, the threats do not collectively result in significant population declines on a short time scale. The threats are imminent because the species is currently facing them across its entire range. Therefore, we have assigned Ostler's peppergrass an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Linum arenicola</E>
                         (Sand flax)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Myrsine fosbergii</E>
                         (Kolea)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Myrsine fosbergii</E>
                         is a branched shrub or small tree found in lowland mesic and wet forests, on watercourses or stream banks, on the islands of Kauai and Oahu, Hawaii. This species is currently known from 14 populations collectively totaling a little more than 100 individuals. 
                        <E T="03">Myrsine fosbergii</E>
                         is threatened by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ) and goats (
                        <E T="03">Capra hircus</E>
                        ) that degrade and destroy habitat and may forage upon the plant, and by nonnative plants that compete for light and nutrients. This species is represented in an 
                        <E T="03">ex situ</E>
                         collection. Although there are plans to fence and remove ungulates from the Helemano area of Oahu, which may benefit this species, no conservation measures have yet been taken to protect this species from nonnative herbivores. Feral pigs and goats are found throughout the known range of 
                        <E T="03">M. fosbergii,</E>
                         as are nonnative plants. The threats from feral pigs, goats, and nonnative plants are imminent and of high magnitude because because they are ongoing and they pose a severe threat throughout the limited range of this species leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Nothocestrum latifolium</E>
                         ('Aiea)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Nothocestrum latifolium</E>
                         is a small tree found in dry to mesic forests on the islands of Kauai, Oahu, Maui, Molokai, and Lanai, Hawaii. 
                        <E T="03">N. latifolium</E>
                         is known from 17 declining populations collectively totaling fewer than 1,200 individuals. This species is threatened by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), and deer (
                        <E T="03">Axis axis</E>
                         and 
                        <E T="03">Odocoileus hemionus</E>
                        ) that degrade and destroy habitat and may forage upon it; by nonnative plants that compete for light and nutrients; and by decreased reproductive viability through the loss of pollinators. This species is represented in an 
                        <E T="03">ex situ</E>
                         collection. Ungulates have been fenced out of four areas where 
                        <E T="03">N. latifolium</E>
                         currently occurs, hundreds of 
                        <E T="03">N. latifolium</E>
                         individuals have been outplanted in fenced areas, and nonnative plants have been reduced in some populations that are fenced. However, these ongoing conservation efforts for this species benefit only a few of the known populations. The threats are not controlled and are ongoing in the remaining unfenced populations. In addition, little natural regeneration has been observed in this species. The threats are imminent because they are ongoing and of high magnitude, since they are severe enough to affect the continued existence of the species, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Ochrosia haleakalae</E>
                         (Holei)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ochrosia haleakalae</E>
                         is a tree found in dry to mesic forests, often on lava, on the islands of Hawaii and Maui, Hawaii. This species is currently known from 8 populations collectively totaling between 64 and 76 individuals. 
                        <E T="03">Ochrosia haleakalae</E>
                         is threatened by fire; by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), and cattle (
                        <E T="03">Bos taurus</E>
                        ) that degrade and destroy habitat and may directly forage upon it; and, by nonnative plants that compete for light and nutrients. This species is represented in 
                        <E T="03">ex situ</E>
                         collections. Feral pigs, goats, and cattle have been fenced out of one wild and one outplanted population on private lands on the island of Maui and one outplanted population in Hawaii Volcanoes National Park on the island of Hawaii. Nonnative plants have been reduced in the fenced areas. The threat from fire is of a high magnitude and imminent because no control measures have been undertaken to address this threat that could adversely affect most 
                        <E T="03">O. haleakalae</E>
                         population sites. The threats from feral pigs, goats, and cattle are ongoing to the unfenced populations of 
                        <E T="03">O. haleakalae.</E>
                         The threat from nonnative plants is imminent and of a high magnitude to the wild populations on both islands, because it is ongoing and adversely affects the survival and reproductive capacity of the majority of the individuals of this species, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Pinus albicaulis</E>
                         (Whitebark pine)—The following summary is based on information in our files and in the petition received on December 9, 2008. 
                        <E T="03">Pinus albicaulis</E>
                         is a hardy conifer found at alpine tree line and subalpine elevations in Washington, Oregon, Nevada, California, Idaho, Montana, and Wyoming, and in British Columbia and Alberta, Canada. In the United States, approximately 96 percent of land where the species occurs is federally owned or managed, primarily by the U.S. Forest Service. 
                        <E T="03">Pinus albicaulis</E>
                         is a slow-growing, long-lived tree that often lives for 500 and sometimes more than 1,000 years. It is considered a keystone, or foundation, species in western North America, where it increases biodiversity and contributes to critical ecosystem functions.
                    </P>
                    <P>
                        The primary threat to the species is from disease in the form of the nonnative white pine blister rust and its interaction with other threats. 
                        <E T="03">Pinus albicaulis</E>
                         also is currently experiencing significant mortality from predation by the native mountain pine beetle. We also anticipate that continuing environmental effects resulting from climate change will result in direct habitat loss for 
                        <E T="03">P. albicaulis.</E>
                         Models predict that suitable habitat for 
                        <E T="03">P. albicaulis</E>
                         will decline precipitously within the next 100 years. Past and ongoing fire suppression is also negatively affecting populations of 
                        <E T="03">P. albicaulis</E>
                         through direct habitat loss. Additionally, environmental changes resulting from changing climatic conditions are acting alone and in combination with the effects of fire suppression to increase the frequency and severity of wildfires. Lastly, the existing regulatory mechanisms are inadequate to address the threats presented above. The threats that face 
                        <E T="03">P. albicaulis</E>
                         are high in magnitude, because the major threats occur throughout all of the species' range and are having a major population-level 
                        <PRTPAGE P="72485"/>
                        effect on the species. The threats are imminent, because rangewide disease, predation, fire and fire suppression, and environmental effects of climate change are affecting 
                        <E T="03">P. albicaulis</E>
                         currently and are expected to continue and likely intensify in the foreseeable future. Thus, we have assigned 
                        <E T="03">P. albicaulis</E>
                         an LPN of 2.
                    </P>
                    <P>
                        <E T="03">Platanthera integrilabia</E>
                         (Correll) Leur (White fringeless orchid)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing rule, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Pseudognaphalium</E>
                         (= 
                        <E T="03">Gnaphalium</E>
                        ) 
                        <E T="03">sandwicensium</E>
                         var. 
                        <E T="03">molokaiense</E>
                         (Enaena)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Pseudognaphalium sandwicensium</E>
                         var. 
                        <E T="03">molokaiense</E>
                         is a perennial herb found in strand vegetation in dry consolidated dunes on the islands of Molokai and Maui, Hawaii. Historically, this variety was also found on Oahu and Lanai. This variety is known from five populations collectively totaling approximately 200 to 20,000 individuals (depending upon rainfall) in the Moomomi area on the island of Molokai, and from 2 populations of a few individuals at Waiehu dunes and at Puu Kahulianapa on west Maui. 
                        <E T="03">Pseudognaphalium s.</E>
                         var. 
                        <E T="03">molokaiense</E>
                         is threatened by feral goats (
                        <E T="03">Capra hircus</E>
                        ) and axis deer (
                        <E T="03">Axis axis</E>
                        ) that degrade and destroy habitat and possibly browse upon it, and by nonnative plants that compete for light and nutrients. Potential threats also include collection for cultural use, and off-road vehicles that directly damage plants and degrade habitat. Weed control is conducted for one population on Molokai; however, no conservation efforts have been initiated to date for the other populations on Molokai or for the individuals on Maui. This species is represented in an 
                        <E T="03">ex situ</E>
                         collection. The ongoing threats from feral goats, axis deer, nonnative plants, collection, and off-road vehicles are of a high magnitude, because no control measures have been undertaken for the Maui population or for the four of the five Molokai populations, and the threats result in direct mortality or significantly reduce reproductive capacity for the majority of the populations, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 3 for this plant variety.
                    </P>
                    <P>
                        <E T="03">Ranunculus hawaiensis</E>
                         (Makou)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ranunculus hawaiensis</E>
                         is an erect or ascending perennial herb found in mesic to wet forests dominated by 
                        <E T="03">Metrosideros polymorpha</E>
                         (ohia) and 
                        <E T="03">Acacia koa</E>
                         (koa) with scree substrate (loose stones or rocky debris on a slope) on the Hawaiian Islands of Maui and Hawaii. This species is currently known from 6 populations collectively totaling 14 individuals on the island of Hawaii. On Maui, it was historically known from an area in east Maui, but individuals have not been seen at this location since 1995. 
                        <E T="03">Ranunculus hawaiensis</E>
                         is threatened by direct predation by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), cattle (
                        <E T="03">Bos taurus</E>
                        ), mouflon (
                        <E T="03">Ovis musimon</E>
                        ), feral sheep (
                        <E T="03">O. aries</E>
                        ), and slugs (
                        <E T="03">Limax maximus, Milax gagates,</E>
                         and 
                        <E T="03">Vaginulus plebeius</E>
                        ); by degradation and destruction of habitat by feral ungulates; and by nonnative plants that compete for light and nutrients. This species is represented in 
                        <E T="03">ex situ</E>
                         collections, and three populations have been outplanted into protected exclosures; however, feral ungulates and nonnative plants are not controlled in the remaining, unfenced populations. In addition, the threat from introduced slugs is of a high magnitude because slugs occur throughout the limited range of this species and no effective measures have been undertaken to control them or prevent them from predating on the plants which can result in death or reduction in reproductive capacity. Overall, the threats to the species from pigs, goats, cattle, mouflon, feral sheep, slugs, and nonnative plants are imminent and of high magnitude. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Ranunculus mauiensis</E>
                         (Makou)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ranunculus mauiensis</E>
                         is an erect to weakly ascending perennial herb found in open sites in mesic to wet forests and along streams on the islands of Maui, Kauai, and Molokai, Hawaii. This species is currently known from 14 populations collectively totaling 198 individuals. 
                        <E T="03">Ranunculus mauiensis</E>
                         is threatened by direct predation by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), mule deer (
                        <E T="03">Odocoileus hemionus</E>
                        ), axis deer (
                        <E T="03">Axis axis</E>
                        ), and slugs (
                        <E T="03">Limax maximus, Milax gagates,</E>
                         and 
                        <E T="03">Vaginulus plebeius</E>
                        ); by habitat degradation and destruction by feral ungulates; and by nonnative plants that compete for light and nutrients. This species is represented in an 
                        <E T="03">ex situ</E>
                         collection. Feral pigs have been fenced out of one Maui population of 
                        <E T="03">R. mauiensis,</E>
                         and nonnative plants have been reduced in the fenced area. One individual occurs in the Kamakou Preserve on Molokai, managed by The Nature Conservancy. However, ongoing conservation efforts benefit only two populations. The threats are imminent and of high magnitude, since they are severe enough to affect the continued existence of the species, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Rorippa subumbellata</E>
                         (Tahoe yellow cress)—The following summary is based on information contained in our files and the petition received on December 27, 2000. 
                        <E T="03">Rorippa subumbellata</E>
                         is a small, branching perennial herb known only from the shores of Lake Tahoe in California and Nevada.
                    </P>
                    <P>
                        Data collected over the last 25 years generally indicate that species occurrence fluctuates yearly as a function of both lake level and the amount of exposed habitat. Records kept since 1900 show a preponderance of years with high lake levels that would isolate and reduce 
                        <E T="03">R. subumbellata</E>
                         occurrences at higher beach elevations. From the standpoint of the species, less favorable peak years have occurred almost twice as often as more favorable low-level years. Annual surveys are conducted to determine population numbers, site occupancy, and general disturbance regime. At least within a certain range, the data clearly show that more individuals are present when lake levels are low and fewer when lake levels are high.
                    </P>
                    <P>
                        Many 
                        <E T="03">Rorippa subumbellata</E>
                         sites are intensively used for commercial and public purposes, and are subject to various activities such as erosion control, marina developments, pier construction, and recreation. The U.S. Forest Service, California Tahoe Conservancy, and California Department of Parks and Recreation have management programs for 
                        <E T="03">R. subumbellata</E>
                         that include monitoring, fenced enclosures, and transplanting efforts when funds and staff are available. Public agencies (including the Service), private landowners, and environmental groups collaborated to develop a Conservation Strategy coupled with a Memorandum of 
                        <PRTPAGE P="72486"/>
                        Understanding-Conservation Agreement. The Conservation Strategy, completed in 2003, contains goals and objectives for recovery and survival and a research and monitoring agenda, and serves as the foundation for an adaptive management program. Because of the continued commitments to conservation demonstrated by regulatory and land management agencies participating in the conservation strategy, the threats to 
                        <E T="03">R. subumbellata</E>
                         from various land uses have been reduced to a moderate magnitude. In high lake level years such as 2011 and 2013, however, recreational use is concentrated within 
                        <E T="03">R. subumbellata</E>
                         habitat, and we consider this threat in particular to be ongoing and imminent. Therefore, we are maintaining an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Schiedea pubescens</E>
                         (Maolioli)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Schiedea pubescens</E>
                         is a reclining or weakly climbing vine found in diverse mesic to wet forests on the Hawaiian Islands of Maui, Molokai, and Hawaii. It is presumed extirpated from Lanai. Currently, this species is known from 8 populations collectively totaling between 30 and 32 individuals on Maui, from 4 populations collectively totaling between 21 and 22 individuals on Molokai, and from 1 population of 4 to 6 individuals on the island of Hawaii. 
                        <E T="03">Schiedea pubescens</E>
                         is threatened by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ) and goats (
                        <E T="03">Capra hircus</E>
                        ) that consume it and degrade and destroy habitat, and by nonnative plants that compete for light and nutrients. Feral ungulates have been fenced out of the population of 
                        <E T="03">S. pubescens</E>
                         on the island of Hawaii. Feral goats have been fenced out of a few of the west Maui populations of 
                        <E T="03">S. pubescens.</E>
                         Nonnative plants have been reduced in the populations that are fenced on Maui. However, the threats are not controlled and are ongoing in the remaining unfenced populations on Maui and the four populations on Molokai. Additional fenced areas are planned for the Hawaii Island population at Pohakuloa Training Area. Nonnative feral ungulates and nonnative plants will be controlled within these fenced areas. Fire is a potential threat to the Hawaii Island population. This species is not represented in an 
                        <E T="03">ex situ</E>
                         collection. Due to the extremely low number of individuals of this species, the ongoing threats from goats and nonnative plants are imminent and of high magnitude. These threats cause mortality and reduced reproductive capacity for the majority of the populations, leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Sicyos macrophyllus</E>
                         ('Anunu)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing determination that we expect to publish prior to making the next annual resubmitted petition 12-month finding. In the course of preparing the proposed listing determination, we are continuing to monitor new information about this species' status so that we can make prompt use of our authority under section 4(b)(7) in the case of an emergency posing a significant risk to the species.
                    </P>
                    <P>
                        <E T="03">Solanum conocarpum</E>
                         (marron bacora)—The following summary is based on information in our files and in the petition we received on November 21, 1996. 
                        <E T="03">Solanum conocarpum</E>
                         is a dry-forest shrub in the island of St. John, U.S. Virgin Islands. Its current distribution includes eight localities in the island of St. John, each ranging from 1 to 144 individuals. The species has been reported to occur on dry, poor soils. It can be locally abundant in exposed topography on sites disturbed by erosion, areas that have received moderate grazing, and around ridgelines as an understory component in diverse woodland communities. A habitat suitability model suggests that the vast majority of 
                        <E T="03">Solanum conocarpum</E>
                         habitat is found in the lower elevation coastal scrub forest. Efforts have been conducted to propagate the species to enhance natural populations, and planting of seedlings has been conducted in the island of St. John.
                    </P>
                    <P>
                        <E T="03">Solanum conocarpum</E>
                         is threatened by the lack of natural recruitment, absence of dispersers, fragmented distribution, lack of genetic variation, climate change, and habitat destruction or modification by exotic mammal species. These threats are evidenced by the reduced number of individuals, low number of populations, and lack of connectivity between populations. Overall, the threats are of high magnitude because they are leading to populations declines for a species that already has low population numbers and fragmented distribution; the threats are also ongoing and therefore imminent. Therefore, we assigned a LPN of 2 to 
                        <E T="03">Solanum conocarpum.</E>
                    </P>
                    <P>
                        <E T="03">Solanum nelsonii</E>
                         (popolo)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Solanum nelsonii</E>
                         is a sprawling or trailing shrub found in coral rubble or sand in coastal sites. This species is known from populations on Molokai (approximately 300 individuals), the island of Hawaii (5 individuals), and the northwestern Hawaiian Islands (NWHI), Hawaii. The current populations in the NWHI are found on Kure (unknown number of individuals), Midway (approximately 260 individuals), Laysan (approximately 490 individuals), Pearl and Hermes (unknown number of individuals), and Nihoa (8,000 to 15,000 individuals). On Molokai, 
                        <E T="03">S. nelsonii</E>
                         is moderately threatened by ungulates which degrade and destroy habitat and which may eat individuals. On Molokai and the NWHI, this species is exposed to threats from nonnative plants that outcompete and displace it. 
                        <E T="03">Solanum nelsonii</E>
                         is exposed to threats by herbivory by a nonnative grasshopper (
                        <E T="03">Schistocera nitens</E>
                        ) in the NWHI. On Kure, Midway, Laysan, and Pearl and Hermes in the NWHI, tsunamis are also a potential threat to 
                        <E T="03">S. nelsonii.</E>
                         This species is represented in 
                        <E T="03">ex situ</E>
                         collections. Ungulate exclusion fences, routine fence monitoring and maintenance, and weed control protect the population of 
                        <E T="03">S. nelsonii</E>
                         on Molokai. Limited weed control is conducted in the NWHI. However, the threats are ongoing and are not being controlled in the majority of sites, they are therefore imminent. These threats are of moderate magnitude because of the relatively large number of plants, and the fact that this species is found on more than one island. Therefore, we have retained an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Trifolium friscanum</E>
                         (Frisco clover)—The following summary is based on information in our files and the petition we received on July 30, 2007. Frisco clover is a narrow endemic perennial herb found only in Utah, with five known populations restricted to sparsely vegetated, pinion-juniper sagebrush communities and shallow, gravel soils derived from volcanic gravels, Ordovician limestone, and dolomite outcrops. The majority (68 percent) of Frisco clover plants occur on private lands, with the remaining plants found on Federal and State lands.
                    </P>
                    <P>
                        On the private and State lands, the most significant threat to Frisco clover is habitat destruction from mining for precious metals and gravel. Active mining claims, recent prospecting, and an increasing demand for precious metals and gravel indicate that mining in Frisco clover habitats will increase in the foreseeable future, likely resulting in the loss of large numbers of plants. Other threats to Frisco clover include nonnative, invasive species; 
                        <PRTPAGE P="72487"/>
                        vulnerability associated with small population size; and drought associated with climate change. Existing regulatory mechanisms are inadequate to protect the species from these threats. The threats to Frisco clover are moderate in magnitude because, while serious and occurring rangewide, they are not acting independently or cumulatively to have a highly significant negative impact on its survival or reproductive capacity. For example, although mining for precious metals and gravel historically occurred throughout Frisco clover's range, and mining operations may eventually expand into occupied habitats, there are no active mines within the immediate vicinity of any known population. The threats are imminent because the species is currently facing them across its entire range. Therefore, we have assigned Frisco clover an LPN of 8.
                    </P>
                    <HD SOURCE="HD2">Ferns and Allies</HD>
                    <P>
                        <E T="03">Cyclosorus boydiae</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Cyclosorus boydiae</E>
                         is a small- to medium-sized fern found in mesic to wet forests along stream banks on the Hawaiian Islands of Oahu and Maui. It has been extirpated from the island of Hawaii. Currently, 
                        <E T="03">C. boydiae</E>
                         is known from seven populations collectively totaling approximately 400 individuals. This species is threatened by feral pigs that degrade and destroy habitat and may eat this plant, and by nonnative plants that compete for light and nutrients. Feral pigs have been fenced out of the largest population on Maui, and nonnative plants have been reduced in the fenced area. No conservation efforts are under way to alleviate threats to the other two populations on Maui, or the two populations on Oahu. This species is represented in an 
                        <E T="03">ex situ</E>
                         collection. The threats are imminent because they are ongoing, and of moderate magnitude because pigs no longer threaten the largest population and nonnative plants have been reduced. Therefore, we have retained an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Huperzia stemmermanniae</E>
                         (Waewaeiole)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Huperzia stemmermanniae</E>
                         is an epiphytic, pendant clubmoss found in mesic-to-wet 
                        <E T="03">Metrosideros polymorpha-Acacia koa</E>
                         (ohia-koa) forests on the Hawaiian Islands of Maui and Hawaii. Only 3 populations are known, collectively totaling approximately 20 individuals. The Maui population has not been observed since 1995. 
                        <E T="03">Huperzia stemmermanniae</E>
                         is threatened by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ), goats (
                        <E T="03">Capra hircus</E>
                        ), cattle (
                        <E T="03">Bos taurus</E>
                        ), and axis deer (
                        <E T="03">Axis axis</E>
                        ) that degrade and destroy habitat, and by nonnative plants that compete for light, space, and nutrients. 
                        <E T="03">Huperzia stemmermanniae</E>
                         is also threatened by randomly occurring natural events due to its small population size. One individual at Waikamoi Preserve may benefit from fencing for axis deer and pigs. This species is represented in 
                        <E T="03">ex situ</E>
                         collections. The threats from pigs, goats, cattle, axis deer, and nonnative plants are imminent and of a high magnitude because they are sufficiently severe to adversely affect the species throughout its limited range, resulting in direct mortality or significantly reducing reproductive capacity and leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Microlepia strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         (Palapalai)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Microlepia strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         is a terrestrial fern found in mesic-to-wet forests. It is currently found on the Hawaiian Islands of Maui, Oahu, and Hawaii in 9 known populations collectively totaling at least 50 individuals. 
                        <E T="03">M. s.</E>
                         var. 
                        <E T="03">mauiensis</E>
                         is threatened by feral pigs (
                        <E T="03">Sus scrofa</E>
                        ) that degrade and destroy habitat, and by nonnative plants that compete for light and nutrients. Pigs have been fenced out of some areas on east and west Maui, Oahu, and on Hawaii, where 
                        <E T="03">M. s.</E>
                         var. 
                        <E T="03">mauiensis</E>
                         currently occurs and nonnative plants have been reduced in the fenced areas. However, the threats are not controlled and are ongoing in the remaining unfenced populations on Maui, Oahu, and Hawaii. Therefore, the threats from feral pigs and nonnative plants are imminent. The threats are of a high magnitude because they are sufficiently severe to adversely affect the species throughout its range, resulting in direct mortality or significantly reducing reproductive capacity and leading to a relatively high likelihood of extinction. Therefore, we have retained an LPN of 3 for this plant variety.
                    </P>
                    <HD SOURCE="HD1">Petitions To Reclassify Species Already Listed</HD>
                    <P>
                        We previously made warranted-but-precluded findings on five petitions seeking to reclassify threatened species to endangered status. The taxa involved in the reclassification petitions are three populations of the grizzly bear (
                        <E T="03">Ursus arctos horribilis</E>
                        ), delta smelt (
                        <E T="03">Hypomesus transpacificus</E>
                        ), and 
                        <E T="03">Sclerocactus brevispinus</E>
                         (Pariette cactus). Because these species are already listed under the ESA, they are not candidates for listing and are not included in Table 1. However, this notice and associated species assessment forms or 5-year review documents also constitute the findings for the resubmitted petitions to reclassify these species. Our updated assessments for these species are provided below. We find that reclassification to endangered status for one grizzly bear ecosystem population, delta smelt, and 
                        <E T="03">Sclerocactus brevispinus</E>
                         are all currently warranted but precluded by work identified above (see Findings for Petitioned Candidate Species). We find that uplisting the Selkirk ecosystem population and the Cabinet-Yaak ecosystem population of grizzly bear is no longer warranted; the species remains listed as threatened. One of the primary reasons that the work identified above is considered to have higher priority is that the grizzly bear population, delta smelt, and 
                        <E T="03">Sclerocactus brevispinus</E>
                         are currently listed as threatened, and therefore already receive certain protections under the ESA. We promulgated regulations extending take prohibitions for wildlife and plants under section 9 to threatened species (50 CFR 17.31 and 50 CFR 17.71, respectively). Prohibited actions under section 9 for wildlife include, but are not limited to, take (
                        <E T="03">i.e.,</E>
                         to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, or collect, or attempt to engage in such activity). For plants, prohibited actions under section 9 include removing or reducing to possession any listed plant from an area under Federal jurisdiction (50 CFR 17.61). Other protections that apply to these threatened species even before we complete proposed and final reclassification rules include those under section 7(a)(2) of the ESA, whereby Federal agencies must insure that any action they authorize, fund, or carry out is not likely to jeopardize the continued existence of any endangered or threatened species.
                    </P>
                    <P>
                        Grizzly bear (
                        <E T="03">Ursus arctos horribilis</E>
                        )—North Cascades ecosystem population (Region 6)—Since 1990, we have received and reviewed five petitions requesting a change in status for the North Cascades grizzly bear population (55 FR 32103, August 7, 1990; 56 FR 33892, July 24, 1991; 57 FR 14372, April 20, 1992; 58 FR 43856, August 18, 1993; 63 FR 30453, June 4, 1998). In response to these petitions, we 
                        <PRTPAGE P="72488"/>
                        determined that grizzly bears in the North Cascade ecosystem warrant a change to endangered status. In 2014, we continue to find that reclassifying this population as endangered is warranted but precluded and we continue to assign a LPN of 3 for the uplisting of the North Cascades population based on high magnitude threats that are ongoing, thus imminent. However, higher priority listing actions, including court-approved settlements, court-ordered and statutory deadlines for petition findings and listing determinations, emergency listing determinations, and responses to litigation, continue to preclude reclassifying grizzly bears in this ecosystem. Furthermore, proposed rules to reclassify threatened species to endangered are a lower priority than listing currently unprotected species (
                        <E T="03">i.e.,</E>
                         candidate species), since species currently listed as threatened are already afforded the protection of the ESA and the implementing regulations. We continue to monitor this population and will change its status or implement an emergency uplisting if necessary.
                    </P>
                    <P>
                        Grizzly bear (
                        <E T="03">Ursus arctos horribilis</E>
                        )—Cabinet-Yaak ecosystem population (Region 6)—Since 1992, we have received and reviewed six petitions requesting a change in status for the Cabinet-Yaak grizzly bear population (57 FR 14372, April 20, 1992; 58 FR 8250, February 12, 1993; 58 FR 43856, August 18, 1993; 58 FR 43856, August 18, 1993; 63 FR 30453, June 4, 1998; 64 FR 26725, May 17, 1999). In response to these petitions, we previously determined that grizzly bears in the Cabinet-Yaak ecosystem warranted a change to endangered status. However, for several years, this population's status has been improving. The population trend has now changed from declining to stable. The U.S. Forest Service has established regulatory mechanisms for motorized access management and attractant storage, and researchers have documented some movement between the Cabinet-Yaak and other populations in Canada. Together, these improvements have reduced the threats to this population. Until the Record of Decision for motorized access management is more fully implemented and we have several more years of a positive population trend, we remain cautious in our interpretation. We conclude that the Cabinet-Yaak ecosystem population continues to face several threats, and retain this populations's threatened status, but we no longer find that the population is warranted for uplisting to endangered status (
                        <E T="03">i.e.,</E>
                         “on the brink of extinction”). This constitutes our not-warranted finding on the six uplisting petitions we received.
                    </P>
                    <P>
                        Grizzly bear (
                        <E T="03">Ursus arctos horribilis</E>
                        )—Selkirk ecosystem population (Region 6)—Since 1992, we have received and reviewed four petitions requesting a change in status for individual grizzly bear populations (57 FR 14372, April 20, 1992; 58 FR 8250, February 12, 1993; 58 FR 43856, August 18, 1993; 64 FR 26725, May 17, 1999). In response to these petitions, we previously determined that grizzly bears within the Selkirk ecosystem warranted a change to endangered status but reclassification was precluded by higher priority listing actions. However, improvements to habitat and the institutionalization of those improvements in National Forest Land Management Plans, as well as new information about population size have significantly reduced threats to this population from habitat destruction, and improved the adequacy of regulatory mechanisms. Population estimates indicate that the population is approaching recovery goals of 90 bears, and levels of human-caused mortality have been low in recent years. Additionally, food storage orders have been implemented and some movement between the Selkirk Mountains and other populations in Canada has been documented. However, until there are significant improvements to regulatory mechanisms in Canada, full implementation of motorized access management by the U.S. Forest Service, and improved population connectivity, we remain cautious in our interpretation. We conclude that the Selkirk ecosystem population continues to face several threats and will retain this populations's threatened status, but we no longer find that the population is warranted for uplisting to endangered status (
                        <E T="03">i.e.,</E>
                         “on the brink of extinction”). This constitutes our not-warranted finding on the four uplisting petitions we received.
                    </P>
                    <P>
                        Delta smelt (
                        <E T="03">Hypomesus transpacificus</E>
                        ) (Region 8) (see 75 FR 17667, April 7, 2010, for additional information on why reclassification to endangered is warranted but precluded)—The following summary is based on information contained in our files. In April, 2010 we completed a 12-month finding for delta smelt in which we determined that a change in status from threatened to endangered was warranted, although precluded by other high priority listings. The primary rationale for reclassifying delta smelt from threatened to endangered was the significant declines in delta smelt abundance that have occurred since 2001. Delta smelt abundance, as indicated by the Fall Mid-Water Trawl survey, was exceptionally low between 2004 and 2010, increased during the wet year of 2011, and decreased again to a very a low level in 2012.
                    </P>
                    <P>The primary threats to the delta smelt are direct entrainments by State and Federal water export facilities, summer and fall increases in salinity and water clarity resulting from decreases in freshwater flow into the estuary, and effects from introduced species. Ammonia in the form of ammonium may also be a significant threat to the survival of the delta smelt. Additional potential threats are predation by striped and largemouth bass and inland silversides, entrainment into power plants, contaminants, and small population size. Existing regulatory mechanisms have not proven adequate to halt the decline of delta smelt since the time of listing as a threatened species.</P>
                    <P>
                        As a result of our analysis of the best available scientific and commercial data, we have retained the recommendation of uplisting the delta smelt to an endangered species with a LPN of 2, based on high magnitude and imminent threats. The magnitude of the threats is high, because the threats occur rangewide and result in mortality at a population level, or significantly reduce the reproductive capacity of the species. Threats are imminent because they are ongoing and, in some cases (
                        <E T="03">e.g.,</E>
                         nonnative species), considered irreversible.
                    </P>
                    <P>
                        <E T="03">Sclerocactus brevispinus</E>
                         (Pariette cactus) (Region 6) (see 72 FR 53211, September 18, 2007, and the species assessment form (see 
                        <E T="02">ADDRESSES</E>
                        ) for additional information on why reclassification to endangered is warranted but precluded)—
                        <E T="03">Sclerocactus brevispinus</E>
                         is restricted to clay badlands of the Uinta geologic formation in the Uinta Basin of northeastern Utah. The species is restricted to one population with an overall range of approximately 16 mi by 5 mi in extent. The species' entire population is within a developed and expanding oil and gas field. The location of the species' habitat exposes it to destruction from road, pipeline, and well-site construction in connection with oil and gas development. The species may be collected as a specimen plant for horticultural use. Recreational off-road vehicle use and livestock trampling are additional potential threats. The species is currently federally listed as threatened by its previous inclusion within the species 
                        <E T="03">Sclerocactus glaucus.</E>
                         The threats are of a high magnitude because any one of the 
                        <PRTPAGE P="72489"/>
                        threats has the potential to severely affect the survival of this species, a narrow endemic with a highly limited range and distribution. Threats are ongoing and, therefore, are imminent. Thus, we assigned an LPN of 2 to this species for uplisting.
                    </P>
                    <HD SOURCE="HD1">Current Notice of Review</HD>
                    <P>We gather data on plants and animals native to the United States that appear to merit consideration for addition to the Lists of Endangered and Threatened Wildlife and Plants (Lists). This notice identifies those species that we currently regard as candidates for addition to the Lists. These candidates include species and subspecies of fish, wildlife, or plants, and DPSs of vertebrate animals. This compilation relies on information from status surveys conducted for candidate assessment and on information from State Natural Heritage Programs, other State and Federal agencies, knowledgeable scientists, public and private natural resource interests, and comments received in response to previous notices of review.</P>
                    <P>Tables 1 and 2 list animals arranged alphabetically by common names under the major group headings, and list plants alphabetically by names of genera, species, and relevant subspecies and varieties. Animals are grouped by class or order. Plants are subdivided into two groups: (1) Flowering plants and (2) ferns and their allies. Useful synonyms and subgeneric scientific names appear in parentheses with the synonyms preceded by an “equals” sign. Several species that have not yet been formally described in the scientific literature are included; such species are identified by a generic or specific name (in italics), followed by “sp.” or “ssp.” We incorporate standardized common names in these notices as they become available. We sort plants by scientific name due to the inconsistencies in common names, the inclusion of vernacular and composite subspecific names, and the fact that many plants still lack a standardized common name.</P>
                    <P>Table 1 lists all candidate species, plus species currently proposed for listing under the ESA. We emphasize that in this notice we are not proposing to list any of the candidate species; rather, we will develop and publish proposed listing rules for these species in the future. We encourage State agencies, other Federal agencies, and other parties to give consideration to these species in environmental planning.</P>
                    <P>In Table 1, the “category” column on the left side of the table identifies the status of each species according to the following codes:</P>
                    <FP SOURCE="FP-1">
                        PE—Species proposed for listing as endangered. Proposed species are those species for which we have published a proposed rule to list as endangered or threatened in the 
                        <E T="04">Federal Register</E>
                        . This category does not include species for which we have withdrawn or finalized the proposed rule.
                    </FP>
                    <FP SOURCE="FP-1">PT—Species proposed for listing as threatened.</FP>
                    <FP SOURCE="FP-1">PSAT—Species proposed for listing as threatened due to similarity of appearance.</FP>
                    <FP SOURCE="FP-1">
                        C—Candidates: Species for which we have on file sufficient information on biological vulnerability and threats to support proposals to list them as endangered or threatened. Issuance of proposed rules for these species is precluded at present by other higher priority listing actions. This category includes species for which we made a 12-month warranted-but-precluded finding on a petition to list. We made new findings on all petitions for which we previously made “warranted-but-precluded” findings. We identify the species for which we made a continued warranted-but-precluded finding on a resubmitted petition by the code “C*” in the category column (see the 
                        <E T="03">Findings for Petitioned Candidate Species</E>
                         section for additional information).
                    </FP>
                    <P>
                        The “Priority” column indicates the LPN for each candidate species, which we use to determine the most appropriate use of our available resources. The lowest numbers have the highest priority. We assign LPNs based on the immediacy and magnitude of threats, as well as on taxonomic status. We published a complete description of our listing priority system in the 
                        <E T="04">Federal Register</E>
                         (48 FR 43098, September 21, 1983).
                    </P>
                    <P>
                        The third column, “Lead Region,” identifies the Regional Office to which you should direct information, comments, or questions (see addresses under Request for Information at the end of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section).
                    </P>
                    <P>Following the scientific name (fourth column) and the family designation (fifth column) is the common name (sixth column). The seventh column provides the known historical range for the species or vertebrate population (for vertebrate populations, this is the historical range for the entire species or subspecies and not just the historical range for the distinct population segment), indicated by postal code abbreviations for States and U.S. territories. Many species no longer occur in all of the areas listed.</P>
                    <P>Species in Table 2 of this notice are those we included either as proposed species or as candidates in the previous CNOR (published November 22, 2013, at 78 FR 70104) that are no longer proposed species or candidates for listing. Since November 22, 2013, we listed 33 species, withdrew 3 species from proposed status, and removed 13 species from the candidate list. The first column indicates the present status of each species, using the following codes (not all of these codes may have been used in this CNOR):</P>
                    <FP SOURCE="FP-1">E—Species we listed as endangered.</FP>
                    <FP SOURCE="FP-1">T—Species we listed as threatened.</FP>
                    <FP SOURCE="FP-1">Rc—Species we removed from the candidate list because currently available information does not support a proposed listing.</FP>
                    <FP SOURCE="FP-1">Rp—Species we removed from because we have withdrawn the proposed listing.</FP>
                    <P>The second column indicates why the species is no longer a candidate or proposed species using the following codes (not all of these codes may have been used in this CNOR):</P>
                    <FP SOURCE="FP-1">A—Species that are more abundant or widespread than previously believed and species that are not subject to the degree of threats sufficient that the species is a candidate for listing (for reasons other than that conservation efforts have removed or reduced the threats to the species).</FP>
                    <FP SOURCE="FP-1">F—Species whose range no longer includes a U.S. territory.</FP>
                    <FP SOURCE="FP-1">I—Species for which we have insufficient information on biological vulnerability and threats to support issuance of a proposed rule to list.</FP>
                    <FP SOURCE="FP-1">L—Species we added to the Lists of Endangered and Threatened Wildlife and Plants.</FP>
                    <FP SOURCE="FP-1">M—Species we mistakenly included as candidates or proposed species in the last notice of review.</FP>
                    <FP SOURCE="FP-1">N—Species that are not listable entities based on the ESA's definition of “species” and current taxonomic understanding.</FP>
                    <FP SOURCE="FP-1">U—Species that are not subject to the degree of threats sufficient to warrant issuance of a proposed listing and therefore are not candidates for listing, due, in part or totally, to conservation efforts that remove or reduce the threats to the species.</FP>
                    <FP SOURCE="FP-1">X—Species we believe to be extinct.</FP>
                    <P>
                        The columns describing lead region, scientific name, family, common name, and historical range include information as previously described for Table 1.
                        <PRTPAGE P="72490"/>
                    </P>
                    <HD SOURCE="HD1">Request for Information</HD>
                    <P>We request you submit any further information on the species named in this notice as soon as possible or whenever it becomes available. We are particularly interested in any information:</P>
                    <P>(1) Indicating that we should add a species to the list of candidate species;</P>
                    <P>(2) Indicating that we should remove a species from candidate status;</P>
                    <P>(3) Recommending areas that we should designate as critical habitat for a species, or indicating that designation of critical habitat would not be prudent for a species;</P>
                    <P>(4) Documenting threats to any of the included species;</P>
                    <P>(5) Describing the immediacy or magnitude of threats facing candidate species;</P>
                    <P>(6) Pointing out taxonomic or nomenclature changes for any of the species;</P>
                    <P>(7) Suggesting appropriate common names; and</P>
                    <P>(8) Noting any mistakes, such as errors in the indicated historical ranges.</P>
                    <P>Submit information, materials, or comments regarding a particular species to the Regional Director of the Region identified as having the lead responsibility for that species. The regional addresses follow:</P>
                    <FP SOURCE="FP-1">Region 1. Hawaii, Idaho, Oregon, Washington, American Samoa, Guam, and Commonwealth of the Northern Mariana Islands. Regional Director (TE), U.S. Fish and Wildlife Service, Eastside Federal Complex, 911 NE. 11th Avenue, Portland, OR 97232-4181 (503/231-6158).</FP>
                    <FP SOURCE="FP-1">Region 2. Arizona, New Mexico, Oklahoma, and Texas. Regional Director (TE), U.S. Fish and Wildlife Service, 500 Gold Avenue SW., Room 4012, Albuquerque, NM 87102 (505/248-6920).</FP>
                    <FP SOURCE="FP-1">Region 3. Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Ohio, and Wisconsin. Regional Director (TE), U.S. Fish and Wildlife Service, 5600 American Blvd. West, Suite 990, Bloomington, MN 55437-1458 (612/713-5334).</FP>
                    <FP SOURCE="FP-1">Region 4. Alabama, Arkansas, Florida, Georgia, Kentucky, Louisiana, Mississippi, North Carolina, South Carolina, Tennessee, Puerto Rico, and the U.S. Virgin Islands. Regional Director (TE), U.S. Fish and Wildlife Service, 1875 Century Boulevard, Suite 200, Atlanta, GA 30345 (404/679-4156).</FP>
                    <FP SOURCE="FP-1">Region 5. Connecticut, Delaware, District of Columbia, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, Virginia, and West Virginia. Regional Director (TE), U.S. Fish and Wildlife Service, 300 Westgate Center Drive, Hadley, MA 01035-9589 (413/253-8615).</FP>
                    <FP SOURCE="FP-1">Region 6. Colorado, Kansas, Montana, Nebraska, North Dakota, South Dakota, Utah, and Wyoming. Regional Director (TE), U.S. Fish and Wildlife Service, P.O. Box 25486, Denver Federal Center, Denver, CO 80225-0486 (303/236-7400).</FP>
                    <FP SOURCE="FP-1">Region 7. Alaska. Regional Director (TE), U.S. Fish and Wildlife Service, 1011 East Tudor Road, Anchorage, AK 99503-6199 (907/786-3505).</FP>
                    <FP SOURCE="FP-1">Region 8. California and Nevada. Regional Director (TE), U.S. Fish and Wildlife Service, 2800 Cottage Way, Suite W2606, Sacramento, CA 95825 (916/414-6464).</FP>
                    <P>We will provide information received in response to the previous CNOR to the Region having lead responsibility for each candidate species mentioned in the submission. We will likewise consider all information provided in response to this CNOR in deciding whether to propose species for listing and when to undertake necessary listing actions (including whether emergency listing under section 4(b)(7) of the ESA is appropriate). Information and comments we receive will become part of the administrative record for the species, which we maintain at the appropriate Regional Office.</P>
                    <HD SOURCE="HD1">Public Availability of Comments</HD>
                    <P>Before including your address, phone number, email address, or other personal identifying information in your submission, be advised that your entire submission—including your personal identifying information—may be made publicly available at any time. Although you can ask us in your submission to withhold from public review your personal identifying information, we cannot guarantee that we will be able to do so.</P>
                    <HD SOURCE="HD1">Authority</HD>
                    <P>
                        This notice is published under the authority of the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ).
                    </P>
                    <SIG>
                        <DATED>Dated:  November 18, 2014. </DATED>
                        <NAME>David Cottingham,</NAME>
                        <TITLE>Acting Director, Fish and Wildlife Service.</TITLE>
                    </SIG>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="xs36,xs36,xs36,r50,r50,r50,r50">
                        <TTITLE>Table 1—Candidate Notice of Review (Animals and Plants)</TTITLE>
                        <TDESC>
                            [Note: See end of 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             for an explanation of symbols used in this table]
                        </TDESC>
                        <BOXHD>
                            <CHED H="1">Status</CHED>
                            <CHED H="2">Category</CHED>
                            <CHED H="2">Priority</CHED>
                            <CHED H="1">
                                Lead
                                <LI>region</LI>
                            </CHED>
                            <CHED H="1">Scientific name</CHED>
                            <CHED H="1">Family</CHED>
                            <CHED H="1">Common name</CHED>
                            <CHED H="1">Historical range</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">MAMMALS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Myotis septentrionalis</E>
                            </ENT>
                            <ENT/>
                            <ENT>Bat, northern long-eared</ENT>
                            <ENT>U.S.A. (AL, AR, CT, DE, DC, FL, GA, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NH, NJ, NY, NC, ND, OH, OK, PA, RI, SC, SD, TN, VT, VA, WV, WI, WY); Canada (AB, BC, LB, MB, NB, NF, NS, NT, ON, PE, QC, SK, YT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Emballonura semicaudata rotensis</E>
                            </ENT>
                            <ENT>Emballonuridae</ENT>
                            <ENT>Bat, Pacific sheath-tailed (Mariana Islands subspecies)</ENT>
                            <ENT>U.S.A. (GU, CNMI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Emballonura semicaudata semicaudata</E>
                            </ENT>
                            <ENT>Emballonuridae</ENT>
                            <ENT>Bat, Pacific sheath-tailed (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Fiji, Independent Samoa, Tonga, Vanuatu.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72491"/>
                            <ENT I="01">C *</ENT>
                            <ENT>6</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Tamias minimus atristriatus</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Chipmunk, Peñasco least</ENT>
                            <ENT>U.S.A. (NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Sylvilagus transitionalis</E>
                            </ENT>
                            <ENT>Leporidae</ENT>
                            <ENT>Cottontail, New England</ENT>
                            <ENT>U.S.A. (CT, MA, ME, NH, NY, RI, VT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>6</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Martes pennanti</E>
                            </ENT>
                            <ENT>Mustelidae</ENT>
                            <ENT>Fisher (west coast DPS)</ENT>
                            <ENT>U.S.A. (CA, CT, IA, ID, IL, IN, KY, MA, MD, ME, MI, MN, MT, ND, NH, NJ, NY, OH, OR, PA, RI, TN, UT, VA, VT, WA, WI, WV, WY), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Urocitellus endemicus</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Squirrel, Southern Idaho ground</ENT>
                            <ENT>U.S.A. (ID).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Urocitellus washingtoni</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Squirrel, Washington ground</ENT>
                            <ENT>U.S.A. (WA, OR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Arborimus longicaudus</E>
                            </ENT>
                            <ENT>Cricetidae</ENT>
                            <ENT>Vole, Red (north Oregon coast DPS)</ENT>
                            <ENT>U.S.A. (OR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R7</ENT>
                            <ENT>
                                <E T="03">Odobenus rosmarus divergens</E>
                            </ENT>
                            <ENT>Odobenidae</ENT>
                            <ENT>Walrus, Pacific</ENT>
                            <ENT>U.S.A. (AK), Russian Federation (Kamchatka and Chukotka).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Canis lupus baileyi</E>
                            </ENT>
                            <ENT>Canidae</ENT>
                            <ENT>Wolf, Mexican gray</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">BIRDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Porzana tabuensis</E>
                            </ENT>
                            <ENT>Rallidae</ENT>
                            <ENT>Crake, spotless (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Australia, Fiji, Independent Samoa, Marquesas, Philippines, Society Islands, Tonga.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Gallicolumba stairi</E>
                            </ENT>
                            <ENT>Columbidae</ENT>
                            <ENT>Ground-dove, friendly (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Independent Samoa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>3</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Calidris canutus rufa</E>
                            </ENT>
                            <ENT>Scolopacidae</ENT>
                            <ENT>Knot, red</ENT>
                            <ENT>U.S.A. (Atlantic coast), Canada, South America.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Gymnomyza samoensis</E>
                            </ENT>
                            <ENT>Meliphagidae</ENT>
                            <ENT>Ma'oma'o</ENT>
                            <ENT>U.S.A. (AS), Independent Samoa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Synthliboramphus hypoleucus</E>
                            </ENT>
                            <ENT>Alcidae</ENT>
                            <ENT>Murrelet, Xantus's</ENT>
                            <ENT>U.S.A. (CA), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Amazona viridigenalis</E>
                            </ENT>
                            <ENT>Psittacidae</ENT>
                            <ENT>Parrot, red-crowned</ENT>
                            <ENT>U.S.A. (TX), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Anthus spragueii</E>
                            </ENT>
                            <ENT>Motacillidae</ENT>
                            <ENT>Pipit, Sprague's</ENT>
                            <ENT>U.S.A. (AR, AZ, CO, KS, LA, MN, MS, MT, ND, NE, NM, OK, SD, TX), Canada, Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater (Bi-State DPS)</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>6</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater (Columbia Basin DPS)</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Centrocercus minimus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, Gunnison</ENT>
                            <ENT>U.S.A. (AZ, CO, NM, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Oceanodroma castro</E>
                            </ENT>
                            <ENT>Hydrobatidae</ENT>
                            <ENT>Storm-petrel, band-rumped (Hawaii DPS)</ENT>
                            <ENT>U.S.A. (HI), Atlantic Ocean, Ecuador (Galapagos Islands), Japan.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Dendroica angelae</E>
                            </ENT>
                            <ENT>Emberizidae</ENT>
                            <ENT>Warbler, elfin-woods</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <PRTPAGE P="72492"/>
                            <ENT I="21">
                                <E T="02">REPTILES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Sistrurus catenatus</E>
                            </ENT>
                            <ENT>Viperidae</ENT>
                            <ENT>Massasauga (=rattlesnake), eastern</ENT>
                            <ENT>U.S.A. (IA, IL, IN, MI, MN, MO, NY, OH, PA, WI), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Emoia slevini</E>
                            </ENT>
                            <ENT>Scincidae</ENT>
                            <ENT>Skink, Slevin's (Guali'ek Halom Tano)</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pituophis melanoleucus lodingi</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, black pine</ENT>
                            <ENT>U.S.A. (AL, LA, MS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pituophis ruthveni</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, Louisiana pine</ENT>
                            <ENT>U.S.A. (LA, TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gopherus morafkai</E>
                            </ENT>
                            <ENT>Testudinidae</ENT>
                            <ENT>Tortoise, Sonoran desert</ENT>
                            <ENT>U.S.A. (AZ, CA, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gopherus polyphemus</E>
                            </ENT>
                            <ENT>Testudinidae</ENT>
                            <ENT>Tortoise, gopher (eastern population)</ENT>
                            <ENT>U.S.A. (AL, FL, GA, LA, MS, SC).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>6</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Kinosternon sonoriense longifemorale</E>
                            </ENT>
                            <ENT>Kinosternidae</ENT>
                            <ENT>Turtle, Sonoyta mud</ENT>
                            <ENT>U.S.A. (AZ), Mexico.</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">AMPHIBIANS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rana luteiventris</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, Columbia spotted (Great Basin DPS)</ENT>
                            <ENT>U.S.A. (AK, ID, MT, NV, OR, UT, WA, WY), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Lithobates onca</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, relict leopard</ENT>
                            <ENT>U.S.A. (AZ, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Notophthalmus perstriatus</E>
                            </ENT>
                            <ENT>Salamandridae</ENT>
                            <ENT>Newt, striped</ENT>
                            <ENT>U.S.A. (FL, GA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gyrinophilus gulolineatus</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Berry Cave</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Hyla wrightorum</E>
                            </ENT>
                            <ENT>Hylidae</ENT>
                            <ENT>Treefrog, Arizona (Huachuca/Canelo DPS)</ENT>
                            <ENT>U.S.A. (AZ), Mexico (Sonora).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Necturus alabamensis</E>
                            </ENT>
                            <ENT>Proteidae</ENT>
                            <ENT>Waterdog, black warrior (=Sipsey Fork)</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FISHES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gila nigra</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, headwater</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gila robusta</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, roundtail (Lower Colorado River Basin DPS)</ENT>
                            <ENT>U.S.A. (AZ, CO, NM, UT, WY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Etheostoma cragini</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Arkansas</ENT>
                            <ENT>U.S.A. (AR, CO, KS, MO, OK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma sagitta</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Cumberland arrow</ENT>
                            <ENT>U.S.A. (KY, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Crystallaria cincotta</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, diamond</ENT>
                            <ENT>U.S.A. (KY, OH, TN, WV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma spilotum</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Kentucky arrow</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Percina aurora</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Pearl</ENT>
                            <ENT>U.S.A. (LA, MS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Moxostoma</E>
                                 sp
                            </ENT>
                            <ENT>Catostomidae</ENT>
                            <ENT>Redhorse, sicklefin</ENT>
                            <ENT>U.S.A. (GA, NC, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Spirinchus thaleichthys</E>
                            </ENT>
                            <ENT>Osmeridae</ENT>
                            <ENT>Smelt, longfin (San Francisco bay-delta DPS)</ENT>
                            <ENT>U.S.A. (AK, CA, OR, WA), Canada.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">PSAT</ENT>
                            <ENT>N/A</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Salvelinus malma</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Trout, Dolly Varden</ENT>
                            <ENT>U.S.A. (AK, WA), Canada, East Asia.</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">CLAMS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Lampsilis bracteata</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Fatmucket, Texas</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Truncilla macrodon</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Fawnsfoot, Texas</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Popenaias popei</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Hornshell, Texas</ENT>
                            <ENT>U.S.A. (NM, TX), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Quadrula aurea</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Orb, golden</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Quadrula houstonensis</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pimpleback, smooth</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Quadrula petrina</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pimpleback, Texas</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">SNAILS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Elimia melanoides</E>
                            </ENT>
                            <ENT>Pleuroceridae</ENT>
                            <ENT>Mudalia, black</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Planorbella magnifica</E>
                            </ENT>
                            <ENT>Planorbidae</ENT>
                            <ENT>Ramshorn, magnificent</ENT>
                            <ENT>U.S.A. (NC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ostodes strigatus</E>
                            </ENT>
                            <ENT>Potaridae</ENT>
                            <ENT>Sisi snail</ENT>
                            <ENT>U.S.A. (AS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Samoana fragilis</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, fragile tree</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula radiolata</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Guam tree</ENT>
                            <ENT>U.S.A. (GU).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72493"/>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula gibba</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Humped tree</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula langfordi</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Langford's tree</ENT>
                            <ENT>U.S.A. (MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Eua zebrina</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Tutuila tree</ENT>
                            <ENT>U.S.A. (AS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis thompsoni</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Huachuca</ENT>
                            <ENT>U.S.A. (AZ), Mexico.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis morrisoni</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Page</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">INSECTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus anthracinus</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus assimulans</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus facilis</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus hilaris</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus kuakea</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus longiceps</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus mana</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Hermelycaena</E>
                                 [
                                <E T="03">Lycaena</E>
                                ]
                                <E T="03"> hermes</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Hermes copper</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hypolimnas octucula mariannensis</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Mariana eight-spot</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Vagrans egistina</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Mariana wandering</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Atlantea tulita</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Puerto Rican harlequin</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Glyphopsyche sequatchie</E>
                            </ENT>
                            <ENT>Limnephilidae</ENT>
                            <ENT>Caddisfly, Sequatchie</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus insularis</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Baker Station (=insular)</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus caecus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Clifton</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus colemanensis</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Coleman</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus fowlerae</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Fowler's</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus frigidus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, icebox</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus tiresias</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Indian Grave Point (= Soothsayer)</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus inquisitor</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, inquirer</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus troglodytes</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Louisville</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus paulus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Noblett's</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus parvus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Tatum</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Megalagrion xanthomelas</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, orangeblack Hawaiian</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ischnura luta</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, Rota blue</ENT>
                            <ENT>U.S.A. (Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Ambrysus funebris</E>
                            </ENT>
                            <ENT>Naucoridae</ENT>
                            <ENT>Naucorid bug (=Furnace Creek), Nevares Spring</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Papaipema eryngii</E>
                            </ENT>
                            <ENT>Noctuidae</ENT>
                            <ENT>Moth, rattlesnake-master borer</ENT>
                            <ENT>U.S.A. (AR, IL, KY, NC, OK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Heterelmis stephani</E>
                            </ENT>
                            <ENT>Elmidae</ENT>
                            <ENT>Riffle beetle, Stephan's</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>8</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Hesperia dacotae</E>
                            </ENT>
                            <ENT>Hesperiidae</ENT>
                            <ENT>Skipper, Dakota</ENT>
                            <ENT>U.S.A. (MN, IA, SD, ND, IL), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Oarisma poweshiek</E>
                            </ENT>
                            <ENT>Hesperiidae</ENT>
                            <ENT>Skipperling, Poweshiek</ENT>
                            <ENT>U.S.A. (IA, IL, IN, MI, MN, ND, SD, WI), Canada (MB).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Capnia arapahoe</E>
                            </ENT>
                            <ENT>Capniidae</ENT>
                            <ENT>Snowfly, Arapahoe</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72494"/>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Lednia tumana</E>
                            </ENT>
                            <ENT>Nemouridae</ENT>
                            <ENT>Stonefly, meltwater lednian</ENT>
                            <ENT>U.S.A. (MT).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cicindela highlandensis</E>
                            </ENT>
                            <ENT>Cicindelidae</ENT>
                            <ENT>Tiger beetle, highlands</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">CRUSTACEANS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C</ENT>
                            <ENT>8</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Stygobromus kenki</E>
                            </ENT>
                            <ENT>Crangonyctidae</ENT>
                            <ENT>Amphipod, Kenk's</ENT>
                            <ENT>U.S.A. (DC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Metabetaeus lohena</E>
                            </ENT>
                            <ENT>Alpheidae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Palaemonella burnsi</E>
                            </ENT>
                            <ENT>Palaemonidae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Procaris hawaiana</E>
                            </ENT>
                            <ENT>Procarididae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FLOWERING PLANTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Abronia alpina</E>
                            </ENT>
                            <ENT>Nyctaginaceae</ENT>
                            <ENT>Sand-verbena, Ramshaw Meadows</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Argythamnia blodgettii</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Silverbush, Blodgett's</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Artemisia borealis var</E>
                                <E T="03">. wormskioldii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Wormwood, northern</ENT>
                            <ENT>U.S.A. (OR, WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus anserinus</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Goose Creek</ENT>
                            <ENT>U.S.A. (ID, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus microcymbus</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, skiff</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus schmolliae</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Schmoll</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus tortipes</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Sleeping Ute</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Boechera</E>
                                 (
                                <E T="03">Arabis</E>
                                ) 
                                <E T="03">pusilla</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Rockcress, Fremont County or small</ENT>
                            <ENT>U.S.A. (WY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>Cebello halumtano</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Calamagrostis expansa</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Reedgrass, Maui</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Calochortus persistens</E>
                            </ENT>
                            <ENT>Liliaceae</ENT>
                            <ENT>Mariposa lily, Siskiyou</ENT>
                            <ENT>U.S.A. (CA, OR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaecrista lineata</E>
                                 var
                                <E T="03">. keyensis</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Pea, Big Pine partridge</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>12</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaesyce deltoidea pinetorum</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Sandmat, pineland</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>9</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaesyce deltoidea serpyllum</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Spurge, wedge</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>6</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Chorizanthe parryi</E>
                                 var. 
                                <E T="03">fernandina</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Spineflower, San Fernando Valley</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Cirsium wrightii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Thistle, Wright's</ENT>
                            <ENT>U.S.A. (AZ, NM), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea kauaulaensis</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                            <ENT>Cycadaceae</ENT>
                            <ENT>Fadang</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyperus neokunthianus</E>
                            </ENT>
                            <ENT>Cyperaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra hematos</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha'iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Dalea carthagenensis</E>
                                 var
                                <E T="03">. floridana</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Prairie-clover, Florida</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Dendrobium guamens</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Dichanthelium hirstii</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Panic grass, Hirst Brothers'</ENT>
                            <ENT>U.S.A. (DE, GA, NC, NJ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Digitaria pauciflora</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Crabgrass, Florida pineland</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Eriogonum soredium</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Frisco</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Eugenia bryanii</E>
                            </ENT>
                            <ENT>Myrtaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Exocarpos menziesii</E>
                            </ENT>
                            <ENT>Santalaceae</ENT>
                            <ENT>Menzies ballart</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Festuca hawaiiensis</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Festuca ligulata</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Fescue, Guadalupe</ENT>
                            <ENT>U.S.A. (TX), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Gardenia remyi</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Nanu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hedyotis megalantha</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Paudedo</ENT>
                            <ENT>U.S.A. (Guam).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                            <ENT>Malvaceae</ENT>
                            <ENT>Ufa-halomtano</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Joinvillea ascendens ascendens</E>
                            </ENT>
                            <ENT>Joinvilleaceae</ENT>
                            <ENT>'Ohe</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Kadua</E>
                                 (=
                                <E T="03">Hedyotis</E>
                                )
                                <E T="03"> fluviatilis</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Kampua'a</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Kadua haupuensis</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Labordia lorenciana</E>
                            </ENT>
                            <ENT>Loganiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Lepidium orbiculare</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Lepidium ostleri</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Peppergrass, Ostler's</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Linum arenicola</E>
                            </ENT>
                            <ENT>Linaceae</ENT>
                            <ENT>Flax, sand</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72495"/>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Maesa walkeri</E>
                            </ENT>
                            <ENT>Primulaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Myrsine fosbergii</E>
                            </ENT>
                            <ENT>Myrsinaceae</ENT>
                            <ENT>Kolea</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Nervilia jacksoniae</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Nothocestrum latifolium</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>'Aiea</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ochrosia haleakalae</E>
                            </ENT>
                            <ENT>Apocynaceae</ENT>
                            <ENT>Holei</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllanthus saffordii</E>
                            </ENT>
                            <ENT>Phyllanthaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllostegia brevidens</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllostegia helleri</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllostegia stachyoides</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Pinus albicaulis</E>
                            </ENT>
                            <ENT>Pinaceae</ENT>
                            <ENT>Pine, whitebark</ENT>
                            <ENT>U.S.A. (CA, ID, MT, NV, OR, WA, WY), Canada (AB, BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Platanthera integrilabia</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>Orchid, white fringeless</ENT>
                            <ENT>U.S.A. (AL, GA, KY, MS, NC, SC, TN, VA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Portulaca villosa</E>
                            </ENT>
                            <ENT>Portulacaceae</ENT>
                            <ENT>Ihi</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pritchardia bakeri</E>
                            </ENT>
                            <ENT>Arecaceae</ENT>
                            <ENT>Lo'ulu (=Lo'ulu lelo)</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pseudognaphalium</E>
                                 (=
                                <E T="03">Gnaphalium</E>
                                )
                                <E T="03"> sandwicensium</E>
                                 var.
                                <E T="03"> molokaiense</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>'Ena'ena</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Psychotria malaspinae</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Aplokating-palaoan</ENT>
                            <ENT>U.S.A. (Guam).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ranunculus hawaiensis</E>
                            </ENT>
                            <ENT>Ranunculaceae</ENT>
                            <ENT>Makou</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ranunculus mauiensis</E>
                            </ENT>
                            <ENT>Ranunculaceae</ENT>
                            <ENT>Makou</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rorippa subumbellata</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Cress, Tahoe yellow</ENT>
                            <ENT>U.S.A. (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Sanicula sandwicensis</E>
                            </ENT>
                            <ENT>Apiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Santalum involutum</E>
                            </ENT>
                            <ENT>Santalaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Schiedea diffusa</E>
                                 ssp. 
                                <E T="03">diffusa</E>
                            </ENT>
                            <ENT>Caryophyllaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Schiedea pubescens</E>
                            </ENT>
                            <ENT>Caryophyllaceae</ENT>
                            <ENT>Ma'oli'oli</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Sicyos lanceoloideus</E>
                            </ENT>
                            <ENT>Cucurbitaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Sicyos macrophyllus</E>
                            </ENT>
                            <ENT>Cucurbitaceae</ENT>
                            <ENT>'Anunu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>12</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Sideroxylon reclinatum austrofloridense</E>
                            </ENT>
                            <ENT>Sapotaceae</ENT>
                            <ENT>Bully, Everglades</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Solanum conocarpum</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>Bacora, marron</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Solanum guamense</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>Bereng-henas halomtano</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Solanum nelsonii</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>Popolo</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Stenogyne kaalae</E>
                                 ssp. 
                                <E T="03">sherffii</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Streptanthus bracteatus</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Twistflower, bracted</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                            <ENT>Apocynaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>Menispermaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A (Guam).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Trifolium friscanum</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Clover, Frisco</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (Guam, Mariana Islands).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Wikstroemia skottsbergiana</E>
                            </ENT>
                            <ENT>Thymelaeaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FERNS AND ALLIES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Asplenium diellaciniatum</E>
                            </ENT>
                            <ENT>Aspleniaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyclosorus boydiae</E>
                            </ENT>
                            <ENT>Thelypteridaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Deparia kaalaana</E>
                            </ENT>
                            <ENT>Woodsiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Dryopteris glabra</E>
                                 var. 
                                <E T="03">pusilla</E>
                            </ENT>
                            <ENT>Dryopteridaceae</ENT>
                            <ENT>Kilau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hypolepis hawaiiensis</E>
                                 var. 
                                <E T="03">mauiensis</E>
                            </ENT>
                            <ENT>Dennstaedtiaceae</ENT>
                            <ENT>Olua</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Huperzia</E>
                                 (=
                                <E T="03">Phlegmariurus</E>
                                ) 
                                <E T="03">stemmermanniae</E>
                            </ENT>
                            <ENT>Lycopodiaceae</ENT>
                            <ENT>Wawae'iole</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C *</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Microlepia strigosa</E>
                                 var. 
                                <E T="03">mauiensis</E>
                                 (=
                                <E T="03">Microlepia mauiensis</E>
                                )
                            </ENT>
                            <ENT>Dennstaedtiaceae</ENT>
                            <ENT>Palapalai</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Trichomanes punctatum floridanum</E>
                            </ENT>
                            <ENT>Hymenophyllaceae</ENT>
                            <ENT>Florida bristle fern</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="72496"/>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="xs36,xs36,xs36,r50,r50,r50,r50">
                        <TTITLE>Table 2—Animals and Plants Formerly Candidates or Formerly Proposed for Listing</TTITLE>
                        <TDESC>
                            [Note: See end of 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             for an explanation of symbols used in this table]
                        </TDESC>
                        <BOXHD>
                            <CHED H="1">Status</CHED>
                            <CHED H="2">Code</CHED>
                            <CHED H="2">Expl.</CHED>
                            <CHED H="1">
                                Lead 
                                <LI>region</LI>
                            </CHED>
                            <CHED H="1">Scientific name</CHED>
                            <CHED H="1">Family</CHED>
                            <CHED H="1">Common name</CHED>
                            <CHED H="1">Historical range</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">MAMMALS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Lynx canadensis</E>
                            </ENT>
                            <ENT>Felidae</ENT>
                            <ENT>Lynx, Canada (New Mexico population)</ENT>
                            <ENT>U.S.A. (CO, ID, ME, MI, MN, MT, NH, NY, OR, UT, VT, WA, WI, WY), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Zapus hudsonius luteus</E>
                            </ENT>
                            <ENT>Zapodidae</ENT>
                            <ENT>Mouse, New Mexico meadow jumping</ENT>
                            <ENT>U.S.A. (AZ, CO, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama glacialis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Roy Prairie</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama pugetensis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Olympia</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama tumuli</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Tenino</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama yelmensis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Yelm</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Cynomys gunnisoni</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Prairie dog, Gunnison's (populations in central and south-central Colorado, north-central New Mexico)</ENT>
                            <ENT>U.S.A. (CO, NM).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Rp</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Gulo gulo luscus</E>
                            </ENT>
                            <ENT>Mustelidae</ENT>
                            <ENT>Wolverine, North American (Contiguous U.S. DPS)</ENT>
                            <ENT>U.S.A. (CA, CO, ID, MT, OR, UT, WA, WY).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">BIRDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Coccyzus americanus</E>
                            </ENT>
                            <ENT>Cuculidae</ENT>
                            <ENT>Cuckoo, yellow-billed (Western U.S. DPS)</ENT>
                            <ENT>U.S.A. (Lower 48 States), Canada, Mexico, Central and South America.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R7</ENT>
                            <ENT>
                                <E T="03">Gavia adamsii</E>
                            </ENT>
                            <ENT>Gaviidae</ENT>
                            <ENT>Loon, yellow-billed</ENT>
                            <ENT>U.S.A. (AK), Canada, Norway, Russia, coastal waters of southern Pacific and North Sea.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Tympanuchus pallidicinctus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Prairie-chicken, lesser</ENT>
                            <ENT>U.S.A. (CO, KA, NM, OK, TX).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">REPTILES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Thamnophis rufipunctatus</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Gartersnake, narrow-headed</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Thamnophis eques megalops</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Gartersnake, northern Mexican</ENT>
                            <ENT>U.S.A. (AZ, NM, NV), Mexico.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Chionactis occipitalis klauberi</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, Tucson shovel-nosed</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">AMPHIBIANS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rana muscosa</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, mountain yellow-legged (northern California DPS)</ENT>
                            <ENT>U.S.A (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Rana pretiosa</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, Oregon spotted</ENT>
                            <ENT>U.S.A. (CA, OR, WA), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rana sierrae</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, Sierra Nevada yellow-legged frog</ENT>
                            <ENT>U.S.A. (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea naufragia</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Georgetown</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea chisholmensis</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Salado</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Anaxyrus canorus</E>
                            </ENT>
                            <ENT>Bufonidae</ENT>
                            <ENT>Toad, Yosemite</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FISHES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Iotichthys phlegethontis</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, least</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Thymallus arcticus</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Grayling, Arctic (upper Missouri River DPS)</ENT>
                            <ENT>U.S.A. (AK, MI, MT, WY), Canada, northern Asia, northern Europe.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72497"/>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Notropis oxyrhynchus</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Shiner, sharpnose</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Notropis buccula</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Shiner, smalleye</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Catostomus discobolus yarrowi</E>
                            </ENT>
                            <ENT>Catostomidae</ENT>
                            <ENT>Sucker, Zuni bluehead</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Rc</ENT>
                            <ENT>U</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Oncorhynchus clarki virginalis</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Trout, Rio Grande cutthroat</ENT>
                            <ENT>U.S.A. (CO, NM).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">INSECTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Strymon acis bartrami</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Bartram's scrub-hairstreak</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Anaea troglodyta floridalis</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Florida leafwing</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">ARACHNIDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Rc</ENT>
                            <ENT>N</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Cicurina wartoni</E>
                            </ENT>
                            <ENT>Dictynidae</ENT>
                            <ENT>Meshweaver, Warton's cave</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FLOWERING PLANTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Agave eggersiana</E>
                            </ENT>
                            <ENT>Agavaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (VI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Arabis georgiana</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Rockcress, Georgia</ENT>
                            <ENT>U.S.A. (AL, GA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Astragalus cusickii</E>
                                 var.
                                <E T="03"> packardiae</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Packard's</ENT>
                            <ENT>U.S.A. (ID).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Brickellia mosieri</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Brickell-bush, Florida</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum corymbosum</E>
                                 var
                                <E T="03">. nilesii</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Las Vegas</ENT>
                            <ENT>U.S.A. (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum diatomaceum</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Churchill Narrows</ENT>
                            <ENT>U.S.A (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum kelloggii</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Red Mountain</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gonocalyx concolor</E>
                            </ENT>
                            <ENT>Ericaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Helianthus verticillatus</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Sunflower, whorled</ENT>
                            <ENT>U.S.A. (AL, GA, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Ivesia webberi</E>
                            </ENT>
                            <ENT>Rosaceae</ENT>
                            <ENT>Ivesia, Webber</ENT>
                            <ENT>U.S.A. (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leavenworthia crassa</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Gladecress, fleshy-fruit</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leavenworthia exigua</E>
                                 var. 
                                <E T="03">laciniata</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Gladecress, Kentucky</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Linum carteri</E>
                                 var
                                <E T="03">. carteri</E>
                            </ENT>
                            <ENT>Linaceae</ENT>
                            <ENT>Flax, Carter's small-flowered</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Mimulus fremontii</E>
                                 var. 
                                <E T="03">vandenbergensis</E>
                            </ENT>
                            <ENT>Phrymaceae</ENT>
                            <ENT>Monkeyflower, Vandenberg</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rp</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Penstemon grahamii</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Beardtongue, Graham's</ENT>
                            <ENT>U.S.A. (CO, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rp</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Penstemon scariosus</E>
                                 var
                                <E T="03">. albifluvis</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Beardtongue, White River</ENT>
                            <ENT>U.S.A. (CO, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Physaria globosa</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Bladderpod, Short's</ENT>
                            <ENT>U.S.A. (IN, KY, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Sedum eastwoodiae</E>
                            </ENT>
                            <ENT>Crassulaceae</ENT>
                            <ENT>Stonecrop, Red Mountain</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>U</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Symphyotrichum georgianum</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Aster, Georgia</ENT>
                            <ENT>U.S.A. (AL, FL, GA, NC, SC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Varronia (=Cordia) rupicola</E>
                            </ENT>
                            <ENT>Boraginaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (PR), Anegada.</ENT>
                        </ROW>
                    </GPOTABLE>
                </SUPLINF>
                <FRDOC>[FR Doc. 2014-28536 Filed 12-4-14; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4310-55-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="72499"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <HRULE/>
            <CFR>42 CFR Parts 405, 424, and 498</CFR>
            <TITLE>Medicare Program; Requirements for the Medicare Incentive Reward Program and Provider Enrollment; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="72500"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                    <CFR>42 CFR Parts 405, 424, and 498</CFR>
                    <DEPDOC>[CMS-6045-F]</DEPDOC>
                    <RIN>RIN 0938-AP01</RIN>
                    <SUBJECT>Medicare Program; Requirements for the Medicare Incentive Reward Program and Provider Enrollment</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This final rule implements various provider enrollment requirements. These include: Expanding the instances in which a felony conviction can serve as a basis for denial or revocation of a provider or supplier's enrollment; if certain criteria are met, enabling us to deny enrollment if the enrolling provider, supplier, or owner thereof had an ownership relationship with a previously enrolled provider or supplier that had a Medicare debt; enabling us to revoke Medicare billing privileges if we determine that the provider or supplier has a pattern or practice of submitting claims that fail to meet Medicare requirements; and limiting the ability of ambulance suppliers to “backbill” for services performed prior to enrollment.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>These regulations are effective on February 3, 2015.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Frank Whelan, (410) 786-1302.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">I. Executive Summary and Background</HD>
                    <HD SOURCE="HD2">A. Executive Summary</HD>
                    <HD SOURCE="HD3">1. Purpose</HD>
                    <HD SOURCE="HD3">a. Need for Regulatory Action</HD>
                    <P>This final rule is necessary to make certain changes to the provider enrollment provisions in 42 CFR part 424, subpart P. This final rule will strengthen program integrity and help ensure that fraudulent entities and individuals do not enroll in or maintain their enrollment in the Medicare program.</P>
                    <HD SOURCE="HD3">b. Legal Authority</HD>
                    <P>Sections 1102 and 1871 of the Social Security Act provide general authority for the Secretary to prescribe regulations for the efficient administration of the Medicare program. Also, section 1866(j) of the Act, codified at 42 U.S.C. 1395cc(j), provides specific authority with respect to the enrollment process for providers and suppliers.</P>
                    <HD SOURCE="HD3">2. Brief Summary of the Major Provider Enrollment Provisions</HD>
                    <P>We are finalizing the following major provisions regarding provider enrollment:</P>
                    <P>• Allowing denial of enrollment if the provider, supplier, or owner thereof was previously the owner of a provider or supplier that had a Medicare debt that existed when the latter's enrollment was voluntarily terminated, involuntarily terminated or revoked and—</P>
                    <P>++ The owner left the provider or supplier that had the Medicare debt within 1 year of that provider or supplier's voluntary termination, involuntary termination, or revocation;</P>
                    <P>++ The Medicare debt has not been fully repaid; and</P>
                    <P>++ We determine that the uncollected debt poses an undue risk of fraud, waste, or abuse.</P>
                    <P>A denial under this provision can be averted if the enrolling provider, supplier, or owner thereof—(1) satisfies the criteria set forth in § 401.607 and agrees to a CMS-approved extended repayment schedule for the entire outstanding Medicare debt; or (2) repays the debt in full.</P>
                    <P>• Allowing denial of enrollment or revocation of Medicare billing privileges if, within the preceding 10 years, the provider or supplier, or any owner or managing employee thereof, was convicted of a federal or state felony offense that CMS determines to be detrimental to the best interests of the Medicare program and its beneficiaries. (Under the previous regulation, enrollment could not be denied or revoked based on a managing employee's felony conviction.)</P>
                    <P>• Allowing revocation of Medicare billing privileges if the provider or supplier has a pattern or practice of submitting claims that fail to meet Medicare requirements.</P>
                    <P>• With the exception noted in section II.B.5. of this final rule, requiring all revoked providers and suppliers (regardless of type) to submit all of their remaining claims within 60 days after the effective date of their revocation.</P>
                    <P>• Limiting the ability of ambulance companies to “back bill” for services furnished prior to enrollment. Under § 424.520(d), physicians, non-physician practitioners, and physician and non-physician practitioner organizations currently cannot bill for services furnished prior to the later of the date the supplier filed a Medicare enrollment application that was subsequently approved by a Medicare contractor or the date the supplier first began furnishing services at a new practice location. (Independent diagnostic testing facilities (IDTFs) and suppliers of durable medical equipment, prosthetics, orthotics, and supplies (DMEPOS) have similar restrictions.) We are expanding this to include ambulance suppliers.</P>
                    <P>• Limiting the ability of revoked providers and suppliers to submit a corrective action plan (CAP) to situations where the revocation was based on § 424.535(a)(1).</P>
                    <HD SOURCE="HD3">3. Incentive Reward Program (IRP)</HD>
                    <P>We may finalize the provisions relating to the IRP in future rulemaking.</P>
                    <HD SOURCE="HD3">4. Summary of Costs and Benefits</HD>
                    <P>The following table provides a summary of the costs and benefits associated with the principal provisions of this final rule.</P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r100">
                        <TTITLE>Table 1—Summary of Costs and Impacts</TTITLE>
                        <BOXHD>
                            <CHED H="1">Provision description</CHED>
                            <CHED H="1">Impacts</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Denial of Enrollment Based on Medicare Debt</ENT>
                            <ENT>Though a savings to the federal government will accrue from such a denial, the monetary amount cannot be quantified.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Expansion of Ability to Deny or Revoke Medicare Billing Privileges Based on Felony Conviction</ENT>
                            <ENT>Though a savings to the federal government will accrue from such a denial or revocation, the monetary amount cannot be quantified.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Revocation Based on Pattern or Practice of Submitting Claims that Do Not Meet Medicare Requirements</ENT>
                            <ENT>Though a savings to the federal government will accrue from such a revocation, the monetary amount cannot be quantified.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Requirement for Revoked Providers and Suppliers to Submit Remaining Claims within 60 Days after Effective Date of Revocation</ENT>
                            <ENT>Monetary amount cannot be quantified. However, we believe this requirement will—(1) limit the Medicare program's vulnerability to fraudulent claims; and (2) allow more focused medical review. This will likely result in some savings to the federal government.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="72501"/>
                            <ENT I="01">Inclusion of Ambulance Suppliers within § 424.520(d)</ENT>
                            <ENT>Will result in a transfer of $327.4 million per year (primary estimate) from ambulance suppliers to the federal government.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Limitation of Ability to Submit CAP to Situations where Revocation based on § 424.535(a)(1)</ENT>
                            <ENT>Monetary amount cannot be quantified. However, the provision will prevent these providers and suppliers from being able to immediately begin billing Medicare again once they submit the correct information.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">B. Background and General Overview</HD>
                    <P>
                        In the April 21, 2006 
                        <E T="04">Federal Register</E>
                         (71 FR 20754), we published a final rule titled, “Medicare Program; Requirements for Providers and Suppliers to Establish and Maintain Medicare Enrollment.” The final rule set forth requirements in part 424, subpart P that providers and suppliers must meet in order to obtain and maintain Medicare billing privileges. Since its publication in April 2006, we have updated subpart P to address a number of enrollment issues.
                    </P>
                    <P>In the April 2006 final rule, we cited sections 1102 and 1871 of the Act as general authority for our establishment of these requirements, which were designed for the efficient administration of the Medicare program. Pursuant to this general rulemaking authority as well as to section 1866(j) of the Act, we proposed several additional changes to our provider enrollment regulations to help ensure that Medicare payments are only made to qualified providers and suppliers.</P>
                    <P>
                        In the April 29, 2013 
                        <E T="04">Federal Register</E>
                         (78 FR 25013), we published a proposed rule that would revise the IRP provisions and certain provider enrollment requirements in part 424, subpart P.
                    </P>
                    <HD SOURCE="HD1">II. Provisions of the Proposed Rule and Analysis of and Responses to Public Comments</HD>
                    <HD SOURCE="HD2">A. Incentive Reward Program (IRP)</HD>
                    <P>We received a number of comments regarding our proposed IRP provisions. They focused largely on several issues.</P>
                    <P>First, a number of commenters stated that the significantly increased reward amount would lead to many reports containing irrelevant or erroneous information that would ultimately impose a heavy burden on CMS and its contractors. Providers would also be seriously burdened because they would constantly have to fight unwarranted complaints, perhaps leaving less time for such providers to treat Medicare beneficiaries.</P>
                    <P>Second, several commenters expressed concern regarding our proposal to limit reward eligibility to the first reporter of information about a provider's actual or potential sanctionable conduct. They contended that this could create “shoot first, ask questions later” situations; such a rush to report could also create tension between providers and patients.</P>
                    <P>Third, several commenters stated that our proposal would encourage whistleblowers to first report their concerns to CMS: (1) Instead of using established internal compliance reporting methods (such as hotlines) created within Medicare provider organizations; and (2) without undertaking any initial validation of facts or discussing the matter with the provider.</P>
                    <P>Fourth, commenters questioned whether CMS has the resources in place to handle the enormous influx of tips and complaints that our proposal would generate.</P>
                    <P>Due to the complexity of the operational aspects of our proposal, we are not finalizing our proposed IRP provisions in this rule. We may finalize them in future rulemaking.</P>
                    <HD SOURCE="HD2">B. Provider Enrollment</HD>
                    <P>As noted previously, in April 2006 we published a final rule that set forth requirements that providers and suppliers must meet in order to obtain and maintain Medicare billing privileges. Since that rule's publication, we have revised and supplemented various provisions in part 424, subpart P to address certain payment safeguard issues. As discussed in the following section, this final rule makes additional changes to subpart P.</P>
                    <HD SOURCE="HD3">1. Definition of Enrollment</HD>
                    <P>Most physicians and non-physician practitioners enroll in Medicare to become eligible to receive payment for covered services furnished to Medicare beneficiaries. However, some physicians and non-physician practitioners who are not enrolled in Medicare via the Form CMS-855I enrollment application may wish to enroll for the sole and exclusive purpose of ordering or certifying items or services for Medicare beneficiaries. Consistent with § 424.507, and assuming all other applicable requirements are met, these individuals are eligible to enroll for the sole purpose of ordering or certifying Medicare items or services by completing the CMS-855O application. The CMS-855O (OMB Approval #0938-0685), which became available for use in July 2011, is exclusively designed to allow physicians and eligible professionals to enroll in Medicare solely to order or certify items or services.</P>
                    <P>Physicians and non-physician practitioners who complete the CMS-855O are not eligible to submit claims to Medicare for services they provide, for they are not granted Medicare billing privileges. Because some of our regulatory provisions did not clearly articulate the difference between enrolling in Medicare: (1) To obtain Medicare billing privileges; and (2) solely to order or certify items or services for Medicare beneficiaries, we proposed three remedial changes.</P>
                    <P>The first change involved the definition of “Enroll/Enrollment” in § 424.502, the initial sentence of which stated: “Enroll/Enrollment means the process that Medicare uses to establish eligibility to submit claims for Medicare-covered services and supplies.” We proposed to change this to read: “Enroll/Enrollment means the process that Medicare uses to establish eligibility to submit claims for Medicare-covered items and services, and the process that Medicare uses to establish eligibility to order or certify for Medicare-covered items and services.” Our purpose was to clarify that the overall enrollment process includes enrollment via the CMS-855O.</P>
                    <P>
                        The second revision concerned paragraph (4) of the definition of “Enroll/Enrollment” in § 424.502. We proposed to change the language in this paragraph from “(g)ranting the provider or supplier Medicare billing privileges” to the following: “(4) Except for those suppliers that complete the CMS-855O form or CMS-identified equivalent or successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, granting the Medicare provider or supplier Medicare billing privileges.” This was intended to emphasize that 
                        <PRTPAGE P="72502"/>
                        although enrollment via the CMS-855O enables the supplier to order or certify Medicare-covered items and services, it does not convey Medicare billing privileges to the supplier.
                    </P>
                    <P>The third change involved § 424.505, which states in part that a provider or supplier, once enrolled, receives Medicare billing privileges. We proposed to revise the second sentence of this section to state: “Except for those suppliers that complete the CMS-855O or CMS-identified equivalent or successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, once enrolled the provider or supplier receives billing privileges and is issued a valid billing number effective for the date a claim was submitted for an item that was furnished or a service that was rendered. (See 45 CFR part 162 for information on the National Provider Identifier and its use as the Medicare billing number.)” Again, our purpose was to clarify that enrollment via the CMS-855O enables the supplier to order or certify Medicare-covered items and services but does not grant Medicare billing privileges to the supplier.</P>
                    <P>The following is a summary of the comments we received on these three changes and our responses:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended that the CMS-855O be modified to require the applicant to provide information about his or her practice location and medical record location. The commenters contended that § 424.510(d)(2)(ii) mandates that each submitted enrollment application include the submission of all documentation to uniquely identify a provider or supplier—including, but not limited to, proof of a practice location and medical record storage location. Such proof, the commenters stated, can help reduce identity theft and other forms of Medicare fraud, waste and abuse. A commenter recommended that CMS deactivate the billing privileges of any individual who enrolled in Medicare using the CMS-855O because the CMS-855O does not collect information on practice locations and medical record storage locations. Another commenter suggested that CMS require individuals who have enrolled using the CMS-855O to provide practice location information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These recommended changes regarding the CMS-855O are outside the scope of this rule, though we may consider adding practice location information to the CMS-855O at a later date.
                    </P>
                    <P>Some of the enrollment requirements in § 424.510 are applicable only to providers and suppliers enrolling in Medicare to obtain billing privileges, and do not apply to providers and suppliers enrolling strictly to order or certify items or services for Medicare beneficiaries. In order to clarify those requirements that apply to all enrollments and those that only apply to enrollments to obtain billing privileges, we are revising § 424.510 as follows:</P>
                    <P>• The first two sentences of existing paragraph (a) will be designated as new paragraph (a)(1).</P>
                    <P>• The third sentence of existing paragraph (a) will be designated as new paragraph (a)(2) and is revised to read: “To be enrolled to furnish Medicare-covered items and services, a provider or supplier must meet the requirements specified in paragraphs (d) and (e) of this section.”</P>
                    <P>• New paragraph (a)(3) will state the following: “To be enrolled solely to order and certify Medicare items or services, a physician or non-physician practitioner must meet the requirements specified in paragraph (d) of this section except for paragraphs (2)(iii)(B), (2)(iv), (3)(ii), (5), (6), and (9).” These paragraphs only apply to individuals enrolling to obtain Medicare billing privileges.</P>
                    <P>With respect to the commenter's suggestion regarding deactivation, enrollment via the CMS-855O does not confer billing privileges. Hence, there are no billing privileges to deactivate.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters disagreed with the use of the CMS-855O, arguing that CMS: (1) Lacks the statutory and regulatory basis to either establish a registration process for ordering and certifying physicians and non-physician practitioners or to use an enrollment application for any purpose other than to enroll a provider or supplier (including physicians and non-physician practitioners); and (2) violates 5 U.S.C. 551 
                        <E T="03">et seq.</E>
                         in its use of the CMS-855O without having issued a proposed and final regulation. The commenters further contended that § 424.500 does not contemplate such a registration process and that CMS did not solicit comments on revising § 424.500 for such purpose. A commenter recommended that CMS: (1) Discontinue use of the CMS-855O until it completes the notice and comment rulemaking process described in section 1871 of the Act; and (2) furnish the legal basis for registering physicians and non-physician practitioners for the sole purpose of ordering or certifying Medicare services or items.
                    </P>
                    <P>Other commenters expressed concern that CMS is using the Paperwork Reduction Act of 1995 (PRA) to circumvent the notice and comment rulemaking requirements of the Administrative Procedure Act as a means of establishing a new Medicare enrollment application—specifically, the CMS-855O. A commenter contended that CMS essentially used the PRA process to prohibit physicians from obtaining Medicare billing privileges via the CMS-855O. The commenter recommended that CMS explain its use of the CMS-855O: (1) Without having utilized the notice and comment rulemaking process; and (2) in lieu of using the CMS-855I, which has a legal basis, has already been subject to rulemaking, and duplicates all of the data on the CMS-855O; the commenter argued that CMS has already established an enrollment application for physicians (that is, the CMS-855I) and that the CMS-855O is therefore duplicative of the CMS-855I. With respect to the second suggestion regarding CMS using the PRA process to prohibit physicians from enrolling to obtain billing privileges, the commenter added that CMS could modify the CMS-855I to accommodate physicians and non-physician practitioners seeking only to order or certify items or services. The commenter stated that this would ease the paperwork burden on such individuals should they later wish to obtain Medicare billing privileges; rather than having to complete two separate forms (the CMS-855I and CMS-855O), the commenter continued, the individual would only need to submit an updated CMS-855I application as part of the enrollment process.</P>
                    <P>Another commenter stated that the Privacy Act Statement for the CMS-855O includes various references to payments to providers and suppliers. Since the CMS-855O is designed for the sole purpose of ordering and certifying, the commenter requested that CMS explain its rationale for including such references in the CMS-855O Privacy Act Statement.</P>
                    <P>
                        <E T="03">Response:</E>
                         As already indicated, comments regarding the use or content of the CMS-855O are outside the scope of this rule. However, we note that section 6405 of the Affordable Care Act gave us the authority to require the Medicare enrollment of physicians and non-physician practitioners who order or certify certain items or services for Medicare beneficiaries. We implemented this statutory provision at § 424.507 via a May 5, 2010 interim final rule with comment period (75 FR 24437) and an April 27, 2012 final rule (77 FR 25284). These two rules, as well as the CMS-855O itself, were subject to a notice-and-comment process. (We solicited public comments on the CMS-855O in two 
                        <E T="04">Federal Register</E>
                         notices as 
                        <PRTPAGE P="72503"/>
                        mandated by the PRA.) Moreover, we disagree with the contention that the PRA process was used to prohibit physicians from obtaining Medicare billing privileges via the CMS-855O. The CMS-855O was not designed as a prohibition of any kind but instead as means of permitting—consistent with section 6405 of the Affordable Care Act—certain physicians and non-physician practitioners to enroll in Medicare solely to order or certify Medicare items or services. We believe that completion of an abbreviated form such as the CMS-855O, rather than all or part of the CMS-855I, has eased the burden on the physician and non-physician practitioner communities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether physicians who submit the CMS-855O are required to revalidate their enrollment with the Medicare contractor every 5 years.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We reserve the right to require individuals who are enrolled solely to order or certify items or services to revalidate their enrollment information every 5 years.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that since CMS did not discuss reassignment in this proposed rule, it would seem that section 1871 of the Act would not preclude CMS from barring physicians and non-physician practitioners from enrolling in Medicare via the CMS-855O and reassigning their benefits to a medical group. The commenter sought clarification as to whether a physician can enroll using the CMS-855O and reassign payment/benefits to either an employer or an entity under contractual arrangement. Another commenter questioned whether a physician can simultaneously submit a CMS-855O and CMS-855R if he or she is billing for services through a group practice.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The concept of reassignment (as that term is used in § 424.80) does not apply to CMS-855O situations because there is no right to payment associated with an enrollment via the CMS-855O. In other words, a physician or non-physician practitioner who enrolls via the CMS-855O does not have Medicare billing privileges, and therefore has no right to payment to reassign via the CMS-855R. If he or she wishes to enroll in Medicare, bill the program for services, and reassign his or her benefits to an eligible party, he or she must complete both the CMS-855I and CMS-855R forms. A CMS-855O form cannot be used as a means of obtaining Medicare billing privileges.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether a physician or non-physician practitioner can use the CMS-855O if he or she submits only very few claims to Medicare per year or whether he or she must use the CMS-855I.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the scenario the commenter poses, the physician or non-physician practitioner must use the CMS-855I because he or she will be billing for Medicare services. As discussed previously, the CMS-855O may only be used by physicians or other eligible practitioners who wish to enroll solely to order or certify items or services. It cannot be used to obtain Medicare billing privileges.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether a Medicare-enrolled physician or non-physician practitioner who also works part-time at (and only orders services from) a rural health clinic (RHC) must complete the CMS-855O for his or her activities at the RHC.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The individual need not complete a CMS-855O in this scenario, for he or she is already enrolled in Medicare via the CMS-855I.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that if suppliers who enroll solely to order or certify Medicare items or services are not granted Medicare billing privileges, the regulatory provisions found in Part 424, subpart P do not apply and CMS does not have the authority to approve, deny, deactivate, or revoke individuals who have enrolled or seek to enroll in Medicare via the CMS-855O solely to order and certify. The commenter recommended that CMS propose a new rule to allow CMS to approve, deny, revoke, or deactivate the enrollment of a physician or non-physician practitioner in such instances.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulations in Part 424, subpart P apply to suppliers who are enrolled or enrolling in Medicare and are not limited to suppliers who have or seek Medicare billing privileges. In light of our changes to §§ 424.502, 424.505, and 424.510, the provisions of subpart P apply equally to suppliers who enroll in order to obtain Medicare billing privileges and those who enroll exclusively to order or certify Medicare items or services.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested clarification as to whether a physician must have a valid enrollment record in PECOS to order infusion and nebulizer drugs or other Part B drugs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe this comment is outside the scope of this final rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters sought clarification from CMS concerning the difference between the use of the term “registration” on the CMS-855O and the proposed changes to §§ 424.502 and 424.505, which use the term “enrollment.” One commenter questioned whether these two terms have the same meaning. Another commenter suggested that CMS establish a definition of “register.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our use of the term “registration” on the CMS-855O was designed to clarify the distinction between enrolling in Medicare to obtain billing privileges and enrolling in Medicare solely to order or certify items and services. In the latter situation, the process is the same irrespective of the precise term that is used to describe it. For this reason, and because the CMS-855O process will now be included within the scope of the enrollment provisions of §§ 424.502, 424.505, and 424.510, we do not believe a separate definition of “register” is warranted or needed.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Citing the current definition of “Enroll/Enrollment” in § 424.502, a commenter noted that the enrollment process includes identifying and confirming the provider's practice locations. The commenter contended that since the CMS-855O does not collect practice location information, referencing the CMS-855O in § 424.502 is inappropriate. The commenter suggested that CMS discontinue use of the CMS-855O until it proposes changes to the definition of “Enroll/Enrollment” that eliminate the reference to practice location data.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As mentioned earlier, we may consider adding practice location information to the CMS-855O at a later date. Therefore, we do not believe that the definition of “Enroll/Enrollment” in § 424.502 should be revised to remove the reference to practice locations. However, we will modify paragraph (2) of the definition of “Enroll/Enrollment” in § 424.502 to account for that paragraph's inapplicability to CMS-855O applications. The current version of paragraph (2) states that the enrollment process includes, “Validation of the provider's or supplier's eligibility to provide items or services to Medicare beneficiaries.” Since suppliers who complete the CMS-855O are enrolling solely to order or certify Medicare items and services, we are modifying paragraph (2) to state: “Except for those suppliers who complete the CMS-855O form, CMS-identified equivalent, successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, validating the provider or supplier's eligibility to provide items or services to Medicare beneficiaries.” We note that the new language in paragraph (2) is the same as that which is being added to paragraph (4).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported our proposed changes to §§ 424.502 and 424.505 to reflect that 
                        <PRTPAGE P="72504"/>
                        some physicians and non-physician practitioners may enroll solely to order or certify certain items or services for Medicare beneficiaries. However, one commenter suggested that the verbiage “or CMS-equivalent or successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services” is too wordy and confusing and should be stricken from both sections.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the commenters' support, we do not believe the quoted language should be stricken from §§ 424.502 and 424.505. This language is necessary to account for the possibility that a different process for enabling individuals to enroll solely to order or certify Medicare items and services could be established in the future.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter believed that there remains confusion in the physician and non-physician practitioner communities regarding the difference between enrolling exclusively to order and certify Medicare services, and enrolling for the purpose of participating in and billing Medicare. The commenter urged CMS to make this distinction clear on the CMS-855O form itself and in all applicable CMS educational efforts.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have undertaken extensive educational efforts—including close collaboration with various professional associations—to clarify for the public and the provider community the distinction between the two processes. We will continue our outreach activities on this issue.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether CMS is changing its longstanding policy of requiring providers and suppliers to submit to CMS or its Medicare contractor the applicable provider enrollment application based on the type of provider or supplier enrolling. The commenter also requested that CMS propose and explain the differences between the Medicare enrollment process to convey Medicare billing privileges and this ostensibly new concept of enrolling solely to order and certify items and services in the Medicare program.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         All providers and suppliers, including those suppliers submitting the CMS-855O, will continue to submit enrollment applications based on the provider or supplier type involved. As for the second comment, we will continue our educational efforts to clarify the distinction between these two processes.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that §§ 424.507 and 424.510 must be revised in order for CMS to establish a registration process for physicians and non-physician practitioners seeking only to order or certify items and services.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our use of the term “registration” on the CMS-855O was intended to articulate the distinction between enrolling in Medicare to obtain billing privileges and enrolling in Medicare strictly to order or certify items and services. In the latter situation, the process is the same regardless of the precise term that is used to describe it. The general procedures for completing the CMS-855O and the contractor's processing of the application are similar to those used for other CMS-855 forms. As such, we do not believe that §§ 424.507 and 424.510 need to be revised to establish a unique process for submitting and reviewing CMS-855O applications. Nevertheless, we have (as explained earlier) revised § 424.510 to clarify which paragraphs in that section do not apply to individuals who enroll solely to order or certify items or services.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether a physician who completes the CMS-855O can elect to be a participating physician even though he or she is ordering services in the Medicare program.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A CMS-855O form cannot be used as a means of obtaining Medicare billing privileges. Medicare participation status does not apply in situations where the physician or non-physician practitioner enrolls solely for the purpose of ordering or certifying items or services. If the individual wishes to enroll in Medicare to furnish Medicare services, he or she must submit a CMS-855I application.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS identify whether any other federal or state health plan or any state Medicaid agency permits a physician or non-physician practitioner to obtain Medicare billing privileges for the sole purpose of ordering or certifying services for their members. The commenter was unaware of any other health plan that permits this.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         One cannot obtain Medicare billing privileges through any state health plan, state Medicaid agency, or federal health plan other than Medicare.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that on May 20, 2011, September 30, 2011, and April 14, 2012, CMS published a summary of the information collection for the CMS-855O in the 
                        <E T="04">Federal Register</E>
                        . The commenter noted that in each of these summaries, CMS stated that the CMS-855O permits a physician to receive a Medicare identification number (without being approved for billing privileges) for the sole purpose of ordering and referring beneficiaries to approved Medicare providers and suppliers. The commenter indicated further that CMS states, in the proposed rule on which the commenter is commenting, that the CMS-855O is exclusively designed to allow physicians and eligible professionals to enroll in Medicare solely to order or certify items or services. The commenter requested that CMS explain this apparent discrepancy. The commenter also requested CMS to outline how giving a physician or practitioner a Medicare billing number (which is already required to be the National Provider Identifier) is consistent with enrolling in the Medicare program. Another commenter questioned why the September 30, 2011 and April 14, 2012 notices refer to the registration of such individuals while our proposed rule refers to enrollment. This commenter also urged CMS to explain why it did not choose to solicit public comments on changes to regulatory provisions found in §§ 424.502 and 424.505 for almost 2 years after adopting and using the CMS-855O.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If the commenter is referring to the use of the term “order or certify” in lieu of the term “order or refer,” we replaced “refer” with “certify” because, as explained in the April 27, 2012 final rule: (1) A “certifying” provider generally means a person who orders/certifies home health services for a beneficiary, and (2) home health services fall within the purview of § 424.507.
                    </P>
                    <P>The Medicare number referenced in the three notices is not a “billing number” and is not intended to grant billing privileges to the individual; it instead serves as an identifier of the physician or non-physician practitioner. Likewise, our revisions to §§ 424.502 and 424.505 do not furnish billing privileges to an individual who is enrolling solely to order or certify items or services.</P>
                    <P>As explained earlier, our use of the term “registration” was intended to clarify the difference between enrolling in Medicare to obtain billing privileges and enrolling in Medicare solely to order or certify items and services.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested whether completion of another CMS-855O is required if the applicable physician or non-physician practitioner moves and opens a new practice in another contractor jurisdiction.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         At this time, a separate CMS-855O is required for each 
                        <PRTPAGE P="72505"/>
                        Medicare contractor jurisdiction in which the individual practices.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 1866(j) of the Act states that the Secretary shall establish by regulation a process for enrolling providers and suppliers; such process shall include, in part, a screening process. A commenter contended that CMS has violated section 1866(j) of the Act because our proposed rule does not establish a screening process for physicians and non-physician practitioners enrolling solely to order or certify items or services. The commenter recommended that CMS propose a moderate level of risk for such physicians and non-physician practitioners because CMS cannot link an order from such individual to the billing by a DMEPOS supplier, imaging facility, or clinical laboratory.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. The screening process implemented pursuant to section 1866(j) of the Act applies to all CMS-855 applications, including the CMS-855O. Regardless of which CMS-855 enrollment application is used, physician and non-physician practitioners are designated to the limited screening level pursuant to § 424.518(a)(1)(i), unless an adjustment applies under § 424.518(c)(3).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS provide the number of individuals enrolled or registered in the Medicare program using the CMS-855O since July 2011.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that contrary to the information found in the CMS-855O Privacy Act Notice, CMS has not updated the PECOS System of Records document to include the CMS-855O. The commenter recommended that CMS update the System of Records document No 09-70-0532 to reflect the collection and dissemination of information from the CMS-855O.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that permitting physicians who do not bill Medicare to order services for Medicare beneficiaries will likely increase Medicare fraud and the number of improper Medicare payments. The commenter recommended that CMS: (1) Explain how it will protect the Medicare Trust Funds from fraud when it cannot verify whether the physician actually conducted an exam or treated a Medicare beneficiary; and (2) require prior authorization for any service ordered by a physician or practitioner who does not have an associated claim for medical services; using prior authorization, the commenter believed, is the only way that Medicare can verify that a physician is treating a patient and not merely signing an order for services.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that in lieu of using the CMS-855O, CMS should exempt infrequent billers or physicians who see Medicare patients at a rural health clinic from deactivation for 3 or 5 years. This approach ensures that a physician can bill if he/she needs to, but reduces the amount of paperwork associated with an annual deactivation process. Another commenter offered several alternatives to the use of the CMS-855O: (1) A 1-year deactivation process for physicians who accept assignment and bill the Medicare program on a regular basis; (2) a 5-year deactivation process for physicians who bill Medicare as non-participating and only bill infrequently; and (3) an exception to the 1-year deactivation process for certain physicians—such as those listed on the CMS-855O—who bill the Medicare program infrequently.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These comments are outside the scope of this rule.
                    </P>
                    <P>After consideration of the comments received, we are finalizing the three proposed changes to §§ 424.502 and 424.505. We are also further modifying the definition of “enroll/enrollment” in § 424.502 and modifying § 424.510(a) as previously discussed.</P>
                    <HD SOURCE="HD3">2. Debts to Medicare</HD>
                    <P>Under § 424.530(a)(6), an application can be denied if “[t]he current owner (as defined in § 424.502), physician or non-physician practitioner has an existing overpayment at the time of filing of an enrollment application.” This provision was established in large part to address situations in which the owner of a provider or supplier incurs a substantial debt to Medicare, exits the Medicare program or shuts down operations altogether, and attempts to re-enroll through another vehicle or under a new business identity.</P>
                    <P>
                        As we explained in II.B.2. of the proposed rule, such situations were discussed in a November 2008 Department of Health and Human Services Office of Inspector General (OIG) Early Alert Memorandum entitled, “Payments to Medicare Suppliers and Home Health Agencies Associated with `Currently Not Collectible' Overpayments” (OEI-06-07-00080). The memorandum noted that anecdotal information from OIG investigators and assistant United States Attorneys indicated that DMEPOS suppliers with outstanding Medicare debts may inappropriately receive Medicare payments by, among other means, operating businesses that are publicly fronted by business associates, family members, or other individuals posing as owners.
                        <SU>1</SU>
                        <FTREF/>
                         In its study, the OIG selected a random sample of 10 DMEPOS suppliers in Texas that each had Medicare debt of at least $50,000 deemed currently not collectible (CNC) by CMS during 2005 and 2006.
                        <SU>2</SU>
                        <FTREF/>
                         The OIG found that 6 of the 10 reviewed DMEPOS suppliers were associated with 15 other DMEPOS suppliers or HHAs that received Medicare payments totaling $58 million during 2002 through 2007.
                        <SU>3</SU>
                        <FTREF/>
                         The OIG also found that most of the reviewed DMEPOS suppliers were connected with their associated DMEPOS suppliers and HHAs through shared owners or managers.
                        <SU>4</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Department of Health and Human Services, Office of Inspector General (OIG). “Early Alert Memorandum: Payments to Medicare Suppliers and Home Health Agencies Associated with `Currently Not Collectible' Overpayments (OEI-06-07-00080),” November 26, 2008, p.1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Ibid. p.1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Ibid. p.7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             Ibid. p.2.
                        </P>
                    </FTNT>
                    <P>We have continued to receive reports of providers, suppliers, and owners thereof accumulating large Medicare debts, departing Medicare, and then attempting to reenter the program through other channels—often to incur additional debts. While our current authority to deny based on § 424.530(a)(6) enables us to stem this practice to a certain extent, it is limited to situations where an enrolling physician, non-physician practitioner, or an owner of the enrolling provider or supplier has a current Medicare overpayment. It does not apply to instances where an enrolling provider or supplier entity has a current Medicare debt, be it an overpayment or some other type of financial obligation to the Medicare program. Furthermore, it does not address cases where an entity with which the enrolling provider, supplier, or owner was affiliated had incurred the debt. We believed that these latter situations were of particular concern to the OIG in the 2008 memorandum. Therefore, we proposed several changes to § 424.530(a)(6).</P>
                    <P>
                        First, we proposed to incorporate the existing language of § 424.530(a)(6) into a new paragraph (a)(6)(i) that would apply to all enrolling providers, suppliers (including physicians and non-physician practitioners), and owners thereof. We stated that we did not believe (a)(6) should be limited to individual physicians and non-physician practitioners. All providers and suppliers, regardless of type, are 
                        <PRTPAGE P="72506"/>
                        responsible for reimbursing Medicare for any debts they owe to the program. Permitting them to enroll additional provider or supplier sites in Medicare when they have existing debts to Medicare potentially endangers the Trust Funds. If the provider or supplier cannot repay its existing Medicare debts, this raises questions about its ability to pay future debts incurred as part of any additional enrollments.
                    </P>
                    <P>We proposed that a denial of Medicare enrollment under paragraph (a)(6)(i) could be avoided if the enrolling provider, supplier, or owner thereof satisfied the criteria set forth in § 401.607 and agreed to an extended CMS-approved repayment schedule for the entire outstanding Medicare debt; agreement to such a schedule would indicate that the provider, supplier, or owner is not seeking to avoid its debts to Medicare. The provider, supplier, or owner thereof could also avoid denial by repaying the debt in full. We also solicited comment on whether the scope of our proposed revision to § 424.530(a)(6)(i) should be expanded to include the enrolling provider or supplier's managing employees (as that term is defined in § 424.502), corporate officers, corporate directors, and/or board members.</P>
                    <P>Second, we proposed to replace the term “overpayment,” as it is currently used in § 424.530(a)(6), with “Medicare debt” in our regulatory text. We noted that “overpayment” more appropriately describes the types of debts that are subject to (a)(6). We also stated that our denial authority under proposed (a)(6) should include all forms of debt to Medicare, not just overpayments. We solicited comments on this proposed change as well as on the appropriate scope of the term “Medicare debt” for purposes of § 424.530(a)(6).</P>
                    <P>Third, we proposed to add a new paragraph (ii) to § 424.530(a)(6) permitting a denial of Medicare enrollment if the provider, supplier, or current owner (as defined in § 424.502) thereof was the owner (as defined in § 424.502) of a provider or supplier that had a Medicare debt that existed when the latter's enrollment was voluntarily or involuntarily terminated or revoked, and the following criteria are met:</P>
                    <P>• The owner left the provider or supplier that had the Medicare debt within 1 year of that provider or supplier's voluntary termination, involuntary termination, or revocation.</P>
                    <P>• The Medicare debt has not been fully repaid.</P>
                    <P>• We determine that the uncollected debt poses an undue risk of fraud, waste, or abuse.</P>
                    <P>Similar to proposed § 424.530(a)(6)(i), we proposed in § 424.530(a)(6)(iii) that the enrolling provider or supplier would be able to avoid a denial under § 424.530 (a)(6) if the enrolling provider, supplier, or owner thereof satisfies the criteria set forth in § 401.607 and agrees to an extended repayment schedule for the entire outstanding Medicare debt of the revoked provider or supplier. We noted our belief that this provision is warranted because agreement to a repayment plan evidences an intention to pay back the debt. We also proposed in § 424.530(a)(6)(iii) that no denial would occur under paragraph (a)(6)(ii) if the debt was repaid in full.</P>
                    <P>We explained that the difference between our proposed § 424.530(a)(6)(ii) and the existing language in § 424.530(a)(6) was that the latter involved situations in which the current owner, physician or non-physician practitioner had a Medicare debt. Section 424.530(a)(6)(ii), on the other hand, would focus on the entity with which the enrolling provider, supplier, or owner thereof had a prior relationship. That is, the “prior entity” had a debt to Medicare rather than the enrolling provider, supplier, or owner thereof. We offered the following illustration: Provider X is applying for enrollment in Medicare. Y owns 50 percent of X. Y was also a 20 percent owner of Supplier Entity Z, which was revoked from Medicare 12 months ago and currently has a large outstanding Medicare debt. The current version of § 424.530(a)(6) could not be used to deny X's application because X's current owner (Y) does not have a Medicare debt. Rather, the entity with which Y was affiliated (Z) has the debt. However, under proposed § 424.530(a)(6)(ii), and assuming the other criteria are met, X's application could be denied because X's owner was an owner of a supplier (Z) that has a Medicare debt. We cited section 1866(j)(5) of the Act, codified at 42 U.S.C. 1395cc(j)(5) and which was established by section 6401(a)(3) of the Affordable Care Act, as authority for proposed paragraph (ii).</P>
                    <P>We proposed the following as factors we would consider in determining whether an “undue risk” exists under paragraph (ii): (1) The amount of the Medicare debt; (2) the length and timeframe that the enrolling provider, supplier, or owner thereof was an owner of the prior entity; and (3) the percentage of the enrolling provider's, supplier's, or owner's ownership of the prior entity. We also noted that the scope and breadth of ownership interests would vary widely (for example, the amount of ownership; direct versus indirect ownership). For this reason, we believed it was important that CMS have the flexibility to make enrollment decisions under § 424.530(a)(6)(ii) on a case-by-case basis, using the factors previously outlined. However, we also solicited comment on the following issues related to these factors:</P>
                    <P>• Whether additional factors should be considered and, if so, what those factors should be.</P>
                    <P>• Which, if any, of the proposed factors should not be considered.</P>
                    <P>• Which, if any, factors should be given greater or lesser weight than others.</P>
                    <P>• Whether a minimum or maximum threshold for consideration should be established for the “amount of Medicare debt” and “percentage of ownership” factors.</P>
                    <P>We also solicited comments on whether paragraph (ii) should apply to the enrolling entity's managing employees (as that term is defined in § 424.502), corporate officers, corporate directors, and/or board members.</P>
                    <P>Many of the comments we received regarding our proposed changes to § 424.530(a)(6) were applicable to two or more of the proposals. Hence, we have summarized and collectively listed all of the comments we received on § 424.530(a)(6). Our responses to these comments are as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported CMS's proposal to use the term “Medicare debt” instead of “overpayment” for the reasons specified in the proposed rule, with one commenter stating that the term “overpayment” has long seemed inaccurate and, at times, confusing to Medicare physicians. One commenter, encouraged CMS to more thoroughly define “Medicare debt.” Another commenter recommended that the term “Medicare debt” be interpreted liberally.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support for our proposed change. We did not propose a definition of “Medicare debt” and do not do so in this final rule; rather, we had sought comments on the appropriate scope of the term for purposes of applying § 424.530(a)(6).
                    </P>
                    <P>
                        With respect to § 424.530(a)(6)(i) and (ii), we agree that the term “Medicare debt” should be interpreted broadly. An existing Medicare liability, simply put, is an unpaid Medicare debt. As such, an existing debt to the Medicare program—regardless of its type, or how the debt was incurred or discovered—may result in the denial of Medicare enrollment under § 424.530(a)(6). The only exceptions to this would be the 
                        <PRTPAGE P="72507"/>
                        situations described in proposed § 424.530(a)(6)(iii) regarding: (1) The satisfaction of the criteria set forth in § 401.607 and the agreement to an extended repayment schedule for the entire outstanding Medicare debt; or (2) the repayment of the debt in full. We are finalizing these two exceptions.
                    </P>
                    <P>We do not believe that specific types of Medicare debt should be articulated in the text of § 424.530(a)(6). Since the particular facts of each case will differ, we must retain the flexibility to address a variety of situations. We also note that our denial authority under § 424.530(a)(6) is discretionary, and there may be instances when a denial under § 424.530(a)(6) might not be warranted. For instance, under § 424.530(a)(6)(ii), our determination as to whether the debt poses an undue risk to the Medicare program will include consideration of the three factors we proposed: (1) The amount of the Medicare debt; (2) the length and timeframe of the ownership interest; and (3) the percentage of ownership interest—as well as two additional factors that we discuss in more detail later in this section—specifically; (4) whether the Medicare debt is currently being appealed; and (5) whether the provider was an owner when the debt was incurred. (These factors will be added at § 424.530(a)(6)(ii)(C).) We will make all final determinations regarding § 424.530(a)(6)(i) and (ii), and may conclude after reviewing the relevant factors that a particular denial under § 424.530(a)(6)(i) is unwarranted.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that CMS limit the term “Medicare debt” to those debts that have undergone and completed the CMS appeals process and final administrative adjudication; the commenter specifically requested that the phrase “after final administration adjudication” be inserted into a definition of “Medicare debt.” Otherwise, the commenter stated, honest and legitimate providers and suppliers could be prohibited from expanding or selling their practices based upon a single claim determination.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have added at § 424.530(a)(6)(ii)(C)(4) the appeal status of the debt as a factor in the determination of whether the debt poses an undue risk to Medicare. However, we are not wholly excluding debts that are being appealed from § 424.530(a)(6)'s application for two reasons. First, a provider or supplier with a Medicare debt (particularly a large debt) that poses an undue risk to the Medicare program should not be given an automatic opportunity to incur future debts with additional Medicare billing privileges simply because the debt is being appealed. Second, permitting providers and suppliers to obtain additional Medicare billing privileges if a Medicare debt is being appealed may encourage providers and suppliers to file meritless appeals simply to avoid and circumvent the application of § 424.530(a)(6)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that an expansion of the word “overpayment” to the word “debt” could lead to inequitable results, such as denials due to debts stemming from—(1) coordination of benefits issues with secondary payers; and (2) meaningful use audits. The commenter urged CMS to strictly narrow the scope of whatever term it finalizes to ensure that physicians do not unreasonably experience enrollment denials.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As alluded to earlier, we believe that any type of Medicare debt—regardless of how it was incurred or discovered—is of concern to us. It is for this reason that we are not excluding particular types of debts (such as those to which the commenter refers) from § 424.530(a)(6)'s scope. Nevertheless, we do not believe that our intended use of the term “Medicare debt” will lead to inequitable results, for we will only exercise our discretion under § 424.530(a)(6) in a careful and consistent manner.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters did not support expanding § 424.530(a)(6)'s purview to include the enrolling entity's current managing employees, corporate officers, directors, or board members. They contended that such an expansion would be excessively broad and unnecessarily complicated.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree that such an expansion would be overly broad and complex. To nonetheless ensure that we can focus on the implementation of our revisions to § 424.530(a)(6), we have decided not to include the enrolling entity's current managing employees, corporate officers, directors, or board members within the scope of § 424.530(a)(6) at this time, although we may consider doing so via future rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed general support for our proposed § 424.530(a)(6)(ii) and stated that CMS identified the appropriate factors to consider in this respect. However, the commenter did: (1) Suggest that CMS also adopt as a factor whether or not the person was an owner at the time the debt was incurred; and (2) urge CMS to exercise its discretion regarding § 424.530(a)(6)(ii) fairly and carefully; the commenter, citing an example, argued that a 5 percent owner for 6 months should not be penalized to the same extent as someone who has been a 50 percent owner for 5 years.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support and, as stated, will apply § 424.530(a)(6)(ii) in a fair and careful manner. We also agree with the commenter's suggestion to include as a factor the party's ownership status at the time the debt was incurred. We have added this as a factor at § 424.530(a)(6)(C)(5), although a finding that the party was not an owner when the debt was incurred will not in and of itself result in § 424.530(a)(6)(ii)'s non-application. All factors and particular circumstances will be considered before a denial under § 424.530(a)(6)(ii) is imposed.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that a physician group may not be aware that an individual physician has unpaid Medicare debt related to previous affiliations. The commenter urged CMS to make such information available in an accessible database.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we understand the commenter's concern, it is ultimately the hiring provider or supplier's responsibility to perform a thorough review of the physician's background, including his or her prior affiliations. We do not believe that such a review should be dependent upon the creation of a publicly available database.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter disagreed with our proposal to add § 424.530(a)(6)(ii), contending that CMS did not explain why it—(1) needs this new authority; and (2) cannot collect a debt through the Federal Payment Levy Program. The commenter also requested CMS to explain why it did not propose revoking existing providers and suppliers that have Medicare overpayments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our rationale for the proposed addition of § 424.530(a)(6)(ii) was contained in the preamble of the proposed rule and is restated earlier in this final rule. While we are aware of the authority furnished by the Federal Payment Levy Program, the issue is not merely the collection of existing Medicare debts; it is also the need to prevent the accumulation of additional Medicare debts. We believe that our denial authority under § 424.530(a)(6)(ii) will be an important step in this direction.
                    </P>
                    <P>
                        We did not propose to incorporate a new revocation reason regarding Medicare debts that would apply to currently enrolled providers (for example, via revalidation), for this is a different situation than what is being described here. However, we may consider establishing such a revocation reason via future rulemaking.
                        <PRTPAGE P="72508"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported the denial of enrollment of providers and suppliers that have existing Medicare debts that have not been fully repaid or if the provider or supplier is not current in its existing repayment schedule. Yet the commenter urged CMS to exclude from § 424.530(a)(6)'s purview debts that: (1) Are currently within a CMS-approved appeals process; and (2) have not been forgiven by CMS due to financial considerations. Other commenters, too, suggested that debts that are currently being appealed or are part of an extended repayment plan should be exempt from § 424.530(a)(6)'s application. With respect to appeals, one commenter contended that the Congress' passage of section 935 of the Medicare Modernization Act (MMA) envisioned a congressional intent to permit physicians to delay repaying an overpayment pending the completion of the appeals process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As explained earlier, we will consider a debt's appeal status in our determination of whether the debt poses an undue risk to the Medicare program under § 424.530(a)(6)(ii). In addition, we will exclude from § 424.530(a)(6)(i) and (ii) those situations where the enrolling provider, supplier, or owner thereof meets the criteria of § 401.607 and agrees to an extended repayment schedule for the entire outstanding Medicare debt. While we are unclear as to the commenter's suggestion that debts that CMS has not forgiven due to financial considerations be excluded from our § 424.530(a)(6) determinations, we can assure the commenter that we will apply § 424.530(a)(6)(i) and (ii) in a careful and judicious manner.
                    </P>
                    <P>We do not believe that our revisions to § 424.530(a)(6) are inconsistent with section 935 of the MMA. Our provisions address enrollment denials, not recoupment. Nothing in § 424.530(a)(6) requires a provider to repay an overpayment prior to the completion of the appeals process.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters opposed our proposed § 424.530(a)(6)(ii), contending that the provision would potentially punish persons and entities who: (1) Were not responsible for the debt; or (2) had only a very limited association with the party that was responsible for the debt. One commenter noted that our proposed criteria for denying enrollment under § 424.530(a)(6)(ii) did not take into account whether the enrolling provider or supplier is actually responsible for the debt. Another commenter contended that our proposal is overreaching and exhibits a lack of understanding of the complexities of the new coordinated care models that are evolving pursuant to payment and delivery reform advanced by the Affordable Care Act. The commenter stated that denials under our proposed provision could be frequent because many of today's systems of health care are diverse, geographically large, and encompass numerous entities and groups.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are adopting as a factor in our § 424.530(a)(6)(ii) determinations whether or not the person was an owner at the time the debt was incurred. In addition, we will only deny a Medicare application under § 424.530(a)(6)(ii) after careful review of all the factors associated with a particular situation. We believe these actions may alleviate to some extent the commenters' concerns about § 424.530(a)(6)(ii)'s application.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS furnish evidence that the problem of suppliers departing Medicare with large, unpaid overpayments and then re-enrolling in Medicare exists with respect to physicians and group practices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As explained in the proposed rule and earlier in this final rule, the OIG's November 2008 Early Alert Memorandum titled “Payments to Medicare Suppliers and Home Health Agencies Associated with `Currently Not Collectible' Overpayments” (OEI-06-07-00080) cautioned that DMEPOS suppliers with outstanding Medicare debts may inappropriately receive Medicare payments by, among other means, operating businesses that are publicly fronted by business associates, family members, or other individuals posing as owners. We also noted our receipt of reports of providers, suppliers, and owners thereof accumulating large Medicare debts, departing Medicare, and then attempting to reenter the program through other channels.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern with CMS's publication of Transmittal 469, which operationalizes the current version of § 424.530(a)(6). The commenter contended that CMS did not abide by the Administrative Procedure Act (APA) in issuing Transmittal 469 because it did not use the prescribed notice and public comment process. Another commenter urged CMS to retract Transmittal 469, contending that certain policies in the transmittal conflict with the contents of our proposed rule, thereby causing confusion in the provider community. Another commenter sought clarification as to how Transmittal 469 would interact with our proposed revisions to § 424.530(a)(6). As an example, the commenter stated that Transmittal 469 contained a $1,500 threshold—which the commenter believed was too low—yet the proposed rule contained no such threshold and does not define the scope of the overpayments that would be subject to our proposed provisions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The publication of Transmittal 469—which has since been rescinded and replaced by Transmittal 479—did not violate the APA. The current version of § 424.530(a)(6) was subject to public notice and comment prior to its enactment. Transmittal 479 adds guidance regarding existing § 424.530(a)(6) to chapter 15 of our Program Integrity Manual (CMS Pub. 100-08).
                    </P>
                    <P>Upon publication of this final rule, we will revise CMS Publication 100-08, chapter 15, to ensure that the guidance to our contractors and the public is consistent with our changes to § 424.530(a)(6).</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter offered several suggestions regarding our proposed changes to § 424.530(a)(6). First, the commenter recommended that CMS exclude from § 424.530(a)(6)'s scope those debts resulting from contractor error or from retroactive changes made by CMS or the Congress. Second, the commenter suggested that CMS establish a debt monetary threshold below which § 424.530(a)(6) would not apply; the commenter cited the $1,500 threshold set forth in the aforementioned Transmittal 469 as an example. Third, the commenter suggested that CMS establish an ownership percentage threshold below which § 424.530(a)(6) would not apply; the commenter recommended 20 percent. The commenter stated that such thresholds would foster consistency and assist CMS's efforts to curb fraud and abuse without unnecessarily burdening providers and suppliers that have small debts.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We mentioned earlier that the amount of the debt and the percentage of ownership will be factors in our § 424.530(a)(6)(ii) determinations, although specific thresholds will not be established due to the need to maintain flexibility to address various situations. In terms of contractor errors, we will be including the debt's appeal status as another factor.
                    </P>
                    <P>We are not adding retroactive changes as a factor because we are unclear as to the types of situations to which the commenter is referring.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS identify the enrollment applications and types of enrollment changes that would be impacted by our proposed revisions to § 424.530(a)(6).
                        <PRTPAGE P="72509"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Initial CMS-855 applications are the only applications subject to § 424.530(a)(6).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for our proposed revisions to § 424.530(a)(6), stating that this will lead to increased scrutiny of the ownership and leadership of provider and supplier organizations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that our proposed § 424.530(a)(6) exceeds the statutory authority granted to the Secretary in 42 U.S.C. 1395cc(j)(5), which provides that the Secretary may deny an application based on a disclosure of a current or previous affiliation, subject to a finding of “undue risk.” At a minimum, the commenter recommended, CMS should revise the proposed regulatory text to: (1) Include the criteria for a finding of undue risk as described in the proposed rule's preamble; and (2) state that a denial of enrollment “may be warranted,” rather than “is warranted”.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter's first recommendation and will revise the regulatory text accordingly. We note that the second recommendation is moot because the regulatory text does not contain the phrase “is warranted.”
                    </P>
                    <P>We disagree with the assertion that our changes to § 424.530(a)(6) exceed our statutory authority. Our expansion of § 424.530(a)(6)(i)—the existing version of which has been in effect since 2009—and our addition of § 424.530(a)(6)(ii) are consistent with the authority in section 1866(j)(1) and (5) of the Act (42 U.S.C. 1395cc(j)(1) and (5)). It is also consistent with our general rulemaking authority in sections 1102 and 1871 of the Act.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported CMS's proposal to extend § 424.530(a)(6)(i) to other provider and supplier entities. The commenter stated that since physicians are in the “limited” screening level in § 424.518(a), it is sensible to include higher risk providers and suppliers in that category as well.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS proposed § 424.530(a)(6)(ii) is based on a false premise that any uncollected debt poses an undue risk of fraud, waste or abuse and does not take into consideration the due process rights that should be afforded to providers through the appeals process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that every uncollected debt poses an undue risk of fraud, waste or abuse. As we stated in the proposed rule, we will make an individual determination—based on the factors set forth at § 424.530(a)(6)(ii)(C)—as to whether the debt in question poses an undue risk. If the debt, after our analysis, does not present such a risk, we will not deny the enrollment application under § 424.530(a)(6)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that certain DMEPOS suppliers are subject to a $50,000 bond requirement. As such, there is an existing avenue—outside of denying enrollment—to address CMS's concerns regarding uncollected debts.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Though it is true that certain DMEPOS suppliers must obtain a surety bond in order to enroll in Medicare, there are at least 1.4 million other Medicare providers and suppliers that do not. Moreover, the presence of a surety bond does not in itself guarantee that the full amount of a Medicare debt will be recovered via the bond. Therefore, we need additional mechanisms—such as those we are finalizing with respect to § 424.530(a)(6)—to help ensure that Medicare debts are repaid and that providers and suppliers with unpaid debts do not incur additional Medicare debts through the establishment of additional enrollments.
                    </P>
                    <P>Given the comments received and the preceding discussion, we are finalizing our proposed revisions to § 424.530(a)(6), albeit with three revisions to § 424.530(a)(6)(ii)(C) and one change to § 424.530(a)(6)(iii):</P>
                    <P>• We are revising § 424.530(a)(6)(ii)(A) to state: “The owner left the provider or supplier with the Medicare debt within 1 year before or after that provider or supplier's voluntary termination, involuntary termination or revocation.” The insertion of “with” in lieu of “that had” and the insertion of “before or after” are merely intended to clarify our original intention that the 1-year period applies to separations occurring prior to or after the provider or supplier's termination or revocation.</P>
                    <P>• To § 424.530(a)(6)(ii)(C) will be added a second sentence that reads: “In making this determination, we consider the following factors:”</P>
                    <P>• New paragraphs (1) through (5) will be added to § 424.530(a)(6)(ii)(C) identifying these factors. The paragraphs state the following:</P>
                    <P>++ The amount of the Medicare debt.</P>
                    <P>++ The length and timeframe that the enrolling provider, supplier, or owner thereof was an owner of the prior entity.</P>
                    <P>++ The percentage of the enrolling provider's, supplier's, or owner's ownership of the prior entity.</P>
                    <P>++ Whether the Medicare debt is currently being appealed.</P>
                    <P>++ Whether the enrolling provider, supplier, or owner thereof was an owner of the prior entity at the time the Medicare debt was incurred.</P>
                    <P>• To ensure consistency in application, in § 424.530(a)(6)(iii) we are combining proposed paragraphs (A) and (B)(1) into a revised paragraph (A) that will read as follows: “(1) Satisfies the criteria set forth in § 401.607; and (2) agrees to a CMS-approved extended repayment schedule for the entire outstanding Medicare debt.” Proposed paragraph (B)(2) will be redesignated as new paragraph (B) and will read as follows: “Repays the debt in full.”</P>
                    <HD SOURCE="HD3">3. Felony Convictions</HD>
                    <P>Under § 424.530(a)(3) and § 424.535(a)(3), respectively, a provider or supplier's Medicare enrollment may be denied or revoked if the provider or supplier—or any owner of the provider or supplier—has, within the 10 years preceding enrollment or revalidation of enrollment, been convicted of a federal or state felony offense that CMS has determined to be detrimental to the best interests of the Medicare program and its beneficiaries. Under § 424.535(a)(3)(i), as currently codified, such offenses include the following:</P>
                    <P>• Felony crimes against persons; such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>• Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>• Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                    <P>• Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.</P>
                    <P>(Section 424.530(a)(3)(i) mirrors § 424.535(a)(3)(i) with the exception of paragraph (D), which uses the phrase: “Any felonies outlined in section 1128 of the Act.”)</P>
                    <P>We proposed several changes to §§ 424.530(a)(3) and 424.535(a)(3).</P>
                    <P>
                        First, we proposed to modify the list of felonies in each section such that any felony conviction that we determine to be detrimental to the best interests of the Medicare program and its beneficiaries would constitute a basis for denial or revocation. We stated that considering the very serious nature of any felony conviction, our authority in §§ 424.530(a)(3)(i) and 424.535(a)(3)(i) should not be restricted to the categories 
                        <PRTPAGE P="72510"/>
                        of felonies identified in (a)(3)(i); this was especially true considering that the types of felony offenses often vary from state to state.
                    </P>
                    <P>Second, we proposed to expand §§ 424.530(a)(3) and 424.535(a)(3) to include felony convictions against a provider or supplier's “managing employee,” as that term is defined in § 424.502. Since certain managing employees of a provider or supplier may have as much (if not more) day-to-day control as an owner, we explained that managing employees should be held to the same standard as owners.</P>
                    <P>Third, we proposed to revise the language “within the 10 years preceding enrollment or revalidation of enrollment” in § 424.530(a)(3) and § 424.535(a)(3) to “within the preceding 10 years.” The existing language has caused confusion as to how the 10-year period is calculated. We believe that our revised wording clarifies this timeframe.</P>
                    <P>Fourth, we proposed to clarify in §§ 424.530(a)(3) and 424.535(a)(3) that the term “convicted”—as used in these two sections—has the same definition as the one set forth in 42 CFR 1001.2. This was intended to address the numerous inquiries we have received regarding the proper interpretation of the term “convicted” as it relates to §§ 424.530(a)(3) and 424.535(a)(3).</P>
                    <P>The following is a summary of the comments received regarding these four proposed changes and our responses thereto.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter urged CMS to retain the current language in §§ 424.530(a)(3) and 424.535(a)(3) that states that CMS will consider the severity of the underlying offense before denying or revoking enrollment. The commenter contended that while some felony convictions may bear directly on a provider's ability to care for patients, other convictions may be irrelevant to patient care—especially those that may be as many as 10 years old. In all instances, the commenter added, CMS should employ its denial and revocation authority under §§ 424.530(a)(3) and 424.535(a)(3) judiciously and should use a reasonableness standard in making such determinations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Regardless of whether the “severity of the underlying offense” language is present in §§ 424.530(a)(3) and 424.535(a)(3), we have always considered—and will continue to do so—the seriousness of the offense in determining whether a denial or revocation is warranted under §§ 424.530(a)(3) and 424.535(a)(3). Therefore, we do not believe that including the “severity” verbiage in §§ 424.530(a)(3) and 424.535(a)(3) is necessary, for CMS already takes this factor into account in such determinations.
                    </P>
                    <P>Although we did propose to expand the categories of felonies that can serve as the basis of a denial or revocation, we are not suggesting that every felony conviction will automatically result in such an action. Each case will be carefully reviewed on its own merits and, as the commenter recommends, we will act judiciously and with reasonableness in our determinations.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters disagreed with CMS's proposed expansion of §§ 424.530(a)(3) and 424.535(a)(3) to include all felonies. They contended that (1) our proposal is arbitrary and an abuse of discretion; and (2) CMS offered no facts to support its proposal. One commenter stated that some felonies—such as those related to drugs, alcohol, or traffic violations—could not reasonably be considered as detrimental to the Medicare program, yet CMS would have the discretion to deny or revoke a provider for such a felony. This could lead to unfair results, particularly if a sentence of less than 3 years (which is the maximum re-enrollment bar period) is imposed. The commenter—as well as several other commenters—requested that CMS reconsider its proposal and: (1) Furnish a definition of “detrimental to the Medicare program or its beneficiaries;” and (2) exclude felonies related to drugs, alcohol, or traffic violations from the scope of §§ 424.530(a)(3) and 424.535(a)(3).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree that our proposal was arbitrary or an abuse of discretion. Section 4302 of the Balanced Budget Act (BBA) amended section 1866 of the Act to furnish CMS with broad authority to refuse to enter into Medicare agreements with individuals or entities convicted of felonies that the Secretary determines to be detrimental to the best interests of the program or program beneficiaries. We identified in the proposed rule the legal grounds for all of our proposed enrollment provisions and explained the policy rationale for each of them. For instance, we indicated the need for flexibility with respect to the application of §§ 424.530(a)(3)(i) and 424.535(a)(3)(i) when considering that categories of felony offenses often vary from state to state. We do not believe that felonies relating to drugs, alcohol, or traffic violations cannot be detrimental to the best interests of Medicare beneficiaries, and thus should be automatically excluded from the purview of §§ 424.530(a)(3) and 424.535(a)(3). While certain felonies carry different, potentially more severe penalties than others, each case is distinct and state law classifications of certain criminal actions can vary widely. Therefore, we must maintain the flexibility to address all potential situations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported our proposed expansion of §§ 424.530(a)(3) and 424.535(a)(3), believing it was a step forward in CMS's attempts to prevent Medicare fraud on the front end.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether CMS will revoke the Medicare billing privileges of a physician who is convicted of a non-violent firearm felony.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The determination of whether a particular conviction will or will not result in the revocation or denial of Medicare enrollment will depend upon the specific facts of each individual situation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that CMS will deny or revoke billing privileges under § 424.530(a)(3) or § 424.535(a)(3), respectively, such that a physician's right to participate in the Medicaid program will be affected.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter correctly notes that under § 455.416(c), a State Medicaid agency must deny enrollment or terminate the enrollment of any provider whose Medicare enrollment is revoked for cause, although there is no corresponding requirement in cases where a provider is denied enrollment in the Medicare program. As noted previously, we will only exercise our authority under § 424.530(a)(3) or § 424.535(a)(3) after consideration of the relative seriousness of the underlying offense and all of the circumstances surrounding the conviction.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that our proposed expansions of §§ 424.530(a)(3) and 424.535(a)(3) violate the principles of federalism established in Executive Order 13132 3(b), 3(c) and 3(d) and diminishes the role of state licensing boards across the country. The commenter requested that CMS furnish justification for expanding the role of the federal government into matters best resolved by state licensing boards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. As mentioned earlier, section 4302 of the BBA (which amended section 1866 of the Act) gave CMS broad authority to refuse to enter into Medicare agreements with individuals or entities convicted of felonies that the Secretary determines to be detrimental to the best interests of the program or program beneficiaries. Additionally, our changes to §§ 424.530(a)(3) and 424.535(a)(3) in no way impair or infringe upon a state 
                        <PRTPAGE P="72511"/>
                        licensing agency's ability to take or not take action on a provider's licensure status in the event of a criminal conviction. Such a decision will—as it should—remain within the purview of the state.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should not deny or revoke a supplier's enrollment based on § 424.530(a)(3) or § 424.535(a)(3) if the supplier made a good-faith effort—using generally accepted employee screening and hiring practices—to ensure that an employee did not have a felony conviction. The commenter added, if CMS desires comprehensive screening for felony convictions, it should work with other government agencies to develop a nationwide database so that employers have one reliable source from which to screen their employees for felony convictions. The commenter further stated that recent enforcement actions by the United States Equal Employment Opportunity Commission (EEOC) have targeted companies for alleged discrimination against minority applicants based on policies to exclude people from employment based on a criminal record. CMS's revisions to §§ 424.530(a)(3) and 424.535(a)(3) should be reconciled with the EEOC's current enforcement position.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. The core issue is not whether the organization made a good-faith effort to determine whether a current or prospective owner or managing employee has a felony conviction. Rather, it is whether the owner or managing employee has such a conviction and whether the conviction poses a risk to the Medicare program or its beneficiaries. In other words, it is the felony conviction itself—not whether the organization screened for such convictions—that is the relevant matter. We note that there are many resources available to help organizations ascertain one's criminal background history; a CMS-initiated project to establish a single, all-encompassing felony database for the use of employers is not necessary. We further add that CMS is not requiring, through its expansion of § 424.530(a)(3) and § 424.535(a)(3), that providers and suppliers perform criminal background checks of their current or prospective owners or managing employees as part of the enrollment process.
                    </P>
                    <P>We do not believe that the EEOC's recent enforcement actions mandate that prospective employers discourage taking into account a prospective employee's criminal background history. Our principal focus in this rule is to protect the Medicare program from individuals and entities that could threaten its integrity, and we believe our expansion of §§ 424.530(a)(3) and 424.535(a)(3) is an important step towards this end.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that providers seeking to hire physicians or managing employees must have clear rules as to the types of felonies that CMS would consider detrimental to the Medicare program. The commenter favored retaining the current versions of §§ 424.530(a)(3) and 424.535(a)(3) because CMS identifies specific felonies that fall within the scope of these two provisions. If, the commenter added, CMS seeks to include additional categories of felonies, it should use the formal rulemaking process to propose these new categories and allow the public to comment. Another commenter stated that our proposed revisions to §§ 424.530(a)(3) and 424.535(a)(3) fail to provide adequate notice of the types of felony convictions that may lead to a denial or revocation of Medicare enrollment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In light of the differences in state laws, it would be impossible to identify in our revised §§ 424.530(a)(3) and 424.535(a)(3) every felony offense that could result in a denial or revocation; indeed, if we accepted the commenter's suggestion, hundreds of crimes—perhaps even identified on a state-by-state basis—might have to be listed. Nevertheless, we agree that retaining the lists of felonies in the current versions of §§ 424.530(a)(3) and 424.535(a)(3) could prove helpful in identifying for the public some of the felonies that may serve as a basis for denial or revocation, respectively. Therefore, we are combining our proposed revisions to §§ 424.530(a)(3) and 424.535(a)(3) with the existing language in both provisions.
                    </P>
                    <P>Section 424.530(a)(3) will state that the provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a Federal or State felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries. Offenses include, but are not limited in scope or severity to—</P>
                    <P>++ Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                    <P>++ Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.”</P>
                    <P>Section 424.535(a)(3) will state that the provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a federal or state felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries. Offenses include, but are not limited in scope or severity to—</P>
                    <P>++ Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                    <P>++ Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.</P>
                    <P>(Revocations based on felony convictions are for a period to be determined by the Secretary, but not less than 10 years from the date of conviction if the individual has been convicted on one previous occasion for one or more offenses.)</P>
                    <P>
                        Note that the previous revisions contain two important changes. First, the current language in §§ 424.530(a)(3) and 424.535(a)(3) refers to a felony offense that CMS “
                        <E T="03">has determined</E>
                         to be detrimental to the best interests of the program and its beneficiaries.” (Emphasis added.) Consistent with our proposed revisions to §§ 424.530(a)(3) and 424.535(a)(3), we are revising this language to include any felony offense that CMS “
                        <E T="03">determines</E>
                         is detrimental to the best interests of the Medicare program and its beneficiaries.” (Emphasis added.) This distinction is important. The phrase “has determined” incorrectly implies that the only felonies that may serve as a basis for denial or revocation are those specifically listed in §§ 424.530(a)(3) and 424.535(a)(3). We believe that the term “determines” makes clearer that the lists of felonies in these two provisions are not exhaustive and 
                        <PRTPAGE P="72512"/>
                        include other felonies that CMS may deem as meeting the “detrimental” standard based on the particular facts of the case. Second, and to further emphasize CMS' discretion to use felonies other than those specified in §§ 424.530(a)(3) and 424.535(a)(3) as grounds for denial or revocation, we have included the phrase “but are not limited in scope or severity” within both provisions.
                    </P>
                    <P>However, notwithstanding these changes, we again stress that we will only exercise our authority under §§ 424.530(a)(3) and 424.535(a)(3) after very careful consideration of the relative seriousness of the underlying offense and all of the circumstances surrounding the conviction. It should in no way be assumed that every felony conviction will automatically result in a denial or revocation.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that in proposing its expansion of §§ 424.530(a)(3) and 424.535(a)(3) to include all felonies, CMS did not comply with section 1(b)(7) of Executive Order 12866 and base its proposal on reasonably obtainable scientific, technical and other information. The commenter recommended that CMS identify the specific felony reasons in a new proposed rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that our proposed changes to §§ 424.530(a)(3) and 424.535(a)(3) violated section 1(b)(7) of Executive Order 12866. To the contrary, the changes were based on a careful consideration of the need to ensure that individuals and entities convicted of a felony offense that is detrimental to the best interests of the Medicare program and its beneficiaries are kept out of the Medicare program. For the reasons previously stated, we believe it is neither feasible nor practical to identify every conceivable felony offense that could result in the application of §§ 424.530(a)(3) or 424.535(a)(3).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS establish protections, such as a knowledge threshold, for suppliers that perform reasonable due diligence to determine if a potential employee has a felony record. The commenter stated that CMS should work with suppliers that act in good-faith to determine if a prospective employee has a felony record rather than automatically excluding a supplier. The commenter specifically suggested adding language to §§ 424.530(a)(3) and 424.535(a)(3) that, in effect, would permit a denial or revocation only if: (1) The provider or supplier knew or should have known about the conviction; (2) the provider or supplier did not have industry standard hiring practices in place; (3) the provider or supplier has not submitted a corrective action plan; (4) the disruption to beneficiaries does not outweigh the provider or supplier's termination due to one individual; and (5) CMS has already established and implemented a comprehensive state and federal database that is available to providers and suppliers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter's suggestion. As stated earlier, it is the felony conviction itself and not the extent of the organization's efforts in performing a criminal background check that is the crucial consideration.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         To improve transparency—and since the OIG publicly posts information about individuals and entities excluded from federal health care programs—a commenter suggested that CMS post on its provider enrollment Web page the name and NPI (if applicable) of any person who has had his or her Medicare billing privileges denied or revoked based upon a felony conviction; the date of the denial or revocation and, if applicable, the length of the re-enrollment bar should be listed as well.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate this suggestion and may consider it in a future initiative to the extent it is consistent with the Privacy Act.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter was concerned that the expansion of the felonies encompassed by § 424.535(a)(3) would be applied to providers and suppliers whose recently submitted revalidation applications were approved. The commenter, in other words, opposed the retroactive application of our proposed § 424.535(a)(3).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our changes to § 424.535(a)(3) do not preclude CMS from reviewing the enrollment records of currently enrolled providers and suppliers to determine if the provider, supplier, or an owner or managing employee thereof has a felony conviction that CMS deems detrimental to the best interests of the Medicare program or its beneficiaries. However, we again stress that not every felony conviction will necessarily result in a denial or revocation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for our proposed revisions to §§ 424.530(a)(3) and 424.535(a)(3).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter agreed with CMS's proposal to clarify that the enrollment bar is for felony convictions “within the preceding 10 years” but suggested that the date be further clarified as “within the 10 years preceding the effective date of the enrollment application.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the commenter's support, we disagree with the commenter's suggestion because it would be difficult to use a future date—that is, a date that could be well after the date the application was submitted—as the 10-year cut-off point.
                    </P>
                    <P>After a careful consideration of the comments and in light of the previous discussion, we are revising §§ 424.530(a)(3) and 424.535(a)(3) as follows:</P>
                    <P>Section § 424.530(a)(3) will state that the provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a federal or state felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries. Offenses include, but are not limited in scope or severity to—</P>
                    <P>++ Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                    <P>++ Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.”</P>
                    <P>Section 424.535(a)(3) will state that the provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a federal or state felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries.</P>
                    <P>Offenses include, but are not limited in scope or severity to—</P>
                    <P>++ Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>++ Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                    <P>
                        ++ Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice 
                        <PRTPAGE P="72513"/>
                        suit that results in a conviction of criminal neglect or misconduct.
                    </P>
                    <P>++ Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.</P>
                    <P>Revocations based on felony convictions are for a period to be determined by the Secretary, but not less than 10 years from the date of conviction if the individual has been convicted on one previous occasion for one or more offenses.</P>
                    <HD SOURCE="HD3">4. Abuse of Billing Privileges</HD>
                    <P>Section 424.535(a)(8) currently states that a provider or supplier's Medicare billing privileges may be revoked if the provider or supplier submits a claim or claims for services that could not have been furnished to a specific individual on the date of service. These instances include, but are not limited to, situations where the beneficiary is deceased, the directing physician or beneficiary is not in the state or country when the service was provided, or when the equipment necessary for testing was not present where the testing is said to have occurred.</P>
                    <P>We proposed to expand this revocation reason by adding a new paragraph (a)(8)(ii) to § 424.535. The existing revocation reason would be incorporated into a new paragraph (a)(8)(i). Proposed new paragraph (a)(8)(ii) would permit revocation if we determine that the provider or supplier has a pattern or practice of billing for services that do not meet Medicare requirements such as, but not limited to, the requirement that the service be reasonable and necessary. We explained that a provider or supplier should be responsible for submitting valid claims at all times and that the provider or supplier's repeated failure to do so poses a risk to the Medicare Trust Funds. We note that the responsibility for submitting valid claims exists irrespective of whether the provider or supplier itself submits the claims or hires a billing agency to perform this function; in either case, the claims are submitted on behalf of the provider or supplier.</P>
                    <P>We solicited comment on what should qualify as a “pattern or practice” under our proposed change. We also proposed several factors we would take into account when determining whether a revocation under § 424.535(a)(8)(ii) is warranted including, but not limited to the following:</P>
                    <P>• The percentage of submitted claims that were denied.</P>
                    <P>• The total number of claims that were denied.</P>
                    <P>• The reason(s) for the claim denials.</P>
                    <P>• Whether the provider or supplier has any history of “final adverse actions” (as that term is defined in § 424.502).</P>
                    <P>• The length of time over which the pattern has continued.</P>
                    <P>• How long the provider or supplier has been enrolled in Medicare.</P>
                    <P>With respect to these factors, we solicited comment on the following:</P>
                    <P>• Whether additional factors should be considered and, if so, what those factors should be.</P>
                    <P>• Which, if any, of these factors should not be considered.</P>
                    <P>• Which, if any, of these factors should be given greater or lesser weight than others.</P>
                    <P>• Whether a minimum or maximum threshold for consideration should be established for the “percentage of claims denied” and “total number of claims denied” factors.</P>
                    <P>We further solicited comment on whether there should be a set knowledge standard associated with our proposed provision—for example, whether revocation is warranted only if the provider or supplier submitted the claims in question with “reckless disregard” as to their accuracy or the provider “knew or should have known” that the claims did not meet Medicare requirements.</P>
                    <P>The following is summary of the comments received regarding § 424.535(a)(8)(ii) and our responses thereto:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that it did not dispute CMS's right to revoke billing privileges if a Medicare provider has a pattern of billing for services that do not meet Medicare requirements. However, the commenter recommended that in applying any criteria regarding the number of claim denials, CMS should take into account the number of denials that were overturned on appeal. Several other commenters also stated that they did not object to CMS's proposal, but urged that results of the administrative appeals process be considered as a significant factor before CMS concludes that a provider has engaged in a “pattern or practice” of submitting improper claims. Other commenters stated that due process mandates that claim denials under appeal be excluded from any measurement that takes into account the number or percentage of denied claims. Another commenter questioned whether an appeal is considered to be successful when it is pursued up to and including the Administrative Law Judge (ALJ) level.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A provider or supplier's claim denial that has been both
                        <E T="03">—</E>
                        (1) fully (rather than partially) overturned on appeal; and (2) finally and fully adjudicated will be excluded from our consideration in determining whether the provider or supplier's Medicare billing privileges should be revoked under § 424.535(a)(8)(ii). This is because, for purposes of § 424.535(a)(8)(ii), the claim denial has been effectively negated. Yet we do not believe a claim denial that fails to meet both of these requirements should be excluded from our review for two reasons. First, excluding claims that are currently being appealed could encourage providers and suppliers to file meritless appeals simply to circumvent the application of § 424.535(a)(8)(ii). Second, merely because a claim is under appeal does not necessarily mean it will be overturned.
                    </P>
                    <P>For purposes of this claim denial exclusion, the term “finally and fully adjudicated” means that—(1) the appeals process has been exhausted; or (2) the deadline for filing an appeal has passed.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters opposed CMS's proposed § 424.535(a)(8)(ii). They stated that: (1) The proposal is arbitrary and subjective and grants too much discretion to CMS and its contractors; (2) CMS failed to include in its proposed rule a thorough discussion of the factors that would be used in making determinations related to § 424.535(a)(8)(ii); (3) did not define “pattern or practice”; and (4) there is nothing in the proposed rule that limits CMS's authority under § 424.535(a)(8)(ii). They added that despite CMS's statement in the proposed rule's preamble that it would not use this provision to revoke providers for isolated and sporadic claim denials or innocent billing errors, there are no safeguards to prohibit CMS or its multiple contractors from doing so. The commenters stated that given the complexity of Medicare's billing and coding rules and the frequency with which they change, Medicare providers would inevitably submit claims that fail to meet Medicare requirements though without any nefarious intent. They urged CMS to furnish appropriate, consistent, and clear guidelines regarding billing, coding, and payment policies before implementing § 424.535(a)(8)(ii). Other commenters stated that contractor errors, which can include a contractor's misinterpretation or misunderstanding of CMS requirements, sometimes result in claim denials.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that our proposal is arbitrary or grants CMS unlimited discretion. To the contrary, and as the commenters noted, we were 
                        <PRTPAGE P="72514"/>
                        very clear in the preamble of the proposed rule that sporadic billing errors would not result in revocation under § 424.535(a)(8)(ii). Although we did not define “pattern or practice” to maintain flexibility to address a variety of factual scenarios, we listed several factors that would be considered in our § 424.535(a)(8)(ii) determinations and requested feedback regarding other potential factors. Additionally, not only will CMS (rather than its contractors) make all such determinations, but also § 424.535(a)(8)(ii) will be applied only: (1) In situations where the behavior could not be considered sporadic; and (2) after the most careful and thorough consideration of the relevant factors. These points cannot be stressed enough.
                    </P>
                    <P>We recognize that Medicare has many rules and requirements regarding billing and coding, and that claims are occasionally submitted in error due to a provider's misunderstanding of these policies or denied incorrectly by the contractor. It is not CMS's intention to revoke billing privileges under § 424.535(a)(8)(ii) in such instances. However, Medicare billing privileges come with a responsibility for the provider to diligently seek and obtain clarification of Medicare policies should there be a misunderstanding or confusion. Constant, repeated, and systemic claim denials (as opposed to sporadic or occasional claim denials) can be indicative of the provider's failure to do so. To address such situations, we believe that the implementation of § 424.535(a)(8)(ii) should not be delayed, as some of the commenters appeared to suggest we do.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed that any appeals stemming from revocations initiated under § 424.535(a)(8)(ii) should be subject to an expedited appeals process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Since the impact of a revocation is the same regardless of the reason involved, we do not believe that revocations based on certain reasons should be subject to a faster appeals process than those predicated on other reasons.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that CMS's proposed § 424.535(a)(8)(ii) will have a chilling effect on the practice of medicine because it gives the federal government significant authority to target honest physicians. The commenter requested that CMS remove this proposed provision from the final rule or at least develop and solicit comments on a process for notifying providers of their billing issues and giving them an opportunity to correct the problem prior to revoking billing privileges.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree that our proposal will have a chilling effect on health care. This rule will not affect providers that take seriously their responsibilities to submit valid claims and to seek clarification when there is confusion or disagreement involving applicable policies. No payer, public or private, should be required to continue doing business with a provider or supplier that demonstrates the type of clear pattern or practice of billing abuse that this rule addresses. Moreover, we do not believe that any additional formal notification to the provider of its billing deficiencies prior to the potential application of § 424.535(a)(8)(ii) is required. Under our current rules and practices, by the time CMS would revoke a provider or supplier under § 424.535(a)(8)(ii), the provider would have received information and education about the reasons for the claim denials on multiple occasions. From the first claim denial, when a provider of supplier is notified of the reason for the denial, providers receive information indicating compliance or non-compliance with Medicare rules and requirements. It is ultimately the provider's responsibility to review its denied claims and to take whatever remedial action is necessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that proposed § 424.535(a)(8)(ii) should have certain objective measures and standards—such as a 50 percent benchmark—to ensure that it is not applied in an arbitrary manner.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We solicited and received several comments regarding whether certain numerical thresholds should be established in § 424.535(a)(8)(ii). After considering these comments, we have concluded that numerical thresholds should not be established because we need the flexibility to address a myriad of scenarios. For example, merely because a provider had over 30 percent of its claims denied does not automatically mean that a § 424.535(a)(8)(ii) revocation should be imposed; likewise, an under-30 percent denial rate does not mean that a § 424.535(a)(8)(ii) revocation is never warranted. Each case must be judged on its own specific facts, and establishing numerical thresholds would, we believe, hinder our ability to do so.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters recommended that CMS exclude providers from the application of § 424.535(a)(8)(ii) for a period of 1 year when Medicare changes the Medicare Administrative Contractor for the provider's state, as providers in such instances must learn new local coverage determination (LCD) policies.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with this recommendation. While we concede that providers in these circumstances often need to learn new LCD policies, claims can be denied for many reasons unrelated to LCDs. We thus believe it would be inappropriate to institute a blanket 1-year exemption in such cases, for we would lose the ability during that time to take action to address repeated claim denials over a period of time. Again, though, and as we have stated elsewhere in this preamble, we recognize that Medicare has many rules and requirements regarding billing and coding, and that claims are sometimes submitted in error due to a provider's honest misunderstanding of these policies. It is not our intention to revoke billing privileges under § 424.535(a)(8)(ii) for such occasional misinterpretations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS delay implementation of § 424.535(a)(8)(ii) for 2 years after the implementation of the ICD-10 standard. The commenter believed that ICD-10's implementation will likely lead to the submission of incorrect claims for a period of time.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that a delay in the implementation of § 424.535(a)(8)(ii) is necessary. Again, any delay of the applicability of § 424.535(a)(8)(ii) would deny us the ability to address situations (unrelated to the ICD-10 implementation) involving repeated claim denials. Furthermore, as we have already noted, we recognize that Medicare has many requirements and that in isolated instances claims are submitted erroneously due to a provider's misinterpretation of these policies. Such occasional misunderstandings will generally not rise to the level of a “pattern or practice” of improper billing, and thus will not warrant revocation under § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that it would be inappropriate for CMS to revoke billing privileges under § 424.535(a)(8)(ii) when no finding of fraud is involved. The commenter recommended that CMS withdraw this proposed provision.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree. Revocation is an administrative remedy separate and distinct from the government's other remedies for fraudulent behavior, and is intended to protect the Medicare program and its beneficiaries from fraud, waste, and abuse. Indeed, many of our existing revocation reasons under § 424.535(a) do not require a finding of fraud. For example, § 424.535(a)(1) permits revocation of the provider or supplier's Medicare billing privileges if the provider or supplier is out of 
                        <PRTPAGE P="72515"/>
                        compliance with Medicare enrollment requirements. The fact that there has not been a legal finding of fraudulent conduct does not automatically mean the behavior or activity in question is compliant with Medicare requirements. We maintain that repeated claim denials over a period of time raise questions as to the provider or supplier's ability or willingness to comply with Medicare's billing and coding requirements and procedures.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter opposed proposed § 424.535(a)(8)(ii), contending that: (1) CMS already has the authority and tools to revoke the billing privileges of unscrupulous actors who defraud or abuse the Medicare program; (2) denial of payment is the appropriate remedy for the submission of an incorrect claim; (3) CMS should not assume that providers cannot correct their existing practices to ensure that accurate claims are submitted; and (4) there is no guarantee that the determination criteria CMS has outlined would not be improperly or inconsistently applied.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We currently do not have the ability to revoke a provider or supplier's billing privileges based on a pattern or practice of submitting non-compliant claims, hence the need for § 424.535(a)(8)(ii). We agree that a claim denial can serve as an adequate remedy in many cases. However a repeated pattern of submitting non-compliant claims indicates that the associated claim denials are not altering the provider's behavior. More serious remedial action—specifically, the revocation of billing privileges under § 424.535(a)(8)(ii)—may thus be necessary in some cases.
                    </P>
                    <P>We do not assume that providers cannot correct their existing practices to ensure that they submit compliant claims. We believe very strongly that they can, which is precisely why a failure to do so could warrant a revocation under § 424.535(a)(8)(ii).</P>
                    <P>CMS, rather than our contractors, will make all determinations under § 424.535(a)(8)(ii) and will consistently apply the criteria.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that existing procedures, including audits, are more than sufficient to detect improper billing and to educate providers in complying with Medicare's intricate rules. The commenter believes that § 424.535(a)(8)(ii) is in effect duplicative of these procedures, and would simply impose another layer of complexity and financial burden on providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter's premise: our current rules and procedures are sufficient to bring most providers into compliance when mistakes or errors are brought to their attention. However, this final rule is focused on providers who cannot or will not come into compliance with our payment requirements after repeated claim denials. Despite our audit practices and educational activities, we continue to see situations where certain providers and suppliers regularly submit non-compliant claims. Clearly, our audit and education activities have not been enough to sufficiently stem this behavior in all instances, thus demonstrating the need for § 424.535(a)(8)(ii). Yet we reiterate that not only will we make all determinations under § 424.535(a)(8)(ii), but also that this provision will be applied in situations where the behavior was not sporadic in nature. We are focused on instances where the provider is engaged in an ongoing pattern of submitting non-compliant claims.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the proposed rule does not explain how or why billing is “abusive” merely because the claim appears not to meet medical necessity criteria.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There are reasons other than a failure to meet medical necessity requirements for which a claim can be denied (although the continuous submission of claims for medically unnecessary services can trigger § 424.535(a)(8)(ii)). The term “abusive,” as used in the context of § 424.535(a)(8)(ii), is meant to capture a variety of situations in which a provider or supplier regularly and repeatedly submits non-compliant claims over a period of time.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that whatever criteria CMS plans to use in determining whether a revocation under § 424.535(a)(8)(ii) is appropriate should be included in the final rule's regulatory text or, as one commenter suggested, be accompanied by a binding administrative document (such as an administrator's ruling) as part of its implementation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have included in the regulatory text the factors that CMS will consider prior to imposing a revocation under § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that before CMS finalizes § 424.535(a)(8)(ii), it should: (1) Instruct its contractors not to repeatedly audit the same beneficiary's claims once the claims have been upheld on appeal or in medical review; (2) instruct its contractors not to audit a provider for a 1-year period if the provider has been audited and found to have an acceptable error rate; (3) restore contractors' ability to use clinical judgment when performing complex medical reviews; (4) develop a comprehensive education program for practitioners who prescribe DMEPOS items; (5) exercise better supervision of its contractors; and (6) establish clear guidelines for calculating provider-specific error rates used to place providers on prepayment review. The commenter believed these changes are necessary to better ensure that providers—who are often confused by CMS policy changes, which the commenter stated are sometimes applied retroactively—are able to submit correct claims and that CMS's policies are consistent, clear, and appropriately announced to providers with adequate notice.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the commenter's suggestions, they are outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that CMS will use audits performed by its contractors (for example, RACs) as a legitimate, ultimate indicator of either fraudulent behavior or noncompliance with Medicare payment policies. The commenter recommended, as did a number of other commenters, that CMS eliminate pre-payment audits as a basis for detrimental action under § 424.535(a)(8)(ii). These commenters stated that some providers undergo pre-payment review merely as a preventative or precautionary measure to make sure that the claims submitted are appropriate and well-documented or because of the amount of the claim. They added that certain providers are subjected to pre-payment review for reasons beyond their control, and that losing billing privileges for being placed on pre-payment review is a draconian and inappropriate penalty. Several other commenters stated that there is no evidence to suggest that placing certain categories of suppliers or product categories under pre-payment review is resulting in lower error rates.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we do not intend to use the results of audits performed by our contractors as the sole and absolute criterion of fraudulent behavior or noncompliance with Medicare payment policies, such results will be considered in our review of all of the factors in § 424.535(a)(8)(ii).
                    </P>
                    <P>We will not consider the provider's pre-payment review status in and of itself as a factor in § 424.535(a)(8)(ii) determinations. Our concern is with actual claim denials, rather than the means through which such denials were issued.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that the claim denials of some individual practitioners and other suppliers sometimes stem from deficiencies in the physician's documentation. The commenters 
                        <PRTPAGE P="72516"/>
                        believed that CMS's inclusion of such claim denials—that is, claim denials based on the insufficient documentation of another provider—in its § 424.535(a)(8)(ii) determinations would be arbitrary and capricious.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree. We believe it is the responsibility of the provider submitting the claim to ensure that all requirements—including, as necessary, proper and compliant supporting documentation—have been met prior to the claim's submission. Repeated denials due to improper documentation are an indication to a provider or supplier that its billing behavior must change in order to become compliant with Medicare requirements—including documentation requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that proposed § 424.535(a)(8)(ii) should contain a knowledge standard that the provider knew that the claims did not meet Medicare requirements. Several other commenters contended that CMS should only revoke billing privileges under § 424.535(a)(8)(ii) if the supplier has specific or actual knowledge of the erroneous nature of a particular claim or set of claims. This would preclude revocations based on honest mistakes; one commenter noted the challenges associated with EHR systems and the possibility that erroneous claims could be submitted as a result. One commenter stated that the proposed provision lacks any standards concerning the state of mind of the entity. Another commenter stated that between the two intent standards that are under CMS consideration—“reckless disregard” and “knew or should have known”—the former would be more appropriate. Another commenter urged CMS to apply § 424.535(a)(8)(ii) only when there is clear evidence that a provider acted knowingly and willfully in submitting non-compliant claims. This commenter stated that under Medicare's complex billing rules, it would be too easy for CMS or a contractor to assert that a provider “should have known” about a billing rule; as such, CMS should delete the phrase “should have known” in the final rule. The commenter believed that CMS should focus more on educating providers about changes to Medicare billing rules than on the punitive remedies outlined in § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although we solicited comments on whether a knowledge standard should be applied to § 424.535(a)(8)(ii), we have decided not to implement such a standard for two principal reasons. First, the burden on CMS of determining the provider or supplier's intent for each claim it submitted (especially when there could be hundreds of claims at issue) would be excessive. Second, if a provider submits a claim with specific or actual knowledge that it does not meet Medicare requirements or with reckless disregard of said compliance, the federal government already has various means to address these situations, such as the False Claims Act. Associating a knowledge standard with § 424.535(a)(8)(ii) would simply duplicate existing authorities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS appears to be attempting to keep providers and suppliers from being able to effectively provide care for beneficiaries and to limit the overall number of providers and suppliers. The commenter believed that: (1) § 424.535(a)(8)(ii) Is based on a rationale that all providers and suppliers are a risk to the Medicare Trust Funds; and (2) CMS has not fully gauged the proposed provision's impact on many honest providers and suppliers that furnish services to Medicare beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are neither attempting to impede patient care nor reduce the number of providers and suppliers. We believe most Medicare suppliers and providers are conscientious about submitting claims that meet Medicare requirements, and this rule will not affect that majority. Once again, we are merely attempting to address the problem of providers and suppliers with patterns of non-compliant claim submissions. Providers and suppliers that are not engaged in a pattern or practice of non-compliant billing will not be adversely affected by § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that a mere difference of opinion about what is medically necessary—a term that is not “black and white”—should not be the basis for a revocation of billing privileges, particularly considering that LCDs and views on medical necessity will differ among MACs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand the commenter's concern and believe that sporadic claim denials based on a lack of medical necessity generally should not result in revocation under § 424.535(a)(8)(ii). However, we do not believe that medical necessity-based denials should be excluded from the scope of § 424.535(a)(8)(ii). It is of concern to us when a provider consistently submits claims for services that are not medically necessary, for this raises quality of care issues as well as the possibility that the provider is seeking to defraud the Medicare program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that while CMS states that § 424.535(a)(8)(ii) is not designed to revoke enrollment for isolated and sporadic claim denials or for innocent errors in billing, the provision itself (as proposed) does not make that intent clear.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulatory text of § 424.535(a)(8)(ii) states that CMS may revoke billing privileges if a provider or supplier has a pattern or practice of submitting claims that fail to meet Medicare requirements. It also identified five factors that we will use to make such a determination, including: (1) The percentage of claims denied; (2) the reasons for the claim denials; (3) a history of final adverse actions; (4) the length of time the pattern has continued; and (5) the length of time the provider or supplier has been enrolled in Medicare.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that some providers submit many claims each year electronically, meaning that a single inadvertent error could easily be repeated on numerous claims. The commenters expressed concern that such errors when repeated could constitute a pattern or practice of submitting erroneous claims under § 424.535(a)(8)(ii). One of these commenters added that in light of the great complexity of Medicare billing and coding requirements, a provider could inadvertently submit a claim that failed to meet at least one Medicare requirement, even though the provider in good-faith believed that the claim was correct.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the possibility that a single inadvertent error on similar electronic claim submissions could result in multiple claim denials. As we stated earlier, we recognize that Medicare has many rules and requirements regarding billing and coding, and that claims are sometimes submitted in error due to a provider's honest misunderstanding of these policies. It is not our intention to revoke billing privileges under § 424.535(a)(8)(ii) for such sporadic misinterpretations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that the following factors—in order of importance—be used in determining whether a “pattern or practice” exists under § 424.535(a)(8)(ii) and that such factors be included in the regulatory text: (1) The reason(s) for the claim denials; (2) the percentage of submitted claims that were denied (for which there should be a minimum threshold); (3) how long the provider has been enrolled in Medicare; (4) whether the provider has had any final adverse actions; and (5) the length of time of the pattern or practice. Another commenter requested 
                        <PRTPAGE P="72517"/>
                        that CMS not use the “total number of claims denied” as a criterion, for this could disproportionately and unfairly impact larger providers that submit many claims. The commenter also requested CMS to clarify whether the percentage of submitted claims that were denied would be determined using individual, subpart, or organizational NPIs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have decided not to give certain factors greater weight in our § 424.535(a)(8)(ii) determinations than other, for the importance of each factor may vary based on the particular situation. We have also decided not to establish a minimum percentage threshold for claim denials; as stated earlier, we need flexibility to address a variety of scenarios. However, we included the five factors that the first commenter identified—all of which we proposed—in the regulatory text as criteria that CMS will consider, as appropriate or applicable, in its § 424.535(a)(8)(ii) determinations.
                    </P>
                    <P>We agree with the second commenter that the “total number of claims denied” factor could present a distorted view of the provider or supplier's billing practices for purposes of § 424.535(a)(8)(ii). Therefore, we will not be finalizing this as criterion.</P>
                    <P>The “percentage of claims denied” criterion will be based on the NPI listed on the claim.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that: (1) The provider should have an opportunity to show that it has remedied any error that occurred; and (2) proposed § 424.535(a)(8)(ii) should be limited to situations that are within the provider's control. With respect to this second suggestion, the commenter stated that providers sometimes rely upon physicians to provide information that must be included on the claim; if such information is incorrect, CMS should not use this as a basis for revocation under § 424.535(a)(8)(ii). Other commenters shared this view.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with both of the commenter's suggestions. We believe that the provider already has an opportunity to remedy an error once it receives a claim denial notice. Repeated errors over a period of time indicate that the provider is not taking necessary corrective steps. Also, while we recognize that providers sometimes rely on physicians for certain information, the provider remains ultimately responsible for ensuring that the claim and the supporting documentation meet Medicare requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that inconsistent claim determinations, policies, and interpretations of policies among MACs would lead to inequitable results under § 424.535(a)(8)(ii). As written, they provide far too much latitude for administrative folly, which is nearly guaranteed to occur. At a minimum, the commenter stated, the proposed rule must not be finalized without: (1) Substantial clarifying text written into the regulation itself; or (2) being accompanied by a binding administrative document (such as an administrator's ruling) for its implementation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated earlier, CMS, rather than its contractors, will make all § 424.535(a)(8)(ii) determinations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended that CMS include in the regulatory text of § 424.535(a)(8)(ii) a statement that the authority to make determinations that a “pattern or practice” does not rest with CMS's contractors. The commenters also suggested that CMS incorporate into the regulatory text the following criteria that CMS should use in making § 424.535(a)(8)(ii) determinations: (1) Whether the provider has any history of “final adverse actions” and the nature of those actions; (2) the length of time over which the pattern or practice has continued; (3) how long the provider has been enrolled in Medicare; (4) whether the pattern or practice occurs throughout the provider or supplier's industry; (5) whether the provider had a specific intent to submit a false or fraudulent claim; (6) whether the provider has a corrective action plan in place; (7) the number of claims overturned on appeal; and (8) the reasons for the claim denials. With respect to the fourth criterion, the commenters stated that consistently high industry-wide error rates among suppliers are the result of constant changes to billing requirements, uncertain and inconsistent interpretation of requirements by regulating and enforcing entities (including Medicare contractors), inadequately written LCDs, and CMS's expectation that suppliers can enforce physician documentation requirements. They recommended that CMS consider addressing high industry-wide error rates through billing requirement reform rather than implementing another instrument of supplier punishment via § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we have stated elsewhere in this final rule, we will make all determinations for revocations under § 424.535(a)(8)(ii). We do not believe this needs to be restated in the regulatory text.
                    </P>
                    <P>Insofar as the commenters' suggested factors for consideration, we agree with the first, second, third, and eighth factors and have included them in the regulatory text. We do not agree with the fourth suggested factor. Each provider or supplier must be reviewed individually, rather than as part of a larger class of providers and suppliers. We do not agree with the fifth suggested factor, either; for reasons already stated, we will not be applying a knowledge standard to § 424.535(a)(8)(ii). We disagree with the sixth factor as well. If a provider is repeatedly and consistently submitting non-compliant claims, this indicates that the provider's corrective action plan—assuming it has one—is either being partially or wholly disregarded or is inadequate. As for the seventh factor, and as stated earlier, a provider or supplier's claim denial that has been both: (1) Fully (rather than partially) overturned on appeal; and (2) finally and fully adjudicated will be excluded from our § 424.535(a)(8)(ii) determinations.</P>
                    <P>Finally, we recognize that there may be special circumstances surrounding the provider or supplier's non-compliant billing that are beyond the scope of the five factors we are finalizing. The particular facts of each case will vary widely, and the scenarios the commenters have presented underscore this point. To effectively address these situations, we believe that a sixth criterion should be established that enables CMS to consider any other applicable and available information regarding the provider or supplier's specific circumstances that CMS deems relevant to its determination of a pattern or practice of non-compliant billing. However, information considered under this criterion will not alone be decisive in our determinations under § 424.535(a)(8)(ii); the five other factors will, of course, be considered as well. Regardless, we believe that such information, to the extent it exists, should be considered in our § 424.535(a)(8)(ii) determinations to help ensure that the Medicare Trust Funds are protected and, by the same token, that providers and suppliers are treated fairly.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended that CMS give low consideration to claim volume and percentage of claims denied as factors under § 424.535(a)(8)(ii) and that thresholds not be established for these criteria. The commenters believed that these factors may lead CMS to focus on the largest suppliers that rely on automated claims administration systems, while missing smaller suppliers that do not attract attention because their data does not exceed certain thresholds.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The number of denied claims will not be a factor in our 
                        <PRTPAGE P="72518"/>
                        § 424.535(a)(8)(ii) determinations, though the “percentage of denied claims” will remain as a factor and one that is no less important than the others. Also, and as explained earlier, we are not establishing thresholds for any of our criteria.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern that § 424.535(a)(8)(ii) could be easily misapplied or misused because the provision is very vague and without clear standards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As previously explained, we are finalizing all but one of the factors we proposed and are adopting an additional factor in response to the comments we received. We believe this will furnish sufficient clarity as to the scope of § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern about the potential application of § 424.535(a)(8)(ii) considering that RACs have a financial incentive to deny claims. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         RACs review claim decisions on a post-payment basis. and are only paid for a claim denial if a Medicare Administrative Contractor (MAC) denial of a claim is upheld on appeal; this, we believe, reduces the incentive for RACs to make inappropriate determinations regarding claims. We also reiterate that claim denials that are reversed on appeal will be excluded from the application of § 424.535(a)(8)(ii) if they meet certain criteria.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged CMS to reconsider revocations based on billing patterns because it does not appear that there is—nor does CMS cite any—statutory authority to support such a remedy.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We cited our statutory authority for § 424.535(a)(8)(ii) and all of our other provider enrollment provisions in both this rule and the proposed rule. Specifically, sections 1102 and 1871 of the Act provide general authority for the Secretary to prescribe regulations for the efficient administration of the Medicare program; also, section 1866(j) of the Act (codified at 42 U.S.C. 1395cc(j)) provides specific authority with regard to the enrollment process for providers and suppliers.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that: (1) There are often good-faith differences between providers and contractors over appropriate coding; and (2) different payers may have different rules, which can cause confusion over the appropriate way to bill. The commenter contended that if there is no evidence that the provider intended to defraud Medicare, the provider should be given a chance to remedy the error. Medicare, the commenter added, should engage in education, counseling, and guidance that leads to correct coding before taking draconian measures.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that frequent claim denials should alert the provider that there may be an issue with its claim submissions and that remedial action may be required. We do not believe that an interim notification from CMS (for example, a “warning letter”) should be a prerequisite for taking action under § 424.535(a)(8)(ii). Further, if the provider has questions regarding CMS's billing and coding requirements, it should review CMS's manuals, educational articles, and other informational documents at CMS's Web site (
                        <E T="03">www.cms.hhs.gov</E>
                        ); the provider may also contact its local MAC if it has additional questions.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that it fully supported proposed § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that Medicare providers are already well aware of their legal obligation to submit correct and accurate claims for services that were reasonable and necessary. They noted that: (1) The current claim submission forms require the physician to certify that the services “were medically indicated and necessary for the health of the patient”; and (2) enforcement agencies already have ample authority under several statutory schemes to penalize providers found to have inaccurate claims, including the False Claims Act. Therefore, the commenters questioned the benefit of or need for § 424.535(a)(8)(ii), especially in light of the danger of CMS overreach in its application of this provision.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge these authorities as well as the certification language on the current claim submission forms. However, we continue to see instances where, despite these obligations, providers and suppliers repeatedly submit non-compliant claims. The other federal authorities provide remedies different from what we have proposed. We thus believe that the authority to revoke billing privileges under § 424.535(a)(8)(ii) can be part of a comprehensive strategy to address these situations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that there do not appear to be any administrative appeal rights if a provider is revoked under § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under § 424.545, a provider or supplier may appeal any revocation of Medicare billing privileges under 42 CFR part 498.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should exclude physicians from the purview of § 424.535(a)(8)(ii) because they fall within the “limited” screening category under § 424.518(a).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree. The issue is the correct submission of claims, rather than the level of screening to which the provider or supplier is normally subject under § 424.518(a).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that revocations under proposed § 424.535(a)(8)(ii) should be limited to instances where CMS has data indicating that the provider is engaging in extreme outlier billing and has an established and ongoing pattern of abusive practices.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated, we will consider, as appropriate or applicable, the six factors discussed previously (and contained in § 424.535(a)(8)(ii)(A) through (F)) in determining whether a revocation under § 424.535(a)(8)(ii) is warranted. A provider or supplier could be an “outlier biller” for any number of reasons. Hence, a provider or supplier that is an “outlier biller” should not automatically be subject to revocation based on § 424.535(a)(8)(ii). We have noted previously that we will only take revocation action under § 424.535(a)(8)(ii) after careful review of factors surrounding the provider or supplier's billing behavior.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that while the proposed rule's preamble indicated that “claims for services that fail to meet Medicare requirements” meant claims denied for failing to satisfy Medicare's medical necessity requirements, the regulatory text did not explicitly state as such. The commenter recommended that CMS either: (1) Delete its proposed § 424.535(a)(8)(ii); or (2) revise the provision to clearly limit “claims for services that fail to meet Medicare requirements” to claims that do not meet medical necessity requirements. The lack of a specific reference to “reasonable and necessary” requirements, the commenter believed, would enable CMS to unreasonably apply § 424.535(a)(8)(ii) to a failure to meet any Medicare requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that revocations under § 424.535(a)(8)(ii) should be limited to claim denials based on medical necessity. Indeed, proposed § 424.535(a)(8)(ii) was not meant to apply only to certain claim denial reasons. Repeated claim denials over a period of time are of concern to us irrespective of the particular reason(s) involved. To alleviate any confusion about the scope of § 424.535(a)(8)(ii), we are deleting the language “for services” from this provision. This will clarify that § 424.535(a)(8)(ii) applies to claims 
                        <PRTPAGE P="72519"/>
                        that are denied for failing to meet Medicare requirements and is not limited to cases where the claim is denied because the 
                        <E T="03">services</E>
                         did not mean Medicare requirements.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should establish a dispute resolution process prior to revoking a provider's privileges related to claims denials for not meeting Medicare requirements. Several other commenters stated that CMS should afford appeal rights under § 424.535(a)(8)(ii) prior to revoking a provider's billing privileges.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenters. No other revocation reason under § 424.535(a) currently has an interim appeals or dispute resolution process, and we do not see any basis or rationale for permitting such processes in the case of § 424.535(a)(8)(ii). As with all other revocation reasons, the provider or supplier may appeal the revocation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that revocations under § 424.535(a)(8)(ii) should be reserved for only the most serious of abuses.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree. As we have stated, § 424.535(a)(8)(ii) will only be applied when it is clearly appropriate. For instance, a § 424.535(a)(8)(ii) revocation could be proper, once all of the appropriate factors have been considered, if—
                    </P>
                    <P>• There is a demonstrable pattern or practice;</P>
                    <P>• The pattern is long-term or has otherwise continued over a period of time;</P>
                    <P>• Education regarding appropriate billing is or has been made available to the provider in the form of claim denial notices, CMS instructional materials (such as manuals and articles) on CMS' Web site, etc., yet the provider or supplier continues to submit non-compliant claims, and</P>
                    <P>• A significant percentage of the provider's or supplier's claims have been denied.</P>
                    <P>(We stress that this is merely an example and should be not be interpreted as the formal establishment of minimum criteria.)</P>
                    <P>We again state that § 424.535(a)(8)(ii) is not targeted toward honest providers and suppliers that make occasional billing mistakes. Our sole focus is on providers and suppliers that engage in a systemic, ongoing, and repetitive practice of improper billing notwithstanding the public availability of CMS educational materials or guidance and CMS' issuance of claim denial notices to the provider. While we hope that this helps to reassure the provider and supplier communities of CMS' intentions, we recognize that concerns may linger. To that end, we plan to issue written guidance to and communicate with the public once this final rule is implemented, whereby we will once again reiterate the objective behind § 424.535(a)(8)(ii) and, as necessary, discuss certain operational aspects of this provision.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS did not—(1) explain how determinations under § 424.535(a)(8)(ii) would be made; (2) explain how errors in a revocation determination can be remedied short of a reapplication after the enrollment bar expires; and (3) furnish rationale as to the specific standards—such as the establishment of a percentage threshold for claim denials—that CMS will use in its determinations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will make all § 424.535(a)(8)(ii) determinations after a careful and thorough consideration of the factors outlined in § 424.535(a)(8)(ii)(A) through (F). As we explained in the proposed rule, any revocation under § 424.535(a)(8)(ii) may be appealed if the provider or supplier chooses to do so.
                    </P>
                    <P>We stated earlier that each case will be judged on its own specific facts, and that establishing specific thresholds would, we believe, hinder our ability to do so. We believe that the factors outlined in § 424.535(a)(8)(ii)(A) through (F) sufficiently indicate to providers and suppliers the rationale we will use in our § 424.535(a)(8)(ii) determinations.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned whether a system would be established to ensure that § 424.535(a)(8)(ii) would be implemented and enforced uniformly across jurisdictions. The commenter also requested which entities (for example, RACs) would be tasked with enforcing these provisions as well as any financial incentives for identifying wrongdoing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Once again, we (not our contractors) will make all determinations regarding whether a § 424.535(a)(8)(ii) revocation should be imposed. We will apply the criteria consistently.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that in light of the seriousness of a revocation under § 424.535(a)(8)(ii), CMS should provide direct notice to a provider that its billing privileges may be revoked if its continues to bill for services that do not meet Medicare requirements. The commenter believed that such a preliminary “warning” could encourage the provider to improve its claim submission accuracy. The commenter also suggested that CMS consider a sliding scale that includes a lower-level consequence—such as a suspension—for less severe occurrences.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that an interim alert to the provider is necessary. The provider's receipt of a substantial number of claim denials, in our view, furnishes adequate notice to the provider that corrective action is necessary.
                    </P>
                    <P>While we appreciate the commenter's suggestion regarding lower-level consequences for less severe cases, we note again that § 424.535(a)(8)(ii) is only intended to address the most severe of situations. Still, we will closely monitor our application of this provision and the scenarios that come before us. Should we determine that other sanctions may be appropriate, we may, as needed, undertake future rulemaking.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should not finalize § 424.535(a)(8)(ii) until the public has had an opportunity to comment on the specific policy CMS will use in defining “pattern or practice.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated, we are not formally defining “pattern or practice” in this rule. We will instead consider a number of factors in our determinations as to whether a § 424.535(a)(8)(ii) revocation is warranted.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that although CMS sought feedback from the provider community regarding § 424.535(a)(8)(ii), it did not believe that engaging in this type of review and analysis during a 60-day public comment period was appropriate. The commenter believed that discussions and collaboration with the provider community via a stakeholder group should occur beforehand.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. While we recognize the provider community's concerns regarding § 424.535(a)(8)(ii), we do not believe that formal discussions with a stakeholder group resulting in an agreement as to what § 424.535(a)(8)(ii) should consist of are necessary prior to the provision's implementation. This is especially true considering that we received valuable comments from providers and suppliers regarding § 424.535(a)(8)(ii) and have incorporated them into our final provisions as needed. We believe that the notice-and-comment process under the APA is the most appropriate means of soliciting feedback from the public.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter, expressing concern about CMS's potential use of statistical analysis in determining patterns under § 424.535(a)(8)(ii), cited several instances in which a claim is denied but cannot automatically or necessarily be considered an abusive billing situation: (1) A patient dies prior 
                        <PRTPAGE P="72520"/>
                        to the interpretation of an applicable test; (2) claims for services deemed not medically necessary; (3) the beneficiary needs a Medicare denial to file secondary insurance; and (4) the beneficiary has exceeded a benefit category unbeknownst to the provider. The commenter believed CMS has the capability to distinguish between (a) abusive billing patterns and (b) claim denials that occur in the normal course of business and are not based on any nefarious intent. The commenter added that in providing examples of what may constitute a pattern of abusive billing behavior, CMS must account for certain specialty-specific situations that can occur due to the nature of the provider-patient encounter; diagnostic services, for example, should not be subject to the same standard as other providers due to the remote nature of the physician-patient relationship.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter's apparent rationale that certain claim denials may be for purely innocuous reasons and that CMS has the ability to distinguish between these situations and extreme instances of non-compliant billing. We note once more that the reason(s) for the claim denials will be a factor in our § 424.535(a)(8)(ii) determinations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that a provider often will not be aware of a pattern of alleged improper billing under § 424.535(a)(8)(ii) until after a contractor performs an audit. Under such circumstances, the commenter believed, the provider should be given an opportunity to correct the allegedly improper billing via a plan of correction.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As already stated, we acknowledge that in sporadic instances providers and suppliers may submit claims in error due to a misunderstanding of Medicare policies. It is not our intention to revoke billing privileges under § 424.535(a)(8)(ii) for such isolated misinterpretations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that in situations where coordination of benefits is involved, a provider must exhaust all efforts to receive payment from a primary payer—such as Medicare—before billing a secondary payer. The commenter urged CMS to exclude coordination of benefit situations from the category of claim denials that can be considered under § 424.535(a)(8)(ii).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we do not believe that such situations should be automatically excluded from the purview of § 424.535(a)(8)(ii), we note that the reasons for the claim denials will be a factor in our § 424.535(a)(8)(ii) determinations. Consequently, the situation the commenter describes will be considered in such determinations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that “length of time” should only be considered as a factor if the provider acted in reckless disregard of whether its claims did not meet Medicare requirements. The commenter added that: (1) The reckless disregard standard should be used in all cases involving § 424.535(a)(8)(ii); and (2) CMS should not use “the total number of claims denied” and “percentage of claims denied” categories in applying § 424.535(a)(8)(ii) because there are many instances in which claims are denied—such as in coordination of benefit situations—for innocuous purposes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated, we will neither be applying a knowledge standard to § 424.535(a)(8)(ii) nor eliminating the “percentage of claims denied” or “length of time” criteria from our analysis. However, we are removing “the total number of claims denied” criterion.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS must furnish the provider community with guidance regarding CMS's requirements for proper medical record documentation, including the frequency of documentation to support medical necessity for each product category. The commenter also recommended the inclusion of these documents within an electronic health record template.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe these comments are outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that a provider's claims are sometimes denied because of insufficient physician medical record documentation; such instances should not be included within the purview of § 424.535(a)(8)(ii) because the provider had no control over the physician's documentation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that denials based on insufficient medical record documentation should be automatically excluded from the scope of § 424.535(a)(8)(ii). Again it is ultimately the provider's responsibility to ensure that the documentation it furnishes in support of a claim meets Medicare requirements, though the reason(s) for the claim denial will be a factor in our § 424.535(a)(8)(ii) determinations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that claims are occasionally denied because information on the certificate of medical necessity is inconsistent with CMS's national coverage criteria. The commenter suggested that the two decisional documents be streamlined to coordinate coverage criteria effectively and uniformly.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe this comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern about what the commenter believed was a lack of definition of “directing physician” as that term is used in § 424.535(a)(8)(i). The commenter stated that the professional component of diagnostic testing services is often not performed in the same physical location or contractor jurisdiction as the technical component, and that the date of service may be different if the interpretation is not done on the same date done as the technical component. Such normal, compliant practices could be misinterpreted under § 424.535(a)(8)(i).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we did not propose any changes to the content of existing § 424.535(a)(8), which is merely renumbered in this final rule as § 424.535(a)(8)(i), this comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter contended that although § 424.535(a)(8)(i) suggests that an abuse of billing privileges includes billing for a service when it would have been impossible to actually provide the service—such as when the physician performing the service was not available to furnish the service, or the patient was not available to receive the service because he or she was out of the state or country—the regulation does not clearly state as such. The commenter expressed particular concern regarding the situation where a laboratory is not in the same state in which the physician who ordered the service is located, meaning that the service could not have been furnished to that beneficiary on that date of service. The commenter requested that CMS clarify that this situation is outside the scope of scenarios to which this rule is meant to apply.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we did not propose any changes to the content of existing § 424.535(a)(8), which is merely renumbered in this final rule as § 424.535(a)(8)(i), we believe this comment is outside the scope of this rule.
                    </P>
                    <P>Given the comments received and the foregoing discussion, we are finalizing proposed § 424.535(a)(8)(ii) with a modification. We are adding new paragraphs (A) through (F) to identify the factors for consideration.</P>
                    <HD SOURCE="HD3">5. Post-Revocation Submission of Claims</HD>
                    <P>
                        Section § 424.535(h) currently states that a revoked physician organization, physician, non-physician practitioner or IDTF must submit all claims for furnished items and services within 60 calendar days of the effective date of the 
                        <PRTPAGE P="72521"/>
                        revocation. As we explained in the proposed rule, the reason for such a relatively short post-revocation claim submission period is to limit Medicare's exposure to future vulnerabilities and potentially fraudulent claims from such revoked individuals and organizations.
                    </P>
                    <P>With this in mind, we proposed to expand § 424.535(h) to require all revoked providers and suppliers to submit, within 60 days after the effective date of the revocation, all claims for items and services furnished prior to the date of the revocation letter. For HHAs, the date would be 60 days after the later of: (1) The effective date of the revocation; or (2) the date that the HHA's last payable episode ends.</P>
                    <P>A summary of the comments received and our responses thereto are as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned why CMS is proposing to grant DMEPOS suppliers an additional 45 days after revocation to submit claims, for § 424.57(d) currently grants DMEPOS suppliers only 15 days to submit claims after revocation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the commenter is misreading § 424.57(d), in that § 424.57(d) does not address the timeframe in which post-revocation claims must be submitted.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for our proposed change, stating that all providers and suppliers would now be treated equally with respect to the post-revocation claim submission requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>Given the very few comments received and the foregoing discussion, we are finalizing our proposed changes to § 424.535(h).</P>
                    <HD SOURCE="HD3">6. Effective Date of Billing Privileges</HD>
                    <P>Under the current version of § 424.520(d), the effective date of billing privileges for physicians, non-physician practitioners, and physician and non-physician practitioner organizations is the later of: (1) The date of filing of a Medicare enrollment application that was subsequently approved by a Medicare contractor; or (2) the date an enrolled physician or non-physician practitioner first began furnishing services at a new practice location. This policy is meant to address our concerns about providers and suppliers being able to bill for Medicare services rendered well before enrollment, for it is not always possible to verify whether a supplier has met all Medicare enrollment requirements prior to the date it submits an enrollment application. Thus, the Medicare program should not be billed for services performed before the later of the two aforementioned dates. In light of this concern, we proposed to expand the scope of § 424.520(d) to include ambulance suppliers, based in part on the elevated risk they pose to the Medicare program as stated in § 424.518. Indeed, in a January 2006 OIG report entitled, “Medicare Payments for Ambulance Transports” (OEI-05-02-000590), the OIG found that 25 percent of ambulance transports did not meet Medicare's program requirements; this resulted in an estimated $402 million in improper payments.</P>
                    <P>As explained in the proposed rule, we did not include certified providers and certified suppliers in our proposed revision to § 424.520(d) because of: (1) Existing limitations posed by § 489.13 on their ability to “backbill” for services; and (2) the extensive, multilayered review process they must undergo prior to enrolling in Medicare. Yet we did solicit comments on whether any other non-certified provider or non-certified supplier types that are not currently subject to a backbilling restriction similar to the one we proposed should be included.</P>
                    <P>The following is a summary of the comments received regarding this proposed change and our responses thereto.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that CMS should treat ambulance services in a manner consistent with physicians and non-physician practitioners when it comes to enrollment and the filing of Medicare claims. Retroactive billing for ambulance services, the commenter continued, should be similar to the 30-day retroactive billing authority that exists for these individuals; the supplier could seek a longer retroactive billing period if it can demonstrate that exigent circumstances led to a situation that forced it to provide transport services prior to the normal billing requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the 30-day and 90-day retroactive billing provisions in § 424.521(a), to which the commenter is referring, should apply to ambulance suppliers to the same extent that they do to physicians, physician groups, non-physician practitioners, and non-physician practitioner groups. This approach would ensure: (1) Consistent treatment between ambulance suppliers and the other supplier types covered under § 424.520(d); and (2) that ambulance suppliers can avail themselves of a brief retroactive billing period if they are able to show that urgent circumstances precluded the supplier from submitting its enrollment application earlier than it did. Therefore, we have revised the regulatory text in § 424.521(a) to include ambulance suppliers.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that proposed § 424.520(d) should have a mechanism by which ambulance suppliers can obtain retroactive billing privileges in situations where the failure to file the enrollment application prior to commencing operations resulted from circumstances beyond the supplier's control; one commenter cited the example of a county-owned ambulance supplier that needs approval from the county's governing board before expanding its service area, a process that could delay the submission of the supplier's application. The commenters had two suggestions in this regard. First, the supplier could file a preliminary CMS-855 application when it anticipates expanding into a new service area; the supplier could supplement the application with additional information at a later date. Second, the supplier could appeal for retroactive billing privileges.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we explained earlier, we have incorporated a revised § 424.521(a) into this final rule. It will permit limited retrospective billing in exceptional circumstances. We believe this will alleviate some of the commenters' concerns.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested CMS to clarify that the “date of filing” of a CMS-855 application is the date on which the contractor initially received the application, not the date on which the contractor deemed the application “complete.”
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The “date of filing” is the date on which the provider or supplier submitted its CMS-855 application via mail or Internet-based PECOS.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that a more definitive distinction must be made as to what is meant by the date of an application that is subsequently approved. One commenter stated that it is not uncommon for contractors to return applications with a request for supporting documentation. Another commenter requested an explicit statement that the date the application is entered into PECOS or a paper CMS-855B is mailed is the effective date of billing privileges, assuming the application is eventually accepted; this would make it clear that a request for additional documentation is part of the original process and does not begin an entirely new cycle.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We indicated earlier that the effective date of billing privileges under § 424.520(d) will be the later of: (1) The “date of filing” of an enrollment application that is subsequently approved; or (2) the date the supplier began furnishing services at a practice 
                        <PRTPAGE P="72522"/>
                        location. The “date of filing” is considered to be the date on which the supplier submitted its CMS-855 application via mail or Internet-based PECOS.
                    </P>
                    <P>The term “subsequently approved” includes application submissions for which the contractor requested additional information from the supplier (or otherwise undertook developmental activities with respect to the application) and the application was ultimately approved. It does not include applications that were rejected under § 424.525 or returned pursuant to CMS Publication 100-08, chapter 15, and were later resubmitted. A contractor's request for additional information does not constitute a final disposition regarding the application; that is, the application is still in process. However, a rejection or return indicates that the contractor was unable to process the application to completion, meaning that the application processing cycle has ended and the supplier must submit a new application.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that municipalities are sometimes required to temporarily curtail their ambulance services and must contract with another ambulance supplier on an emergency, short-term basis; in such emergency situations, it may not be possible for the municipality to quickly secure all of the necessary paperwork to permit Medicare billing for transport services. The commenter stated that the municipality should not be held financially responsible for providing appropriate transport services for such emergency patients.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In response to the comments received, we have revised § 424.521(a) to allow ambulance suppliers limited retrospective billing in exceptional circumstances.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS clarify how the 2006 OIG report supports CMS's proposed § 424.520(d). The OIG report, the commenter contended, did not indicate whether the ambulance transports discussed therein occurred prior to the date the ambulance supplier submitted its enrollment application; citing the OIG report is misleading and creates an unfair and negative view of all ambulance suppliers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our citation of the report was not intended to disparage all ambulance suppliers but to present examples of instances where certain ambulance suppliers were not in compliance with Medicare requirements. Our concern about non-compliance is the precise reason for our revision to § 424.520(d). We explained earlier that allowing an extensive period of backbilling makes it difficult to verify whether an ambulance supplier was in compliance with Medicare requirements well before it submitted an enrollment application.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS: (1) Furnish the information it used to single-out ambulance suppliers in § 424.520(d); and (2) explain why it did not propose a similar backbilling limitation for other supplier types such as clinical laboratories and mass immunization roster billers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we discussed in the proposed rule, we elected to include ambulance suppliers within § 424.520(d) based on: (1) Their status as moderate-risk category suppliers under § 424.514; (2) the OIG report cited in the preamble; and (3) other program integrity issues we have detected regarding ambulance suppliers. Indeed, these issues were outlined in a July 31, 2013 notice (78 FR 46339) in which we imposed a temporary moratorium on the enrollment of new ground ambulance suppliers in several Texas counties; a similar moratorium was imposed effective January 30, 2014 against ambulance suppliers in the Philadelphia, Pennsylvania area (79 FR 6475).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the loss of revenue to ambulance suppliers resulting from § 424.520(d) could preclude them from expanding into new areas.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand the commenter's concern. Yet as we have stated, it is not always possible for us to verify that the supplier met all enrollment requirements many months prior to the application submission. To ensure that Medicare payments are made to suppliers that we have confirmed met enrollment requirements at the time the service was provided, we believe it is necessary to restrict the period of backbilling.
                    </P>
                    <P>Given these comments and in accordance with the previous discussion, we are finalizing our proposed change to § 424.520(d). We have also revised the regulatory text of § 424.521(a) to include ambulance suppliers.</P>
                    <HD SOURCE="HD3">7. Effective Date of Re-Enrollment Bar</HD>
                    <P>Currently under § 424.535(c), a revoked provider, supplier, delegated official, or authorizing official is barred from participating in Medicare from the effective date of the revocation until the end of the re-enrollment bar. The re-enrollment bar is a minimum of 1 year, but not greater than 3 years, depending on the severity of the basis for revocation. In accordance with § 424.535(g), the effective date of a revocation is either of the following:</P>
                    <P>• Thirty days after CMS or the CMS contractor mails notice of its determination to the provider or supplier.</P>
                    <P>• If the revocation is based on a federal exclusion or debarment, felony conviction, license suspension or revocation, or if the practice location is determined by CMS or its contractor not to be operational, the date of the exclusion, debarment, felony conviction, license suspension or revocation, or the date that CMS or its contractor determined that the provider or supplier was no longer operational constitutes the effective date of the revocation and, hence, the date on which the re-enrollment bar commences.</P>
                    <P>We proposed to revise § 424.535(c) to specify that all re-enrollment bars begin 30 days after CMS or the CMS contractor mails notice of the revocation determination to the provider or supplier. The rationale for this change was to address situations where the revocation is based on a federal exclusion or debarment, felony conviction, license revocation or suspension, or non-operational status. Due to potential delays in the updating of databases with criminal conviction and licensure information, the revocation effective dates for these actions can be months prior to the date the contractor mails the revocation letter, and it is from these retroactive effective dates that the re-enrollment bar runs. By starting the re-enrollment bar period after the revocation letter is sent, the full period can be imposed.</P>
                    <P>A summary of the comments we received as well as our responses follow:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that CMS identify the reason for its statement in the preamble discussion for proposed § 424.535(a)(3) regarding months of potential delay in updating databases with criminal conviction and licensure information. The commenter further requested CMS to indicate: (1) Whether the requirement under § 424.516 for physicians, non-physician practitioners, and owners to report a felony conviction within 30 days is being waived; and (2) if § 424.516 is being waived, whether CMS is also waiving the requirement in § 424.565 that CMS assess an overpayment back to the date of the adverse action.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We indicated in the proposed rule that there could be instances where a delay exists in updating a state Web site with felony or licensure data. With respect to the commenter's two requests, this rule 
                        <PRTPAGE P="72523"/>
                        does not waive the aforementioned requirement to report felony convictions or the overpayment assessment mandate in § 424.565.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter disagreed with CMS's proposed revision to § 424.535(c) because this would effectively limit overpayment collections from the date of the felony conviction or guilty plea, or would expose physicians and non-physician practitioners to higher Medicare overpayment amounts. The commenter stated that CMS should retain the current policies in these two provisions until it explains: (1) Their impact on the overpayment provision found in § 424.565; and (2) CMS's intent to impose overpayments based on an OIG exclusion or felony conviction from the date of the felony conviction or exclusion, the date of the revocation letter, or the actual revocation date.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our revision to § 424.535(c) neither addresses nor impacts overpayment determinations or collections. It simply specifies when the enrollment bar begins. For example, if a provider is revoked with a retroactive effective date, the enrollment bar—whatever the length—will commence as specified in § 424.535(c). Yet the effective date of the revocation (and from which date overpayments can be collected) will be the same as that which currently exists under our regulations.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that our proposal that all re-enrollment bars would begin 30 days after CMS mails the revocation notice to the provider appears prudent, for it would streamline and simplify current policy. The commenter also expressed support for our additional proposals to eliminate redundancies and make technical corrections to the regulatory text.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>Given this, we are finalizing our proposal to revise § 424.535(c) to state that the re-enrollment bar is effective 30 days after CMS or its contractor mails notice of its revocation determination to the provider or supplier.</P>
                    <HD SOURCE="HD3">8. Corrective Action Plans</HD>
                    <P>Consistent with § 405.809, a provider or supplier whose Medicare billing privileges are revoked may currently submit a corrective action plan (CAP). The CAP must provide evidence that the provider or supplier is in compliance with Medicare requirements. If CMS or the Medicare contractor determines that the provider or supplier is, in fact, compliant with Medicare requirements, the provider or supplier's billing privileges can be reinstated.</P>
                    <P>We proposed to revise § 405.809 to state in new paragraph (a)(1) that a provider or supplier may only submit a CAP when the revocation was based on § 424.535(a)(1), which states in part that a provider or supplier's billing privileges may be revoked if the provider or supplier is determined not to be in compliance with our enrollment requirements. We stated that providers and suppliers generally should not be exonerated from failing to fully comply with Medicare enrollment requirements simply by furnishing a CAP, for it is the duty of providers and suppliers to always maintain such compliance. The proposed exception for § 424.535(a)(1) was based on our experiences where a provider or supplier revoked under § 424.535(a)(1) had only minimally failed to comply with our enrollment requirements. To revoke its billing privileges when the problem can be quickly and easily corrected via a CAP could in some instances lead to unfair results. In cases where § 424.535(a)(1) is one of several reasons for a particular revocation, the provider would be able to submit a CAP with respect to the § 424.535(a)(1) revocation reason. For the other revocation grounds, though, the provider would not be able to use the CAP process; the provider would instead have to use the appeals process under Part 498.</P>
                    <P>We also proposed in new paragraph (a)(2) that providers and suppliers would have only one opportunity through a particular CAP to correct all of the deficiencies that served as the basis of the revocation. We expressed our view that providers and suppliers should not be given multiple opportunities to become compliant when it is crucial that such compliance always be maintained.</P>
                    <P>We further proposed to delete the last sentence of § 424.535(a)(1), which reads: “All providers and suppliers are granted an opportunity to correct the deficient compliance requirement before a final determination to revoke billing privileges, except for those imposed under paragraphs (a)(2), (a)(3), or (a)(5) of this section.” This sentence was inconsistent with our proposed change to § 405.809(a)(1).</P>
                    <P>Lastly, we proposed to incorporate the existing language of § 405.809 into a new paragraph § 405.809(b).</P>
                    <P>A summary of the comments we received on these proposed changes and our responses follow:</P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters noted that under CMS's proposal to restrict the availability of CAPs, a CAP could not be used in cases where a revocation occurred due to the provider's failure to report a practice location under § 424.535(a)(9). Although these commenters generally supported the proposed change, they urged CMS to clarify the definition of a “practice location” for ambulance services because Medicare contractors may be interpreting this term differently; for instance, some may define it as the location of the supplier's management, billing, or administrative staff, while others consider it to be where the supplier garages and/or maintains its vehicles.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We clarified the meaning of the term “practice location” as it pertains to ambulance suppliers in CMS Transmittal 499, dated December 27, 2013.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters opposed our proposed change to § 405.809 and urged CMS to allow CAPs to be available for additional scenarios beyond those encompassed by § 424.535(a)(1). One commenter stated that many enrollment violations can be cured. The commenter stated that CAPs should be permitted except in cases where a CAP clearly jeopardizes program integrity or beneficiary health and safety. Another commenter expressed concern about CMS's statement in the preamble concerning the revocation of billing privileges for failing to report a practice location change; to have the provider in such an instance go through the appeals process without the availability of a CAP, the commenter believed, would be unjust. Another commenter stated that CMS should never be unwilling to receive correct information and that, in the commenter's opinion, Medicare contractors furnish misleading and inaccurate information to providers and suppliers during the enrollment process.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we explained in the proposed rule, we believe that CAPs are inappropriate in a number of revocation situations and should accordingly be unavailable; to illustrate, revocations based on a failure to timely report a practice location change should not be retroactively corrected via a CAP. Indeed, we must be promptly notified of all practice location changes so we can ensure that services are only performed at valid locations and, consequently, that payments are made correctly. More basically, it is the provider or supplier's responsibility—as indicated on the CMS-855 forms that the provider or supplier completes and signs as part of the enrollment process—to report changes to CMS on a timely basis.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS eliminate the provider enrollment CAP process and work with Medicare contractors to 
                        <PRTPAGE P="72524"/>
                        eliminate revocations based on a trivial matter.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that CAPs are appropriate for revocations based on § 424.535(a)(1), and they will remain available. Moreover, we stress that revocations are not imposed for trivial reasons. Each prospective revocation is carefully reviewed to ensure that there are legitimate grounds for taking such action and that the integrity of the Medicare program warrants it.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that there generally is not enough time for a provider to submit both a corrective action plan and appeal, for the latter is frequently not filed until the results of the former are known. The commenter thus recommended that CMS either discontinue the CAP process or require its contractors to decide upon and respond to a CAP within 10 days of receipt.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that the CAP process should be entirely discontinued or that a provider must wait until the CAP determination has been made before filing an appeal. In fact, many providers and suppliers file a CAP and an appeal as part of the same package. Requiring a 10-day period is unnecessary and could hinder the reviewer's ability to conduct a thorough, careful analysis of the merits of the CAP.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter urged the continued use of CAPs in situations where the provider misinterpreted a requirement or failed to comply with an administrative or record-keeping requirement but otherwise acted in good-faith.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CAPs will remain available for revocations based on § 424.535(a)(1). With respect to other revocation reasons that we suspect the commenter may classify as “record-keeping” in nature—specifically, § 424.535(a)(9) and (a)(10)—we do not view these as mere administrative requirements. The reporting mandates referred to in paragraph (a)(9)—and which are codified in § 424.516(d)(1)(ii)—help ensure that CMS has correct, up-to-date information on the provider so CMS can determine if a provider or supplier is still in compliance with Medicare requirements. The maintenance of documentation requirements referred to in paragraph (a)(10) and codified in § 424.516(f) assist CMS in confirming that the physician or other eligible professional was qualified to order or certify the item or service that the provider or supplier furnished.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter stated that unless DHHS can provide suppliers with accurate and routine visibility to statistics (such as the supplier's error rates, enrollment file, and beneficiary complaints) that furnish an opportunity for suppliers to investigate, respond to, and correct potential deficiencies, CMS should not finalize its proposed change to § 405.809.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Much of the data the commenter refers to is either currently available to individual providers and suppliers (for example, by reviewing the provider or supplier's PECOS record) or can be made available to them upon request. However, it is ultimately the provider or supplier's responsibility to ensure that it has sufficient internal controls to detect deficiencies on its own. Providers and suppliers must be proactive in their efforts to comply with Medicare requirements. Thus, we do not believe that the commenter's contention constitutes grounds for withdrawing our proposed change to § 405.809.
                    </P>
                    <P>Given these comments and the aforementioned discussion, we are finalizing our proposed CAP provisions without modification.</P>
                    <HD SOURCE="HD3">9. Revisions to §§ 424.530(a)(5) and 424.535(a)(5)</HD>
                    <P>We also proposed to revise §§ 424.530(a)(5) and 424.535(a)(5). We stated in the proposed rule that the language in these two subsections is redundant. To illustrate, the first sentence of § 424.530(a)(5) states that a provider or supplier's Medicare enrollment may be denied if, upon on-site review or other reliable evidence, CMS determines that the provider or supplier is not operational or is not meeting Medicare enrollment requirements. Later, paragraphs § 424.530(a)(5)(i) and (a)(5)(ii) essentially repeat this language. The same repetition is evident in § 424.535(a)(5), wherein paragraphs (a)(5)(i) and (a)(5)(ii) effectively duplicate the language in the first sentence of § 424.535(a)(5).</P>
                    <P>Accordingly, we proposed to revise § 424.530(a)(5) to state that the provider or supplier's enrollment can be denied if (u)pon on-site review or other reliable evidence, CMS determines that the provider or supplier is either of the following: (1) Not operational to furnish Medicare-covered items or services; or (2) otherwise fails to satisfy any Medicare enrollment requirements. Likewise, we proposed to revise § 424.535(a)(5) to state that a provider or supplier's Medicare billing privileges would be revoked if (u)pon on-site review or other reliable evidence, CMS determines that the provider or supplier is either of the following: (1) No longer operational to furnish Medicare-covered items or services; or (2) otherwise fails to satisfy any Medicare enrollment requirements.</P>
                    <P>We also proposed to add the phrase “or other reliable evidence” to § 424.535(a)(5) for two reasons. First, § 424.530(a)(5) currently contains the “or other reliable evidence” standard, and we believe these two paragraphs (§ 424.530(a)(5) and § 424.535(a)(5)) should have consistent standards. Second, we believe it is important to be able to ascertain and take action under § 424.535(a)(5) against a non-operational or non-compliant provider or supplier through means other than a site review.</P>
                    <P>We received one comment regarding these proposed changes:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested clarification of the term “other reliable evidence” as it is used in § 424.530(a)(5) and § 424.535(a)(5).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The term means any credible evidence that demonstrates that the provider is not in compliance with Medicare requirements.
                    </P>
                    <P>Given the foregoing, we are finalizing the proposed changes discussed in section II.B.9 of this final rule albeit with one very minor technical edit. The term “enrollment requirements” will be changed to “enrollment requirement” to clarify our original intention that the provider or supplier's non-compliance with any enrollment requirement can constitute grounds for revocation.</P>
                    <HD SOURCE="HD3">10. Technical Changes</HD>
                    <P>We also proposed certain technical changes related to our provider and supplier enrollment regulations.</P>
                    <P>In § 424.530(a)(1), we proposed to change the word “section” to “subpart P” in the first sentence so that the sentence would read—“[t]he provider or supplier is determined not to be in compliance with the enrollment requirements described in this subpart P or in the enrollment application applicable for its provider or supplier type, and has not submitted a plan of corrective action as outlined in part 488 of this chapter.” The purpose of this change was to clarify that the provider or supplier must comply with all of the provider enrollment provisions in 42 CFR subpart P, not merely those in § 424.530.</P>
                    <P>For the same reason, we proposed to revise § 424.535(a)(1) to state as follows: “The provider or supplier is determined not to be in compliance with the enrollment requirements described in this subpart P or in the enrollment application applicable for its provider or supplier type, and has not submitted a plan of corrective action as outlined in part 488 of this chapter.”</P>
                    <P>
                        Also, in § 424.535(a)(3)(ii) we proposed to change the term “denials” 
                        <PRTPAGE P="72525"/>
                        to “revocations,” as § 424.535 does not address denials.
                    </P>
                    <P>Finally, § 498.5(l)(4) states that for appeals of denials based on § 424.530(a)(9) related to temporary moratoria, the scope of the review is limited to whether the temporary moratorium applies to the provider or supplier. Yet § 424.530(a)(10), rather than § 424.530(a)(9), applies to temporary moratoria. We proposed to correct § 498.5(l)(4) by changing the reference to § 424.530(a)(9) therein to § 424.530(a)(10).</P>
                    <P>We received no comments on these proposed technical changes. Therefore, we are finalizing these revisions without modification.</P>
                    <HD SOURCE="HD2">C. General and Other Comments</HD>
                    <P>We also received a number of general comments regarding the proposed rule. A summary of these comments and our responses are as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter indicated general support for the changes in this rule that expand CMS's enrollment denial authority, for this would improve CMS's ability to detect new fraud schemes. However, the commenter expressed concern that CMS's anti-fraud efforts could inadvertently harm law-abiding physicians who unintentionally make a mistake during the enrollment process—a process, the commenter believed, that has become increasingly complicated. The commenter recommended that CMS continually evaluate PECOS and remove and identify unnecessary and outdated requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although we are unclear as to the specific anti-fraud effort(s) or regulatory provision(s) of concern to the commenter, we are committed to ensuring that the enrollment process poses as minimal a burden as possible on those providers and suppliers that are conscientious about complying with Medicare requirements. We have taken steps in this direction, including—but not limited to—allowing providers and suppliers to complete CMS-855 applications via the Internet as opposed to requiring a paper application. We also, as the commenter suggested, regularly evaluate PECOS, our Program Integrity Manual instructions, and our regulations to determine whether improvements or revisions are necessary. We believe it is important and indeed necessary to strive to achieve an appropriate balance between ensuring the integrity of the Medicare Trust Funds and easing the burden on the provider and supplier communities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that CMS develop the systems and resources necessary to effectively implement our new provider enrollment requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will ensure that the resources are available and the necessary systems changes are made to implement the provider enrollment requirements outlined in this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that CMS consider sharing with other payers (both public and private) information regarding actions taken against providers pursuant to our proposed provisions (for example, revocations under § 424.535(a)(8)(ii)). The commenter stated that such dissemination of data is critical to the prevention of fraud and abuse in our nation's health care system.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter that the exchange of information between medical payers is important to the prevention of health care fraud and abuse. CMS, is working to expand the exchange of information with other payers as evidenced by its initiative, the Healthcare Fraud Prevention Partnership.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that any final decision regarding the revocation of a provider's Medicare billing privileges should come from CMS Central Office rather than from the Medicare contractor.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         For reasons mentioned earlier, we agree.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for CMS's clarification that the re-enrollment bar does not apply if a revocation is based on the provider's failure to respond timely to a revalidation request or other request for information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that physicians need more information and education on common billing and coding mistakes and better guidance on how to avoid audits. The commenters recommended that CMS: (1) Publicly release information on frequent billing and coding errors, including aggregate statistics on such errors at a local (MAC level) and national level, as well as by specialty; (2) educate providers on these errors through existing educational channels (for instance, Open Door Forum calls and MedLearn Matters articles); (3) develop a dedicated web presence for publishing the aforementioned information and an associated CMS email list-serve to disseminate new data as it becomes public; (4) provide technical assistance for physician practices—primarily those with a high volume of coding and billing errors—on how to avoid these errors, perhaps through an expanded scope of work for Medicare's quality improvement organizations (QIOs); and (5) furnish additional guidance on the myriad of Medicare rules and regulations, which the commenter believes are often burdensome and confusing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these suggestions and will continue, as necessary, to expand our outreach efforts to providers and suppliers regarding important coding and billing issues.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         With respect to §§ 424.530(a)(1) and 424.535(a)(1), a commenter stated that CMS should make available to providers various information (for example, the supplier's error rates, enrollment file, and beneficiary complaints) that would enable providers to investigate and address potential deficiencies. Only through this vehicle can a provider confirm that it is in compliance with enrollment requirements and, if necessary, take corrective action.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we stated earlier in response to a similar comment, much of this information is either currently available to the provider or can be made available upon request. Still, providers must be proactive in establishing adequate internal controls to ensure compliance with Medicare requirements; such compliance should not be contingent upon the provider first receiving substantial quantities of information from CMS.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that program integrity is best ensured when providers fully understand how to comply with complex Medicare requirements. The commenter thus urged CMS to issue final rules regarding the requirements of mandatory compliance programs (as outlined in the Affordable Care Act) as soon as possible. The commenter added that CMS should work with the OIG to update the current compliance guidance by working with industry stakeholders.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's concerns. However, the compliance plan provisions outlined in section 6401 of the Affordable Care Act are outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that if CMS sees any provider or Medicare debt as a risk and plans to do everything possible to prevent unnecessary threats to Medicare beneficiaries and the Medicare Trust Funds, this gives CMS unrestrained discretion to deny enrollment or revoke billing privileges. The proposed rule, the commenter continued, does not focus on narrowly tailoring the approach to target fraud and abuse but instead seems geared towards reducing the total number of providers (including those not engaged 
                        <PRTPAGE P="72526"/>
                        in fraudulent or abusive actions) based on CMS's apparent belief that doing so will concomitantly reduce fraud and abuse.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have repeatedly stated in numerous forums and throughout this rule that the overwhelming majority of Medicare providers and suppliers submit claims that meet Medicare requirements. It is not CMS's overriding objective to reduce the total number of Medicare providers and suppliers. Nonetheless, a small percentage of providers and suppliers are engaging in fraudulent, wasteful, inappropriate, or abusive activities. Our provider enrollment revisions are directed at such providers and suppliers, and we believe that removing them, as necessary, from the Medicare program will only serve to benefit Medicare beneficiaries, the Trust Funds, the taxpayers, and the hundreds of thousands of legitimate Medicare providers and suppliers that have proven to be reliable partners of the program.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that the proposed rule would give CMS's contractors unprecedented discretion to revoke Medicare billing privileges. The commenter also stated that CMS must clearly articulate the appeal rights that providers have in revocation cases.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated previously, a MAC must receive prior CMS approval before revoking a provider's Medicare billing privileges. With respect to appeal rights in revocation cases, these are outlined in 42 CFR part 498 and in CMS Publication 100-08, chapter 15.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter supported the proposed rule's intent to reduce the time necessary to institute a recovery of Medicare funds for a provider who has submitted bad or faulty billings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support for our anti-fraud efforts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter urged CMS to amend its opt-out policy to allow physicians to opt-out of the Medicare program without a requirement to reaffirm the opt-out. After the 2-year minimum required by law, the commenter explained, the opt-out period should be effective indefinitely unless and until the physician chooses to terminate his or her opt-out status and private contracts with patients in order to rejoin Medicare as a participating or non-participating physician.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This comment is outside the scope of this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned why Medicaid was excluded from the scope of our proposed rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have chosen to address only Medicare enrollment in this rule, though Medicaid enrollment may be addressed in the future.
                    </P>
                    <HD SOURCE="HD1">III. Provisions of the Final Rule</HD>
                    <HD SOURCE="HD2">A. Incentive Reward Program</HD>
                    <P>In light of the complexity of the operational aspects of our proposal, we are not finalizing our proposed IRP provisions in this rule. We may finalize them in future rulemaking.</P>
                    <HD SOURCE="HD2">B. Enrollment Provisions</HD>
                    <P>Based on public comments, we are finalizing our proposed provider enrollment provisions with the following revisions:</P>
                    <P>• In § 424.502, we are modifying paragraph (2) of the definition of “Enroll/Enrollment” to read as follows: Except for those suppliers who complete the CMS-855O form, CMS-identified equivalent, successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, validating the provider or supplier's eligibility to provide items or services to Medicare beneficiaries.</P>
                    <P>• In § 424.510, we are redesignating the first two sentences of existing paragraph (a) as new paragraph (a)(1).</P>
                    <P>++ Revising the third sentence of existing paragraph (a) and redesignating as new paragraph (a)(2). The new paragraph (a)(2) will state the following: To be enrolled to furnish Medicare-covered items and services, a provider or supplier must meet the requirements specified in paragraphs (d) and (e) of this section.</P>
                    <P>++ Adding a new paragraph (a)(3) that states the following: To be enrolled solely to order and certify Medicare items or services, a physician or non-physician practitioner must meet the requirements specified in paragraph (d) of this section except for paragraphs (2)(iii)(B), (2)(iv), (3)(ii), (5), (6), and (9).</P>
                    <P>• In § 424.521, we are revising paragraph (a) to include ambulance suppliers.</P>
                    <P>• In § 424.530 we are making the following revisions:</P>
                    <P>++ Revising § 424.530(a)(3).</P>
                    <P>++ In § 424.530(a)(5), we are changing “requirements” to “requirement.”</P>
                    <P>—Paragraph (a)(6)(ii)(A) we are revising the sentence to state that the owner left the provider or supplier with the Medicare debt within 1 year before or after that provider or supplier's voluntary termination, involuntary termination or revocation.</P>
                    <P>—In paragraph (a)(6)(ii)(C)—</P>
                    <P>—Adding additional language to the introductory text, a second sentence that reads: In making this determination, we consider the following factors.</P>
                    <P>
                        —Adding new paragraphs (a)(6)(ii)(C)(
                        <E T="03">1</E>
                        ) through (
                        <E T="03">5</E>
                        )
                    </P>
                    <P>—In § 424.530(a)(6)(iii), we are making the following changes:</P>
                    <P>—Combining proposed paragraphs (A) and (B)(1)</P>
                    <P>
                        —Redesignating proposed paragraph (a)(6)(iii) as new paragraph (B)(
                        <E T="03">2</E>
                        ).
                    </P>
                    <P>• In § 424.535 we are making the following revisions:</P>
                    <P>++ Revising paragraph (a)(3).</P>
                    <P>++ In § 424.535(a)(5), we are changing “requirements” to “requirement.”</P>
                    <P>++ Adding paragraphs A through F to paragraph (a)(8)(ii).</P>
                    <HD SOURCE="HD1">IV. Collection of Information Requirements</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995, we are required to provide 30-day notice in the 
                        <E T="04">Federal Register</E>
                         and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. In order to fairly evaluate whether an information collection should be approved by OMB, section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires that we solicit comment on the following issues:
                    </P>
                    <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency.</P>
                    <P>• The accuracy of our estimate of the information collection burden.</P>
                    <P>• The quality, utility, and clarity of the information to be collected.</P>
                    <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques. We are soliciting public comment on each of these issues for the following sections of this document that contain information collection requirements (ICRs):</P>
                    <HD SOURCE="HD2">A. ICRs Regarding the Definition of Enrollment (§ 424.502, § 424.505, and § 424.510)</HD>
                    <P>
                        Our revisions to § 424.502, § 424.505, and § 424.510 reflect the existing usage of the CMS-855O (OMB Approval number 0938-0685) and, as such, will not impose any additional information collection burden. Consistent with § 424.507, an individual who wishes to enroll in Medicare for the sole purpose of ordering or certifying items or services for Medicare beneficiaries can become eligible to do so by completing the CMS-855O. Use of the CMS-855O commenced in July 2011, and OMB at that time approved the information collection burden associated with its use. The CMS-855O is approved under 
                        <PRTPAGE P="72527"/>
                        OMB control number 0938-1135 and expires August 31, 2015.
                    </P>
                    <HD SOURCE="HD2">B. ICRs Regarding the Debts to Medicare (§ 424.530(a)(6))</HD>
                    <P>Our revisions to § 424.530(a)(6) will likely result in an increase in application denials. While these revisions will not directly impose an information collection burden, the increase in denials could lead to more appeals from denied providers and suppliers. However, we are unable to estimate the number of possible denials because we do not have data available that can support such an estimate. Accordingly, we cannot project the potential information collection burden that could arise from an increased number of: (1) Appeals of denials; or (2) resubmitted enrollment applications from the denied providers and suppliers.</P>
                    <HD SOURCE="HD2">C. ICRs Regarding the Felony Convictions (§§ 424.530(a)(3) and 424.535(a)(3))</HD>
                    <P>Although our revisions to §§ 424.530(a)(3) and 424.535(a)(3) do not directly impose paperwork burdens, they will likely result in an increase in application denials and revocations, respectively. Yet we cannot estimate the potential increase in denials and revocations based on these changes, for we do not have data available that can support such an estimate. Therefore, we are unable to project the potential information collection burden that may result from an increased number of appeals of denials and revocations.</P>
                    <HD SOURCE="HD2">D. ICRs Regarding the Abuse of Billing Privileges (§ 424.535(a)(8)(ii))</HD>
                    <P>Our addition of § 424.535(a)(8)(ii) will likely lead to an increase in the information collection burden because there will be a concomitant increase in revocations and associated appeals. However, we are unable to estimate the number of potential revocations. We do not have data available that can help us make such an estimate, for each situation will have to be reviewed and addressed on a case-by-case basis.</P>
                    <HD SOURCE="HD2">E. ICRs Regarding the Post-Revocation Submission of Claims (§ 424.535(h))</HD>
                    <P>We do not believe that our revisions to § 424.535(h) will result in a change in the information collection burden. While the claims in question will need to be submitted within a shorter timeframe (60 days), they will likely be submitted regardless of the applicable submission period. The shorter timeframe will, in general, neither increase nor decrease the number of claims submitted.</P>
                    <HD SOURCE="HD2">F. ICRs Regarding the Effective Date of Billing Privileges (§ 424.520(d))</HD>
                    <P>Our revisions to § 424.520(d) will most likely result in a decrease in the information collection burden because fewer claims will be eligible for submission under this change. Yet we are unable to project the extent of the decrease in the number of claims because we do not have data available to support such an estimate. Therefore, we cannot estimate the decrease in the information collection burden.</P>
                    <HD SOURCE="HD2">G. ICRs Regarding the Effective Date of Re-Enrollment Bar (§ 424.535(c))</HD>
                    <P>We believe that our revisions to § 424.535(c) will neither increase nor decrease the information collection burden. With or without this revision, the provider will still need to submit the applicable CMS-855 application (based on the provider or supplier type involved) after the expiration of the re-enrollment bar in order to enroll again in Medicare.</P>
                    <HD SOURCE="HD2">H. ICRs Regarding the Corrective Action Plans (§ 405.809)</HD>
                    <P>Our revisions to § 405.809 will result in a decrease in the information collection burden because there will be a reduction in the number of CAPs submitted. However, we are unable to project the extent of the decrease in submitted CAPs because we do not have sufficient data to support such an estimate.</P>
                    <HD SOURCE="HD2">I. ICRs Regarding the Revisions to § 424.530(a)(5) and § 424.535(a)(5)</HD>
                    <P>Our revisions to §§ 424.530(a)(5) and 424.535(a)(5) will not result in a change to the information collection burden, for we do not believe there will be any change in the number of denials or revocations, respectively. We note that § 424.530(a)(5) already permits revocation based upon a site review “or other reliable evidence.” Thus, we do not foresee any change in the number of: (1) Appeals of denials, or (2) resubmitted enrollment applications from denied providers and suppliers. As for § 424.535(a)(5), the “or other reliable evidence” standard is not in the current version of that paragraph. But we note that § 424.535(a)(1) permits revocation if the provider or supplier is determined not to be in compliance with the enrollment requirements in this section, or in the enrollment application that is applicable to its provider or supplier type. Therefore, the authority to revoke based on reliable evidence of non-compliance is largely similar to the reasons for revocation stated in § 424.535(a)(1). Hence, we do not believe there will be any change in the number of: (1) Appeals of revocations; or (2) resubmitted enrollment applications from revoked providers and suppliers.</P>
                    <P>The aforementioned burden projections for our provider enrollment revisions are identical to those we proposed and on which we solicited comments. We received no comments on these estimates.</P>
                    <HD SOURCE="HD1">V. Regulatory Impact Analysis</HD>
                    <HD SOURCE="HD2">A. Statement of Need</HD>
                    <P>This final rule is necessary to make important revisions to certain Medicare provider enrollment requirements in order to strengthen our program integrity efforts and to help ensure that fraudulent parties neither enroll in nor maintain their enrollment in the Medicare program.</P>
                    <HD SOURCE="HD2">B. Overview</HD>
                    <P>We have examined the impacts of this rule as required by Executive Order 12866 on Regulatory Planning and Review (September 30, 1993), Executive Order 13563 on Improving Regulation and Regulatory Review (January 18, 2011), the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, section 202 of the Unfunded Mandates Reform Act of 1995 (March 22, 1995; Pub. L. 104-4) and Executive Order 13132 on Federalism (August 4, 1999).</P>
                    <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). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year).</P>
                    <P>
                        As explained in more detail later in this section, we encountered several uncertainties in estimating the economic impact of many of our final provisions. We could not estimate the number of denials and revocations that might stem from the finalized enrollment changes. We were also unable to estimate the potential monetary savings to the federal government or the costs to providers and suppliers resulting from the remaining finalized revisions. However, we estimate that our change to § 424.520(d) will result in an annual transfer of more than $100 million from providers and suppliers to the federal government. Therefore, we have 
                        <PRTPAGE P="72528"/>
                        prepared an RIA because this is a major rule.
                    </P>
                    <P>The RFA requires agencies to analyze options for regulatory relief for small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organization, and small governmental jurisdictions. Most entities and most other providers and suppliers are small entities, either by nonprofit status or by having revenues below Small Business Administration thresholds that range from $7 million and $35.5 million per year. Individuals and states are not included in the definition of a small entity.</P>
                    <P>As we stated in the proposed rule, several provisions will have at least some effect on certain small entities. These include: (1) The changes at § 424.520(d) to the effective date of billing privileges for ambulance suppliers; (2) the changes at § 424.530(a)(6) regarding Medicare debt; (3) the addition of § 424.535(a)(8)(ii) concerning patterns or practices of non-compliant claim submissions; (4) the revision of § 424.535(h) regarding the submission of claims after revocation; and (5) the revision of § 405.809 concerning the reinstatement of provider or supplier billing privileges following corrective action. Yet as discussed later in this section, we do not believe that this final rule will have a significant economic impact on a substantial number of small entities.</P>
                    <P>Section 424.520(d), which changes the effective date of billing privileges for ambulance suppliers, will only impact newly-enrolling ambulance suppliers. Each year, new ambulance providers constitute only a very small addition to the overall universe of the roughly 1.4 million Medicare-enrolled providers and suppliers—an average of 1,127 ambulance suppliers enrolled in Medicare each year between 2006 and 2011. We further note that this provision will not affect their ability to bill for services furnished after the later of the two events specified in § 424.520(d)(1) and (2).</P>
                    <P>Denials and revocations under, respectively, § 424.530(a)(6) and § 424.535(a)(8), will not occur until after a careful examination by CMS of: (1) The level of undue risk that the unpaid debt poses; or (2) the criteria for determining whether the provider or supplier has a pattern or practice of submitting non-compliant claims. As such, while we anticipate an increase in some denials and revocations under these two provisions, we do not believe they will impact a substantial number of small entities.</P>
                    <P>Our revisions to § 424.535(h) will not have a significant impact on small businesses because: (1) Only a small number of Medicare providers and suppliers have their billing privileges revoked; and (2) the revoked provider's claims will likely be submitted regardless of the shorter submission period.</P>
                    <P>Our revisions to § 405.809 will impact the ability of some small entities to submit CAPs in response to a revocation. However, these entities will still be able to file a request for reconsideration. The overall effect of this change will thus not impact a substantial number of small entities.</P>
                    <P>In short, we believe that the vast majority of providers and suppliers—both small and large—do not commit fraud, have not been convicted of a felony, and are otherwise compliant with Medicare enrollment requirements. Consequently, they will not be affected by most of the provisions in this rule.</P>
                    <P>Section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital that is located outside of a Metropolitan Statistical Area for Medicare payment regulations and has fewer than 100 beds. We are not preparing an analysis for section 1102(b) of the Act because we have determined and the Secretary certified that this final rule will not have a significant impact on the operations of a substantial number of small rural hospitals.</P>
                    <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. In 2014, this is approximately $141 million. We believe that this final rule will have no consequential effect on state, local or tribal governments or on the private sector.</P>
                    <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a proposed rule (and subsequent final rule) that imposes substantial direct requirements or costs on state and local governments, preempts state law, or otherwise has federalism implications. Since this regulation does not impose any costs on state or local governments, the requirements of Executive Order 13132 are not applicable.</P>
                    <HD SOURCE="HD2">C. Anticipated Effects</HD>
                    <P>We indicated in section IV. of this final rule that there may be an ICR burden associated with several of our provider enrollment provisions but that the burden cannot be estimated. The following sections discuss other potential costs—as well as savings—associated with our enrollment changes.</P>
                    <HD SOURCE="HD3">1. Definition of Enrollment</HD>
                    <P>As stated earlier, use of the CMS-855O commenced in July 2011. Our revisions to §§ 424.502, 424.505, and 424.510 are intended to clarify that the CMS-855O does not convey billing privileges. As such, these changes will not result in any additional costs or savings.</P>
                    <HD SOURCE="HD3">2. Debts to Medicare</HD>
                    <P>Our revisions to § 424.530(a)(6) will likely result in additional application denials. Yet we are unable to estimate the number of potential denials because we do not have data available to support such an estimate. Therefore, we cannot project any costs in possible lost billings to providers and suppliers or any associated potential savings to the government.</P>
                    <P>While there may be an increase in costs to the federal government from identifying and making available to enrollment contractors information about individuals that were associated with a revoked entity with an unpaid Medicare debt, we are unable to estimate the magnitude of any such increase. We also anticipate that an increase in costs will be offset by savings to the government—(1) in preventing billing by such providers and suppliers, and (2) the repayment of debt by these providers and suppliers.</P>
                    <HD SOURCE="HD3">3. Felony Convictions</HD>
                    <P>As stated in section IV.B. of this final rule, our revisions to § 424.530(a)(3) and § 424.535(a)(3) will likely result in additional application denials and revocations, respectively. However, we are unable to estimate the potential increase in denials and revocations and associated appeals, for we do not have sufficient information to support such a projection. Thus, we cannot project the potential costs to providers and suppliers in lost billings or the potential costs or savings to the government arising from these revisions.</P>
                    <HD SOURCE="HD3">4. Abuse of Billing Privileges</HD>
                    <P>
                        Our addition of § 424.535(a)(8)(ii) will likely result in an increase in revocations. Yet we are unable to project the number of providers and suppliers that might be revoked based on this change because we do not have data 
                        <PRTPAGE P="72529"/>
                        available to help us make such an estimate. Thus, we cannot forecast the potential costs to providers and suppliers in lost billings or the possible costs or savings to the government arising from this provision.
                    </P>
                    <HD SOURCE="HD3">5. Post-Revocation Submission of Claims</HD>
                    <P>Our revision to § 424.535(h) is unlikely to increase or decrease the number of claims submitted. While the revoked provider or supplier's claims will need to be submitted within a shorter timeframe, we believe that the vast majority of claims will still be submitted. Therefore, we project only a negligible change in costs to providers and suppliers in their claim submissions.</P>
                    <HD SOURCE="HD3">6. Effective Date of Billing Privileges</HD>
                    <P>The revisions to § 424.520(d) will likely result in a decrease in claims submitted to Medicare. Rather than being able to bill for Medicare services furnished up to 12 months prior to enrollment, newly enrolling ambulance suppliers will be unable to bill for services furnished prior to the later of: (1) The date of filing a Medicare enrollment application that was subsequently approved; or (2) the date the supplier first began furnishing services at a new practice location.</P>
                    <P>According to our statistics, and as stated earlier, an average of 1,127 ambulance suppliers enrolled in Medicare each year between 2006 and 2011. We will use this figure in our calculations. As a result of our revisions, these suppliers could lose up to 10 months in potential Medicare billings for services furnished prior to the later of the two events cited in § 424.520(d).</P>
                    <P>Based on our data, the average ambulance supplier receives approximately $581,000 in Medicare payments per year, though this of course varies by individual supplier. Ten-twelfths of this amount (that is, 10 months divided by 12 months) is $484,167. Thus, we estimate that up to $545.7 million each year (or $484,167 × 1,127) in savings to the federal government could accrue as a result of this change.</P>
                    <P>We emphasize that our $545.7 million estimate is a high-end estimate. There may be new ambulance suppliers that, absent our change to § 424.520(d), would have met our requirements less than 10 months prior to enrollment. For instance, if the average newly enrolling ambulance supplier would have met our requirements 3 months prior to enrollment, the potential savings would be roughly $163.7 million (or $581,000 × 3/12 × 1,127). If the average figure is 6 months, our projection would be approximately $327.4 million. We have no way of predicting the ratio of ambulance suppliers that would have met our requirements 10 months, 6 months or 3 months (or any other point) prior to enrollment. Therefore, we will use these three timeframes as, respectively, high-end, primary, and low-end estimates in the accounting statement.</P>
                    <HD SOURCE="HD3">7. Effective Date of Re-Enrollment Bar</HD>
                    <P>Our revisions to § 424.535(c) will result in a longer re-enrollment bar than that which currently exists in cases where the basis of the revocation occurs months before the issuance of the revocation letter. The longer period during which a provider or supplier is unable to re-enroll in Medicare may result in lost billings to the provider or supplier. This may also lead to savings to the government because a provider or supplier that may have been billing Medicare will not be eligible to do so as soon as would otherwise be the case. However, we are unable to project the possible costs to providers and suppliers or the savings to the federal government because we do not have data available to support such estimates. We also cannot estimate: (1) How many providers and suppliers will be affected by this proposed change; or (2) the specific types of providers and suppliers that will be affected.</P>
                    <HD SOURCE="HD3">8. Corrective Action Plans</HD>
                    <P>Our revisions to § 405.809 will result in a reduction in the number of CAPs submitted, as noted in the ICR. This may result in lost billings to the provider or supplier in cases where CMS' acceptance of a CAP has occurred more quickly than a reversal of the revocation at the appeals level, as the CAP review process often takes place sooner than the reconsideration process. The reduction in the submission of CAPs will probably also result in a savings to the federal government due to a decrease in the resources needed to review the CAPs. However, we cannot estimate the potential lost billings of providers or suppliers resulting from this proposed provision, or the savings to the federal government. We do not have data that can assist us in predicting: (1) The number of provider and suppliers that our proposed change will impact; or (2) the specific types of providers and suppliers that will be affected.</P>
                    <HD SOURCE="HD3">9. Revisions to § 424.530(a)(5) and § 424.535(a)(5)</HD>
                    <P>We stated earlier that we do not believe there will be any change in the total number of denials or revocations based on our revisions to §§ 424.530(a)(5) and 424.535(a)(5). Therefore, we do not anticipate any resultant change in overall costs or savings.</P>
                    <HD SOURCE="HD3">10. Technical Changes</HD>
                    <P>As these are simply technical revisions, there are no costs or savings associated with these provisions.</P>
                    <HD SOURCE="HD2">D. Comments Received and Conclusion</HD>
                    <P>While we were unable—and remain unable—to furnish detailed cost and savings estimates for many of our enrollment revisions, we solicited comments from the public regarding their views as to the potential burdens and costs of our proposals as well as the possible savings. We received several comments, which are summarized and accompanied by our responses as follows:</P>
                    <P>
                        <E T="03">Comment:</E>
                         With respect to our savings estimates for the proposed change to § 424.520(d), a few commenters believed that our projections were inflated and that actual data (as opposed to estimates) should be used. One of the commenters suggested that CMS use data regarding Medicare payments made for services furnished prior to the submission of the CMS-855B. The other commenter recommended that CMS calculate the actual payments made to new ambulance suppliers after January 1, 2011, for this is the date on which CMS began limiting payments to suppliers to 12 months from the date of service per § 424.520(d).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We indeed based our estimates on actual data—specifically, the actual average amount of payments a Medicare-enrolled ambulance supplier receives per year. As we indicated in the proposed rule, we cannot predict the number of ambulance suppliers that would have met CMS's requirements at various points (for example, 3 months; 10 months) prior to enrollment. Therefore, we can only furnish high-end, primary, and low-end estimates. Despite the commenters' request for greater monetary specificity, we believe that our estimates are reasonable.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern that CMS did not furnish more detailed monetary estimates of the rule's potential impact on providers and beneficiaries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we explained in both sections III. and IV. of the proposed rule, we were unable to formulate 
                        <PRTPAGE P="72530"/>
                        detailed workload, cost, or savings projections for many of our provisions because—(1) the necessary background data were not available; and (2) future behavior often cannot be predicted. Thus, we solicited feedback from the public that could perhaps assist us in developing quantifiable, numerical estimates, though we received very few comments in response to our request. Therefore, we are finalizing our proposed projections while reiterating our inability to develop estimates with respect to other provisions.
                    </P>
                    <P>In light of these comments, we are finalizing the estimates as previously outlined.</P>
                    <HD SOURCE="HD2">E. Accounting Statement and Table</HD>
                    <P>
                        As required by OMB Circular A-4 (available at link 
                        <E T="03">http://www.whitehouse.gov/sites/default/files/omb/assets/regulatory_matters_pdf/a-4.pdf</E>
                        ), we have prepared an accounting statement.
                    </P>
                    <P>The “transfer” category in Table 2 reflects the application of a 7 percent and 3 percent annualized rate to the high-end, primary, and low-end estimates referred to in section IV.C.2.f. of this final rule and involving our change to § 424.520(d).</P>
                    <P>The 7 and 3 percent figures were applied over a 10-year period beginning in 2013, with the figures in the accounting statement reflecting the average annualized costs over this period.</P>
                    <P>The accounting statement does not address the potential financial benefits of this proposed rule from the standpoint of its effectiveness in preventing or deterring certain providers and suppliers from enrolling in Medicare or maintaining their enrollment in Medicare. It is not possible for us to quantify these benefits in monetary terms. In addition, the statement does not include those provisions previously discussed that may result in a cost or savings that nevertheless cannot be estimated.</P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,10,10,10,10,10,10">
                        <TTITLE>Table 2—Accounting Statement and Table</TTITLE>
                        <TDESC>[In millions]</TDESC>
                        <BOXHD>
                            <CHED H="1">Category</CHED>
                            <CHED H="1">
                                Primary 
                                <LI>estimates</LI>
                            </CHED>
                            <CHED H="1">
                                Low 
                                <LI>estimates</LI>
                            </CHED>
                            <CHED H="1">
                                High 
                                <LI>estimates</LI>
                            </CHED>
                            <CHED H="1">Year dollars</CHED>
                            <CHED H="1">Discount rate</CHED>
                            <CHED H="1">
                                Period 
                                <LI>covered</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">Transfers:</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="03">Resulting from the change in the effective date of billing privileges for ambulance suppliers</ENT>
                            <ENT>
                                327.4 
                                <LI>327.4</LI>
                            </ENT>
                            <ENT>
                                163.7 
                                <LI>163.7</LI>
                            </ENT>
                            <ENT>
                                545.7 
                                <LI>545.7</LI>
                            </ENT>
                            <ENT>
                                2013 
                                <LI>2013</LI>
                            </ENT>
                            <ENT>
                                7% 
                                <LI>3%</LI>
                            </ENT>
                            <ENT>
                                2014-2023 
                                <LI>2014-2023</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">From Whom to Whom</ENT>
                            <ENT A="05">Transfers from Ambulance Suppliers to Federal Government.</ENT>
                        </ROW>
                        <TNOTE>* Rounded to the nearest hundred-thousandth.</TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">F. Alternatives Considered</HD>
                    <P>As stated, our provider enrollment provisions are needed to help ensure that fraudulent parties do not enroll in or maintain their enrollment in the Medicare program. Nonetheless, we did consider four alternatives when preparing our enrollment provisions.</P>
                    <P>First, with respect to § 424.530(a)(6)(i) and (ii), we considered and elected to propose and finalize an exception to these denial reasons for providers, suppliers, and owners thereof that have agreed to an extended repayment schedule. We believe that such an agreement indicates a willingness to satisfy the debt.</P>
                    <P>Second, we considered expanding the scope of § 424.520(d) to include all certified providers and certified suppliers. Yet as we explained previously, there already: (1) Is an exhaustive and extensive review process for certified providers and certified suppliers, and (2) are limitations posed by § 489.13 on the ability of such providers and suppliers to “backbill” for services.</P>
                    <P>Third, we contemplated eliminating CAPs altogether, as the existing appeals process affords providers and suppliers adequate due process rights. In the interests of fairness and efficiency, we elected to retain the CAP process for revocations based on § 424.535(a)(1). We believe this will continue to give certain providers and suppliers an additional opportunity to remedy inadvertent or minor errors without subjecting all parties to the lengthier appeals process, although we continue to believe that eliminating the CAP process for all other revocation reasons is warranted.</P>
                    <HD SOURCE="HD2">G. Impact on Beneficiary Access</HD>
                    <P>We do not believe that our finalized provisions will impact beneficiary access. While some providers and suppliers may have their Medicare enrollment applications denied or their Medicare billing privileges revoked as a result of these provisions, we believe this number will be small.</P>
                    <P>In accordance with the provisions of Executive Order 12866, this final rule was reviewed by the Office of Management and Budget.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>42 CFR Part 405</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health professions. Kidney diseases, Medical devices, Medicare, Reporting and recordkeeping requirements, Rural areas, X-rays.</P>
                        <CFR>42 CFR Part 424</CFR>
                        <P>Emergency medical services, Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 498</CFR>
                        <P>Administrative practice and procedure, Health facilities, Health professions Medicare, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <P>For the reasons stated in the preamble of this final rule, the Centers for Medicare &amp; Medicaid Services amends 42 CFR chapter IV as follows:</P>
                    <REGTEXT TITLE="42" PART="405">
                        <PART>
                            <HD SOURCE="HED">PART 405—FEDERAL HEALTH INSURANCE FOR THE AGED AND DISABLED</HD>
                        </PART>
                        <AMDPAR>1. The authority for part 405 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>Secs. 205(a), 1102, 1861, 1862(a), 1869, 1871, 1874, 1881, and 1886(k) of the Social Security Act (42 U.S.C. 405(a), 1302, 1395x, 1395y(a), 1395ff, 1395hh, 1395kk, 1395rr and 1395ww(k)), and sec. 353 of the Public Health Service Act (42 U.S.C. 263a).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="405">
                        <AMDPAR>2. Section 405.809 is revised to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 405.809 </SECTNO>
                            <SUBJECT>Reinstatement of provider or supplier billing privileges following corrective action.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General rule.</E>
                                 A provider or supplier—
                            </P>
                            <P>
                                (1) May only submit a corrective action plan for a revocation for 
                                <PRTPAGE P="72531"/>
                                noncompliance under § 424.535(a)(1) of this chapter; and
                            </P>
                            <P>(2) Subject to paragraph (a)(1) of this section, has only one opportunity to correct all deficiencies that served as the basis of its revocation through a corrective action plan.</P>
                            <P>
                                (b) 
                                <E T="03">Review of a corrective action plan.</E>
                                 Subject to paragraph (a)(1) of this section, CMS or its contractor reviews a submitted corrective action plan and does either of the following:
                            </P>
                            <P>(1) Reinstates the provider or supplier's billing privileges if the provider or supplier provides sufficient evidence to CMS or its contractor that it has complied fully with the Medicare requirements, in which case—</P>
                            <P>(i) The effective date of the reinstatement is based on the date the provider or supplier is in compliance with all Medicare requirements; and</P>
                            <P>(ii) CMS or its contractor may pay for services furnished on or after the effective date of the reinstatement.</P>
                            <P>(2) Refuses to reinstate a provider or supplier's billing privileges. The refusal of CMS or its contractor to reinstate a provider or supplier's billing privileges based on a corrective action plan is not an initial determination under part 498 of this chapter.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <PART>
                            <HD SOURCE="HED">PART 424—CONDITIONS FOR MEDICARE PAYMENT</HD>
                        </PART>
                        <AMDPAR>3. The authority for part 424 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <AMDPAR>4. In § 424.502, the definition of “Enroll/Enrollment” is amended by revising the introductory text and paragraphs (2) and (4) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.502 </SECTNO>
                            <SUBJECT>Definitions</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Enroll/Enrollment</E>
                                 means the process that Medicare uses to establish eligibility to submit claims for Medicare-covered items and services, and the process that Medicare uses to establish eligibility to order or certify Medicare-covered items and services. The process includes—
                            </P>
                            <STARS/>
                            <P>(2) Except for those suppliers that complete the CMS-855O form, CMS-identified equivalent, successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, validating the provider or supplier's eligibility to provide items or services to Medicare beneficiaries;</P>
                            <STARS/>
                            <P>(4) Except for those suppliers that complete the CMS-855O form, CMS-identified equivalent, successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services, granting the Medicare provider or supplier Medicare billing privileges.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <SECTION>
                            <SECTNO>§ 424.505 </SECTNO>
                            <SUBJECT>[Amended]</SUBJECT>
                        </SECTION>
                        <AMDPAR>5. Section 424.505 is amended by removing the phrase “Once enrolled, the provider or supplier receives” and adding in its place the phrase “Except for those suppliers that complete the CMS-855O form or CMS-identified equivalent, successor form or process for the sole purpose of obtaining eligibility to order or certify Medicare-covered items and services; once enrolled the provider or supplier receives”.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <AMDPAR>6. Section 424.510 is amended by revising paragraph (a) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.510 </SECTNO>
                            <SUBJECT>Requirements for enrolling in the Medicare program.</SUBJECT>
                            <P>(a)(1) Providers and suppliers must submit enrollment information on the applicable enrollment application. Once the provider or supplier successfully completes the enrollment process, including, if applicable, a State survey and certification or accreditation process, CMS enrolls the provider or supplier into the Medicare program.</P>
                            <P>(2) To be enrolled to furnish Medicare-covered items and services, a provider or supplier must meet the requirements specified in paragraphs (d) and (e) of this section.</P>
                            <P>(3) To be enrolled solely to order and certify Medicare items or services, a physician or non-physician practitioner must meet the requirements specified in paragraph (d) of this section except for paragraphs (d)(2)(iii)(B), (d)(2)(iv), (d)(3)(ii), and (d)(5), (6), and (9) of this section.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <AMDPAR>7. Section 424.520 is amended by revising paragraph (d) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.520 </SECTNO>
                            <SUBJECT>Effective date of Medicare billing privileges.</SUBJECT>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Physicians, non-physician practitioners, physician and non-physician practitioner organizations, and ambulance suppliers.</E>
                                 The effective date for billing privileges for physicians, non-physician practitioners, physician and non-physician practitioner organizations, and ambulance suppliers is the later of—
                            </P>
                            <P>(1) The date of filing of a Medicare enrollment application that was subsequently approved by a Medicare contractor; or</P>
                            <P>(2) The date that the supplier first began furnishing services at a new practice location.</P>
                        </SECTION>
                        <AMDPAR>8. Section 424.521 is revised to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.521 </SECTNO>
                            <SUBJECT>Request for payment by physicians, non-physician practitioners, physician and non-physician organizations, and ambulance suppliers.</SUBJECT>
                            <P>(a) Physicians, non-physician practitioners, physician and non-physician practitioner organizations, and ambulance suppliers may retrospectively bill for services when the physician, non-physician practitioner, physician or non-physician organization, and ambulance supplier has met all program requirements, including State licensure requirements, and services were provided at the enrolled practice location for up to—</P>
                            <P>(1) Thirty days prior to their effective date if circumstances precluded enrollment in advance of providing services to Medicare beneficiaries; or</P>
                            <P>(2) Ninety days prior to their effective date if a Presidentially-declared disaster under the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (Stafford Act) precluded enrollment in advance of providing services to Medicare beneficiaries.</P>
                            <P>(b) [Reserved]</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <AMDPAR>9. Section 424.530 is amended by revising paragraphs (a)(1), (a)(3) introductory text and (a)(3)(i), and (a)(5) and (6) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.530 </SECTNO>
                            <SUBJECT>Denial of enrollment in the Medicare program</SUBJECT>
                            <P>(a) * * *</P>
                            <P>
                                (1) 
                                <E T="03">Noncompliance.</E>
                                 The provider or supplier is determined to not be in compliance with the enrollment requirements in this subpart P or in the enrollment application applicable for its provider or supplier type, and has not submitted a plan of corrective action as outlined in part 488 of this chapter.
                            </P>
                            <STARS/>
                            <P>
                                (3) 
                                <E T="03">Felonies.</E>
                                 The provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a Federal or State felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries.
                            </P>
                            <P>(i) Offenses include, but are not limited in scope or severity to—</P>
                            <P>(A) Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                            <P>
                                (B) Financial crimes, such as extortion, embezzlement, income tax 
                                <PRTPAGE P="72532"/>
                                evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.
                            </P>
                            <P>(C) Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                            <P>(D) Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.</P>
                            <STARS/>
                            <P>
                                (5) 
                                <E T="03">On-site review.</E>
                                 Upon on-site review or other reliable evidence, CMS determines that the provider or supplier:
                            </P>
                            <P>(i) Is not operational to furnish Medicare-covered items or services; or</P>
                            <P>(ii) Otherwise fails to satisfy any Medicare enrollment requirement.</P>
                            <P>
                                (6) 
                                <E T="03">Medicare debt.</E>
                                 (i) The enrolling provider, supplier, or owner thereof (as defined in § 424.502), has an existing Medicare debt.
                            </P>
                            <P>(ii) The enrolling provider, supplier, or owner (as defined in § 424.502) thereof was previously the owner (as defined in § 424.502) of a provider or supplier that had a Medicare debt that existed when the latter's enrollment was voluntarily terminated, involuntarily terminated, or revoked, and all of the following criteria are met:</P>
                            <P>(A) The owner left the provider or supplier with the Medicare debt within 1 year before or after that provider or supplier's voluntary termination, involuntary termination or revocation.</P>
                            <P>(B) The Medicare debt has not been fully repaid.</P>
                            <P>(C) CMS determines that the uncollected debt poses an undue risk of fraud, waste, or abuse. In making this determination, CMS considers the following factors:</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) The amount of the Medicare debt.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) The length and timeframe that the enrolling provider, supplier, or owner thereof was an owner of the prior entity.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) The percentage of the enrolling provider, supplier, or owner's ownership of the prior entity.
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) Whether the Medicare debt is currently being appealed.
                            </P>
                            <P>
                                (
                                <E T="03">5</E>
                                ) Whether the enrolling provider, supplier, or owner thereof was an owner of the prior entity at the time the Medicare debt was incurred.
                            </P>
                            <P>(iii) A denial of Medicare enrollment under this paragraph (a)(6) can be avoided if the enrolling provider, supplier or owner thereof does either of the following:</P>
                            <P>
                                (A)(
                                <E T="03">1</E>
                                ) Satisfies the criteria set forth in § 401.607; and
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Agrees to a CMS-approved extended repayment schedule for the entire outstanding Medicare debt.
                            </P>
                            <P>(B) Repays the debt in full.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="424">
                        <AMDPAR>10. Section 424.535 is amended by revising paragraphs (a)(1) introductory text, (a)(3), (a)(5), (a)(8), (c), and (h) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 424.535 </SECTNO>
                            <SUBJECT>Revocation of enrollment and billing privileges in the Medicare program.</SUBJECT>
                            <STARS/>
                            <P>(a) * * *</P>
                            <P>
                                (1) 
                                <E T="03">Noncompliance.</E>
                                 The provider or supplier is determined to not be in compliance with the enrollment requirements described in this subpart P or in the enrollment application applicable for its provider or supplier type, and has not submitted a plan of corrective action as outlined in part 488 of this chapter. The provider or supplier may also be determined not to be in compliance if it has failed to pay any user fees as assessed under part 488 of this chapter.
                            </P>
                            <STARS/>
                            <P>
                                (3) 
                                <E T="03">Felonies.</E>
                                 (i) The provider, supplier, or any owner or managing employee of the provider or supplier was, within the preceding 10 years, convicted (as that term is defined in 42 CFR 1001.2) of a Federal or State felony offense that CMS determines is detrimental to the best interests of the Medicare program and its beneficiaries.
                            </P>
                            <P>(ii) Offenses include, but are not limited in scope or severity to—</P>
                            <P>(A) Felony crimes against persons, such as murder, rape, assault, and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                            <P>(B) Financial crimes, such as extortion, embezzlement, income tax evasion, insurance fraud and other similar crimes for which the individual was convicted, including guilty pleas and adjudicated pretrial diversions.</P>
                            <P>(C) Any felony that placed the Medicare program or its beneficiaries at immediate risk, such as a malpractice suit that results in a conviction of criminal neglect or misconduct.</P>
                            <P>(D) Any felonies that would result in mandatory exclusion under section 1128(a) of the Act.</P>
                            <P>(iii) Revocations based on felony convictions are for a period to be determined by the Secretary, but not less than 10 years from the date of conviction if the individual has been convicted on one previous occasion for one or more offenses.</P>
                            <STARS/>
                            <P>
                                (5) 
                                <E T="03">On-site review.</E>
                                 Upon on-site review or other reliable evidence, CMS determines that the provider or supplier is either of the following:
                            </P>
                            <P>(i) No longer operational to furnish Medicare-covered items or services.</P>
                            <P>(ii) Otherwise fails to satisfy any Medicare enrollment requirement.</P>
                            <STARS/>
                            <P>
                                (8) 
                                <E T="03">Abuse of billing privileges.</E>
                                 Abuse of billing privileges includes either of the following:
                            </P>
                            <P>(i) The provider or supplier submits a claim or claims for services that could not have been furnished to a specific individual on the date of service. These instances include but are not limited to the following situations:</P>
                            <P>(A) Where the beneficiary is deceased.</P>
                            <P>(B) The directing physician or beneficiary is not in the state or country when services were furnished.</P>
                            <P>(C) When the equipment necessary for testing is not present where the testing is said to have occurred.</P>
                            <P>(ii) CMS determines that the provider or supplier has a pattern or practice of submitting claims that fail to meet Medicare requirements. In making this determination, CMS considers, as appropriate or applicable, the following:</P>
                            <P>(A) The percentage of submitted claims that were denied.</P>
                            <P>(B) The reason(s) for the claim denials.</P>
                            <P>(C) Whether the provider or supplier has any history of final adverse actions (as that term is defined under § 424.502) and the nature of any such actions.</P>
                            <P>(D) The length of time over which the pattern has continued.</P>
                            <P>(E) How long the provider or supplier has been enrolled in Medicare.</P>
                            <P>(F) Any other information regarding the provider or supplier's specific circumstances that CMS deems relevant to its determination as to whether the provider or supplier has or has not engaged in the pattern or practice described in this paragraph.</P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Reapplying after revocation.</E>
                                 If a provider, supplier, owner, or managing employee has their billing privileges revoked, they are barred from participating in the Medicare program from the date of the revocation until the end of the re-enrollment bar.
                            </P>
                            <P>(1) The re-enrollment bar begins 30 days after CMS or its contractor mails notice of the revocation and lasts a minimum of 1 year, but not greater than 3 years, depending on the severity of the basis for revocation.</P>
                            <P>(2) The re-enrollment bar does not apply in the event a revocation of Medicare billing privileges is imposed under paragraph (a)(1) of this section based upon a provider or supplier's failure to respond timely to a revalidation request or other request for information.</P>
                            <STARS/>
                            <P>
                                (h) 
                                <E T="03">Submission of claims for services furnished before revocation.</E>
                                 (1)(i) 
                                <PRTPAGE P="72533"/>
                                Except for HHAs as described in paragraph (h)(1)(ii) of this section, a revoked provider or supplier must, within 60 calendar days after the effective date of revocation, submit all claims for items and services furnished before the date of the revocation letter.
                            </P>
                            <P>(ii) A revoked HHA must submit all claims for items and services within 60 days after the later of the following:</P>
                            <P>(A) The effective date of the revocation.</P>
                            <P>(B) The date that the HHA's last payable episode ends.</P>
                            <P>(2) Nothing in this paragraph (h) impacts the requirements of § 424.44 regarding the timely filing of claims. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="498">
                        <PART>
                            <HD SOURCE="HED">PART 498—APPEALS PROCEDURES FOR DETERMINATIONS THAT AFFECT PARTICIPATION IN THE MEDICARE PROGRAM AND FOR DETERMINATIONS THAT AFFECT THE PARTICIPATION OF ICFs/MR AND CERTAIN NFs IN THE MEDICAID PROGRAM </HD>
                        </PART>
                        <AMDPAR>11. The authority citation for part 498 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P> Secs. 1102, 1128I and 1871 of the Social Security Act (42 U.S.C. 1302, 1320a-7j, and 1395hh).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="498">
                        <SECTION>
                            <SECTNO>§ 498.5 </SECTNO>
                            <SUBJECT>[Amended]</SUBJECT>
                        </SECTION>
                        <AMDPAR>12. In § 498.5, paragraph (l)(4) is amended by removing the cross-reference “§ 424.530(a)(9)” and adding the cross-reference “§ 424.530(a)(10)” in its place.</AMDPAR>
                        <EXTRACT>
                            <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program) </FP>
                        </EXTRACT>
                    </REGTEXT>
                    <SIG>
                        <DATED>Dated: August 8, 2014.</DATED>
                        <NAME>Marilyn Tavenner,</NAME>
                        <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                        <DATED>Approved: November 20, 2014.</DATED>
                        <NAME>Sylvia M. Burwell, </NAME>
                        <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2014-28505 Filed 12-3-14; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>79</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2014</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="72535"/>
            <PARTNO>Part V</PARTNO>
            <PRES>The President</PRES>
            <PROC>Proclamation 9217—International Day of Persons With Disabilities, 2014</PROC>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <PROCLA>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="72537"/>
                    </PRES>
                    <PROC>Proclamation 9217 of December 2, 2014</PROC>
                    <HD SOURCE="HED">International Day of Persons With Disabilities, 2014</HD>
                    <PRES>By the President of the United States of America</PRES>
                    <PROC>A Proclamation</PROC>
                    <FP>Each year, the United States joins with the international community to celebrate the inherent dignity and worth of every person. In America and in countries around the world, individuals with disabilities support families, strengthen their communities, and contribute to the global economy. On International Day of Persons with Disabilities, we reaffirm the fundamental principle that those with disabilities are entitled to the same rights and freedoms as everyone else: to belong and fully participate in society, to live with respect and free from discrimination, and to make of their lives what they will.</FP>
                    <FP>Nearly a quarter century ago, the Congress came together to pass the Americans with Disabilities Act (ADA), a landmark civil rights bill and a historic milestone in our journey toward a more perfect Union. The first Nation on earth to comprehensively declare equality for its citizens with disabilities, we enshrined into law the promise of equal access, equal opportunity, and equal respect for every American. The ADA was a formal acknowledgement that individuals with disabilities deserve to live full and independent lives the way they choose, and today, my Administration continues to fight to give every person a fair shot at realizing their greatest potential. We are working to rigorously enforce the protections against disability-based discrimination and expand workforce training and employment opportunities for people with disabilities, including our wounded warriors and those with serious disabilities. Today's theme, “Sustainable Development: The promise of technology,” reminds us that as we strive to increase accessibility in our communities, we cannot allow the benefits of groundbreaking innovation to be out of reach for those who seek to participate fully in our democracy and economy.</FP>
                    <FP>Disability rights are not only civil rights to be enforced here at home; they are universal rights to be recognized and promoted around the globe. That is why I am proud that during my time in Office, the United States signed the Convention on the Rights of Persons with Disabilities, and why I continue to call on the Senate to provide its advice and consent to the ratification of what is the first new human rights convention of the 21st century. Around the world, more than 1 billion people experience a disability. These women, men, and children seek a fair chance to complete an education, succeed in a career, and support a family—and the United States stands with them wherever they live.</FP>
                    <FP>America continues to be the world leader on disability rights. Today, we celebrate the courage and commitment of all who have agitated and sacrificed to bring us to this point, and all who continue to press ahead toward greater access, opportunity, and inclusion. With advocates from around the world and all those whose lives have been touched by a disability, we can build on our progress. Let us recommit to fostering a society free of barriers and full of a deeper understanding of the value each person adds to our global community.</FP>
                    <FP>
                        NOW, THEREFORE, I, BARACK OBAMA, President of the United States of America, by virtue of the authority vested in me by the Constitution 
                        <PRTPAGE P="72538"/>
                        and the laws of the United States, do hereby proclaim December 3, 2014, as International Day of Persons with Disabilities. I call on all Americans to observe this day with appropriate ceremonies, activities, and programs.
                    </FP>
                    <FP>IN WITNESS WHEREOF, I have hereunto set my hand this second day of December, in the year of our Lord two thousand fourteen, and of the Independence of the United States of America the two hundred and thirty-ninth.</FP>
                    <GPH SPAN="1" DEEP="62" HTYPE="RIGHT">
                        <GID>OB#1.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <FRDOC>[FR Doc. 2014-28774</FRDOC>
                    <FILED>Filed 12-4-14; 11:15 am]</FILED>
                    <BILCOD>Billing code 3295-F5</BILCOD>
                </PROCLA>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
